Quotation Management for Consulting: Proposals Built to Be Approved, Not Just Admired

Consulting is sold on a document describing work that does not yet exist, produced by people the client has mostly not worked with, to solve a problem whose size nobody has yet measured. Everything distinctive about quoting in this industry follows from that combination of uncertainty and trust.

It means the proposal has to do more than price. It has to demonstrate that the firm understands the problem, set out an approach specific enough to be argued with, name what will exist at the end, and make clear what the client themselves has to contribute. A proposal that is mostly credentials and a fee is asking to be compared on rate, which is the comparison a good firm least wants.

The most common structural mistake in consulting quoting is pricing a full programme at the moment of least information. The firm either pads the estimate to cover the unknown, which loses the work, or prices it optimistically and absorbs the difference, which wins unprofitable work.

A short diagnostic quoted and delivered on its own resolves both. The client buys a small, defined piece with a clear deliverable. The firm learns enough to scope the real work properly. And the second proposal is written from evidence rather than from assumption, which makes it both more accurate and considerably easier to approve. It also gives a nervous client a low-risk way to find out whether they want to work with this team at all.

Clients buying consulting are buying people, and they know it. The pattern they fear, and have often experienced, is a proposal presented by senior figures and delivered by a team they never met. It is the single fastest way to damage the reputation of a firm in a market where reputation is the entire asset.

Quoting the team by name and grade, with the days each is expected to contribute, turns staffing into a commitment. It also imposes a useful internal discipline, because a proposal that names people cannot be written without checking whether those people are genuinely available in that window. Where substitution later becomes unavoidable, it is then a conversation with the client rather than something they notice in a meeting.

Consulting timelines rarely slip because the analysis was slower than expected. They slip because interviews could not be scheduled, data arrived in the wrong form, workshop attendance was thin, or a decision the plan depended on was deferred.

Listing these as commitments rather than as a polite request changes what happens when one fails. The delay becomes attributable to a dependency both parties agreed to, rather than to consultants who appear to be behind schedule.

Outcome language is attractive in a proposal and unhelpful in a scope. A firm cannot guarantee that the organisation will change, because most of that depends on the client. What it can commit to is what will exist: a diagnostic report, a costed options paper, a target operating model, a set of workshops run, a plan handed to a named owner.

Describing deliverables as artefacts, with a form and a delivery point, makes the engagement completable. It also makes the difference between advice and implementation explicit, which is the boundary clients most often assume runs somewhere further along than the firm intended.

The sponsor reads the proposal for whether the firm understands the problem. Whoever authorises the spend reads it for whether the expenditure can be defended. Those are different documents wearing the same cover, and a proposal that serves only the first stalls quietly in an approval process nobody warned the firm about.

Recording the approval path on the opportunity is what makes this manageable: who sponsors it, who authorises it, whether a framework or panel rate applies, whether a competitive process is required, and when the budget cycle allows a decision. Follow-up can then be genuinely useful, offering the business case input or the procurement documentation the process needs, rather than asking a sponsor who is already convinced whether they have decided.

A signed engagement letter or contract, and where the client requires one, a purchase order. The accepted version, with its phases, team, rates and client commitments, becomes the reference for delivery and for any extension. Time capture, engagement economics, resourcing, document production, invoicing, tax and your accounts continue in the systems that already handle them. What remains here is the record of the opportunity, the versions, the approval path, the rates committed, and the reasons the proposals you did not win were lost.

Read next: all CRM features, lead management software, sales automation, CRM for small business, CRM vs Excel, CRM by industry, and India pricing.