Expert and business books

How to write a book as a consultant or coach

August 16, 2026 · The StoryProp team

Consultants and coaches sit on more finished prose than they think. Every discovery call, every workshop, every patient explanation of the same principle to the fourth skeptical executive this quarter — that is the book, already composed, already tested on a live audience, just not written down. You write it by capturing the practice rather than starting a separate project: log what clients ask, build the chapters on the framework you already teach, disguise the case stories properly, and hand the method over in full. That last move is the one that pays. A 2024 study of business book ROI surveyed 301 published nonfiction authors: 31% reported a consulting revenue increase after publishing, and among the 80 who reported consulting income the median increase attributed to the book was $50,000 cumulative. The problem is rarely material. The problem is architecture, ethics, and the peculiar temptation to turn two hundred pages of teaching into one long pitch.

This piece is about the consultant's specific version of the job. The general method — finding the argument inside the expertise, then building chapters from the argument — is covered in turning your expertise into a book, and the wider question of standing is covered in how to position yourself as an expert. What follows assumes your expertise lives where a consultant's always does: in the room, with clients.

Your client work is the raw manuscript

Most people who wonder how to write a book as a consultant picture starting from a blank page, as though the book were a separate project from the practice. It isn't. Your engagements have already produced the three things a nonfiction draft needs most: the questions readers actually ask, the order in which they need the answers, and proof that your answers survive contact with reality.

So before you outline anything, start a running log. After each call or workshop, take ten minutes and write down what got asked, in the client's words rather than yours. Note where people pushed back, because resistance marks the chapters that will need the most care. Note which explanation finally landed after three that didn't, because the one that landed is the paragraph you keep. Record who said what in which context, and when; months from now, that specificity is the difference between evidence and vague recollection.

The log will also correct your table of contents. A pricing consultant might assume chapter one is her value-based pricing model. Then she reads back a year of notes and finds that every engagement actually began somewhere else — with a leadership team afraid to raise prices at all. The real first chapter is about fear, not formulas. Clients reveal the true order of a book by the order in which they get stuck.

Frameworks make good chapter spines

Most working consultants and coaches carry a framework: a three-stage model, a diagnostic, a sequence of moves with a name. This is a gift to the book, because it solves the hardest structural problem in nonfiction, which is order. Each stage becomes a chapter or a section, and each chapter can answer the same four questions: what this stage is, what it costs to skip it, what it looked like inside a real engagement, and what the reader can attempt on their own before anyone hires anyone.

The books that built practices this way are easy to name. Gino Wickman's Traction set down the Entrepreneurial Operating System — a named framework with a fixed sequence of meetings, scorecards and quarterly rocks — and a network of certified EOS Implementers now teaches that same sequence to companies Wickman never meets. Michael Bungay Stanier's The Coaching Habit did the compact version for coaches — a short, fixed set of questions, one per chapter. No public source attaches a consulting-revenue number to either book, and the mechanism is the interesting part anyway — a framework written down carefully enough that other people can run it is a framework that scales past the author's own calendar.

But the spine is not the whole body. A framework rendered faithfully, stage by stage, with nothing else, reads like slideware. What makes a chapter a chapter is friction: the client who accepted the diagnosis and then quietly ignored it, the rollout that failed the first time and why, the caveat you always give in the room but somehow left out of the deck. On the page, your authority comes less from the model's elegance than from the scars of applying it.

Client stories in a book: disguise, composite, or ask

Client stories are the consultant's great advantage and the consultant's great liability. Used well, they carry the book; used carelessly, they can cost you the relationships the book exists to create. You have three tools, and most books need all of them: anonymization, composites, and permission.

Anonymize by function, not just by name. Swapping “Meridian Logistics” for “a logistics company” is no disguise at all if the story includes a botched reorganization that everyone in the client's industry watched happen. Change the industry, the geography, the scale — whatever details are doing identifying work without doing teaching work. The test is not whether a stranger could name the client. It is whether the client's own colleagues could.

Composites go further: one story assembled from several engagements, true in pattern, fictional in particulars. They are legitimate, and often kinder than a thin disguise, but disclose them. A single line in the front matter saying that case stories are composites with details changed costs you little and protects a great deal. What you may not do is present a composite as a specific, verifiable triumph. Readers forgive constructed examples; they do not forgive learning that a thing presented as real was assembled.

