The short answer
A good consulting proposal restates your situation accurately, summarizes what was found and what each problem costs, defines the scope and deliverables, explains how success will be measured against a baseline, sets out the timeline, the price and payment terms, states what the consultant and the owner each commit to, and explains how the engagement ends. If any of these are vague or missing, ask before you sign.
- Findings priced in dollars are the backbone of a strong proposal.
- Deliverables should be things you'll have, not activities.
- Measures, risk and exit terms belong in writing.
Most owners skim proposals for the price and the start date. That's understandable — they're the parts that affect you first. But the rest of the document tells you whether the engagement will work. A proposal that's specific about your business, your problems and how success will be measured is a strong predictor of a specific, productive engagement. A proposal that could have been sent to any company is a strong predictor of generic work.
The ten elements of a good proposal
1. An accurate picture of your situation
The proposal should open by describing your business and your problems in terms you recognize. Not a generic paragraph about "businesses facing challenges," but your revenue range, your team, your main frustrations and what you told the consultant you wanted. If it reads like it was written about someone else, the consultant wasn't listening.
2. Findings, with a price on each
For proposals that follow discovery, this is the heart of the document. What did the consultant find, and what does each problem cost per year? Underpriced services, labor hours that don't turn into billable work, late invoicing, jobs that lose money line by line — each with a dollar figure. Priced findings let you judge priorities and value; without them, you're buying opinions. We explain what a proper diagnosis looks like in what a business diagnostic uncovers.
3. A clear scope
What problems will the engagement address, and — just as important — which will it not? Clear exclusions prevent disputes later and show the consultant has thought about focus. A scope that promises to fix everything usually fixes nothing well.
4. Deliverables you'll actually have
Deliverables should be tangible outcomes, not activities. "Weekly meetings" is an activity. "A repriced service menu implemented in your quoting system" is a deliverable. So is "a job-costing process your estimator runs weekly," "documented procedures for the twelve core tasks in dispatch," and "a management meeting your team runs without the consultant." Our article on what you should have when an engagement ends goes into detail.
5. Measures of success, with a baseline
Which numbers will change, from what starting point, measured where? The strongest proposals name specific figures from your own financial statements and record the baseline before work starts. Soft measures like "improved alignment" may be real but can't be verified.
6. A realistic timeline
Phases, milestones and review points — not just a start and end date. Quick wins should appear early, with deeper structural work later. A plan that promises everything in the first month is as unrealistic as one with no milestones for a year.
7. Who will do the work
The proposal should name the person or people who will be in your business, and describe their role. If the proposal is vague here, ask directly.
8. Price, payment terms and extras
The total investment, how it's paid, and anything not included — travel, software, other advisors. Payment tied to milestones is common and reasonable. For context on typical structures, see consulting fee structures explained.
9. Mutual commitments and risk
What the consultant commits to, and what you commit to in return: access to numbers, time for working sessions, named people responsible for changes. If there's a guarantee, its terms — measure, baseline, period, remedy — belong here in full.
10. How the engagement ends
How the work winds down once goals are met, how either side can end it early, and what notice is required. A confident consultant doesn't need to lock you in. See how to end a consulting engagement cleanly.
A sample outline of a strong proposal
If it helps to see the elements together, here's the shape of a proposal that would pass every test above. Length varies, but the order is logical: your business first, the consultant last.
- Your situation — a half page describing the business and what you said you wanted.
- What we found — each problem, the evidence for it, and its cost per year, ranked by value.
- What we recommend — the fixes, in sequence, with quick wins first and why.
- Scope and exclusions — what's in, what's out.
- Deliverables — what you'll have at the end: processes, tools, routines, trained people.
- Measures — the baseline numbers, the targets, where they'll be measured and when.
- Timeline — phases, milestones and review points.
- People — who does the work and what's expected from your team.
- Investment — fee, payment schedule, and anything outside the fee.
- Commitments, risk and exit — guarantees, mutual obligations, and how the engagement ends.
Notice how little of that outline is about the consultant. Credentials and past results belong in the conversation that led to the proposal; by this point, the document should be almost entirely about your business and what will change in it.
What bad proposals have in common
- Boilerplate. Pages of the consultant's philosophy and credentials, very little about your business.
- A program, not a plan. The same modules every client gets, regardless of what's wrong.
- Activities instead of outcomes. Lists of meetings, workshops and reports with no statement of what will change.
- No numbers. No priced findings, no baseline, no target.
- Long lock-ins. Minimum terms with no way out if the work isn't delivering.
- Hidden costs. A low headline fee with extras for everything.
More warning signs are in business consultant red flags.
How our proposals are built
Our proposals come at the fourth step of our process — findings and guarantee, which covers the scope of work and budget. By then we've been inside your business: floor walks, ride-alongs, interviews and a detailed audit of your numbers. The proposal lays out what we found, what each problem costs in dollars per year, what fixing it is worth, and the sequenced plan. It names the deliverables and the measures, sets out what we commit to and what we ask of you, and puts the 2×1 guarantee in writing: at least two dollars of additional net profit for every dollar of consulting investment, on a measurement basis defined in the agreement.
Questions to ask about any proposal
- Which findings drove the priorities, and why these first?
- What will I have in hand at the end that I don't have today?
- Which numbers will change, and how will we both see it?
- What will you need from me and my team each week?
- What happens if we're not seeing progress at the first review?
- What would you cut if the budget were smaller?
A good consultant welcomes these questions, because they show you're treating the engagement seriously. The answers often improve the proposal.
Frequently asked questions
How long should a consulting proposal be?
Length matters less than specificity. A focused proposal of a few pages that describes your business, priced findings, deliverables and measures is better than a long one filled with generic material.
Should a proposal come before or after discovery?
A proposal for discovery can come first; a proposal for the full engagement should come after it. A detailed engagement proposal written before anyone has examined your business is based on assumptions.
Can I negotiate a consulting proposal?
Yes. Scope, phasing, payment terms and review points are all reasonable to discuss. Narrowing scope to the highest-value problems is often the best way to adjust the investment.
Is a proposal the same as a contract?
Not always. Some firms combine them; others issue a separate engagement agreement. Either way, the key terms — scope, deliverables, measures, price, commitments and exit — should end up in the signed document.
Should a proposal include the consultant's past results?
A brief reference to relevant results is fine, but it shouldn't dominate. The proposal's job is to describe your business, the problems found and how they'll be fixed. Detailed case studies are better shared in conversation or on a results page.
What should I do if two proposals are hard to compare?
Put their key elements side by side in a table: findings, deliverables, measures, who does the work, price, risk and exit terms. The more complete proposal usually becomes obvious. See cheap vs. expensive consultants.
Where to start
A good proposal starts with a good conversation. Ours is free and focused on your numbers, not on us. Start the free assessment — about five minutes — and you'll hear back within one business day. Before you sign anything, read the contract terms every owner should check.
