How to Write a Book as a Consultant: Hours, Ownership and Client Evidence

Every consultant we speak to has the same two problems with the book, and neither of them is writing. The first is time: every hour on the manuscript is an hour you could have billed, and the book always loses that argument in a busy month. The second is ownership: your best material sits inside client reports, under NDAs, or in a methodology your firm calls its own.

Generic advice skips both. “Find your big idea and write 500 words a day” is not a plan for someone whose calendar is sold in days and whose evidence belongs partly to other people. This guide is the consultant-specific version.

What a book does in a consulting sales cycle

Consulting is bought slowly and on trust. A buyer hears your name, checks you out, has a first call, asks for a proposal, and then sells the decision internally to people who never met you. We would argue a book does more in the middle of that sequence, as a credibility document during scoping, than at the top as a way of finding strangers.

There is some evidence that substantive content changes how buyers respond. In the 2024 LinkedIn and Edelman research, 9 in 10 decision-makers and C-suite executives said they were more receptive to outreach from a company that consistently publishes high-quality thought leadership. LinkedIn sells B2B advertising, so read that as a direction rather than a promise.

On books specifically, Josh Bernoff’s 2024 Business Book ROI study of about 300 respondents found that 31% of authors boosted their consulting revenue, while 34% had no gross profit even after counting speaking and consulting income. Bernoff himself says the study probably overstates the benefits because of survivor bias. The honest reading: a book helps some consultants a great deal and many not at all, and the difference is mostly whether it was built for a buyer and a next step.

How to use the finished book in proposals and first calls is covered in our main-site guide to the authority book for consultants, along with where to draw the line on giving away your IP. This article stays with the production problem.

Price the book in billable hours before you start

Most consultants underestimate the book because they think in words, not hours. The best public record we found is from Mo Bunnell, who logged every 15-minute block of his traditionally published book, The Snowball System. His total was 813.25 hours. Planning and first draft took 255 hours; drafting, revising and copy-editing together took 389. Marketing and launch prep added 168.5.

That is one person and one publishing route, so treat it as a reference point. Self-publishing removes the proposal hours; a ghostwriter or drafting tool cuts drafting hours but not the thinking, checking and approving.

Do the arithmetic for your practice. The 389 writing hours at an illustrative $200 an hour come to $77,800 of time. Few consultants are fully utilised, so the true cost is lower, but the calendar cost is what kills consulting books: drafting stops the week a big engagement starts and rarely restarts.

Three rules we would hold any consulting author to:

• Budget it like an engagement. Fixed weekly hours in your calendar. Two protected half-days beat “whenever it’s quiet”.
• Use bench time for the work only you can do. The evidence ledger and the chapter plan need your judgement. Drafting can be shared.
• Do not start in the first month of a large project. Start in a gap, get the plan finished, and let drafting run through the busy period at a lower rate.

The three ways to produce the manuscript trade money for your hours very differently:

Route	Your hours	What you pay	Where it fails for consultants
Write it yourself	Highest: drafting, revising and checking are all yours	Editor and design only	Stalls in busy quarters; the book takes years
Ghostwriter	Interviews and chapter reviews	The largest cash outlay	Your voice and evidence filtered through someone else; confidentiality now involves a third party
AI or guided software working from your documents	Material gathering, review, verification and approval	Lowest cash outlay	Generic output if it works from general knowledge instead of your material; you still check every claim

We compare these routes in detail in writing a business book without a ghostwriter.

Who owns what you know: independent versus firm-affiliated consultants

Generic book advice never asks this, and it changes the plan. What follows is general information based on US law, not legal advice. Other countries have their own rules, and your contracts matter more than any general principle.

If you work for a firm

US copyright law treats “a work prepared by an employee within the scope of his or her employment” as a work made for hire, and for those works the employer is considered the author unless both sides have signed a written agreement saying otherwise. If you build frameworks, diagnostics and decks as part of your job, assume the firm owns them. Employment contracts often add publication approval and outside-activities clauses on top.

Our view is blunt: if you are employed at a firm, either write the book with the firm, as a firm book with its approval and support, or wait until you leave and write from your own judgement rather than the firm’s toolkit. A “personal” book built on firm methodology, written quietly at weekends, is the worst of both.

If you are independent

You start in a stronger position: methods you developed outside any employment are generally yours. The risk sits in client contracts, which often assign deliverables to the client and, in better drafts, carve out your pre-existing know-how and tools. Read each one. A report you wrote may legally belong to the client even though the thinking in it is yours, so do not paste from deliverables. Re-express the idea from scratch.

