How do you hand over an AI system to the client's team?
Client delivery · Pro 1
Short answer
Plan it from the start. Provide documentation for different readers: how to use it, how to run and monitor it, how it is built, and why key decisions were made. Hand over the eval set and how to run it, runbooks for common failures, and access and secrets transfer. Pair with their engineers before leaving and agree a support window.
Deeper answer
The Diátaxis approach separates tutorials, how-to guides, reference and explanation, which helps each reader find what they need.
The real test of a handover is whether the client's team can change a prompt, re-run evals and fix a common incident without you. Run that test before the engagement ends.
What a strong answer covers
- Documentation for different readers
- Eval set and how to run it
- Runbooks for failures
- Access and secrets transfer
- Pairing, training and a support window
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- What goes into a runbook?
- How would you check the client can run it without you?
Common mistakes
- A single giant document nobody reads
- Leaving without handing over evals
Learn it
Practice Client delivery questionsMore on this topic
- How would you connect an AI assistant to a client's SharePoint, Salesforce and Jira?
- How do you update a client's executives on an AI project?
- A client tells you their AI assistant invented a policy clause and a customer acted on it. What do you do?
- Midway through a project, the client keeps adding requests. How do you handle it?
- How do you move an AI solution from proof of concept to production?
- You start with a new enterprise client. How do you run discovery?
- A client says 'automate our sales process'. What do you do first?
- The client's staff are worried your automation will replace them. How do you handle it?
- What goes into a scope of work for an AI project?