FounderWiseDecisions, not feeds
← All articles FounderWise · Long-form

The roadmap promise you made in a meeting

You said it would probably be ready by Q3. They wrote it down as a commitment, told their own stakeholders, and you have now sold something twice: to them, and to everyone who did not get one.

12 Nov 2026 12 min read By Joshua Pi’Rwot
Share X LinkedIn

In a renewal conversation you said the reporting module should be ready around the third quarter. It was a genuine estimate, hedged twice, and you meant it as an indication.

It is now in their internal plan with your company’s name against it. You gave away a commitment you did not price, to one customer, in a sentence you have already forgotten.

Why these three models

The decision is whether to commit to a roadmap item for a customer, and what to say when you will not. The features that fire are a standing that a missed date draws down, a flexibility you surrender the moment you name a quarter, and a set of other customers who will learn that commitments are available if you ask.

Three lenses. Reputation decay produces a cycle answer about what a miss actually costs. Option value produces a random answer about what you handed over. Reciprocity produces an equilibrium answer about the customers who did not get one. The second is the part nobody prices, and the third is the part that arrives six months later looking unrelated.

1. What a missed date actually draws down

Start with the cost, because it is not the feature and it is not the customer’s disappointment.

Standing with a customer is a flow rather than a balance. It is topped up by what they observe you delivering, drawn down by what you fail to deliver, and it decays on its own when neither happens.1 A missed roadmap date is a draw, and its size depends on what has been paid in recently rather than on the whole history of the relationship.

Which explains a pattern that otherwise looks arbitrary. The same slipped quarter is absorbed easily by one customer and becomes a renewal problem with another of similar size, and the difference is usually not the feature. It is whether anything else landed for them in the preceding months.

The second-order effect is the one that compounds. A customer who has been given a date and not received it discounts the next date, which means your future estimates carry less information for them even when they are accurate. You have not only spent standing, you have degraded the instrument you use to manage expectations.

A missed date does not just cost you the date. It costs you the value of every date you give them afterwards.

There is a distinction inside the miss that decides most of its cost. A slip you announce in January, unprompted, with a revised date, is one kind of draw. The same slip discovered by the customer in July because the thing is not there is a different event. It tells them nobody on your side was tracking their plan, which is a claim about your operation rather than about the feature. Announce slips at the moment you know, and a broken promise becomes evidence that you monitor your commitments.

Watch for the customer who does the opposite of complaining. A distributor in Nairobi who built their stock reporting around your module and did not get it often does not escalate. They rebuild it in a spreadsheet, stop asking, and go quiet, and the quiet reads as acceptance until the renewal is declined by email with no reason attached. Silence after a missed date is the more dangerous response, because it removes your chance to pay anything back in. Call the accounts that stopped asking.

The practical consequence is that the recovery has to be an observable delivery rather than an explanation. When a date slips, the top-up is shipping something they can see, on the revised date, without fail. One kept revised commitment restores more than three careful updates about why the first one moved.

2. You handed over an option and charged nothing

The second lens prices what the sentence actually transferred, which is more than an expectation.

Before you named a quarter, you had the freedom to sequence your roadmap against whatever you learned in the next six months: a larger customer’s need, a technical discovery, a market change. That flexibility is worth more the more uncertain the next six months are, which for an early company is a great deal.2

Naming a date converts that flexibility into a fixed obligation. You now carry the cost of every alternative you can no longer take, and the customer holds something valuable which they paid nothing for and which was not part of the negotiated price.

That is the reframe: a roadmap commitment is a term with a value, and it should be traded rather than volunteered. The instruments are ordinary and are available if raised at the time. A commitment in exchange for a longer contract. A commitment in exchange for a reference or a design partnership. A commitment attached to a price. Or the version that costs you least and is usually accepted: a commitment to a review date rather than to a delivery date, meaning we will tell you in February whether this is in the first half.

The reason the hedging in your original sentence bought you nothing is worth stating. A costless message conveys information only where both parties’ interests point the same way, and here they do not: the customer needs a date to plan with, so they record the usable version and discard the qualifiers.4 You said probably and they heard Q3, and neither of you was being careless.

