Start hereConsultant OS ToolsCompare PlaybooksResources Finance Stack ↗ Get the $97/mo OS

Pillar Guide · AI Infrastructure

AI Workflows for
Solo Consultants.

AI tools don't save time by default — they save time when each one is assigned to a specific workflow job and connected to the rest of the system. This is the complete AI infrastructure for a solo consulting practice: every tool mapped to its job, every prompt explained, and the Workflow Compression metric for each layer.

Updated May 2026 · 22 min read · 3,800 words

AI is a workflow layer, not a tool category.

The consultants who get the most leverage from AI aren't the ones using the most tools — they're the ones who've assigned each AI tool a specific job in a specific workflow and connected those tools so their outputs feed into each other. Claude's proposal draft feeds into PandaDoc. Fathom's transcript feeds into Claude's prep prompt. Perplexity's research feeds into the discovery call prep brief.

The alternative — using AI ad hoc, pasting things into ChatGPT occasionally, trying different tools without a system — produces inconsistent results and requires constant re-learning. The system approach produces compounding returns: the more you use it, the faster each workflow runs, because your prompts get better and your context gets richer.

This guide maps the AI infrastructure for each stage of the consulting workflow. It covers the right tool for each job, the specific prompts that work at consultant-level complexity, and the Context Reconstruction Cost reduction each system produces.

Workflow Compression — AI vs Manual baseline
Proposal writing
85%
Discovery call prep
80%
Meeting notes & summary
90%
Prospect research
70%
Status report writing
75%
Context reconstruction
88%

Four tools. Every AI job in the practice covered.

The solo consultant AI stack doesn't need to be large. Four tools — assigned to specific jobs, connected deliberately — cover every knowledge-work task in the practice. Adding more tools beyond these four typically increases Operational Surface Area without proportionate capability gain.

Tool Primary job Secondary job Cost
Claude Pro Long-form writing: proposals, reports, strategy memos Context reconstruction, deliverable drafting, email writing $20/mo
Fathom Discovery call recording, transcription, AI summary All client call notes, action item extraction $0
Perplexity Pro Prospect research, industry context, verifiable facts Competitive landscape, market sizing, news monitoring $20/mo
Notion AI (optional) In-portal summarization, action item extraction Meeting note formatting, status update drafting $10/mo

Total AI stack cost: $40/month (or $50/month with Notion AI). This is separate from but compatible with the automation stack (Make, HubSpot, Calendly). Together they form the complete consultant OS at $97/month total. See the complete OS guide →


Claude — The primary AI for client work.

Claude is the right AI for the high-complexity, long-form writing tasks that define consulting delivery. Proposals, strategy memos, client reports, engagement summaries, status updates — these are documents where voice, structure, and nuance matter, and where a mediocre first draft is worse than no draft at all. Claude's strength in these tasks comes from its ability to follow complex, structured prompts and maintain consistent quality across long outputs.

Claude Pro — $20/month
Long-form writing · Context management · Strategic thinking
Primary AI

Where it fits: Claude handles five distinct jobs in the consulting workflow — (1) proposal drafting from discovery call notes, (2) context reconstruction before client calls, (3) deliverable drafting from structured briefs, (4) client communication rewrites ("make this email clearer and more direct"), and (5) strategic analysis frameworks when you need to think through a client problem before engaging.

Why Claude over ChatGPT for consulting work: Two specific advantages. First, Claude's extended context window (200K tokens on Pro) handles full engagement histories — you can paste an entire project's worth of meeting notes, the original proposal, and the current deliverable draft in one context, and Claude maintains coherence across all of it. ChatGPT's context is shorter and less reliable at the edges. Second, Claude follows structured prompts more reliably — when you specify eight required sections, it produces eight sections without improvising extras or skipping ones it finds difficult.

When to use ChatGPT instead: Tasks that benefit from web browsing and real-time information (use Perplexity for this instead), image generation (DALL-E integration), or code generation tasks where GPT-4's coding capability is preferred. For pure text work at consulting complexity, Claude is the better choice.

Proposal compression
85% vs manual baseline
Context window
200K tokens (Pro)
Best for
Long-form, structured writing

Five core Claude prompts for consultants.

