Sales promised a customer a feature that doesn't exist yet. How do you handle it?

Question

Accepted Answer

Stay calm and solve the immediate problem, then fix the process so it stops recurring. Blowing up at Sales feels satisfying but burns the relationship and doesn't help the customer. There are really two problems here: **this deal** and **the broken process** that created it.

## Handling the immediate situation

- **Get the facts fast.** What exactly was promised, to whom, by when, and how firm is the commitment? "Promised" and "hinted at on a roadmap" are very different.
- **Assess feasibility honestly.** Can we deliver a real version in time? A reduced version? A manual or semi-manual stopgap that satisfies the customer while we build the real thing?
- **Bring options to the table** with Sales and the PM, not blame. "We can't build the full feature in two weeks, but here's a thin version that covers their actual use case" turns a crisis into a save.
- **Protect the customer relationship.** If something must change, it's far better to reset expectations early and honestly than to miss a hard commitment silently.
- **Never quietly sacrifice quality or the existing roadmap** without making the trade-off visible to leadership. If we say yes, something else slips, and that has to be a conscious decision.

## Fixing the process

- **Find the root cause without blame.** Usually Sales lacks visibility into what's buildable, or there's no fast channel to check.
- **Create a lightweight "can we promise this?" path** — a Slack channel or a quick check with the TL/PM before commitments are made.
- **Share a clear, current view of what exists vs. roadmap** so Sales sells reality.
- **Build the relationship** so Sales sees engineering as an ally that helps close deals, not a department that says no.

## Pitfalls to avoid

- **Public blame.** It poisons cross-functional trust and makes the next handoff worse.
- **A flat no** with no alternative. You may sink a real deal unnecessarily.
- **A heroic death march** that ships something fragile and burns the team out.

## Why it matters

How a Tech Lead handles this moment defines their reputation. Handle it with maturity and you become the person who turns Sales' mistakes into wins and earns trust across the company. Handle it with ego and you become the bottleneck everyone routes around.