The general form is to keep the sentence and change what it commits to. Founders say a quarter because they want to give something in the moment, and the useful discovery is that a dated decision satisfies most customers nearly as well as a dated delivery, because what they actually need is to be able to plan.

The decision date has one failure mode, and it is fatal when it happens. It works because it is a promise you keep, so February has to produce an actual answer, including the answer that this will not be built. Defer at that meeting and you have taught the customer that your decision dates behave exactly like your delivery dates, and you have spent the instrument that was going to replace them. Put the February conversation in your own calendar on the day you offer it.

The cheapest version of all of this costs one paragraph. After any call where a timeline came up, write back what you said and what it commits to: we discussed reporting, it is on the roadmap, it is not scheduled, and I will confirm in February. That email is what their internal plan gets built from, and it arrives before the version they wrote down has hardened. It is also the only record that survives when their contact moves on.

And when you have no intention of building it, say so. A clear no is expensive to say and therefore respected, and it costs far less than a vague yes that is discovered to be a no in month five.

3. The customers who did not get one

The third lens is about everyone outside the room, and it is the part that never gets connected back to the original meeting.

Commitments become known. Customers in the same sector talk, your team references the commitment in other calls, and the roadmap item eventually appears in a release note attributed to a request. And people respond to perceived unfairness rather than to absolute treatment, at a cost to themselves, which is why the reaction is stronger than the thing warrants.3

The specific consequence is a rule you have created without stating it. If commitments are available to customers who push, then pushing is the way to get one, and over two renewal cycles your roadmap is allocated by willingness to escalate rather than by what serves the product. Nobody decides that and everyone can see it afterwards.

The repair is the same as for any allocation that has drifted into discretion. Have a stated basis: what earns a dated commitment, whether it is contract length, design partnership, or being the third customer to request the same thing. Publish the basis rather than the commitments. That gives every conversation the same reference and it means a no is about the rule rather than about the customer’s importance.

If you are reading this with three loose commitments already outstanding, the repair is a pass through the accounts rather than a policy that starts today. List what has been said to whom, by anyone on your side, and split it in two. The ones you intend to honour get a written date and enter the plan as scheduled work. The ones you do not get a call before their planning cycle rather than after it, with a clear no and something you can actually offer instead. That costs an uncomfortable week. Leaving it costs renewals that fail for reasons nobody writes down.

It also protects you in the case where you want to make an exception, because an exception against a stated basis is a decision you can explain, while an exception against no basis is simply what happened to the person who asked hardest.

What the three say together

  • Commit to a decision date rather than a delivery date. It satisfies the planning need and costs you almost nothing.
  • If you do commit to delivery, trade it: contract length, design partnership, price, or a reference.
  • Write down what earns a commitment, and share the basis rather than the commitments.
  • When a date slips, the repair is a kept revised date, not a good explanation.

Where they disagree

The option argument and the reputation argument disagree about how much to say in the room.

The option view says give nothing without a trade, because every unpriced commitment is flexibility surrendered for free and the accumulation of them is what turns a roadmap into a queue of obligations to individual accounts.

The reputation view says that a founder who refuses to indicate anything is difficult to plan around, that customers reasonably need some sense of direction, and that excessive caution reads as evasion, which itself draws down standing. Saying nothing has a cost too.

The reconciliation is in the precision rather than the generosity. Be very specific about what you are committing to and very willing to share direction. This is on our roadmap, we have not scheduled it, and I will tell you in February whether it makes the first half gives them almost everything they need for planning and commits you to a conversation rather than a build. What fails is the middle: an unqualified quarter offered warmly in a meeting, which is heard as a delivery date and was intended as a direction.

What none of them contain

None of the three prices what the commitment does to your team. An engineering group that learns dates are set in sales conversations stops treating the roadmap as a plan, and the cost shows up as estimates that quietly include a defensive margin.

None of them handles the commitment that is right to make. Some customers are worth reorganising a roadmap around, and a founder who applies this article rigidly will decline a trade that was clearly worth taking. The point is to price the term, not to refuse it.

And one property the ensemble will not produce: the person you said it to may not be there in Q3. Contacts move, and a commitment made to an individual who has left is remembered by your team and by nobody at the customer, which is a reason to put anything that matters in writing to the account rather than to the person.