PROMPT 1 — Context reconstruction before a client call
I have a client call in [TIME] with [CLIENT NAME] at [COMPANY]. Here are my notes from our last three sessions: [Paste last 3 Notion meeting note entries] Here is our current project scope: [Paste SOW summary or deliverable list] Prepare me for this call with: 1. A 3-sentence summary of where we are and what's been decided 2. The three most important things to cover today based on our project status 3. Any open items or decisions that are overdue 4. One thing I should be careful about based on the history Keep it to one page. I need to read this in 4 minutes.
PROMPT 2 — Status report from meeting notes
Write a client status update email based on today's meeting notes. Meeting notes: [Paste Fathom AI summary] Project context: [One paragraph on where the engagement stands] The email should: - Open with the 2–3 most important things that happened or were decided - List action items with clear owners and due dates - Note any blockers or decisions needed from the client side - Close with what happens next and when Tone: professional and direct. Under 300 words. No filler phrases like "as discussed" or "per our conversation."
PROMPT 3 — Scope creep response email
Write a professional response to a client who has requested work outside our agreed scope. Their request: [describe the out-of-scope request] Our agreed scope: [paste relevant SOW section] Our change order rate: $[X]/hour or $[Y] for this specific addition The email should: - Acknowledge their request positively (no "that's out of scope" language) - Confirm we can absolutely do it - Reference our change order process naturally - Include the specific scope and cost of the addition - Make it easy for them to say yes Keep it under 150 words. Make it feel collaborative, not transactional.
PROMPT 4 — Deliverable first draft from brief
Write the first draft of [DELIVERABLE TYPE] for [CLIENT NAME]. Project context: [2–3 sentences on the engagement and their situation] This deliverable should accomplish: [What the client will do with this document] Key inputs and data: [Paste relevant research, meeting notes, or analysis] Required sections: [List the sections you want] Constraints: - Length: [X pages or Y words] - Audience: [Who will read this] - Tone: [direct/consultative/executive-facing] - Format: [bullet points/prose/tables] Flag anything where you'd need more information or where assumptions are required.
PROMPT 5 — Discovery call debrief and proposal setup
I just finished a discovery call with [NAME] at [COMPANY]. Here's the Fathom AI summary: [Paste summary] Extract and organize the six proposal-ready fields: 1. CURRENT SITUATION: Their exact words, specific numbers 2. COST OF THE PROBLEM: Revenue/time/opportunity impact they mentioned 3. DESIRED OUTCOME: Specific measurable goal they named 4. CONSTRAINTS: Budget, timeline, team, tools, previous attempts 5. DECISION PROCESS: Who else decides, timeline, competing options 6. THEIR LANGUAGE: Verbatim phrases I should use in the proposal Also note: one thing that seemed most important to them, and one potential objection I should be ready for.

Fathom — The call intelligence layer.

Fathom solves the Context Reconstruction Cost problem at the source. Every client call — discovery, kickoff, check-in, delivery review — is automatically transcribed and summarized. The AI summary identifies action items, decisions made, and key discussion points. You stop taking notes during calls and start listening fully. Post-call, you have a searchable record rather than reconstructed memory.

Fathom — Free
Unlimited Zoom recording · AI transcription · Action item extraction
Free forever

What it does: Fathom joins every Zoom call automatically once configured. It records, transcribes in real time, and generates an AI summary within 2–3 minutes of the call ending. The summary includes: a brief overview, key discussion points, decisions made, and action items with implied owners. The full transcript is searchable — you can find any moment from any call in seconds.

The workflow integration: After every client call, paste the Fathom AI summary into the relevant section of the client's Notion portal. This is the weekly 10-minute update habit — Fathom produces the content, you paste it in. The portal becomes a running record of every decision, every action item, and every discussion point without any manual writing. Context Reconstruction Cost drops to near-zero because the record is complete.

Discovery call specific use: After a discovery call, use Prompt 5 above (Claude debrief prompt) with the Fathom summary as input. Claude extracts the six proposal-ready fields in structured format. This replaces the 20–30 minutes most consultants spend writing up discovery notes from memory — and produces more accurate, complete input for the proposal because it's working from a verbatim transcript, not reconstructed notes.

Limitation: Fathom's free tier covers Zoom only. If you use Google Meet or Microsoft Teams regularly, Fathom charges $19–$29/month for those platforms. Otter.ai is the alternative — it covers more platforms and has its own AI summary capability, though the summary quality is slightly lower than Fathom's at the time of writing.