There is also an ethical layer. The IMC USA code of ethics asks members to protect confidential client information that is not public knowledge (Article 5.0) and not to use other consultants’ or firms’ proprietary information or methodologies without consent (Article 12.0). That second article matters if you left a firm and built your practice on habits you learned there.

Your situation	Likely owner of the method	Check before writing	Safe default
Employee at a consulting firm	The firm, for work within your job	Employment contract, IP and publication policy	Write it as a firm book, or wait
Partner or equity holder	Depends on the partnership agreement	Partnership and IP terms	Agree rights in writing first
Independent, own method	You, subject to client contracts	Each client’s IP and confidentiality clauses	Teach the method; never reuse deliverable text
Associate working under another consultancy	Often the prime contractor, plus its client	Your associate agreement	Get consent from both
Ex-firm, now independent	You for your judgement; the firm for its tools	Old employment agreement; IMC USA Article 12.0	Write from your own experience, not their templates

Turn engagements into an anonymised evidence ledger

Testing your point of view and turning your method into a framework are covered in how to write a thought leadership book. Here we deal only with the raw evidence.

Open a spreadsheet with one row per engagement. Columns:

1. Problem pattern in the buyer’s words, taken from the proposal.
2. What you did differently from the client’s previous attempts.
3. What changed, only if you have the numbers in a document.
4. Permission level: named with written consent, disguised, or pattern only.
5. Source document where the evidence lives.

Fifteen rows usually show the book’s real subject faster than months of thinking. They also give you evidence most consultants overlook: counts across your own work. A hypothetical line such as “in 11 of 15 restructuring engagements, the delay sat in one approval step” is safer than a named case study, harder to identify, and in our opinion more persuasive to a sceptical buyer than one vivid story.

From experience to manuscript: the sequence we would use

1. Write the business case in one paragraph. Name the buyer, the problem they pay to solve, and the paid next step the book leads to. If you cannot, stop here.

2. Pull the archive. Proposals, statements of work, final reports, steering-committee decks, workshop materials and your own articles. Proposals are the best raw material, better than final reports, because they explain the problem in the buyer’s language before it was solved. Strip client names and identifiers from every document before anyone else sees it.

3. Build the evidence ledger from the section above.

4. Sort it into chapters. Group rows by the problem they illustrate, not by client or date. Our guide to organising years of experience into book chapters covers this step in detail.

5. Draft from your material, in your voice. This is where your hours go if you do it alone. If you use AI, it needs your documents and your writing samples to work from; asked a general question, it returns the consensus your buyers have already read. See training AI on your writing style and writing a book from your own documents.

6. Run a sign-off pass. Send relevant passages to clients who could recognise themselves, and to your firm if you are affiliated. Then give the full draft to two readers who look like your buyer, not to other consultants.

7. Edit, then publish. A professional editor is not optional for a book that represents your judgement.

Guided book software is one option for step 5. WritebookAI, for example, runs a source analysis of the PDF, Word and text files you upload (decks can be exported to PDF), shows what the material covers and what is missing, and resolves gaps in a verification interview before building a chapter plan. Chapters are drafted from your material in a voice profile built from your own writing samples; when a client result or statistic is missing, the draft leaves it out and asks you instead of inventing it. You approve every chapter. It does not review your NDAs, decide who owns your IP, or replace a copy-editor, and you should read its privacy policy before uploading anything from client work. If you would rather hand the whole project to a person, a ghostwriter is the better fit.

A worked example: one book idea, two consultants

Here is a hypothetical pair. Both have spent a decade on procurement cost reduction for mid-sized manufacturers, and both want to write the same book: why savings programmes lose most of their gains in the second year.

Consultant A is independent. She owns her diagnostic, which she built after going solo. Her ledger has 14 engagements: three clients agree in writing to be described in disguised form, the rest become pattern-level counts. Two contracts assign all deliverables to the client, so she rewrites those insights from scratch. Her business case: the book leads to a fixed-price savings-retention review. She blocks Tuesday and Thursday mornings and starts the plan in a four-week gap between projects.

Consultant B is a director at a mid-sized firm. The diagnostic he uses daily was built by the firm, and his employment contract requires approval for external publications. Rather than writing quietly, he proposes a firm book with his name on the cover, the firm paying for editing and design, and its legal team reviewing the client material. It will take longer to agree and less time to write. If the firm says no, his best move is to wait, not to publish a lightly disguised version of the firm’s method.

Your first two weeks

Open three documents: your last five proposals, your current client contracts, and, if you are employed, your employment agreement. Read the contracts first. Then write the one-paragraph business case and start the ledger with the five proposals.

By the end of the second week you will know who the book is for, what you are allowed to put in it, and whether you have evidence for a whole book or only a strong article. Each answer is useful. Only one of them means you start writing.