"sales promises features engineering can't build what to do"

"When sales and engineering are in chronic conflict over commitments, the problem is never that either side is wrong — it's that you don't have a system that forces them to agree before commitments are made. The fix is a formal pre-sales technical review process, not another all-hands about communication and respect."

Sales Keeps Promising Features Engineering Says Are Impossible.

You’ve been in this meeting. Sales is frustrated because engineering won’t build what was promised to close a deal. Engineering is frustrated because they weren’t consulted before the promise was made. The deal is at risk. Both sides feel disrespected. And you, the CEO, are managing two adults who should be working together but are instead sending passive-aggressive Slack messages about timelines.

This dynamic has a name. I call it the commitment gap — the distance between what gets promised in a sales conversation and what engineering has capacity and context to actually deliver. And it will not get better with a meeting about communication. It will only get better when you build a process that closes the gap structurally.

Why This Keeps Happening

Sales reps close deals. That’s how they’re measured and what they’re rewarded for. When a prospect says “we’d sign if you could do X,” the incentive is to say yes and figure out X later. This isn’t bad faith — it’s rational behavior given how the role is designed.

Engineering teams plan and commit to things they believe they can actually deliver. When a commitment lands on their plate that they had no part in scoping, they feel disrespected and they’re often right to — they’re being handed an obligation without any of the context or negotiation that led to it.

Neither side is broken. The system is broken. Specifically: you don’t have a process that requires sales and engineering to agree on technical feasibility before a commitment is made to a customer.

The Fix: Pre-Sales Technical Review

This is not complicated, but it requires discipline to implement.

Any custom feature, integration, or technical commitment above a certain threshold — define this: maybe it’s anything that would take more than two weeks of engineering time — requires sign-off from a technical stakeholder before it goes into a contract or verbal commitment to a customer.

The process looks like this:

Sales identifies a prospect request that involves custom technical work.
Sales submits a request to a designated technical reviewer (this might be the CTO, a lead engineer, or a product manager with technical authority) with a description of what the customer wants and the approximate deal value.
Technical reviewer responds within 48 hours with one of three answers: yes (we can do this in the implied timeframe), yes-but (we can do this but it will take X longer or require Y tradeoff), or no (this is not feasible given current architecture/roadmap).
Sales uses that response to close or renegotiate the deal.

That’s it. No committee. No lengthy back-and-forth. A designated person with the authority to say yes or no, operating on a short timeline so sales doesn’t lose deal momentum.

What You Have to Do as the CEO

This process only works if you enforce two things simultaneously.

First: sales cannot make technical commitments without going through the review. This means consequences when they do — not a lecture, an actual consequence. The first time a rep skips the process and promises something, you catch it, you address it directly, and the rep understands that the deal will be restructured rather than handed to engineering as an unfunded mandate.

Second: engineering has to honor the commitments that go through the review. If they sign off on something, they own it. You can’t have a review process where engineering says yes and then doesn’t deliver — that defeats the entire purpose and destroys sales’s trust in the process.

The CEO is the only person who can enforce both sides of this. Neither the head of sales nor the CTO can do it alone because each has a natural interest in their own team’s position. This is leadership work, not management work.

The Harder Issue: Roadmap Ownership

The pre-sales review process handles the tactical problem. The strategic problem underneath it is usually about who owns the roadmap and how much of engineering’s capacity is allocated to customer commitments versus product investment.

At most companies dealing with this conflict, the answer is: we don’t have an explicit allocation. Engineering just does whatever is most urgent, and customer commitments and roadmap work compete for the same pool of capacity with no principled basis for prioritization.

Fix this: define what percentage of engineering capacity is allocated to customer commitments (including post-sales customization and implementation work). Make that number explicit and known to sales. When sales is asking for more customer-specific work than that capacity allows, the conversation becomes “which existing commitment do we deprioritize?” rather than “why can’t engineering work faster?”

That question is answerable. “Why can’t engineering work faster?” is not.

What to Say to Both Teams

To sales: “I understand you’re trying to close deals, and I want to help you do that. The pre-sales review process is not a gate to slow you down — it’s a tool to give you an honest answer you can work with before you’ve committed to a customer. Nothing is worse than closing a deal we can’t deliver.”

To engineering: “I understand you’re frustrated at being handed commitments you had no part in making. The review process fixes that — you will be consulted before commitments are made. In exchange, when you sign off on something, it’s on you to deliver.”

Both of these are true. Both sides will respect you more for saying them clearly.

If your sales and engineering teams are in chronic conflict over commitments, I’ve structured this exact process for companies at multiple growth stages. In a 15-minute call, I can help you figure out what the right review threshold is for your company, who should own the technical sign-off, and how to introduce this without it feeling like bureaucracy. Book a free 15-min call.