What changes on the climb is the operating system, the systems and team and motion that run the firm. The strategy can hold. This is the field guide to rebuilding the machine at each altitude.
Scaling a services firm from $10M to $100M is an operating problem more than a strategy problem. The offer that won at $5M can keep winning; what breaks is the machine around it. The systems, the leadership structure, and the way you allocate capital and people all have to change as you climb, and the firms that stall are running a smaller firm's operating system at a bigger firm's revenue. Diagnose the altitude, rebuild the machine to match, and the climb continues.
Growth runs in altitudes, and each one is a different operating reality. The Five Camps name the bands: Base Camp under $3M, Camp 1 from $3M to $10M, Camp 2 from $10M to $30M, Camp 3 from $30M to $100M, and the Summit above $100M. What you prioritize, how you spend, and where you put your best people all shift from one camp to the next. The Altitude Model is the frame for matching your moves to the altitude you're actually at.
When revenue outgrows the systems running it, you get the Operating-System Gap: leaders all working hard, no single system coordinating them, and a founder pulled into every decision. It reads as stalled growth and leaking margin. The gap gets blamed on people or communication, and the operating system is the thing that surfaces where the real problems live, so you fix the cause and the growth resumes.
Three failures show up on the climb, usually in this order. Go-to-market caps first: the founder is still the sales engine, and the team can close but can't generate its own pipeline. Margin leaks next, as senior people do junior work and scope creeps under volume. And the leadership system strains last, when enough people are in the building that nothing self-organizes. Each one traces back to an operating system built for a lower altitude.
Revenue puts you in a band, and two signals tell you the camp you're really operating: how your go-to-market actually runs, and how good your operating system is. If growth still depends on the founder's relationships and the leadership team works hard without one system coordinating it, you're operating below your revenue. That read is the starting point, because the move that opens Camp 2 looks nothing like the move that opens Camp 3.
Some founders have climbed this exact hill before and can run the rebuild. Most are seeing a given altitude for the first time. The honest question is whether you want an outside frame or someone who has built the machine and will build it again with your team. The operator versus consultant decision walks that call, and the strongest signal is a track record of doing the exact work and moving the number.
You change the operating system while the strategy can hold. The systems, team, and go-to-market motion that carry a firm through one revenue band become the ceiling at the next. Scaling means rebuilding the machine at each altitude, so the firm stops depending on the founder.
Growth stalls when the firm outgrows its operating system. The founder is still the sales engine, referral flow flattens, the team can close but can't generate pipeline, and delivery margin leaks under volume. The revenue got bigger while the systems stayed the same size.
The middle, roughly $10M to $50M, is the hardest. Founder-led sales, informal delivery, and founder-centric decisions all hit their limit at once, and rebuilding the machine mid-climb costs momentum, cash, and culture. That danger zone is nicknamed the Icefall.
The model shows you where your firm stands. The conversation shows you the next move.