Five Phases: Incubate to Embed

Welcome back to Built to Scale. We've covered growth versus scale, the Menu of Services, and the ratio collapse. Today we put those pieces on a ladder — the Scale Framework's five phases.

Every service, every internal process, every customer-facing capability your team runs sits somewhere on this ladder, whether anyone's ever labeled it or not. Here are the five rungs.

Incubate. This is where you identify and develop an initial solution for a small set of customers — custom, non-repeatable, and deliberately not yet part of your Menu of Services. Somebody on your team solves a specific problem for a specific customer in a specific way, and that's fine — that's exactly what Incubate is for. The mistake happens later, not here. The KPI at this stage is not ROI — the book is explicit that ROI is the wrong measure this early, because you don't have the volume to make it meaningful yet. Instead, track Customer Impact Score, Time to Solution, and Revenue Influence per Customer.

Validate. Now you take that custom solution and test it across a broader, but still selective, audience. It enters your Menu of Services as a Pilot, with limited availability. You're checking whether the pattern actually holds outside the one customer who inspired it. KPIs shift to Customer Adoption Rate, Service Efficiency Ratio, and now — finally — ROI benchmarking, because you have enough repetition for the number to mean something.

Expand. The service gets standardized and executed consistently across multiple teams, not just the original one that built it. This is where inconsistency gets expensive if you skip it — two teams delivering "the same" service in two different ways is worse than one team delivering it slowly, because now customers get a different experience depending on who they happen to reach. KPIs here: Market Penetration Rate, Customer Retention, Operational Cost per Execution, and revenue uplift.

Amplify. Wider teams, external teams, or technology take over large-scale execution, specifically to reduce cost and increase efficiency. This is where automation usually enters in a serious way — not as a pilot, as the primary execution path. KPIs: Service Volume Growth Rate, Execution Time per Resource, Cost-to-Serve, Automation Ratio, and win rate.

Embed. The service becomes a fully integrated, productized part of the system — full automation, genuine self-service, no human required unless the customer wants one. KPIs: Self-Service Adoption Rate, Support Ticket Escalation Rate — where low is good, meaning the automation is actually working — Net Promoter Score, and ROI measured as incremental revenue against the cost of the self-service platform itself.

Two things about this ladder that people get wrong on first read. First: it's not mandatory that every service climbs to the top. Some solutions are genuinely not feasible to standardize or automate further, and stopping at Expand, or even staying at Incubate forever for something truly bespoke, is a legitimate outcome — not a failure to reach Embed. Second: the framework is linear in its overall progression, but it allows iteration within each phase. You don't have to nail Validate perfectly on the first attempt before moving forward — you can cycle within a phase until the pattern is solid, then advance.

The practical exercise for this episode: take five services your team runs today — pick real ones, not hypotheticals — and place each one on this ladder honestly. Most leaders doing this for the first time find their portfolio badly skewed toward Incubate. Lots of custom, one-off fixes, very little that's actually been standardized, let alone automated. That skew is exactly why hiring keeps feeling like the only lever — nothing's been designed to reduce the need for it.

Next episode, the last in this run: building a strategic Scale Team, and the org design question every growing company eventually has to answer — who actually owns moving a service up this ladder. The Scale Imperative is out now from Routledge. See you next time.