The best consultants bill for insight, not for typing.
And yet, most consulting work follows the same pattern: spend an hour in a brilliant client conversation, then spend two hours afterward turning that conversation into a deliverable. The discovery call becomes a proposal. The strategy session becomes a brief. The stakeholder interview becomes a report.
The thinking happens in the room. The writing happens at your desk. And the gap between the two is where your margins shrink.
The margin problem at every level
Consulting is a leverage business. The more client-facing hours you can deliver without proportional back-office hours, the more profitable you are. Every hour spent on post-meeting write-ups is an hour you can't bill, can't spend with another client, and can't use to grow your practice.
At large firms, this is supposed to be solved by structure. Partners bring the insight, managers shape the narrative, analysts do the typing. But anyone who's worked at a firm knows the reality: the analyst wasn't in the room. They get a Slack message with three bullet points and are expected to produce a polished brief from it. The partner reviews, sends it back with comments, the analyst revises. By the time the client sees something, it's the next day and two people have spent time on a document that should have taken one person twenty minutes.
For independents and boutique firms, the problem is starker. There's no analyst. There's just you, the meeting, and the two hours of admin that follows.
What actually happens after a client meeting
You just finished a 60-minute strategy session. You discussed go-to-market challenges, identified three priority areas, and outlined a preliminary approach for each. You know exactly what needs to happen next.
The old workflow looks like this: drive back to the office, open the laptop, stare at a blank document, try to remember the exact wording of that insight the client reacted to, draft for 45 minutes, format for 20 more, send. Two hours before the client sees anything. By then, the conversation has cooled. The urgency has faded.
The alternative: step into the hallway, open your phone, record a five-minute voice summary of what was discussed and decided. Upload it. Select "Strategy Brief." Review the output. Send.
Ten minutes. The client receives a structured brief while the meeting is still fresh in both your heads.
Speed is a signal
When a client receives a strategy brief ten minutes after the meeting, it communicates something that no amount of polishing can replicate: this person understood what we discussed, and they've already organized the path forward.
This isn't theoretical. Consultants using this workflow report that clients notice the speed immediately. "Looks great," sent as a reply within the hour, while the conversation is still top of mind. That kind of responsiveness builds trust faster than any credentials deck.
In one case, a requirements discussion with a prospective client turned into a signed engagement because the proposal was generated and sent the same afternoon. The client had expected to wait a week. They got a structured document the same day, with their priorities accurately captured and a clear scope of work. The speed didn't just impress them. It removed the window where they might have gone with someone else.
Contrast that with the brief that arrives the next morning, clearly written from partial notes, missing the nuance of what was actually discussed. Which consultant would you trust more?
The deliverables that don't need a keyboard
Not every consulting deliverable can be generated from a conversation. Research-heavy reports and data analysis still need the keyboard. But a surprising number of the documents consultants produce every week are really just structured translations of conversations they already had.
Post-meeting strategy briefs. Follow-up emails with action items and timelines. Stakeholder interview summaries. Requirements documents from needs-assessment calls. Weekly progress updates. Steering committee briefings.
These aren't creative writing exercises. They're structured documents with predictable formats. The content already exists in the conversation. It just needs to be extracted, organized, and formatted. That's exactly the kind of work that shouldn't require an hour of typing.
The compound effect
Run the rough numbers. A consultant with four client meetings a day, saving even 30 minutes per write-up, recovers two hours daily. That's ten hours a week, roughly 500 hours a year. At a billing rate of $200/hour, that's $100,000 in capacity that comes back. Available for more client work, business development, or simply leaving at a reasonable hour.
Scale that across a five-person firm: 2,500 hours. More than a full-time hire's worth of productive capacity, without the overhead, the onboarding, or the management complexity.
These are projections, not guarantees. The actual savings depend on how many meetings you have, how long your write-ups typically take, and which deliverables you automate first. But even at half these numbers, the math is hard to argue with.
Start with your most repetitive deliverable
Every consultant has one. The weekly update. The post-call summary. The stakeholder debrief. The one you could probably write in your sleep but still takes 45 minutes because it has to be structured and formatted and polished before anyone sees it.
Pick that one. Record your next version as a voice note instead of writing it. Compare the output to what you'd normally produce.
If it's 80% as good in 10% of the time, the math is obvious.
If it's better, and that does happen, it changes how you think about where your time should go.
