Where Consulting Margin Actually Dies
Consulting projects rarely overrun because the work was hard. They overrun because two words were never written down: assumed and excluded. The client assumed the workshop was included; the quote didn’t say. The consultant assumed the data would be ready; nobody checked. Six weeks of unpaid drift later, both parties feel betrayed and neither can point to the moment it went wrong — because the moment was a silence.
This template is the anti-silence. A fixed-fee quote built so that every assumption is named, every exclusion is explicit, and the project’s success is defined in writing before the first invoice.
The Quote’s Real Sections
Beyond the obvious — client, contact, project summary in a long text field — the structure carries the four sections that fixed-fee work stands on:
- The deliverables. What the client will physically receive — reports, workshops, models, implementations — as a multiple choice list you control, not a paragraph they imagine.
- The assumptions. The load-bearing section: what must be true for this fee to hold. Data available on day one, stakeholders reachable within a week, decisions made in steering meetings rather than corridors. Each assumption is a yes/no item the client confirms — and each confirmed assumption is a future change request that prices itself.
- The exclusions. What this fee does not buy: the adjacent analysis, the extra region, the implementation phase everyone keeps gesturing at. Named exclusions feel blunt for about a day, then protect the relationship for a year.
- The success measure. How both sides will know the project worked — a short text field the client completes, because success defined by the payer is the only definition that survives the steering committee.
Change Control, Stated Upfront
The quote closes with its own constitution: how scope changes get priced, who approves them, and the plain statement that work outside the confirmed assumptions is a new conversation with a new number. This isn’t defensiveness — it’s the professional courtesy of predictability, and clients respect quotes that respect their own boundaries. A legal acknowledgment of the terms timestamps the agreement at submission.
Feeding the Proposal Pipeline
Accepted quotes should leave a trail: webhooks carry confirmed terms into the practice’s project system, and hidden fields tag each quote’s source so the pipeline learns which referrals become which projects. Adjacent formats for advisory work sit in the consultation collection, the sales category, and the estimate shelf.
Frequently Asked Questions
Value-based or day-rate pricing for consulting?
Value-based where outcomes are measurable and the client agrees on them; day-rate where they don’t. The success-measure field settles which world you’re in — a client who can’t name success isn’t ready for value pricing, and now you know before quoting it.
How many assumptions is too many?
As many as are true — typically eight to fifteen for a substantial engagement. A quote with three assumptions isn’t confident, it’s unexamined; the list is where the expertise actually shows.
The client balks at the exclusions section. Now what?
Walk it through live — exclusions read as clarity, not hostility, when explained. A client who still wants everything included is describing a different project, and the honest response is a different quote.
Should the quote include the discovery phase?
Quote discovery separately and first for any engagement above a certain size: a fixed-price discovery protects both sides from the giant assumption neither party has examined yet. It is the cheapest insurance consulting sells.