Starting a Consulting Business: The Nine Documents That Do the Work of a Business Plan
Most of what gets written about starting a consultancy is about positioning: pick a niche, name the niche, register a company, build a website. All of it matters, and none of it is the bottleneck. The bottleneck is that consulting is sold and delivered through documents — and most new consultants write each one from scratch, badly, at the worst possible moment: the proposal the night before the call, the scope paragraph after the work has already started, the invoice chase composed while angry.
A business plan does not land a client. These nine documents do. Five of them get you the first client; the other four keep that client from eating your margin, an hour at a time.
Write them once, when you are calm. Then stop negotiating from a blank page.
1. The one-page service description
Not a brochure. One page that answers five things: what you do, who it is for, what changes because of it, what it costs to start, and how a first conversation happens.
The test: a stranger reads it and can say back what you do without using your own job title. If all they can repeat is "consultant," the page is a resume, not a service.
Where it earns its keep: every inbound conversation now starts from the same definition, so you stop re-explaining your own business five times a week.
2. The rate card, with its logic on the back
Three tiers, not a menu: a small version, the normal version, a larger version. For each one — what is included, what is explicitly not, typical timeline, price. On the back, one paragraph of logic: how you set the number, what makes it larger, what makes it smaller.
The back page is not for the client. It is for you, the night before the call where someone says "that's too expensive." A price you can explain is a price you can hold.
One method for the three tiers: price the middle one first, from the work it actually takes. The small version exists to make starting easy — it should be small enough to decide on in one call. The large version exists to make the middle look like the sensible choice, which it is. If two tiers are ever chosen with equal frequency and the third never, the tiers are decoration, not a rate card.
And if drafting the pricing conversation itself is the part that stalls, the Solo Consultant Prompt Vault ($19, one-time) has a dedicated section for it: quoting, defending the number, and trading scope instead of discounting.
3. The discovery call script
Twelve questions in order, including the two that new consultants skip: "What have you already tried?" and "What budget range are you working within?"
The second one is not rude. Arriving at a proposal with no number is what turns a proposal into a guess. And the script's real job is to keep you from talking: you are collecting the exact sentences you will reuse in the proposal — the client's own words for the outcome they want.
The twelve, for the first draft:
- What made you look for help now?
- What have you already tried?
- What does success look like — how will you know it worked?
- Who else is affected by this?
- Who signs off?
- What is the deadline, and what happens if it slips?
- What budget range are you working within?
- What would make this a bad idea?
- Where will the internal pushback come from?
- What is the smallest version of this that would still be worth doing?
- What happens if you do nothing?
- Is there anything you expected me to ask that I have not?
Question ten quietly prices the small tier before you ever build a rate card. Question twelve catches the expectation you were both carrying and neither had said.
4. The one-page proposal
The client's problem in their words, what you will deliver, what it costs, what happens next, and when the offer expires. One page. A long proposal reads as evidence that you do not know which parts matter.
Send it with a date attached, or walk through it live. A proposal with no next step is a document that sits in an inbox until it quietly stops existing.
For the reasoning behind the one-page version: The Proposal Doesn't Need Writing. It Needs Deciding.
5. The scope document: what is in, what is out, what a change costs
A list of deliverables, a matching list of exclusions, and one sentence that prices change: "Anything not listed above is a new conversation, quoted before it starts."
The exclusions list is the section clients thank you for later, and the only thing standing between you and nine months of small favours.
More on how scope actually expands: Scope Doesn't Creep. It Gets Invited.
6. The kickoff agenda
The first sixty minutes set the tone for the whole engagement. Who decides what, how you will communicate, what "done" looks like, what happens when something slips, and the first three tasks with owners and dates.
Send it twenty-four hours before the call. A written agenda also tells the client, without saying it, that meetings with you have a shape.
Anchor it to a written definition of done, not a feeling: Define Done Before You Start, or Argue About It Later
7. The weekly note template
Five lines: done, next, blocked, decisions, what you need from them. Same day every week, same order.
It is the document that makes progress visible without a status meeting, and the record that settles later disagreements — because it was written while it was still true. A version of this, pointed at your own business instead of the client's, is the Monday Review.
8. The change message
When a client asks for something outside the scope, most consultants write an essay of apology. Three sentences work better:
"This sits outside what we scoped. It is [amount] of extra work, which I can do for [price], or we can trade it against [existing item]. Which would you prefer?"
That message is the difference between a scope change that costs you a weekend and one that costs the client a decision.
9. The invoice, and the two emails that follow it
One invoice template with your payment terms printed on it — so the terms are a fact of the invoice, not a negotiation later — plus two short follow-ups: the friendly one at seven days past due, the firm one at twenty-one. Both dated, specific, and free of apology.
"Invoice 1042 was due on the 30th. Can you confirm it is in this week's payment run?"
If drafting those sentences is the part that stalls you, the Solo Consultant Prompt Vault ($19, one-time) has a whole section for it: chasing without burning the relationship, in prompts you fill and send.
The order to write them in
Write the first five in a single weekend. Write the last four the weekend you sign your first client, while the lessons are fresh.
Everything else — the logo, the website copy, the niche paragraph you keep rewriting — can wait until there is a paying engagement to interrupt. For the first month, keep all nine in one folder. The goal is not a polished brand; it is never again negotiating a price, a scope, or a deadline out of thin air.
Where templates stop helping
A template gives you the shape of the document. It cannot give you the number, the trade-off, or the nerve to hold a price while someone waits for you to move. That part is not drafting; it is judgment. It is also the whole difference between a consultancy with documents and a consultancy with work.
If you cannot explain a sentence in your own template to a client, take it out. A borrowed line you cannot defend is worse than an awkward one you can.
What a model can and cannot do at this stage
The drafting half is genuinely delegable now. Given your raw material — a messy call transcript, an email thread, a half-formed scope list — a capable chat model produces a usable first version of most of the documents above in minutes: the proposal skeleton in the client's own words, the exclusions you forgot, the follow-up message you have been avoiding for a week.
What it cannot do is pick your rate, decide what belongs out of scope, or tell you whether the project is worth taking. Hand it your thinking and it organizes; hand it nothing and it invents.
That division of labour is the design of the Solo Consultant Prompt Vault ($19, one-time): sixty prompts in six sections — pricing and quoting, scoping and saying no, mid-project communication, delivering bad news, invoices and chasing, and turning finished work into proof — each with the variables to fill and the output format to expect. It is a set of working documents, not a course, and it makes no promise about what you will earn.
Keeping the nine alive
These documents are not a one-time build. Two maintenance habits keep them honest: after every fifth proposal, spend twenty minutes updating the one that felt hardest to fill — the friction is a signal about what has changed in your business. And once a quarter, reread the exclusions list of your most recent scope document against what actually happened in the project; every item that appears in reality but not on the page is either a missing exclusion or a missing line item.
A template that no longer matches how you work is not a shortcut. It is a slow way of writing the wrong document.
The test
Pick the document you have been avoiding. For most new consultants it is the exclusions list, because writing it forces you to admit what you will not do, and to whom.
Write a bad version today. A bad exclusions list that exists beats a perfect one you will write "when there is time" — and the first client conversation will show you which lines were actually load-bearing.
This note describes a set of documents and a drafting workflow. No revenue outcomes, client results, or success rates are claimed. Bracketed placeholders are slots to fill from your own pricing and scoping. Nothing here is legal advice; your own contract terms govern.