Scale or Specialize Business:The Year Two Fork in the Road
Scale or specialize business is the fork every partner network meets in year two. Compare widening against deepening and use five filters before you commit.
Nobody sends a calendar invite for the biggest strategic call your business will ever face. It simply arrives. Somewhere near the end of Year 2 — the founding cohort converted to paid, a second cohort finding its feet, recurring revenue finally behaving like recurring revenue — you lift your head from delivery and notice that the scale or specialize business question has arrived and the next move is no longer obvious.
The fork has two roads. One road widens the machine: more partners, more markets, more revenue streams, a third and possibly fourth cohort, a sales function, enterprise licensing, a bigger platform. The other road deepens it: the same partner base made more excellent, the methodology made sharper, the data made richer, revenue per partner climbing while the network stays the same size — and the founder's life getting calmer, not busier.
Each road has a serious thinker standing on it. Verne Harnish built the case for disciplined expansion in Scaling Up. Paul Jarvis built the case for deliberate restraint in Company of One. Neither is wrong, and both have done the homework — which is precisely what makes this crossroads uncomfortable.
What is wrong — reliably, repeatably wrong — is standing at the fork and refusing to pick. Because while you hesitate, momentum picks for you.
How to decide: scale or specialize business
Drift always selects the road that demands the least deliberate effort. A founder who loves selling slides into expansion without ever checking whether the systems can carry it. A founder worn down by two years of building slides into "consolidation" that is really just coasting. In both cases a direction got chosen — by inertia rather than evidence — and the founder will spend Year 3 living with a strategy nobody actually decided on.
You are in a better position than that. By now the four-week vacation test has either passed cleanly or exposed exactly which systems still depend on your hands. Either result is useful: it is real data about what you have built. Month 24 is the moment to put that data to work, hold the two roads up against each other honestly, and commit to an answer on the scale or specialize business decision.
Road One: Widen the Machine
Harnish — Density Compounds, If the Systems Hold
The Scaling Up argument runs like this: when your systems can carry the load and market demand justifies it, scale produces value that no amount of polishing can. Network effects strengthen as the network gets denser. The data moat deepens faster when more assessments flow in. The brand becomes harder to ignore as practitioners appear in more markets. And the valuation multiple expands, because scale is the clearest proof of repeatability a buyer can see.
In practice, widening looks specific. A third cohort launches on a compressed free runway — 3-6 months rather than the 12 the founding cohort received, because the proof now exists. New geographies open only where inbound, content-driven demand has already validated them. Enterprise licensing emerges as larger organizations ask to run the methodology internally. And the platform matures from a delivery tool toward a marketplace where practitioners and clients find each other without you brokering every introduction.
But the expansion case only stands when three preconditions are true at the same time. The quality machinery — certification, performance management, community infrastructure — must be able to absorb roughly 50% more practitioners without buckling. Demand must already be outrunning capacity: you are turning prospective partners and clients away, not hunting for them. And the founder must be genuinely out of delivery, because if the founder is still the bottleneck, every partner you add simply multiplies the bottleneck.
Harnish's expansion is governed expansion. The pace is never "sign partners as fast as you can" — it is "add partners as fast as your quality bar allows." In his research, the companies that scaled successfully held their standards through the climb. The ones that broke had outgrown their own systems.
Road Two: Deepen the Machine
Jarvis — First Ask Whether Bigger Even Serves You
Company of One is not an anti-growth book; it is an anti-default book. Business culture treats growth as self-evidently good, bigger as automatically better, and standing still as failure. Jarvis refuses every one of those assumptions and demands that growth earn its place before it gets pursued.
He has a structural point. Most service businesses optimize somewhere between 50 and 200 practitioners. Past that range, the complexity of running a larger network frequently eats the marginal revenue it brings in. Quality control strains. Community cohesion thins out. Governance has to formalize — and formality carries a price tag in both money and cultural flexibility.
The depth play is concrete too. Rather than recruiting 30 new partners in Year 3, you help your existing 40 partners each lift their revenue by 20%. Ecosystem revenue travels the same distance — without the onboarding spend, the quality exposure, or the management load of a bigger roster. And because the system stays simpler, the founder's quality of life rises instead of eroding.
Depth also feeds the moat. More assessment data accumulates in the verticals you already own instead of thin coverage spreading across new ones. The partners you have get superb training instead of more partners getting adequate training. The content library grows richer rather than merely broader. Everything that makes the ecosystem defensible — data depth, partner excellence, methodological precision — sharpens by going deeper, not wider.
Jarvis's forcing question: what is enough? Define it in writing. If 40 excellent partners on healthy recurring revenue already delivers the income, the freedom, and the impact you started this for, then expansion past that line is not ambition. It is reflex.
Five Filters Before You Commit to Scale or Specialize Business
Run the Choice Through Evidence, Not Mood
At Month 24, get your leadership team in a room — and your governance council, if you have one — and run the decision through five filters. They will not make the choice for you, but they will make it far clearer than gut feel ever could.
Filter 1: What did you build this for? This is the filter nobody applies first, and it should be. Some founders are building empires. Some are building lifestyles. Some are building an asset to sell. The scale or specialize business choice has no right answer until you answer this — and only the founder can.
Filter 2: Is demand outrunning capacity? If you are turning prospective partners and clients away, widening simply harvests demand that already exists. If you are still marketing hard just to fill the capacity you have, widening builds empty rooms — and empty capacity burns cash.
Filter 3: Is partner quality holding? Open the health dashboard. Green-status partners above 70%, with the bottom 20% under active management, suggests infrastructure that can carry more weight. A falling share of green partners means expansion will accelerate the fall.
Filter 4: Is the founder actually out of delivery? A passed four-week vacation test means the founder is free to work ON expansion instead of IN delivery. A failed test means the founder's hours belong to system-building right now — not to adding partners on top of a system that still needs them.
Filter 5: Can the balance sheet fund the bet? Widening spends money before it returns any. Reserves of 6+ months and recurring revenue clearing fixed costs with room to spare mean the foundation can take it. Tight cash means depth — protecting and strengthening what already exists — is the responsible road.
Both roads lead somewhere worth going, so the scale or specialize business decision is about fit, not right and wrong. Pick yours at Month 24 — deliberately, with the data in front of you — and then hold the line for 12 months before you reopen the question.