Sold, Delivered, Invoiced: Reconciling the Customer Promise Across the UK SME

Most UK SMEs do not lose margin in a single dramatic decision. They lose it in the small distance between what a customer was led to expect and what the business actually supplied. A fast turnaround mentioned on a call, a bespoke finish added to win a tender, a named account contact offered as reassurance: each can be reasonable in isolation. Taken together, they become an informal promise book that operations absorbs through overtime, expediting and rework, while finance absorbs the consequences through credit notes, delayed cash and thinner margins.

A 360 promise audit is a practical way to close that distance. It does not begin with blame. It begins with evidence: a sample of recent deals viewed from three sides of the same transaction, namely sales, delivery and invoicing.

Why the customer promise needs its own record

Many SMEs have a CRM record, a quotation, a job sheet and an invoice. Fewer have a single view of the promise that connects them. The sales team remembers the relationship. Operations remembers the workaround. Finance remembers the adjustment. Each version may be accurate in its own way, yet none provides the whole picture.

That matters because the cost of a promise is rarely visible at the point it is made. A shorter lead time may be met by paying for expedited components. A bespoke request may be absorbed by a supervisor who reallocates staff at short notice. A flexible payment term may be approved to secure the order and then quietly increase working capital pressure. Individually these look like sensible compromises. In aggregate they can become an operating model that is difficult to price, plan or repeat.

The audit exists to make that model visible before it becomes entrenched.

A three-way reconciliation, not a blame exercise

Select a sample of recent closed deals, ideally fifteen to twenty from the past quarter or six months. Cover a mix of products or services, account sizes, salespeople and channels. For each deal, build a simple three-column record.

First, capture what was sold. Use the quotation, proposal, order confirmation, CRM notes and relevant emails. Record the core scope, lead time, service commitments, inclusions, exclusions and commercial terms. Where possible, distinguish between what was formally offered and what was mentioned conversationally.

Second, capture what was delivered. Use job sheets, delivery notes, support logs, project plans and internal correspondence. Look for additional work, revised timings, extra reviews, priority handling and any bespoke elements that were not in the original scope.

Third, capture what was invoiced and collected. Use the invoice, credit notes, payment record and any subsequent adjustments. Note discounts, write-offs, late payments and disputed items.

Then compare the three columns. The aim is not to prove that one function is at fault. It is to identify where the promise, the delivery and the commercial outcome diverge, and to understand why.

The mismatches worth counting

A small number of recurring mismatch types usually emerge.

• Scope drift: bespoke work, extra reports, additional site visits or minor customisations that were never priced.
• Timing pressure: lead times sold on best-case assumptions while operations plan with buffers and absorb the difference through overtime or expedited supply.
• Service expectations: response times, named contacts, reporting frequency or review meetings that became standard practice without being costed.
• Commercial terms: extended payment days, settlement discounts or included extras that sales treated as relationship-building and finance treated as margin leakage.
• Change control gaps: verbal variations that were delivered but never documented, approved or invoiced.

Quantify where you can. Estimate the hours of rework, the premium paid for expedited delivery, the value of credit notes and the cash impact of extended terms. Ranges are acceptable. The purpose is not false precision but a realistic sense of what the current promise costs.

Turning findings into a workable promise

Once the sample has been reviewed, bring sales, operations and finance together for a structured workshop. Present the evidence as a shared operational issue rather than a departmental critique.

Agree a small number of promise tiers. For example, a standard offer, an enhanced offer and a bespoke offer. For each tier, define what is included, what is excluded, the delivery assumptions, the approval route for exceptions and the pricing logic. This does not need to be bureaucratic. A one-page promise charter, supported by an order acceptance checklist, is often enough to change behaviour.

Update sales materials so that the external message matches the internal standard. Add the relevant promise fields to the CRM or order form. Give operations a clear route to flag when a requested promise cannot be met without additional cost or risk. Give finance a seat at the table before non-standard terms are approved.

Governance that keeps the promise honest

A promise audit should not be a one-off exercise. Review a small sample each quarter and track a handful of indicators: quote-to-delivery variance, rework hours, invoice adjustments and the number of approved promise exceptions. When a new service or product is launched, require a short promise review before it is sold.

It also helps to examine sales incentives. If reward is based solely on booked revenue, there is little incentive to protect delivery capacity or margin. A more balanced view, including renewal, delivery quality or margin after adjustments, can reduce the pressure to overpromise.

A promise audit does not narrow ambition. It makes ambition deliverable. When sales, operations and finance work from the same view of what the business can genuinely provide, the result is a customer promise that can be sold with confidence, delivered without hidden strain and invoiced without unpleasant surprises.