Sales promised it. Product never agreed. Now what?

A customer expects a feature next month. Sales says it was essential to winning the deal. Product says the feature was never approved. Engineering says nobody has explained what it actually needs to do. The founder is invited to an urgent meeting where each department brings evidence that another department exists.

Broken sales and product handoffs create a particularly unpleasant kind of work. The company must repair the external promise while investigating an internal disagreement. Start with the customer consequence, then fix the commitment process. Publicly deciding who is the villain rarely clarifies the delivery date.

Establish what was promised before discussing the solution

Collect the actual words from the proposal, contract, email or meeting notes. Separate a request, an expression of interest, a planned capability and a firm commitment. These may have become interchangeable during the internal retelling.

Ask what the customer needs to achieve, what they understood would happen and by when. A promised “integration” could mean a manual import, an automated transfer or a full operational connection with support responsibilities. Each interpretation implies different work.

In a hypothetical software company, a prospect wants monthly reporting from its finance system. Sales describes this as an integration, while product imagines a new platform capability. A conversation reveals that an approved file export would satisfy the immediate need. That does not excuse an inaccurate promise, but it creates an option the label concealed.

Repair the immediate situation with one accountable message

Assign a person to own the customer communication and bring the relevant departments into the decision. Do not send the customer three conflicting explanations from three people. They bought something from one company, even if your chat channels have developed separate foreign policies.

Explain what has been confirmed, what remains uncertain and when you will provide the next update. Avoid inventing a new deadline to relieve the discomfort of the conversation. Where contractual consequences matter, involve the appropriate commercial and legal specialists.

A useful phrase is: “We are confirming the scope and delivery options against your intended outcome. I will bring you an agreed proposal on Thursday. Until then, I cannot responsibly confirm that date.” The update needs to happen on Thursday, including when the answer remains difficult.

Decide whether this is product work or a bespoke service

A request can be commercially valuable without belonging in the standard product. Ask whether other customers share the need, whether it fits the direction and whether the company can maintain it. Include support, documentation and future changes, not only the first build.

A bespoke service should have its own scope, price and ownership where appropriate. Otherwise, the apparent win may quietly consume product capacity and leave the company supporting a special arrangement indefinitely. The sales result and the delivery economics belong in the same conversation.

Compare the requested build with a narrower solution, a partner route, a later release or a clear refusal. In the hypothetical reporting example, a supported export could bridge the immediate need while the team evaluates broader demand. A workaround needs an expiry or review point so it does not become permanent by forgetting to leave.

Make the opportunity cost visible

If the team brings one request forward, something else may move back. Name it. Do not let an urgent sale displace work invisibly, then criticise delivery for missing the earlier plan. The company needs to understand the change it has chosen.

HM Treasury's Green Book provides a general discipline of comparing costs, benefits and risks across options. Applied here, that means considering alternatives and displaced work rather than treating the new deal's revenue as the only relevant number.

Estimate effort with the people who will perform the work. Explain uncertainty and dependencies. A quick early estimate may help a commercial conversation, but it should be labelled provisional and revisited once the need is clear. A number becomes a commitment very easily once it appears in a slide.

Create a lightweight promise gate

You do not need a committee for every customer question. Define the types of commitment that require approval: new capabilities, delivery dates, special integrations, nonstandard support or significant changes to the product. Ordinary sales conversations should continue without waiting for permission to describe existing functionality.

For approval, use a short record: customer outcome, proposed promise, deadline, commercial value, delivery implications and decision owner. Keep it in an accessible place and record the decision. The person approving a date must understand the capacity and dependencies behind it.

A salesperson should have a useful alternative to saying yes prematurely: “That capability needs confirmation from our product team. I can arrange a short discussion to understand your workflow.” Provide a reasonable response time, or the process will invite workarounds during real sales pressure.

Separate information from authority

Sales has valuable access to buyer problems. Product needs that information. But relaying a request does not automatically make it a delivery commitment. Equally, product should not dismiss commercial information simply because it arrived with an uncomfortable deadline.

The Scrum Guide places accountability for product value and backlog management with the Product Owner. Companies using different methods still need an explicit decision owner. Define how commercial evidence informs priorities and who resolves disagreement.

The founder may retain final authority over a strategic exception. If so, document the exception and its consequences. A special decision can be sensible. An invisible special decision makes it impossible for other teams to plan honestly.

Review the incentives behind the argument

If sales is rewarded for signed deals while delivery absorbs all the exceptional work, each team may be responding rationally to its own targets. Bring customer fit, implementation effort and continuing support into commercial review. Work with the people responsible for compensation before changing incentives.

Product can also create problems by being slow, vague or dismissive. If sales receives no usable answers, it may fill the silence. Agree how the product team responds to commercial questions and make existing capabilities easy to understand.

A joint review of recently won and lost deals can help both teams see the pattern. Discuss customer outcomes, recurring requests, promises and actual delivery effort. Keep the purpose focused on improving decisions, rather than assembling a monthly courtroom with coffee.

Make the handover useful after the deal closes

The implementation team needs the customer's goal, stakeholders, agreed scope, constraints and definition of success. It also needs to know what was discussed but excluded. A contract link and “great opportunity” are rarely sufficient instructions.

Confirm understanding with the customer at the start of delivery. Record changes and keep sales informed when a commercial expectation needs attention. Review whether the handover reduced rework or merely added another document nobody used.

If your business keeps winning deals that create internal emergencies, I can help map the handoff, clarify commitment authority and connect product priorities to commercial reality. Tell me where promises become problems. My product and delivery experience spans employment, external collaborations and ventures of my own. For a wider leadership question, read when external product leadership fits.

Questions people ask

What should you do when sales promises an unapproved feature?

Confirm the exact promise and the customer’s intended outcome before choosing a solution. Assign one owner for communication, assess delivery options with the relevant team and explain when a reliable update will arrive. Avoid replacing the original unsupported promise with another guessed deadline. Address any contractual implications with the appropriate specialists, then review how the commitment was made.

How can sales and product teams align without slowing every deal?

Define which promises require approval and provide a short, accessible path to a decision. New capabilities, delivery dates and nonstandard support usually deserve explicit review. Give sales accurate information about existing functionality and a reasonable response time for exceptions. Capture customer needs as evidence, while keeping authority to commit capacity and priorities clear.

Should a product team build features for one large customer?

Sometimes, but compare commercial value with implementation, maintenance, support and displaced work. Decide whether the request belongs in the standard product or needs a separately scoped service. Explore a narrower solution or later delivery as alternatives. If leadership approves an exception, record its consequences and owner so other teams can plan around the actual decision.