Buyer tools
Seven working checklists we use with buyers, published in full. No form, no download wall — the questions are on the page so you can forward one to a colleague or paste a row into your own document.
Each tool names the question, what a useful answer is specific about, and what the answer actually tells you.
1,000+ organizations served since 2015 across AI data, translation, localization, media, and interpretation.
1,000+ organizations served · 300+ languages · 4,500+ dialects
The set
Each one names the question to ask, what a useful answer is specific about, and what the answer actually tells you. Nothing here is behind a form.
Before you ask suppliers to scope AI data collection or production work. A scope decision record naming, for every line, what the supplier does, what stays with your team, and which assumption is still unagreed.
Open this toolWhen a supplier says "yes" and you need to know what that answer rests on. A record pairing each claim with the evidence supporting it, the dependency still open, and the decision that evidence allows you to make.
Open this toolBefore collection, onboarding or data transfer begins. A provenance schedule for the SOW: permitted use, a named owner per activity, and the record that stays with each item as it moves.
Open this toolBefore a successful pilot is allowed to become production. A stage-gate record: what must be seen before each increase, who approves it, and what stops the ramp.
Open this toolRun this with both sides before the first production hand-off. A readiness check with a named owner against every item, and an honest record of what has actually happened so far.
Open this toolBefore an annotation or linguistic-review guideline reaches the people who will apply it. An approved clarification, written back into the guideline itself, with the section that changed and confirmation the working team received it.
Open this toolBefore a language list is treated as delivery coverage. A coverage decision per combination: the variety and script required, who is validated and available, credible capacity, and what happens if it cannot be staffed.
Open this toolWhat a tool leaves behind
Each one is published in full and meant to be used: taken out of the set, worked through, and handed on with the answers on it.
No form and no download wall. Each checklist runs to a different length because the question it answers is a different size.
The deliverable is not the checklist. It is the written record it leaves behind, and the decision that record lets somebody else make.
Where to go next
These checklists sit alongside the longer buyer guides, which work through a whole vendor decision, and the resource hub, which collects the guides, field notes and case evidence in one place.
Stuck on a row?