AI Guides › Trend Watch

The Difference Between A Roadmap And A Promise

Name: JulieMango AI Agent Marketplace Plans
Brand: JulieMango

By Nigel Guy · 3 min read

A company publishes a roadmap, and you quietly start planning around it. The feature you need is listed for "later this year," so you hold off on a workaround, delay switching tools, or tell your team it's coming. It feels like prudent planning. In practice you've converted a statement of intent into a delivery date that nobody actually committed to — and when it slips, the cost lands on you, not on them.

The rule: a roadmap tells you what a company currently wants to build; a promise tells you what they've committed to deliver. Plan only around the second, and treat the first as useful weather, not a schedule.

The Commitment Ladder

Most public statements about future features sit somewhere on this ladder. Work out which rung you're actually looking at before you plan anything.

Rung	What it looks like	How much to plan around it
1. Aspiration	"We're exploring," "we believe the future is," a vision post or keynote slide	Nothing. Interesting context only.
2. Roadmap item	Listed on a public roadmap, often with a loose quarter or "coming soon"	Note it. Don't delay any decision for it.
3. Preview or beta	Available to some users, possibly behind a waitlist or flag	Test it if you can. Don't depend on it yet.
4. Dated, specific commitment	A named date, a named scope, ideally in writing to paying customers	Reasonable to plan around, with a fallback.
5. Contractual	In your agreement, service terms, or order form	Plan around it. This is the only rung with recourse.

The gap between rung 2 and rung 4 is where most planning mistakes happen. A roadmap item can look very specific — a name, a screenshot, a quarter — and still be a rung 2 statement.

The mechanism

Find the rung before you react. Ask: has this company said when, what exactly, and to whom? If any of those three is missing, you're below rung 4.
Read the hedging language literally. "Planned," "targeting," "aiming for," "subject to change" are not filler. They're the company telling you, accurately, that this isn't a commitment.
Price the cost of waiting. Write down what it costs you to wait for the feature versus building a workaround now. If waiting is cheap, wait. If waiting blocks real work, don't let a rung 2 item hold it hostage.
Set your own deadline. Decide the date after which you stop waiting and act regardless — and put it in your calendar, not your head.
Keep the fallback alive. Whatever you'd do if the feature never shipped, keep it viable until the feature is actually in your hands.

What to skip

Skip the ritual of refreshing a public roadmap page to see whether an item has moved columns. Column moves are low-information; the only signal that matters is the feature arriving in a form you can use. And skip announcing roadmap items to your team or clients as if they were dates — you'll end up owning a slip you had no control over.

Guardrails

Roadmaps are genuinely useful for understanding direction and priorities. This isn't an argument for ignoring them, only for not scheduling around them.
Items do get cut, delayed, or reshaped, sometimes for good reasons. A slip isn't necessarily bad faith — which is exactly why you shouldn't treat the roadmap as a promise in the first place.
If a feature genuinely matters to a purchase decision, ask for it in writing. What a sales conversation implies and what a contract says are different documents.
Anything you've been told about timing should be re-verified against the company's current official page — roadmaps change without much notice.

All 751 AI guides · JulieMango plans from £17/mo