Short answer
Triage the live promise like an incident: scope what was committed in writing, price the build honestly, and decide within a week. Then fix the system, because chronic promise-selling is a symptom rather than a discipline failure. The goal is not sales obedience. It is making the honest path the fast path.
The contract is signed. Somewhere in a call, a demo, or a redlined statement of work, the customer was told the integration exists, or is on the roadmap for next quarter, which in their reading is the same sentence. Engineering heard about it from the kickoff invitation.
Everyone is angry at the wrong altitude: at the salesperson, rather than at the missing system that made the promise possible and rational. Firing the messenger of an absent process is the most common response and the least useful one.
The triage, this week
Speed matters more than fairness in the first week, because every day the promise sits unexamined is a day the customer builds plans on it and the cost of correction rises. Run these four steps in order and finish inside five working days. Assigning blame is a separate conversation and it can wait; the commitment cannot.
- Get the commitment in writing: contract language, email trail, demo recording. Separate what was promised from what was implied, because those need different responses.
- Price the real build rather than the optimistic one, and name explicitly what it displaces from the current quarter.
- Decide at the right table: build and log it, renegotiate scope or timeline with the customer now, or unwind while credibility is intact.
- Tell the customer the truth this week, whichever call you made.
Step three has three legitimate outcomes and founders routinely forget the middle one. Renegotiating a timeline six weeks after signature is an awkward conversation. Renegotiating it at go-live, with the customer’s own launch plan already built on your date, is a churn event.
“In every one of these I have run, the customer was more forgiving than the founder expected and the internal damage was worse than they expected. People forgive an early correction. They do not forgive discovering at go-live that you knew in March.”
The system fix, this quarter
The triage handles one promise. The system stops the next eleven. Every element below exists to make the honest path faster than the workaround, because a gate that is slower than going around it will be gone around, no matter what the policy says. Sales teams are not adversaries here; they are responding to the incentives and the friction you built.
- A published capability sheet sales can commit from freely: current features, supported configurations, live integrations. Freedom inside the fence.
- A pre-proposal gate: anything off the sheet needs product sign-off before it reaches the prospect. One channel, same-day response, so the gate beats the workaround on speed.
- Compensation hygiene: holdbacks or clawbacks on deals carrying unapproved commitments.
- A monthly roadmap conversation between sales leadership and product, so sales stops guessing what is coming and inventing it instead.
What is actually happening, one level down
A single rogue promise is an incident. A pattern of them is a message, and the message is that sales cannot win with the current product story. When the honest pitch does not close, salespeople reach for the future tense, and no gate or clawback will hold against that pressure indefinitely. At that point the question stops being about process compliance and becomes a product question: is the story wrong, is the market wrong, or is the product genuinely behind?
Nobody with authority is usually choosing between those three, which is why the pattern persists. If promises are the only way deals close, the roadmap conversation is overdue by about two quarters, and our guide to telling a product problem from a sales problem is the right next read.
What good looks like in 90 days
Ninety days is enough to publish the sheet, run the gate long enough for sales to trust its speed, and close at least one deal through it rather than around it. The measurable signal is not zero exceptions, which would mean the fence is drawn too tight. It is that exceptions arrive before the proposal instead of after the signature.
| Before | After | |
|---|---|---|
| Where product finds out | The kickoff invitation | The pre-proposal channel, before the prospect hears anything |
| Turnaround on an exception | Weeks of escalation | Same day |
| Who carries the cost | Engineering, silently, next quarter | The deal, priced honestly at proposal time |
| What the customer hears | A date that moves | What exists today, and what is genuinely committed |
Third promise this quarter?
Thirty minutes, no pitch deck. You will leave knowing whether it is a process gap or a product story gap.
Book a Product Strategy SessionFrequently asked questions
Should we ever fire the salesperson?
For breaking a working system that they understood and had a fast path through, possibly. For navigating the absence of one, no: you would be firing the person who found the only available route to a signature. The distinction is whether a gate existed, whether it was quick, and whether they knew about it. If any of those three is missing, the failure is upstream of them.
Does the gate slow deals down?
The same-day response makes it faster than the current cycle, which is promise, discover, escalate, renegotiate, apologise. Sales teams that resist gates on principle usually accept them within a month once they experience the response time, because an answer in six hours is worth more to a deal than a guess that unravels in six weeks.
What if the promise is already in the signed contract?
Then it is a commercial obligation and the options narrow to build it, renegotiate it, or unwind the relevant clause, all of which are still better than silence. Price the build including what it displaces and take the decision to whoever owns both revenue and roadmap. Our piece on the enterprise customization trap covers how to price a one-account build honestly.
How do we stop this without making sales feel policed?
Give them more freedom inside the fence than they currently have outside it. Most capability sheets end up broader than what sales was informally comfortable committing to, because nobody had ever written down what the product genuinely does. The gate then applies to a much smaller surface, and it reads as support rather than supervision.
One promise is an incident to be triaged. A pattern of promises is a product decision nobody has made yet, and the sooner someone names which of the three causes is operating, the cheaper the correction is. If the underlying gap is that nobody owns that call, our guide to capacity versus direction is where to start.