The Promise Inventory: A Quarterly Reckoning of Sales Commitments and Delivery Capacity

Every closed-won deal carries a second contract, one that is rarely written down in a single place. It is made up of the lead times mentioned on a call, the reporting format promised in a proposal, the named specialist implied by an account plan, and the reassuring phrase that onboarding will be straightforward. These are not merely sales artefacts. They are operational load forecasts, expressed in the language of customer expectation.

For UK SMEs, the risk is not that sales teams are dishonest or that delivery teams are inflexible. The risk is that neither group has a routine for comparing what was promised with what can be delivered. The gap surfaces later as overtime, subcontracting, margin erosion or, worse, a renewal conversation in which the customer holds the business to a commitment it never costed properly.

A quarterly promise inventory is a practical response. It does not require a new system or a lengthy audit. It requires a sample of recent deals, a disciplined reading of the commitments inside them, and an honest test against delivery capacity.

Why the promise portfolio deserves attention

Most businesses review pipeline, revenue and forecast. Fewer review the operational obligations that sit inside the deals already won. Yet a signed contract is only the formal layer of the promise. Around it sit proposals, statements of work, email threads, call notes and implementation plans. Each can contain commitments about timing, staffing, customisation, support response, data migration, integration or future functionality.

Some of these promises are explicit and contractual. Others are implicit: the customer reasonably expects a dedicated contact because the sales lead used that phrase; the customer expects a faster response because the proposal emphasised priority service; the customer expects a bespoke report because an example was shown during the pitch. Implicit promises are not less real simply because they are harder to locate. They become real when delivery is asked to honour them.

Treating these commitments as a portfolio rather than a series of individual handovers changes the question. Instead of asking whether one deal can be delivered, the leadership team asks what the accumulated set of promises implies for capacity, cost and service levels in the coming quarter. That is a more useful question for a growing UK business, particularly where sales cycles are shortening and delivery teams are already close to full utilisation.

A quarterly method

The review should be proportionate. For most SMEs, a sample of eight to twelve closed-won deals from the previous quarter is sufficient to reveal patterns. Include the largest deals, the most bespoke deals and at least one deal that was treated as standard. The aim is not statistical precision. It is to expose the commitments that the organisation is currently carrying without a shared view of their cost.

Assemble a small panel: a sales lead, a delivery or operations lead, and a finance representative where margin exposure is likely. The tone matters. This is a reconciliation exercise, not a blame exercise. Sales teams often make promises because they are close to the customer and want to win the work. Delivery teams often absorb them because they want to protect the relationship. The review exists to give both groups the same information before the next quarter begins.

Next, build a promise register. For each sampled deal, read the proposal, statement of work, contract, implementation plan and relevant email or call notes. Extract each commitment into a row with a small set of fields: deal name, promise, whether it is explicit or implicit, the owner, the trigger or due date, the delivery dependency, the current status and any margin impact. The register does not need to be elaborate. A spreadsheet is adequate. The discipline lies in reading for promises rather than for commercial terms alone.

Implicit promises require a deliberate question: what would a reasonable customer expect from the language used? Ask sales and delivery to answer that separately, then compare. Where their interpretations differ, the business has found a handover risk. That difference is often more valuable than a lengthy customer survey, because it identifies the exact point at which expectation and capacity diverge.

Testing the promises against capacity

Once the register is complete, classify each promise. Some will be standard: the business delivers this routinely and has capacity to absorb it. Some will be variants: the promise is close to standard but requires configuration, additional reporting or a different service level. Others will be new: the promise creates a small project, a specialist dependency or a change to the operating model.

The capacity test should be applied to the non-standard promises. For each one, ask whether it can be delivered in the promised timeframe without overtime, without subcontracting and without eroding the margin assumed at sale. If the answer is no on all three counts, the promise is either a capacity risk or a pricing problem. If it is no on one or two counts, the business needs to decide which trade-off it is willing to make and whether the customer should be told.

Timing deserves particular attention. Promises often cluster around quarter-end, renewal dates or implementation windows. A promise that is manageable in isolation can become unmanageable when five similar commitments fall due in the same month. The review should therefore compare the promise portfolio with the delivery calendar, not only with total capacity.

Reading the results

The output should be a short leadership summary rather than a detailed audit file. It might state the number of non-standard promises, the estimated delivery hours they imply, the number that breach capacity in the coming quarter and the margin at risk if they are honoured as understood. It should also identify recurring patterns: bespoke reporting, named individuals, response-time commitments, future-phase functionality, undocumented assumptions about customer effort.

Those patterns inform decisions. The business may choose to renegotiate scope before implementation begins, adjust pricing for non-standard commitments, add capacity in a specific role, standardise certain proposal language or introduce a delivery sign-off for promises above a defined threshold. None of these decisions requires a wholesale change of sales culture. They require a feedback loop.

Making it routine

A quarterly promise inventory can be completed in a focused session if the sample is kept small and the register is maintained between reviews. Over time, the business can add a simple field to its CRM or deal sheet: non-standard promises and delivery sign-off. That single control reduces the chance that a commitment made to win a deal becomes an unplanned cost after signature.

The renewal conversation is the final test. Customers renew against what they believe was promised, not against what the contract technically requires. A promise inventory gives the business a clearer view of that expectation before renewal, while there is still time to close the gap. For UK SMEs seeking sustainable growth, the discipline is not to sell less ambitiously. It is to know what the sales pipeline has already committed operations to deliver.