Start a brief
Bring the language problem your team cannot carry alone.
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.
What happens next
A person reads your brief, not an autoresponder.
We reply with feasibility and scoping questions, under NDA where you need it. Pricing and production commitments stay human-reviewed — never an automated quote.
Buyer questions
Ask the questions weak vendors avoid.
Short answers for buyers checking fit, coverage, quality method, and next-step readiness.
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?
It is read by a person rather than routed into an automated sequence. The first reply addresses feasibility — which pairs are staffed, which would need a recruitment window, and what in the scope has to be settled before any number is meaningful.
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.
Capability at a glance
The answers most briefs open by asking for.
Buyers rarely start with who we are. They start with a list of fields to fill. Here are ours, so the first email can be about the work instead.
- Languages and locales
- 300+ languages and 4,500+ dialects, quoted per locale rather than per language — because the dialect decides whether a dataset is usable, whether a market accepts a release, and which specialist the work goes to.
- Specialist network
- 110,000+ verified language specialists — linguists, annotators, and reviewers — plus voice talent and subtitlers, matched to the language, domain and task before assignment.
- Capacity and mobilisation
- Named availability confirmed per pair before scoping. Coverage is reported as staffed today or needing a recruitment window, in writing, before a launch date or release window is agreed.
- Sourcing constraints
- Specialists can be sourced against geographic, residency, locale and demographic requirements — including native-only, in-country, and speaker-diversity quotas where a data programme demands them.
- Deliverables and specs
- Work is delivered to the receiving specification: structured formats and schemas for data and annotation work, and timed-text, audio and platform conformance for media — subtitle reading speed, line limits, cue timing, channel and sample-rate requirements included.
- Comparable work
- 62 documented case studies stating the scope, the constraint that made it difficult, and the measured result — across AI data programmes, partner overflow, and media releases. 2,000+ AI projects delivered and 1,000+ brands served since 2015.
- Certifications
- ISO 9001:2015 quality management, ISO 27001:2022 information security, and ISO 17100 translation services — scoped to translation specifically, and stated that way rather than implied across every line.
- Commercial basis
- Quoted in the unit the work is measured in — per word, per audio hour, per approved hour, per finished minute, per batch, per item — with what the unit includes stated alongside it, whether the quote is for you or for a client you quote onward.
Need this against your own template? Convert your scope between units and check the deadline, then send the brief with your language list, content type, volume and deadline, and the acceptance criteria you will judge the output against — those four decide feasibility, and the reply addresses them directly.