Six weeks into our largest deal of the year, the VP of Ops emailed a one-line ask: "Before we sign, can you confirm SSO with our identity provider and the reporting export will ship by Q2?" It read like a formality. It was not. Legal wanted that sentence turned into a contract exhibit, and our CTO wanted to know why I was making engineering promises in a sales email.
That tension, between what closes the deal and what your team can actually deliver, is the whole game once you start selling to enterprise buyers. Here's the framework I built after getting burned once and getting it right four times since.
Why "it's on the roadmap" isn't an answer
Enterprise buyers aren't being difficult when they ask for roadmap commitments. They're protecting themselves. Someone on their side is going to stand up in a budget review next year and defend the decision to buy from a smaller vendor instead of the incumbent, and "they said it was coming" is a weak thing to have on record if it doesn't ship. So they push for specificity, and if you're vague, they either walk or make their procurement team write the specificity into the contract for you, usually as a penalty clause tied to a date you never agreed to internally.
The mistake most founders make is answering this like a product question when it's actually a risk-allocation question. The prospect isn't asking "will you build this." They're asking "who eats the cost if you don't." Answer that question directly and the roadmap conversation gets a lot shorter.
The three-tier response
I now sort every roadmap ask into one of three buckets before I respond, and I say the bucket out loud to the prospect instead of hiding it.
Tier 1: already built or actively in development with a shipped date on our internal board
For this tier, I commit in writing, with a date, and I put it in the order form as a delivery milestone, not a marketing promise. If we slip, we owe a specific remedy, usually a credit, occasionally an extended trial. I only do this for things engineering has already scoped, because the exposure is real and I've been wrong about "two-week feature" estimates before.
Tier 2: directionally planned but not scoped
This is where most roadmap asks actually land, and where founders get into trouble by either promising too much or being so vague the prospect loses confidence. My script: "This is a direction we're actively investing in and I can show you the design thinking behind it, but I'm not going to put an unscoped date in a contract. I'd rather under-promise here than build a clause we both regret in six months. What I can commit to is a 30-day check-in after signing where you see actual progress, not a slide." That last sentence matters more than the framework. It gives the buyer a concrete, near-term accountability moment instead of a distant date, which is usually what they actually wanted.
Tier 3: not planned, and only came up because this one prospect asked
Say so. "That's not on our roadmap today. If it's a blocker for you, I want to know now rather than have it surface after signing." Founders avoid this sentence because it feels like losing the deal. In my experience it does the opposite: buyers who've been burned by vendors that say yes to everything trust you more the moment you say no to something specific.
Keep the commitment out of the wrong document
One habit that's saved me repeatedly: roadmap commitments go in an order form exhibit or a mutual action plan, never in a sales email thread and never as a verbal promise on a call. Email threads get forwarded to legal as "evidence of what was promised" months later, stripped of the tone and caveats that were obvious in the room. If a commitment is real enough to make, it's real enough to write into the document that actually governs the relationship, and if it isn't, that's a signal you shouldn't be making it yet.
I also stopped letting engineering leaders sit in on roadmap discussions with prospects unless a Tier 1 item is on the table. Not because I don't trust them, but because engineers answer "can we build this" (usually yes, eventually) when the buyer is really asking "will this exist by the date I need it," and those are different questions with different owners.
The math on why this is worth doing carefully
A missed roadmap commitment on a $60K enterprise contract doesn't just cost the renewal. It costs the reference call the next prospect asks for, and it costs your AE's credibility on the next deal with the same buyer's network, since enterprise procurement circles are smaller than they look. Compare that to the cost of a slightly slower sales cycle because you asked for a week to get an engineering estimate before responding. The slower cycle is cheaper every time, and prospects who are serious about buying will wait a week for an accurate answer. The ones who won't wait a week were probably going to be a difficult account anyway.
What I'd tell a founder hearing this ask for the first time
Don't answer a roadmap commitment request on the call it's asked. Say "let me get you a precise answer by Friday" and go find out, in writing, whether engineering will actually sign up for the date before you do. The prospect isn't evaluating your answer's speed, they're evaluating whether your commitments hold up, and the fastest way to prove they don't is to promise something on a call that quietly changes three weeks later in a follow-up email nobody remembers agreeing to.
The goal isn't to say yes more. It's to make every yes mean something specific enough that both sides can hold each other to it.
Frequently asked questions
How do I respond when an enterprise prospect asks for a roadmap commitment before signing?
Sort the request into three tiers: already-scoped work you can commit to in writing with a remedy if you slip, directional work you'll discuss openly but won't date in a contract, and anything not currently planned, which you should say plainly rather than imply.
Should roadmap commitments go in the contract?
Only Tier 1 commitments, already-scoped work with an internal ship date, belong in an order form exhibit with a defined remedy if missed. Anything less certain should stay a verbal or written direction, not a contractual obligation.
What happens if I overpromise a roadmap item to close a deal?
You risk more than the renewal. A missed commitment damages reference calls and your team's credibility with the buyer's broader network, which in enterprise procurement is smaller and more connected than it looks.
Is it okay to tell an enterprise prospect something isn't on the roadmap?
Yes, and it often builds more trust than a vague yes. Buyers who've dealt with vendors that agree to everything tend to trust a specific no more than an ambiguous maybe.