The roadmap space nobody asks for: a platform stability case study

At a Glance

Problem: The business was chasing aggressive B2B customer growth on a platform that could not carry it. The total number of sessions we could book at one time was capped well below what the business needed. Every new district we signed made the ceiling more visible.

Why I acted: We went through three engineering leadership changes in three years. During those gaps I covered the engineering roadmap alongside product, which meant I was close enough to the platform to see what the growth conversations were missing. Nobody was consistently defending the platform itself.

Approach: I carved out protected roadmap space for stability and scalability work, then tied every one of those epics to company OKRs so the connection between invisible platform work and the business goal stayed visible to everyone.

Outcome: We roughly tripled the number of sessions we could book at a time. Retention held above 95%. And with a customer base that was not leaking, the business grew its B2B customers 7x over three years.

The constraint nobody was naming

Growth planning has a way of assuming the platform underneath it will just keep up. Ours would not have.

The clearest signal was booking capacity. The total number of tutoring sessions we could book at one time was severely limited, nowhere near what the business plans required. That is not a bug you file and forget. It is a hard ceiling on revenue, sitting quietly under every optimistic growth slide.

I was in a position to see it because I was covering more than product. Three engineering leadership changes in three years meant that during the gaps, the engineering roadmap landed on my desk too. That is not a situation you would design, but it gave me something valuable: a full view of both what the business wanted to sell and what the platform could actually deliver.

Those two pictures did not match. Someone had to say so.

The fight for roadmap space

Here is the uncomfortable part of platform work: nobody asks for it. Customers ask for features. Sales asks for features. Stakeholders ask for features. Nobody has ever asked for a more scalable session booking architecture, right up until the day they cannot book a session.

So the case for stability work is a case you have to make yourself, and keep making. My argument was simple: none of the features matter if the platform cannot carry the customers we are signing. Growth on an unstable platform is just churn with a delay.

That argument bought the space, but arguments fade between planning cycles. What held the space was structure. I dedicated a real portion of the roadmap to stability and scale, treated it as non-negotiable capacity rather than leftover capacity, and made sure it survived quarterly planning every time feature pressure came back. Which it always did.

The mechanism: OKRs as the connective tissue

The thing that kept invisible work fundable was making it visible in the language the business already used.

Every stability epic tied directly to a company OKR. Not loosely, not by vibe. When leadership looked at the roadmap, they did not see a mysterious block of engineering time labeled platform work. They saw epics with a stated line to the goals they had set themselves. The question “why is product focused on this instead of that” mostly stopped being asked, because the answer was written into the work.

The operating rhythm mattered too. I ran quarterly planning to set the commitments, then scrum inside the quarter to deliver them. The quarterly layer is where stability work gets defended. The sprint layer is where it quietly gets done.

What the numbers did

The capacity work paid off first and most concretely: we roughly tripled the number of sessions we could book at a time. The ceiling that had been sitting under the growth plan was gone.

Retention held above 95%. I want to be precise about the claim here, because retention is never one team’s number. Tutoring quality, service, and account teams carry retention every single day. What the platform work did was protect it. A district that funds a tutoring contract expects sessions to book and the product to hold up. Stability kept the platform from ever becoming the reason a customer left.

And that is the real mechanism behind the growth number. When retention holds above 95%, the business is not spending its energy replacing lost customers. It is compounding. Over three years the B2B customer base grew 7x, roughly doubling year after year, and it grew on a foundation that was not cracking underneath it.

The lesson

The work that growth stands on is usually work nobody asked for.

Features win the deal. The platform keeps the customer. A roadmap that only funds what people are asking for is quietly betting that the foundation will hold on its own, and foundations do not work that way.

The job of a product leader in that moment is not to choose between growth and stability. It is to show, in the language of the business goals, that one is what the other stands on. OKRs were how I made that visible. The protected roadmap space was how I made it real. The tripled capacity and the retention rate are what it looks like when the bet pays off.