Design Partner Quickstart
Start with one service, not an AI transformation program
The first FYY pilot should cover one recurring service for a small number of existing clients. A strong candidate already has paying demand, repeats weekly or monthly, and produces an outcome the client can accept or request to revise.
1. Choose the workflow
Write down:
- who the client is;
- what starts the work;
- which inputs are required;
- what the final deliverable contains;
- the promised turnaround;
- which decisions require an expert;
- what counts as client acceptance.
Avoid broad goals such as “build an AI consultant.” Prefer a specific promise such as “deliver a cited weekly growth review by Tuesday afternoon.”
2. Prepare examples
Collect 10–20 past tasks, including routine work, difficult exceptions, incomplete client inputs, and results that required revision. Remove unnecessary sensitive data before the initial setup.
3. Name the responsible people
Assign a service owner, at least one expert who can accept handoffs, and one operations contact for invitations, overdue tasks, and incident escalation.
4. Rehearse coverage and exit before inviting clients
Before using real client material, name the primary and backup on-call owners, staffed hours, emergency response targets, and the person authorized to pause delivery. Use synthetic material to rehearse expert takeover, notification-failure compensation, Runtime recovery, client export, a deletion request, and partnership exit at least once.
Define recovery with a business signal you can verify, such as work returning to a safe state or the client receiving a usable delivery. Acknowledging an alert does not close the incident. Client exports must exclude expert-only notes, secrets, private expert knowledge, and every other client’s data; deletion starts only after new work is stopped, retention obligations are resolved, and any requested export is complete.
5. Invite the first clients
Begin with one to three existing clients who understand that the service is in a staffed pilot. Keep the current commercial relationship in place while the workflow is validated.
Before the invitation, agree on staffed hours, the human escalation route, the read-only history window, and the boundaries for export, retention, and deletion.
6. Measure four delivery cycles
Track expert time, response time, takeover rate, revision rate, client acceptance, model and tool cost, and every case where the service could not complete safely.
Continue with Designing an Expert Service.