- 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 shells cover AI data, translation, interpretation, subtitling and captioning, localization, and transcription under one DD request review.
- Constraint
- Service pages cannot rely on public case studies yet; each service must show its operating proof through DD-owned artifacts.
- DD action
- DD separates the request by work type, confirms missing inputs, names the PM contact, and returns a written scope before production.
- Evidence available
- Private proof can include a service-specific start checklist, QA summary format, delivery-note format, and sample sourcing review.
- 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.