The Date Sales Promised and Delivery Never Saw
3 min read14-Nov-2026
Why does sales promise dates the floor can't meet?
The Structural Pattern
A commitment enters the business wherever the deal is being won. A sales call, an email, a message sent to hold a customer who is about to walk. At that moment, the person making the promise is focused on the deal in front of them. The week on the floor three months out is somewhere else entirely.
The delivery calendar that must absorb the commitment is a separate system, maintained by a separate team, visible to different people. Between the promise and the calendar there is no checkpoint. The date is set, and only later does anyone discover whether the week it landed on had room.
Watch where the number actually comes from. On a good day it is a considered estimate. On a busy one it is the date that would be true if nothing else were running, quoted by someone who has no way to know what else is running. The busier the firm gets, the more often the second version is the one the customer hears.
This is the signature of capacity mismatch, and it is a structural gap rather than a human one. What is missing is a place where a commitment is tested against real load before it is made.
By the time the slip is visible, the decision that caused it is weeks old and several conversations back. Operations gets the blame for a commitment it never made and never saw coming.
Why the Usual Fixes Fail
Three responses are common, and all three miss. Tightening sales targets treats a visibility gap as a behaviour gap. Pushing delivery to work harder taxes the people already absorbing the mismatch. Adding headcount scales the floor without touching the handoff that oversold it.
One firm we looked at had added two people to the floor after a bad quarter of slips. The next quarter slipped again, in the same way, because the extra capacity was being sold the moment it appeared, by a sales motion that still could not see it.
Each response can look reasonable in a single quarter. Across a year, they compound the problem, because none of them change where or how a date gets created.
The Repair
The fix is architectural and modest. One shared surface where every promised date is booked against the real delivery calendar before it is confirmed. A rule, held without exception, that a date is not final until the team carrying it has seen the load it joins.
The surface itself can be simple. It has to show what delivery can clear in a week, what is already committed against those weeks, and it has to refuse to let a new date be confirmed until it has been placed against both. Tool choice matters far less than the rule that sits on top of it.
In practice, this shifts a single thing: the authority to create a commitment now sits with someone who can see the week. That is a small change in who clicks confirm, and a large change in what the business can promise with a straight face.
The firms that install this still promise boldly. They just promise accurately, which is a different and more valuable thing. Dates hold, escalations fall, and the delivery team stops starting every week behind.
The Principle
A date your delivery calendar never agreed to is a liability with a deadline, and the customer always finds out last.
If your firm is making commitments faster than delivery can absorb them, the MetMov structural health check maps exactly where that break sits.
Related reading: the cost of hero culture when a handful of people carry every deadline; why founder-led sales stops working past a certain scale; and the pillar piece on building the operating system for founder-led firms.
Discussion
Ready to install your Operating Spine?
Ninety days to install the cadence, the numbers and the decision rights, run by your own team. A short scoping call is where we work out whether it fits.