Hand over an AI workflow so a client's team can run it: named owner, prompt library, written reasoning, review cadence and a consultant-free week
A consultant's checklist for leaving an AI system the client can keep running: access held by a named employee, a dated prompt library, the reasons behind choices, a standing review and a few health metrics, over a 90-day handover.
Evidence: The author reports this. We have not checked it beyond reading the source.
The business problem
AI workflows built by a consultant often decay after the consultant leaves, because nobody on the client's team owns the prompts, the access or the reasoning.
What was tried
Five things the client team must own: access and admin rights held by a named employee, not a shared login or the consultant's account; a living prompt and workflow library with each prompt's purpose, last edit date and editor; the reasoning behind decisions such as the model chosen or a lead-score cutoff; a review cadence with a named owner, weekly for the first month and then monthly; and three or four health metrics such as output volume and edit time. Run the handover over 90 days: transfer access in the first two weeks, build alongside staff so an internal person edits a prompt unaided by day 45, deliver and sign off documentation by day 75, and finish with a week where the team runs everything without the consultant. Put the handover terms in the contract.
What was reported (not reported)
The article gives one example: an agency paid just under £14,000 for a content workflow, and six months after the consultant left its outputs had become generic and sometimes wrong because the one person who understood the setup had left. The fix took four hours. No results from using the checklist are reported.
Limitations
Written by a consultant who sells AI consulting and coaching and links to booking and tools throughout. The evidence is one anecdote plus the author's own experience, and the six-month decay window and 90-day timeline are rules of thumb without sources. It treats ownership as the main cause of failure and does not weigh the cost of the extra handover work.
What you need
A client team member who can own the system, and a contract that gives time for the handover before final payment.
Sources
- Lilach Bullock (marketing and AI consultant) ↗ Vendor case study, publication date unknown
Source published: unknown. Last reviewed here: October 14, 2026. Spot a mistake? Tell us.
Related workflows
Split client deliverables into AI gathers, a person checks and a lead decides, with a three-pass evidence pack and a short method note
A consultancy founder sets out how a small advisory firm can use AI on client work: AI gathers and sorts, a named person opens every source, the lead decides what reaches the client, and the client is told what AI did.
Run a one-person company on five building blocks: a browser agent, a coding agent, scheduled routines, memory notes and approval gates
A solo founder of a physical-product business with no employees describes the five pieces of an agent setup and the rules that keep it safe: run a workflow by hand twice, write memory notes, gate money paths, then schedule it.
Plan ten Claude Code skills for a small service business, one a day, and review the first 20 to 50 runs before anything is sent or paid
An agency guide lists ten back-office tasks to turn into Claude Code skills, such as inbox triage, reply drafts, invoice processing and weekly reconciliation, with a rule to review early runs by hand before irreversible actions.
Run a solo consulting practice on Claude Cowork agents with a three-pass quality check before anything reaches a client
A former strategy consultant describes a plugin that gives a solo consultant agents for proposals, kickoff packs, research and deliverables, with source checking and two independent audits before delivery.