What the Proposal Promised: Reconciling Sales Language With Delivery Reality Before 2027
Photo: TheAHL, CC BY 2.0, via Wikimedia Commons
Most UK mid-market firms can produce, within an hour, a list of what they sold last quarter. Far fewer can produce a list of what they promised. The two are not the same. An order form records a price and a term; the surrounding proposal, capability deck, implementation plan and email trail record a set of expectations about speed, responsiveness, scope and outcome. Operations inherits those expectations the moment the contract is countersigned, usually without having read the sentence that created them.
The gap is rarely dishonest
It is structural. Proposals are drafted by people rewarded for winning, often from templates that were accurate two years ago. Delivery is managed by people rewarded for stability, who see the document for the first time at handover. Between the two sits a week or a month in which nobody owns the translation. Commitments about turnaround times, named individuals, integration scope or reporting depth arrive in the delivery queue without a cost attached.
In professional services firms the exposure is sharper than in most sectors, because the product is the promise. A software vendor can patch a gap quietly. A firm that has pledged a two-week turnaround, a partner-led review or a fixed-fee scope has pledged labour it may not have.
What a promise audit actually counts
A promise audit is not a customer satisfaction exercise and not a contract review. It is an inventory of the language the business uses to sell, tested against the capacity it has to deliver. Commitments tend to cluster into five families:
- Speed. Response times, delivery windows, onboarding durations, escalation clocks.
- Certainty. Service levels, uptime, delivery dates, availability of specific named people.
- Scope. What is included, how many revisions, how much training, which integrations.
- Skill. Seniority of the team, sector experience, certifications, named leads.
- Outcome. The commercial result implied in a business case or a case study.
The last is the most expensive and the least examined. A claim that a client achieved a 30 per cent reduction in processing time is, in the hands of a competent buyer, a commitment to replicate it.
A 90-day sprint, phased deliberately
The work is best done in four phases, each with a defined output, so that it does not collapse into an open-ended review.
Days 1 to 15: assemble the corpus. Gather every artefact that has faced a customer in the last 24 months: successful bids, capability decks, statements of work, onboarding packs, the marketing site, webinar recordings, even demo scripts. Strip duplicates and agree a single repository. The point is completeness, not judgement; resist the urge to edit as you collect.
Days 16 to 45: map promise to owner. For each commitment, record its source document, its exact wording, the customer segment it was made to, the delivery owner, and the evidence that capacity exists today. Around 70 per cent of entries will be supportable. The remainder will fall into three buckets: true and documented, true but undocumented, and unsupported. That third bucket is the audit's real output.
Days 46 to 70: price the gap. Overpromising has a cost even when no complaint is made. Capture it in four places: unbilled delivery hours absorbed into projects, service credits and goodwill discounts, escalation and rework time, and the discount conceded at renewal to compensate for a promise missed. Add the cost of the contingency capacity bought late, at agency rates, to plug the hole. Finance can usually supply the first two; the third and fourth require a short interview programme with delivery leads.
Days 71 to 90: decide, then govern. Each unsupported promise receives one of four verdicts: withdraw it, reword it so it is defensible, price it so the cost is recovered, or fund the capacity to deliver it. Verdicts should be signed off by a small group with authority over both sales and operations. Anything left undecided returns to the next cycle with a named owner and a date.
Make the register permanent
The audit decays quickly if it remains a one-off project. Two light mechanisms hold it: a promise register that new proposal language must draw from, and a sign-off gate in the bid process for any commitment outside it. Neither needs software to begin with. A controlled document and a fortnightly thirty-minute review are enough for most firms turning over between £10m and £250m.
Wording matters as much as governance. Replace absolute commitments with calibrated ones. "Dedicated account manager" becomes a named role with a stated response window. "Full integration" becomes a defined list of systems and formats. The commercial intent survives; the delivery exposure does not.
Before the contracting season opens
UK buyers typically finalise budgets and supplier decisions in the first quarter. Proposals issued in January will be written from whatever templates exist in December. Firms that run this exercise through the winter enter 2027 selling what they can actually deliver, and quoting for it accordingly. That is a quieter advantage than a new proposition, but a more durable one.
The honest test is simple. Take the last five proposals the firm sent. Ask the delivery lead to confirm, line by line, that each commitment is achievable at current capacity. If that conversation has not happened, the audit has already told you where to start.