Discuss your project
Send the language pair, content type, volume, deadline, quality requirement, security requirement, and any buyer-side constraints.
A human MoniSa team scopes the project before pricing or production commitments.
We review your brief and clarify the work
Our team checks the languages, schedule and review requirements, then follows up on details needed to scope the project. We can discuss confidentiality requirements before you share sensitive files.
Contact questions
What should I include in a project brief to get a useful answer?
The language pairs, the content type, the volume and deadline, and the acceptance criteria the output will be judged against. Those four determine feasibility. A brief missing them can only be answered with assumptions, and wrong assumptions are the usual reason an estimate and an invoice disagree.
What happens to a brief after it is sent?
We review the languages, content, schedule and review needs. The first reply clarifies which pairs are available, where additional sourcing may be needed and what details we need to scope the work.
Can I ask about language coverage before committing to anything?
Yes, and that is the sensible order. Send the language list before the contract; the coverage position — staffed today versus needing a recruitment window — comes back in writing before a launch date is agreed.
What happens if you cannot staff one of my language pairs?
We confirm availability or the recruitment window for each requested pair before agreeing the date. New contributors must meet the project qualification and pilot requirements before production.