Permission is for the stories worth telling straight. When an engagement is recognizable no matter how you dress it, or when naming the client would strengthen the story and honor them, ask — in writing — and show them the actual passage rather than describing it. Check your agreements first; many engagements sit under confidentiality clauses that settle the question for you. Even where no contract forbids it, apply a simpler test: if this client read the page cold, would they feel ambushed? A story that fails the test gets disguised further or cut, however good it is. You can usually keep the lesson and lose the sting; one honest way is to recast yourself as the person who got it wrong.

The sales-pitch trap

Now the trap that catches coaches in particular: the book that is secretly a funnel. Every chapter narrows to the same conclusion — this is hard, call the author. The tell is what the writing withholds. A pitch-book gestures at the method but keeps the working parts vague, because its author is afraid that a reader who understood everything would never become a client.

That fear has it backwards. A book that always closes never opens. Readers can smell withheld information, and what they conclude is not that you are deep but that you see them as leads. Give the method away — the diagnostics, the sequences, the failure modes, the judgment calls. The reader who takes it all and implements alone was never going to hire you; the reader who sees exactly how much judgment the method demands in practice is the one who calls. More than 70% of the authors in the ROI study reported an increase in leads or gigs after publication, and among those who saw one, the study describes typical volumes of around ten speaking gigs, seven workshop gigs, dozens of consulting leads, or scores of coaching sessions.

There is independent evidence for the mechanism underneath that. The 2025 Edelman–LinkedIn B2B Thought Leadership Impact Report, which surveyed nearly 2,000 global professionals, found that 86% of decision-makers are more likely to invite an organisation that consistently produces high-quality thought leadership into an RFP process, 73% consider thought leadership a more trustworthy basis for judging a firm's capabilities than its marketing materials and product sheets, and 60% say it makes them willing to pay a premium. The report measures published thought leadership broadly rather than books specifically — but a book is the densest, most durable form of it a practice can produce, and it is the one a prospect can read cover to cover before your first conversation.

Drafting and publishing without stalling the practice

The other enemy is the calendar. A consultant's book gets written in the seams of client work, so the process has to survive interruption. The ROI study put the median time authors spent actually writing at 10 months — 12 months for traditionally published authors, 6 for self-published — and that clock excludes proposal, submission and production. Treat it like an engagement with yourself: defined scope, a standing session, and notes good enough that you can reload context after two weeks away. Draft in small units — one case story, one stage of the framework — rather than promising yourself a chapter and then dreading it.

This is where a project-aware drafting partner earns its keep. StoryProp is AI book writing software built around a permanent, ordered project conversation, and the decisions you confirm — the framework's structure, each story's disguise, the voice you have settled on — get promoted to records the agent reads before it drafts. Once you have ruled that the logistics client is now a Midwestern medical-device firm, drafts stay ruled that way; the real details do not drift back in. Interview notes and research live separately from the book's canon, saved with sources and dates, which is exactly the evidence-versus-story boundary a consultant's book has to maintain. Revision is pointed: change the passage you name, and the chapters you were happy with stay as they were.

As for how to publish a book as a coach or consultant, the route — a traditional house, a hybrid arrangement, doing it yourself — matters less than most coaches fear, because the book's main job in a practice is not shelf placement. The study's own numbers make that measurable: across all authors, 47% of the revenue a book generated came from sources other than the book, and among authors generating $25,000 or more it was 69%. The chart below is the shape of it.

The speaking half of that chart is the one most often exaggerated. Bureau rate cards publish tiers rather than measurements, so the figure to hold on to is the within-author one from the ROI study: 34% of business-book authors reported a speaking-fee increase after publishing, and among those reporting speaking income the median increase attributed to the book was $30,000 cumulative. The same study recorded 31% of authors seeing no increase in any category, and found that copies sold predicted neither ROI nor whether an author met their stated goals. So whichever route you take, protect the job that actually pays: a clean, well-edited text with your name on it, in front of the right readers. The route decision can wait until a manuscript exists. Most stalled books stall long before it would have mattered.

The book you are best equipped to write is the one you already deliver out loud, one client at a time. The calls happened. The framework holds. The stories are sitting in your notes, waiting to be disguised properly and told well. Writing them down is not a departure from the practice. It is the practice, compounding.

Your framework, your disguised case stories, and the rules you have set for both can live in one project that remembers them. StoryProp drafts from what you have already decided, so the book grows between engagements instead of restarting after every gap.

← All posts