Solution-Centric MarketingMagnetic Messaging FrameworkTHE TRUTH

Should we sell features that are still on the roadmap?

Greg Rosner

By Greg Rosner

Founder of PitchKitchen · Author of StoryCraft for Disruptors

· 9 min read

TL;DR

When a company's present-tense story can't carry a deal, reps reach for the future tense and the roadmap becomes the close. It works every time, because a promise is free to make and impossible to disprove in the room. The cost lands somewhere the rep isn't standing: an onboarding that opens with a debt, a renewal conversation about a feature instead of a result, and a product roadmap authored by the objections nobody could answer. Banning roadmap talk gets you vaguer roadmap talk. The fix is upstream, in a present-tense story strong enough that nobody reaches past it.

The scene I'm in this week

Tuesday afternoon, mid-August. The CRO of a $21M Series B company, VC-backed, selling fraud and compliance software to credit unions. He sent me a call recording and one sentence. Why is a deal we won in March already wobbling?

I listened to the whole thing. Nineteen minutes in, the prospect asked about a specific reporting workflow. The rep, who's good, paused for about a second and said it was on the roadmap for Q4. The prospect said great. You can hear the temperature of the call change right there. Two weeks later it closed.

I asked the CRO whether it shipped. He said it was still being scoped. I asked whether it was on the roadmap back in March, when the rep said it was. He went quiet for a beat and said it was on a list.

There's a difference between a roadmap and a list, and everybody inside a company knows exactly what that difference is. The buyer has no way to know it.

Then he told me the part he'd actually called about. That customer's first quarterly business review had just happened, and the entire thirty minutes went to the reporting workflow. Nobody asked whether their compliance reviews had gotten faster, or about the exam they'd just passed clean. Thirty minutes on a feature that doesn't exist yet.

He said something I've now heard almost word for word from four different founders this year. We won that deal on the roadmap, and now we own it.

Naming what's actually broken

Here's what happened on that call, and some version of it happens in most B2B companies I sit with. The rep hit a moment where the present tense ran out. Everything true about the product today had already been said. The buyer wanted one more thing. The only currency left in the room was the future.

That's the Roadmap Loan. You borrow credibility from a version of your product that doesn't exist yet to close a deal that exists right now. The loan always clears the gap, because a promise costs nothing to make and can't be disproven in the moment.

The interest comes due later, and it comes due somewhere the rep isn't standing. Onboarding opens with a debt. The customer success manager inherits a relationship that starts with an obligation nobody wrote down. Product gets a requirement that arrived through a sales call instead of a strategy. And the renewal conversation twelve months out is about whether you shipped the thing, rather than whether the customer got what they came for.

This is just truth: reps don't take the loan because they're dishonest. They take it because the present tense didn't have enough in it. When the true story of what you do today is clear, specific, and aimed at a problem the buyer actually has, the future tense stays in the drawer. When that story is vague, the future is the only room left to move into.

That's Solution-Centric Marketing with a due date attached. A company that describes itself by capability gets compared by capability, and any capability gap can be papered over with a promise. Nobody promises their way out of a point of view, because a point of view can't be added to a backlog. If your team keeps drifting toward feature talk in the first place, that gravity has its own diagnosis in Why does our messaging keep sliding back to features after we fix it?.

Why this is worse now than ever

Building got cheap. That's the shift, and it cuts against the roadmap promise in a way most sales leaders haven't priced in yet.

When a feature took three quarters and a staffed team, a roadmap commitment meant something real. It was an allocation of a scarce resource, and the buyer knew it. The promise carried weight because the cost sitting behind it was visible from the outside.

Now a competent team ships a version of most things in weeks. The market has already repriced that. Margin of Safety reported in February 2026 that roughly $300 billion in market value came out of SaaS valuations following the frontier agentic tool releases, which is the market saying out loud that a feature list is no longer an asset anybody pays a premium for.

The promise now depreciates from both ends. It's worth less to the buyer, who half suspects the thing is easy to build now. It's worth less to you, because on the day you finally ship it, it doesn't differentiate you either. You paid for a deal with an asset that lost value between the signature and the release.

There's a second turn of the screw. Your buyer's research runs through a machine now, and the machine reads your present tense only. It retrieves what you published: your site, your docs, your comparison pages, whatever third parties wrote about you. It has no way to retrieve what your rep said in a room in March. The strongest asset in your sales motion is the one asset that appears nowhere the buying committee does its homework, and the other four people on that committee are getting a description of your company with no roadmap in it at all.

The diagnostic ... run this on your last five closed deals

