AI client work for consultancies: a practical playbook
4 minutes read

Generic AI drafts are a bigger problem for consultancies, because the output goes straight to a paying client. A practical playbook for AI work you can bill for.
Generic AI drafts hurt consultancies more than most teams, because there is no internal buffer. What you produce is what the client pays for. A product team can fix a vague, unsourced draft internally; for a consultancy, that draft is the deliverable. "AI helped with this" has to mean more.
This playbook shows how to use AI on real client work so you can review it, defend it and sign it off.
Why the bar is higher for consultancies
The client scrutinises client-facing AI work as well as your own team does. Three things make it harder than general AI use.
A research summary, a strategy or a first draft of a report goes to a client who is paying for the firm's judgement, so there is no room for a confident claim nobody can support. Every client is different, so a draft written from generic knowledge will be generic. And consultancies handle other firms' material: if someone pastes it into a public chat tool to get a faster draft, the firm has a client-trust problem, whether or not anyone has noticed yet.
Consultancies that use AI well move faster on the parts of delivery that used to take senior hours. Most people use AI through a chat window and a generic prompt, which does not suit client work.
The playbook
The goal is a first draft a principal can review quickly and sign off. Four moves get you there.
| Move | What it fixes | Result |
|---|---|---|
| Work from approved sources per client | Ungrounded claims, client-data risk | Drafts built on trusted material under agreed access rules |
| Keep evidence visible for review | Slow, full-rewrite review | Each claim shows its source, so review is a check |
| Keep the senior reviewer accountable | AI output going out unchecked | A person signs off on every deliverable |
| Reuse what works across clients | Rebuilding the same process each time | A method from one good project is repeatable |
Work from approved sources, per client
Decide, for each client, what the AI may use: the external sources you trust, your firm's prior work and methods, and the client material the engagement permits. This keeps the draft sourced and keeps client data inside the rules you agreed to. It is the biggest difference between AI you can bill for and AI you have to hide. The connected knowledge guide covers how to connect your firm's own stack and data.
Keep the evidence visible for review
The account lead reviewing a draft should see where each claim came from and which parts are the model's assumptions. They can then check the draft instead of rebuilding it. Without visible evidence, the reviewer re-sources everything, and the time saved on drafting is lost at review.
Keep the senior reviewer accountable
No consultancy should let an AI draft reach a client unreviewed, and no vendor should suggest otherwise. AI gets the reviewer to a draft they can trust sooner but does not replace them: the person who signs off is accountable for the work. The complete guide to reliable AI client work sets out the full argument.
Reuse what works across clients
Consultancies run the same shapes of work repeatedly: a research brief, a positioning analysis, a first draft of a report. Once a method produces a reliable result, save it as a reusable workflow so the team starts the next client from a proven process instead of a blank window. Everyone on the team can then repeat what worked on one good project. See reusable AI workflows for how that works.
Cost per client
AI usage is tied to client work, so you need to know what each engagement costs. Hebno shows AI usage by team and client. That is useful but deliberately not the headline: controlling the cost of work you cannot deliver gains nothing, so reliable delivery comes first and cost visibility follows.
Getting started
You do not need an engineer or an IT project to start. Pick one recurring kind of client work, define the approved sources for it, and run a real brief through the reliable-work sequence: sources, draft with visible evidence, expert review, sign-off. If the reviewed draft gets you to a sendable deliverable faster, expand from there.
