What goes into a scope of work for an AI project?
Client delivery · Pro 1
Short answer
The problem and goal, the specific use case and users, what will be delivered, measurable acceptance criteria (for example 90% correct field extraction on an agreed test set), what is out of scope, assumptions and client responsibilities such as data access, the timeline with milestones, and how changes are handled.
Deeper answer
AI projects need acceptance criteria tied to an eval set agreed with the client, because 'it works' means different things to different people. State that quality is measured on that set, not on every possible input.
Name dependencies clearly: data access, security approvals, subject experts' time. Most AI project delays come from these, not from the model.
What a strong answer covers
- Problem, goal and use case
- Deliverables
- Measurable acceptance criteria on an agreed test set
- Out of scope and assumptions
- Client responsibilities, timeline and change process
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- How would you write acceptance criteria for a RAG assistant?
- What client responsibilities would you list?
Common mistakes
- Vague acceptance criteria
- No change process
Learn it
- 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 hand over an AI system to the client's team?
- 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?