- Buyer type
- Operations buyer deciding whether DD should receive a translation, interpreting, media, localization, transcription, or AI data request.
- Problem
- The buyer needs the correct service option before sending files, because a wrong starting point creates quote noise and delivery risk.
- Scope
- Six service areas cover AI data, translation, interpretation, subtitling and captioning, localization, and transcription.
- Constraint
- Service pages cannot rely on public case studies yet; each service must show its operating proof through DD-owned artifacts.
- DD action
- DD reviews the request by work type and missing inputs, then proposes a contact, review plan, and written scope for confirmation.
- Evidence available
- Ask whether a relevant start checklist, review format, delivery-note format, or sample sourcing record can be shared under the engagement terms.
- Outcome
- The buyer knows which DD service fits the requirement and what evidence to request before a vendor decision is made.
- Disclosure status
- DD shares service-method proof without client names. Engagement summaries require client approval or appropriate disclosure terms.