Why coaches and consultants are early adopters
Coaches and independent consultants tend to be ahead of larger professional services firms on AI adoption, for reasons that are mostly structural. No compliance team to slow things down. No firmwide tooling decisions to wait on. A livelihood that depends on being useful to a small number of clients, which makes the time math obvious quickly.
What coaches are actually using AI for is narrower than the hype suggests. Not "AI coaching in place of the session" — that replaces the core product and most established coaches won’t go near it. Instead: AI as research assistant, note wrangler, content generator, and framework productizer. The parts of the practice that are not the session itself.
Core workflow: your notes as a searchable assistant
If you’ve been coaching for even a few years, you have a large informal knowledge base — session notes, client agreements, books you’ve annotated, your own writing. Historically this material was scattered across Notion, Evernote, Google Docs, physical notebooks, and whatever tool you were using three laptops ago. AI now lets you turn that corpus into something you can actually ask questions of.
The minimum viable version
- Consolidate. Pick a directory. Dump every coaching-relevant document into it — sessions, agreements, frameworks, your own writing, books you’ve highlighted.
- Convert. Run the pile through a batch converter so everything ends up as markdown. Our batch conversion handles PDFs, Word docs, EPUBs, and HTML in one pass. Markdown is what AI tools read most fluently, and the folder is easier to grep through by eye than the original mess.
- De-identify where needed. Replace client names with initials or role labels ("Client A, VP Marketing, 40s"). This both protects client confidence and forces you to think in patterns rather than specifics.
- Load into a Project. Create a Claude Project or ChatGPT Project, attach the files. Alternatively, use NotebookLM (Google), which is purpose-built for this and gives better citations.
- Ask questions. "What patterns do I see in first-year founders struggling with delegation?" "Find every session where I used the accountability ladder framework." "Pull direct quotes from clients about the fear of charging more."
That’s the whole stack. It takes a weekend to set up and a steady hour a month to maintain. The jump in how quickly you can prep for sessions and spot patterns across your practice is hard to describe until you’ve done it. See the AI coaching assistant guide for the detailed build.
Client prep: the session before the session
Most coaches prep for sessions by flipping through notes from the last call. AI lets you do something better: ask structured questions about the client’s arc so far.
A realistic prep routine, 15 minutes before a call:
- "Summarize my last three sessions with this client in one paragraph. What were the main themes?"
- "What commitments did they make in the last session that I should check on? Quote the specific language they used."
- "What patterns show up across all my notes with this client that I might not be tracking consciously?"
- "Draft three possible opening questions for today’s session based on where we left off."
The client experience is "my coach remembers everything." The actual mechanism is "my coach has a system for remembering." Either way the client gets better service; the first way is unsustainable, the second is.
Follow-up notes and between-session summaries
The recurring post-session grind: transcribe your notes, write up action items, send a summary to the client. AI is nearly lossless at this. Dictate 4 minutes of voice notes into your phone, run the transcription through Claude with a prompt like:
"Turn these rough session notes into a clean summary for the client. Include: (1) what we discussed, (2) the insights the client arrived at themselves, (3) the two commitments they made for this week, (4) a suggested question for them to sit with. Use warm, direct language. No bullet lists at the top, one at the bottom for the commitments."
Ten minutes of cleanup turns into two minutes of review. Multiply by your weekly session load and you’ve found three hours a week that used to be admin.
Productizing your methodology
The higher-leverage move: turn your named framework into something that runs without you. Three flavors, in increasing difficulty:
1. The custom GPT as a methodology sampler
Build a custom GPT (or a Claude Project configured for public sharing if your client base uses Claude) trained on your books, worksheets, and case studies. Configure it to walk a user through your framework on a small problem they bring. Share the link on your website and in lead magnet emails. Prospective clients get a meaningful sample of your thinking; you get a differentiator and a steady trickle of "I tried the GPT and now I want to work with you directly" leads.
2. The structured intake-to-diagnosis flow
A harder build but genuinely valuable. The user answers a series of questions (either through a form or through a free-form conversation). The AI applies your framework to their answers and produces a diagnostic. This is the lowest tier of what you do, packaged to run without your time. The pricing sits somewhere between "free lead magnet" and "first paid session." See the use-case page on coaching assistants for examples.
3. The full digital program with AI support
A cohort-based or self-paced program where AI handles the steady-state questions ("what does Module 3 suggest I do with a team member who keeps missing deadlines?") and you handle the live calls and edge cases. This is the biggest leverage move and also the biggest shift in how your practice operates. Not for everyone.
For building against a library of your books and writing, see build an AI assistant from books — the guide walks through converting ebooks and long-form content into something queryable.
What to keep out of AI chats
The parts of coaching that don’t belong in ChatGPT, no matter how tempting:
- Full unredacted client narratives. The details clients share in session are often the most sensitive content in their lives. Aggregate patterns are fine. Specific stories tied to specific names aren’t.
- Financial specifics of client companies. Revenue numbers, cap tables, compensation packages — if a client shared this with you under NDA, the NDA covers feeding it to a hosted AI.
- Clinical mental health territory. If a session touches on clinical material — serious depression, suicidal ideation, trauma — that is not terrain for AI assistance. Refer to a licensed clinician and keep AI out of the chain of custody.
- Legal advice. Tempting when a client asks a legal question. Coach the decision, refer the advice. AI will confidently draft legal text and often get it wrong in ways that hurt clients.
A real-world example: coach with 150 client hours to synthesize
Coach working with early-stage founders, three years into a practice, has roughly 150 hours of session notes spread across Notion and hand-written journals. Wants to write a book based on patterns from the work.
- Digitize. Phone-scan the handwritten journals. Run through a handwriting-to-text converter (our handwriting converter works for this).
- Export and convert. Export all Notion pages. Batch-convert everything to markdown.
- De-identify. Find-and-replace client names with generic labels. Ten minutes of tedium, saves future headaches.
- Theme extraction. Load into a Claude Project. Prompt: "Across these 150 sessions, identify the 5-7 recurring themes that showed up in first-year founders. For each theme, pull 3-5 representative quotes."
- Validate. Read through the output with the actual notes open. Refine the themes based on what feels true vs what feels AI-plausible-but-off.
- Outline. Use the themes as book-chapter scaffolding. Write the book yourself — AI produces clean but generic prose; your voice is what makes the book yours.
Total time to go from "drawer of notes" to "credible book outline based on actual patterns in my work": two weekends. Without AI: three months of transcription and theme-hunting that nobody has time for, which is why the book never gets written.
The tone problem, and what to do about it
A risk that’s real enough to name. AI-drafted follow-up notes and emails often sound very slightly off — too smooth, too well-structured, too coach-y. Clients notice before they can articulate why. If every email from you sounds like it came out of the same template, something’s been lost.
Two habits that help. First, don’t use AI output verbatim — always rewrite at least the opening and the closing so your voice leads and lands. Second, feed the AI samples of your actual writing as a style anchor. "Here are three of my previous session summaries — write the next one in this voice" produces much better results than generic instructions about tone.
One tool stack that works
If you’re starting from nothing and want a practical starting point that most coaches can work with:
- Claude Pro as the default chat. Long context window, softer tone, good Project feature for keeping reference docs around.
- NotebookLM for source-grounded work — when you want the AI to stay faithful to specific materials and give citations.
- A batch converter for keeping the corpus current. Our batch convert page handles the periodic dumps.
- Notion or Obsidian as the source of truth for notes. AI reads from the export; humans edit in the original.
- A custom GPT or Claude Project published as a methodology sampler, once you’ve got the corpus clean.
Not a huge stack. Most of the leverage comes from the first two items. The rest is keeping your corpus healthy enough that the AI has good material to work with.
Where to read further
The coaches landing page has more product-focused detail if you want to go deeper on the tooling. The blog post coaches using AI assistants covers what specific coaches are building right now, with examples. And for the book-library version — turning books you’ve highlighted and annotated into something you can query — see the post on extracting quotes from books with AI.