Three tests. You can run all three this week without hiring anybody, and the first one takes about twenty minutes.

  1. 1The Tense Count. Pull the recordings of your last three closed-won calls and tally two things: claims about what the product does today, and claims about what it will do. Most leaders expect a lopsided count in favor of the present and find something closer to even, with the future tense bunched in the last ten minutes, right where the deal turned. Mark the exact minute the tense flips. That's the point where your story stopped carrying the weight and the roadmap picked it up.
  2. 2The Promise Trace. Take your last five closed deals and write down every commitment anybody made about something that didn't exist yet. Then fill in three columns: did it ship, did it ship by the date the rep named, and did that customer renew. Almost nobody runs this, which is why almost nobody knows the real conversion rate of a roadmap promise inside their own company. Run it once and you'll walk into your next forecast meeting with a different question.
  3. 3The Not-Building List. Ask three people on your team, separately, to name three things you have deliberately decided not to build and why. If they can't, you don't have a position. You have a backlog and a sales team improvising against it. A company that can say out loud what it refuses to build has made a real decision about who it's for, and on a live call that decision outperforms any single feature you could promise.

What I see across 100+ B2B companies

I've sat with more than a hundred B2B companies in the $5M-$75M range, and this one is consistent enough that I can usually call it before I hear the recordings.

The Roadmap Loan almost never shows up in a company with a weak product. It shows up in companies with strong products and thin stories. The product does something hard and valuable, nobody inside the building has ever put that into a sentence a buyer can repeat, and the sales conversation runs on comparison instead. Comparison ends at a gap. A gap ends at a promise.

The second pattern is the direction the promise runs. It's nearly always a match to something a competitor already has. Nobody takes a Roadmap Loan to fund a bet nobody else is making. They take it to close the distance on somebody else's checklist, which tells you the deal was being run inside a frame the company didn't write. That's the same machinery I unpacked in Who writes the criteria B2B buyers evaluate you on?

The third pattern sits upstream of both. In these companies, the product roadmap is largely set by whatever sales needed last quarter. Founders describe that to me as being responsive to the market. What it actually is: a product strategy authored by the objections nobody could answer.

Are founders overbuilding because AI made building too easy?

... founder posting on r/SaaS, May 2026

That question ran on r/SaaS in May and the thread underneath it was a few hundred people recognizing themselves. For most of the companies I work with, the honest answer runs a little differently. Building didn't get easy enough to explain it. Promising got easy, and somebody downstream has to go make the promises true. If you're currently trying to work out whether your stall is the product or the message, Is our slow growth a messaging problem or a product problem? splits that question properly.

A real example

A $47M PE-backed company, work order and inspection software for commercial property management firms. They came to me with what they were sure was a churn problem. Net revenue retention had slid from 112 to 94 over five quarters and every post-mortem landed on onboarding.

We ran the Promise Trace across eighteen months of closed deals. Thirty-one of forty-three closed-won deals carried at least one roadmap commitment. Nineteen of those commitments shipped. Six shipped inside the quarter the rep had named. And the deals that carried a promise renewed at less than half the rate of the deals that didn't, even though they were larger on average at signature.

That last number is what got the room quiet. Their biggest deals were their sickest deals. They were bigger because they'd been bought with more future.

We left the sales team alone. The promise was a symptom, so we did the messaging work first. The company had spent four years describing itself as a platform for property operations, which is true and says nothing. What was actually true, and what their best customers said out loud the moment we interviewed them, was much narrower. They were the only vendor in the category built for operators whose work happens inside tenant spaces they can't schedule around, where the person who lets the tech in isn't the person paying the invoice and never has been. Unglamorous, specific, real. It came out of the founder's mouth in the first hour of discovery and had never appeared in a single piece of their marketing.

Six months after we documented that in a Magnetic Messaging Framework and rebuilt the sales narrative on top of it, the Tense Count on their calls had moved from roughly even to about four to one in favor of the present. Roadmap commitments in closed deals went from thirty-one across eighteen months to four. Average deal size came down about nine percent. Net revenue retention came back to 108.

Smaller deals, healthier company, and a CRO who stopped dreading the QBR calendar.

What this means for you

If your reps are selling the future, this isn't a discipline problem and a policy won't fix it. Ban roadmap talk and you'll get vaguer roadmap talk, delivered with more eye contact. The future tense is filling a hole. The only durable fix is making the present tense strong enough that nobody reaches past it.

That work happens upstream of the sales conversation. The tool for it is the Magnetic Messaging Framework (MMF), the strategic narrative system built around four anchors: category design, villain framing, an old-way / new-way contrast, and a promised-land outcome. Two of those four carry most of the weight on this particular problem.

Villain framing settles what you're against, and that's what makes a Not-Building List possible in the first place. You can only refuse to build something with any confidence once you know what you believe goes wrong in your customer's world. Category design settles what you're comparable to, and that's what keeps the deal from running on somebody else's feature grid, where every conversation eventually arrives at a gap.

Why it matters practically: one of your reps is going to hit that moment in a call next week. Nineteen minutes in, a buyer asks for one more thing. That rep either has a sentence that's true today and lands harder than the missing feature, or reaches for Q4. That sentence exists in writing somewhere in your company or it doesn't, and no amount of coaching conjures it up in the moment.

