“The Science of Scaling” – Mark Roberge

Scale at All Costs Is Not a Strategy

If you have spent any time around startups, you have heard the blueprint: scale at all costs. Grow as fast as you can, raise the next round, and sort out the details later. Revenue growth is the first slide of the board deck and the first question investors ask. After 25 years in the IT industry on both the vendor and customer side, I have watched plenty of companies chase that curve. Some made it. A lot of them did not. So when I saw that Mark Roberge had written a follow up to The Sales Acceleration Formula, I picked up The Science of Scaling: Using Data to Decide When, and How Fast, to Scale Revenue right away. Roberge was the founding CRO at HubSpot, is a Senior Lecturer at Harvard Business School, and is a Managing Partner at Stage 2 Capital. I joined their Catalyst program as a Limited Partner, and I continue to learn from him whenever I read, listen, or watch his content.

The Problem: A Premature Obsession With Revenue

Roberge opens with a claim that is hard to argue with. Startups fail at an unnecessarily high rate because they fixate on top line revenue growth before they have earned the right to scale. He is not saying to grow slower. He is saying to grow healthier. The pattern he describes will be familiar to anyone who has watched a Series A company. They hit what feels like product-market fit, raise money, hire a pile of salespeople, and hope the curve bends upward. Most of the time it does not. His diagnosis is that founders are scaling haphazardly rather than scientifically, and the book is built around two questions that most of us answer with gut feel: when should we scale, and how fast?

Step One: Define Product-Market Fit With Data

The first section is where the book won me over. Everyone uses the term product-market fit to justify big decisions, but few of us could write down a definition that is not a feeling. Roberge argues that long term customer retention is the best statistical proof, but retention is a lagging indicator. You do not have the luxury of waiting a year to find out. So he proposes a leading indicator in a simple format: P percent of customers achieve E event(s) within T time.

The examples make it concrete. Slack looked at customers sending a couple thousand team messages in the first 30 days. HubSpot looked at customers adopting five features out of twenty five within 60 days. What I like is that the event has to be objective, measurable, tied to customer value, and aligned with your unique value proposition. “The customer sees value” does not qualify. “The customer processed their first transaction” does. Coming from a technical background, I appreciated that this turns a fuzzy debate into something you can instrument and put on a dashboard.

Step Two: Prove the Go-to-Market Works

Product-market fit is only half of it. The second stage is go-to-market fit, which means you can acquire and retain customers consistently and scalably. Roberge anchors this to unit economics, using the familiar benchmarks of LTV to CAC above 3, payback under 12 months, and a magic number above 1.0. Just like retention, those are lagging numbers, so he translates them backward into near term activity goals your team can track weekly.

This section also reinforces something I wrote about in my review of The Sales Acceleration Formula: the right hire depends on the stage. In the early days he wants a blend of product manager and account executive. In the go-to-market fit stage he wants a process builder who can codify the playbook. Only once you reach scale do you bring in the more traditional process executor. Another idea that stuck with me is building the playbook from the buyer’s journey outward instead of starting with a deck about your product. As someone who manages Solutions Engineers, I could not agree more that the best conversations start with listening.

Step Three: Scale Is a Pace, Not an Event

This is the answer to the second question, and it is the part I expect to quote to people. Roberge’s point is that scale is a pace, not a single lump sum event. The classic mistake is hiring ten salespeople in January and having two left in December. The organization has not built the capacity to recruit, onboard, and coach that many people at once, and a flawed hiring formula gets multiplied by ten.

His alternative is to scale as fast as possible without losing product-market fit or go-to-market fit, and to use the two leading indicators as a speedometer. Hire two salespeople a month for six months and watch the gauges. If they hold, accelerate. If they break, stop and fix the problem. I can see this being a much better conversation to have with a board than “trust us, we will hire fast.” It gives leaders a predictable plan and a data driven reason to speed up or slow down.

Moats, Not Just Momentum

The final phase is called Growth and Moat, and it covers what happens when competitors notice your success. Roberge cautions against confusing a temporary advantage, like a feature the competition has not built yet, with a sustainable one. His test is a good thought experiment: imagine a team of talented engineers leaves a big tech company, raises a lot of money, copies your product, and sells it for half the price. Why do you still win? Network effects, category leadership, viral distribution, switching costs, and learning algorithms are the kinds of answers he points to. I would add that in the networking and observability world I work in, switching costs and data gravity are very real moats, and plenty of vendors lean on a feature that will not last a year.

Why This One Stuck With Me

What I appreciate most is that Roberge takes the same engineering mindset he brought to sales in his first book and applies it to the question every founder and revenue leader eventually faces. Define the inputs, measure the outputs, and iterate. The book is organized so that each phase explains how pricing, hiring profile, demand generation, compensation, and sales process should evolve as you earn the right to move forward. That makes it practical rather than theoretical.

If I have a caveat, it is that the framework is most naturally suited to B2B software companies with subscription revenue and a reasonably quick path to measuring customer success. If you sell very large, long cycle enterprise deals, you will have to adapt the cohort approach, and Roberge acknowledges as much with a customer health card alternative. Still, the underlying logic travels well.

If you are a founder, a CRO, or anyone who has been handed a growth target and a hiring plan without a clear way to pressure test either one, this book is worth your time. It will not slow you down. It will help you grow in a way that holds up after the first year.

Comments are closed.

Create a website or blog at WordPress.com

Up ↑