Knowing how to consult and knowing how to run a consulting business are different skills, and you need both. This module is the operator's layer: how to get clients, define what you'll actually do, price it without underselling or scaring them off, and keep the relationship healthy enough to do it again.

Positioning and finding clients

The first instinct — "I help any business with anything" — is the weakest possible position, because it gives no one a reason to call you. The counter-intuitive truth: a sharp niche wins more work than broad generality. "I help early-stage B2B software companies fix their pricing" is far easier to refer, market, and trust than "business consultant." You can broaden later; start narrow enough to be the obvious choice for someone. Clients arrive mainly through referrals, reputation (writing, speaking, visible expertise), and warm networks — rarely cold pitches. So the long game is doing good work that people talk about, and being known for one specific thing.

Scoping — the contract that prevents pain

Most consulting disasters trace back to a fuzzy scope. Before any work, agree in writing: the problem, the specific deliverables (a report? a model? an implemented change?), what is explicitly out of scope, the timeline, and what 'done' looks like. The phrase to fear is "while you're at it, could you also…" — scope creep is how a profitable project quietly becomes a loss. You don't refuse; you say "happy to — that's a separate piece, here's what it would add." Clarity is kindness, to both sides.

The proposal and the statement of work

A good proposal mirrors the Pyramid Principle: show you understand their problem (often better than they stated it), lay out your approach, define deliverables and timeline, state price and terms, and establish why you're credible. Lead with their problem, not your resume — clients buy a proposal that proves you grasp their situation far more readily than one that lists your services. The statement of work (SOW) is the proposal's binding cousin: the document that pins down scope, deliverables, dates, fees, and what happens when things change (a change-order process). It's not bureaucracy — it's what protects the relationship when memories diverge three weeks in.

Pricing — stop selling hours

• Time-based (hourly/daily) — simple, but caps income at hours-in-a-day and perversely punishes you for being fast.
• Fixed-fee / project-based — quote a price for a defined outcome. Rewards efficiency, gives the client certainty, and requires you to scope well so you don't underprice.
• Value-based — price against the value created (a slice of the savings or revenue you unlock). Most lucrative and hardest; needs trust and a clear link between your work and the outcome.
• Retainer — a recurring fee for ongoing access/advice. Predictable income; the basis of a stable practice.

The mindset that matters most: clients aren't buying your time, they're buying a result. A diagnosis that saves a six-figure mistake is worth far more than the hours it took. Price the result, defend it with the value, and resist the instinct to discount yourself out of nervousness.

Managing the relationship

Three habits keep clients happy and returning: communicate proactively (a short update before they ask beats a perfect report that's silent for three weeks); manage expectations honestly (under-promise, over-deliver — never the reverse); and make them look good (your real client is often a person whose reputation rides on hiring you — help them win internally). Repeat business and referrals, not heroic new pitches, are what make a consulting business sustainable. After a project, capture a short case study and ask for an introduction — that's the engine of the next project.

Test yourself