Before files land in a shared folder, the strongest English ↔ Somali projects already answer four questions: who will read this, how formal it should sound, when it must be ready, and what “done” means on delivery day.
Most first calls circle the same topics: document type, language direction, whether Somali should feel formal or everyday, and whether a glossary already exists. Those answers change word count assumptions, rate structure, and how many review rounds you should plan.
I also ask about delivery format — Word, bilingual table, XML, or UI export — because layout and character limits matter as much as meaning.
What to send with your first brief
Share audience notes (parents, field staff, app users), a sample paragraph of preferred tone, and any terms that must stay in English. If legal or marketing must sign off, say so early so the timeline includes their review — not only mine.
When turnaround is tight, we agree what “done” means: draft for internal review, or publish-ready with a final proof.
How I quote after the call
Quotes cover service type, estimated words or strings, subject risk, and deadline. Rush work is possible, but it should be priced and scoped as rush.
You get a short written confirmation: language direction, files included, delivery format, and what is out of scope.
Share audience notes, a sample paragraph, and any preferred terms. AfriNative can then quote honestly and start with the right tone from day one.