This is the work I do. I build Magnetic Messaging Frameworks for founder-led B2B companies in the $5M-$75M range, where sales are stalling because the message isn't doing its job. I'm Greg Rosner, I wrote Story Craft for Disruptors, and most of my week is spent helping CEOs find the truest thing about their company and get it written down clearly enough that everyone repeats it the same way, including the AI now briefing their buyers.

Three things worth doing this week:

  1. 1Run the Tense Count on your last three closed-won recordings. Twenty minutes. Mark the minute the future tense starts, because that's the exact spot where your story ran out of room.
  2. 2Build the Not-Building List with your leadership team. Three items, a reason attached to each, in your sales enablement before the quarter turns. It's the fastest item on this page and it changes how a rep handles a gap on Monday.
  3. 3Pull the renewal rate on deals that carried a roadmap commitment against deals that didn't. If there's a real gap, you're holding the number that turns the messaging conversation into a business conversation instead of a taste conversation.

Questions People Ask

FAQ

Should we sell features that are still on the roadmap?

Only when the commitment is real, dated, and something you'd put in writing. The trouble starts when a roadmap reference gets used to close a gap rather than to describe a plan. If the feature is what won the deal, you've sold a future release instead of your product, and the renewal conversation will be about that release rather than about the results the customer got.

Why do our sales reps keep promising features we haven't built?

Because the present-tense story runs out mid-call. Reps reach for the future when everything true about the product today has been said and the buyer still wants one more thing. It's rarely a discipline problem. It's a signal that nobody has written a sentence about what you do today that lands harder than the missing feature does.

How do we stop sales from driving our product roadmap?

Start by counting how much of it already came from there. Pull the last eighteen months of roadmap additions and mark which ones originated in a deal you were losing. Then decide what you're deliberately not building and why, and put that list in front of the sales team. A rep who can defend an omission stops needing a promise to fill it.

Do customers churn because of unmet roadmap promises?

Often, and it shows up as an onboarding problem in the post-mortems. A deal bought on a future release starts the relationship with a debt, so the first business review is about the feature rather than the outcome. Run your last five closed deals against renewal data, split by whether a roadmap commitment was attached, and the pattern usually shows itself in one afternoon.

What should a rep say when a prospect asks for a feature we don't have?

Say you don't have it, then say what you'd do instead and why you made that choice. A deliberate omission with a reason behind it reads as conviction and moves a buyer. An apology reads as a gap. That answer only exists if the company has decided what it stands for, which is a messaging decision made long before the call started.

Related reading

More from PitchKitchen

Magnetic Messaging Framework

Why does our messaging keep sliding back to features after we fix it?

This week a $19M Series B founder pulled up the homepage we clarified eight months ago, and it had quietly turned back into a feature list. Nobody rewrote the core copy on purpose. It crept. A capability line here, a new integration there, and the outcome story that used to open the page is now buried under a spec sheet. He thought the message went stale. Here's the harder truth: the message didn't decay, it fell. There's a gravity to it, and if you don't build something to hold it up, it drops back to describing what you built instead of what changes for the buyer. Here's why the fix never sticks, why AI makes the fall faster, and three tests to catch it before your win rate does.

Read post →

Solution-Centric Marketing

Who writes the criteria B2B buyers evaluate you on?

A medical device software CEO forwarded me a forty-row vendor evaluation matrix and asked how he was losing on it. Eleven of the rows were near-verbatim from a competitor's 2024 buyer's guide. He'd been arguing with a document his competitor wrote, in a language his competitor chose, for two years.

Read post →

Magnetic Messaging Framework

Is our slow growth a messaging problem or a product problem?

When growth stalls, a founder's instinct is to doubt the product and build more, because building feels like progress. It's almost always the message. Here's why the Product Panic keeps a $5M-$75M B2B company stuck, a three-test diagnostic to tell a message problem from a product problem, and the fix that stops you spending two quarters of engineering on the one thing that wasn't broken.

Read post →

Want this kind of thinking shipping for you?

Reps reach for the future tense when the present tense isn't strong enough to carry the deal. A policy won't fix that, because the hole it's filling was dug upstream.

That's the 90-Day Magnetic Messaging Sprint. One quarter, one fixed price: we extract your story, build the Magnetic Messaging Framework and your AI Brand Twin, then ship the website and sales enablement that run on it. $25K–$45K fixed for the quarter, and you own all of it at the end.

About the Author

Greg Rosner

Greg Rosner

Founder, PitchKitchen · Author of StoryCraft for Disruptors · Creator of the Magnetic Messaging Framework™

Greg is a B2B messaging therapist for growth-stage CEOs ($5M-$75M). He helps founders extract the truth they've been hiding from themselves, name the villain in their industry, and build the messaging infrastructure that scales their voice through AI. PitchKitchen has worked with 100+ B2B companies across SaaS, healthtech, fintech, cybersecurity, and AI-driven solutions.