The one action that survives the ignorance: in your next customer conversation, replace the quarter with a decision date. We will tell you by the end of February whether this is in the first half. It gives them what they need to plan, it costs you nothing you have not already spent, and it is a promise you can keep.

Who has to move

The founder, and in the meeting rather than afterwards, because the sentence is the whole event and there is no correcting it later without a conversation nobody wants to have. The instinct under a renewal or a hard question is to give something, and a quarter is the cheapest-feeling thing available in the moment and the most expensive afterwards. The cheapest first test is a phrase prepared in advance and used every time, because these commitments are never made deliberately, they are made when a founder is asked a direct question and does not want to disappoint the person in front of them.

Sources and notes

  1. Martin W. Cripps, George J. Mailath and Larry Samuelson, Imperfect Monitoring and Impermanent Reputations, Econometrica 72(2), 2004, pages 407 to 432, developed at book length in George J. Mailath and Larry Samuelson, Repeated Games and Reputations: Long-Run Relationships, Oxford University Press, 2006. Under imperfect monitoring a reputation is temporary rather than permanent and must be replenished by observed conduct. Used in section 1 for treating a missed date as a draw against a recent balance rather than against the whole relationship.
  2. Sanjit S. Dhami, The Foundations of Behavioral Economic Analysis, Oxford University Press, and the options literature it references. The value of retaining flexibility rises with the uncertainty of the period it covers, which is why an early-stage company gives away more than it realises when it fixes a sequence six months out. Used in section 2. No option value is computed; the argument requires only that the value be positive and uncompensated.
  3. Jeffrey Carpenter and Andrea Robbett, Game Theory and Behavior, MIT Press. Inequity aversion and reciprocity, including the finding that people respond to allocations they judge unfair even at a cost to themselves, are developed in the chapters on social preferences. Used in section 3 for the reaction of customers who learn that commitments were available and not offered to them.
  4. Jeffrey Carpenter and Andrea Robbett, Game Theory and Behavior, MIT Press. Cheap talk, and the result that a costless message conveys information only where interests are sufficiently aligned, explains why a hedged verbal indication is heard as a commitment anyway: the customer cannot distinguish an estimate from a promise, so they record the version that is useful to them. Cited for the framing of the opening and for the recommendation in section 2 that a clear refusal is costly and therefore respected.

A note on a number this article does not give. There is no rule for how far ahead a roadmap can be committed. It depends on how much of your engineering capacity is already promised and how volatile your market is. What transfers is the substitution: a decision date is nearly as useful to the customer and vastly cheaper to you.

Joshua Agonya Pi’Rwot, Founder.

Lock in your calls.

You’ve marked 0 of 5. Now choose how often you want the signals.

Step 1 · Pick your cadence

The DispatchWeekly · your Monday 5 callsFreealways

Step 2 · Where to send it

Personalize your BriefThe Brief

Tune every edition to the markets and industries you actually act on.

🔒 Unlock personalization — The Brief, $19.99/mo →
Free Dispatch forever · upgrade anytime · we never share your details.
Know where you stand?
The Dispatch tells you what changed. Knowing what to do about it is a different question, and it is the one FounderWise answers. Start with the free Traction Audit: 12 questions, about 3 minutes, scored out of 100.
Find out where you stand →

For teams, syndicates & programs

Recommended
Team
$15/seat · mo
Daily Brief for the whole team (min 3 seats).
  • Everyone on the same signal
  • Admin + shared watch-list
  • One invoice · ~25% off solo
Get Team →
Cohort License
$1,500/cohort
One cohort of up to 30 founders, for accelerators, funds & programs.
  • MVP Studio and GTM Studio for every founder
  • Your logo, your cohort
  • A funder report on what each founder did
Talk to us →
Pass the Dispatch on
Know a founder making these calls blind? Send them this week’s five — free, every Monday.

Decisions, not feeds. · Curated by Joshua Pi’Rwot · FounderWise · Free Audit · Store · parent of Business Growth Accelerator

Call committed. We’ll hold you to it.
Know where you stand →