Meeting notes compression
90% vs manual note-taking
Platform
Zoom (free) · Meet/Teams (paid)
Context Reconstruction Cost reduction
~88%

Perplexity — Research with citations.

The most important distinction between Perplexity and Claude for research tasks: Perplexity cites its sources. For consulting work — where you may need to present market data, competitive intelligence, or industry benchmarks to clients — cited research is meaningfully more valuable than AI-generated content you can't verify. Claude is excellent for writing and analysis; Perplexity is better for any research task where the answer's accuracy matters and you'd need to verify it anyway.

Perplexity Pro — $20/month
Prospect research · Industry context · Verifiable data · News monitoring
Research layer

Pre-call prospect research: Before a discovery call, a 10-minute Perplexity research session produces: a company overview with recent news, the prospect's background from LinkedIn, the industry context for their problem, and 2–3 relevant case studies or data points you can reference naturally in the conversation. This is the input for Prompt 1 in Claude (context reconstruction) — Perplexity provides the external context; Fathom provides the call history; Claude synthesizes them into a pre-call brief.

The research prompt that works: "Tell me about [Company Name]. Include: what they do, their business model, recent news or changes, their typical challenges in [their industry], and any public information about [Prospect Name]. Cite your sources. I'm preparing for a discovery call and need accurate, current information."

Competitive landscape research: When a client asks "who else is doing this?" or "what are our competitors doing?", Perplexity produces cited answers faster than any manual research process. The follow-up prompt: "What do [Competitor names] do differently from [Client] in [specific area]? Cite your sources and note the date of the information." The date note matters — Perplexity's training data has a cutoff, and for fast-moving industries, you want to know whether the information is current.

Free vs Pro: Perplexity's free tier uses its own AI model and limits Pro searches. The $20/month Pro plan unlocks Claude and GPT-4 as search backends — meaning you get the research capabilities of Perplexity's source retrieval combined with the reasoning quality of frontier models. At consulting use volume (10–20 research sessions per week), Pro pays for itself quickly in recovered research time.

Prospect research compression
70% vs manual research
Key advantage vs Claude
Cited, verifiable sources

Context management — the hidden ROI of AI in consulting.

The highest-leverage application of AI in solo consulting isn't writing — it's context management. A consultant with three active clients at different project stages carries significant cognitive overhead: remembering where each project stands, what was decided last week, what each client cares most about, and what needs to happen before the next call. This overhead is real work that's currently done by memory and email-searching — both unreliable and time-consuming.

The system that eliminates this: Notion client portals (structured, persistent context) + Fathom meeting notes (automatic call documentation) + Claude context reconstruction prompts (rapid re-immersion). Together, they reduce Context Reconstruction Cost from 30–45 minutes per client per week to under 5 minutes. At three active clients, that's 75–120 minutes per week recovered — from a 30-minute afternoon setup and a 10-minute weekly update habit.

📋

Notion: persistent structured context

The client portal contains the full engagement history in structured form — decisions, deliverables, meeting notes, next steps. This is what you give Claude when you need context reconstruction. The structure makes it scannable in 2 minutes and parseable by AI in seconds.

🎙️

Fathom: automatic call documentation

Every call becomes a searchable, summarized record automatically. No note-taking during calls. No "I think we decided X" — you know exactly what was decided, when, and by whom. Paste the summary into the Notion portal. The record builds itself.

🤖

Claude: rapid re-immersion

Before any client interaction, paste the last 3 Notion meeting notes + current scope into Claude with the context reconstruction prompt. Get a 4-minute briefing covering current status, priorities, open items, and one thing to watch. Arrive fully oriented at every call.


Additional prompts for the consulting workflow.

Retainer renewal email
Write a retainer renewal email to [CLIENT NAME]. Our engagement started: [date] What we've accomplished: [2–4 bullet points of outcomes achieved] Current retainer: $[X]/month for [scope description] Proposed renewal: [same / adjusted scope and price] Renewal date: [date] The email should: - Open by briefly acknowledging what we've accomplished together - Transition naturally to the renewal conversation - State the proposed terms clearly and directly - Make it easy to say yes with a simple next step Tone: warm but professional. Under 200 words. Don't oversell — let the outcomes speak.
Discovery call prep brief (after Perplexity research)
I have a discovery call with [NAME], [TITLE] at [COMPANY] in [TIME]. Perplexity research summary: [Paste Perplexity research output] Their pre-call questionnaire answers: - Current situation: [answer] - Goals: [answer] - Timeline: [answer] Prepare a pre-call brief with: 1. Three smart diagnostic questions I should ask 2. Two things to watch out for — risks or misalignments 3. The one thing I most need to clarify before proposing 4. One way to demonstrate I've done my homework in the first 2 minutes Keep it to half a page.
Weekly client update (from portal + Fathom)
Write a brief weekly update email for [CLIENT NAME]. This week's Fathom meeting summary: [Paste summary] Current project status (from Notion portal): [Paste status board snapshot — in progress / complete / next] The email should cover: - What happened this week (2–3 sentences) - What's next and when they can expect it - Anything needed from them Under 150 words. Direct. No filler. Reads like it was written by someone who values their time and the client's.
Difficult client conversation — reframe
Help me prepare for a difficult conversation with a client. The situation: [Describe what happened — missed deadline, budget concern, scope dispute, unhappy with deliverable] My interpretation of the problem: [What you think went wrong] What I want to achieve in the conversation: [Maintain relationship / agree on path forward / reset expectations] Give me: 1. How to open the conversation (first 2–3 sentences) 2. The key thing I need to acknowledge or own, if anything 3. The proposed path forward I should put on the table 4. How to close the conversation so both parties feel aligned Be direct. Don't sugarcoat the situation I'm describing.

The AI workflow from prospect to closed project.

Stage
Pre-discovery
Perplexity researches prospect (10 min). Claude combines Perplexity output + questionnaire answers into prep brief. Consultant arrives informed.
Stage
Discovery call
Fathom records and transcribes. Consultant focuses entirely on listening and asking the right questions. Call ends. Fathom summary ready in 2 minutes.
Stage
Post-discovery
Claude Prompt 5 extracts six proposal fields from Fathom summary (5 min). Claude Proposal Prompt generates 8-section draft (90 sec). Edit (15–20 min). Send via PandaDoc.
Stage
Active engagement
Fathom summaries → Notion portal (weekly, 5 min). Claude Prompt 1 reconstructs context before each call (4 min). Claude Prompt 2 writes status update emails (3 min).
Stage
Delivery
Claude Prompt 4 drafts deliverables from structured briefs. Perplexity provides cited data and research where needed. Deliverables go through client review in Notion portal.
Stage
Renewal / close
Claude retainer renewal prompt drafts the renewal email. Make automation creates a 90-day referral ask task in HubSpot. Engagement closes with a documented record in Notion, a renewal conversation in progress, and a future referral request queued.

Four AI patterns that waste time instead of saving it.

Mistake 1

Using AI without structured prompts

Ad hoc "write me a proposal for a strategy consulting engagement" produces generic output. Structured prompts with the six discovery fields, the client's exact language, and the specific outcome produce proposal-quality drafts. The prompt is the skill — the AI is the execution. Invest time in prompt development, not tool switching.

Mistake 2

Treating AI output as final

Every AI output requires a pass for accuracy and voice. Claude will infer specifics you didn't provide, use your billing rate incorrectly, or write in a slightly more formal register than your natural voice. The 15–20 minute edit pass isn't overhead — it's where you add the judgment that the AI can't have.

Mistake 3

Not giving AI enough context

The quality of AI output scales directly with the quality of context you provide. A proposal prompt with shallow discovery notes produces a shallow proposal. A prompt with verbatim client language, quantified problem costs, and specific outcome metrics produces a proposal that reads like you understood the client perfectly. The context is the work.

Mistake 4

Using AI for everything

Not every task benefits from AI involvement. Strategic recommendations that require your judgment, nuanced client relationship decisions, and pricing negotiations are human tasks. Using AI on these introduces latency without value. The system works best when AI handles the structured, repeatable components and humans handle the judgment-intensive ones.


Get the AI prompt library

All five core Claude prompts plus 8 additional prompts for every recurring consultant workflow — formatted, tested, and ready to use. Free with your email.

  • Context reconstruction prompt
  • Discovery debrief + proposal setup prompt
  • Status report from meeting notes
  • Scope creep response template
  • 8 additional workflow prompts

Free for subscribers

No spam. Unsubscribe any time.


Pillar Guide
Complete Consultant OS Guide →
Template
AI Proposal Template →
Article
Notion Client Portal →
Article
Best AI Tools for Consultants →
Reference
OS Glossary →
Trust
How We Evaluate Tools →