Level 2 and Level 3 are two stages of organisational maturity in a scaling venture. At Level 2, delivery is repeatable but depends on the founders — they're still in the room for every key decision. At Level 3, the company scales without them: authority is explicit, delivery is systematic, partners can carry the product.
There is nothing wrong with Level 2. Many serious deep-tech ventures operate there, and at modest size it's a sustainable place to be. It can even scale for a while — founders absorb more by working harder, hiring more, holding more in their heads. It works, until the cost shows up: burnout, delivery that quietly degrades, a round that prices in the dependency. The real question isn't whether Level 2 is acceptable. It's whether you're choosing to stay, or trying to leave without redesigning what holding it together requires.
Most ventures attempt the crossing the same way: more process, more senior hires. Both are the right moves — and for a few weeks it feels like Level 3. Then pressure hits, and the system snaps back.
Not because the people are weak. Not because the process is wrong. Process and headcount are necessary — but not sufficient. Level 3 is redistribution of authority. That is what neither can replace. This page covers the mechanics: what the crossing requires, why most attempts fall back, and how to tell from the inside whether you're crossing or oscillating.
Not as a framework abstraction — as the behaviour you recognise in your own organisation under pressure. Answer for where you are, not where you aspire to be.
Level 2 is typical for deep-tech companies in the late go-to-market phase — often 25–50 FTEs, €2–4M ARR. The crossing is not about size. It is about design.
In the framework's own terms, this is the most important scaling step a venture takes — more decisive than the move from prototype to product. This contrast covers one dimension, Organisation; the Scaling System Maturity Framework also assesses Technology and Trust across the same four levels. The Technology dimension has the same failure mode, one layer down — architecture and positioning oscillating instead of crossing together →
Faced with scaling, founders make two rational moves: add process, and hire senior people to professionalize. Both are necessary. Both will fail without the same underlying structural redesign — because Level 3 is not about more process or more headcount. It is about redistribution of authority.
Both moves are necessary.
Neither is sufficient.
When a venture recognises it needs to scale, it typically makes two rational moves — and both are correct. It adds process: OKRs, governance cadences, structured planning cycles. And it brings in senior people: VPs, a COO, experienced managers hired to "professionalize" the company. These are not mistakes. The problem is what is still missing.
Neither move addresses the underlying structure. Without redesigning how authority is distributed, how interfaces between teams work, and how commitments are made and held — process becomes choreography and senior hires become expensive friction.
Then pressure hits: a delivery delay, a regulatory constraint, a key customer escalation, a funding milestone at risk. And the system collapses — not because of the people, but because the structural foundation wasn't changed.
Level 3 is not more process. It is not more people. It is redistribution of authority. That is what process alone cannot install, and what headcount cannot replace.
Process is necessary. Without explicit authority behind it, it collapses the first time it costs the founder control.
In the best case: oscillation. Formal authority and real authority alternate depending on who speaks last. In the worst case: active destabilisation — burn rate rises, friction multiplies, the most capable senior hires leave because they cannot do their job.
Explicit decision rights that hold under pressure. Clear interfaces between teams. Commitments as contracts, not intentions. This structural redesign must accompany process and people — not follow them. Process and senior hires are the vehicles. Structural redesign is the engine.
Nine questions identify which trap is active in your venture — and which of the three structural upgrades is the binding constraint.
Crossing from Level 2 to Level 3 requires making three things explicit that at Level 2 remain implicit, personality-dependent, or urgency-driven. Process and senior hires are necessary to carry these — but they cannot substitute for them. Each one alone is insufficient. The crossing requires all three.
Clear inputs, outputs, and quality thresholds between teams
What this means Every handoff between teams has a defined input specification, an expected output, and an agreed quality threshold — and these hold without constant mediation by the founders or senior leadership.
Without it: coordination cost stays inside the people, not the system. Scaling multiplies the coordination debt.
Explicit decision rights and escalation paths that hold under pressure
What this means Every significant decision category has a named owner with the authority to decide — not just the responsibility to recommend. Escalation paths are defined and used only as the genuine exception, not the default.
Without it: authority stays personal. The system is only as fast as its most constrained decision-maker.
Deadlines and goals as contracts, not negotiable intentions
What this means Commitments made inside the organisation are treated as reliable contracts — not as intentions that can be renegotiated when priorities shift or pressure rises. The system, not the individual, makes commitments verifiable.
Without it: institutional buyers sense it before they can name it. Trust lives in people, not process. Scale requires the opposite.
If these three remain personality-dependent — if any of them still requires the founder to function — you are not at Level 3. Process is in place and senior people are in seat, but the system is oscillating between Level 2 and the appearance of Level 3.
A venture adds process — and the right process. It brings in senior people — the right people. For a few weeks it looks like Level 3. Then pressure hits, and the system snaps back to Level 2 behaviour. This is not transition. It is oscillation — and it compounds cost faster than the underlying technical or market challenge.
OKRs, governance cadences, formal roles, structured planning — plus senior managers hired to professionalize. All the right moves. For a few weeks it feels like Level 3. Founders feel ready to scale. The metrics improve. The system looks more mature.
A delivery delay. A customer escalation. A key hire departure. A funding milestone at risk. Any real pressure event that requires the system to perform under load — not just in calm periods.
Founders override formal decisions. Teams renegotiate commitments informally. Priorities shift mid-cycle. Escalations bypass structure. The process was real, but it wasn't load-bearing.
The crisis passes. The system settles back to Level 2. But each oscillation compounds the cost: trust erodes, team confidence in the process drops, and the next crossing attempt starts from a lower baseline.
"Structure that only works in calm periods is not structure. It is choreography. A venture that adds process but reverts to heroics under pressure is not in transition — it is oscillating, and oscillation compounds cost in trust, speed and valuation."The Scaling System Maturity Framework — CompoundWorks
If this pattern is active in your company, the Diagnostic Sprint goes inside — four weeks, full access — to define what the structural decisions need to be and how to make them stick.
Staying at Level 2 is a coherent state. Oscillating is not — it burns resources in all three dimensions simultaneously without making progress in any of them.
Every oscillation cycle degrades institutional trust — internally and externally. The team stops believing in the process. Customers notice the inconsistency between what is promised and what is delivered. Institutional buyers cannot build a procurement case on a system that reverts under pressure.
Each recovery cycle takes longer than the last. The heroics required to pull the system back become more elaborate. Senior people who should be focused on the next growth event are consumed by recurring crises that the structure should resolve but doesn't.
Investors who understand scaling systems recognise oscillation — even when they don't have the word for it. They see it in the patterns: recurring delivery issues, founder over-involvement in operations, commitment-to-delivery gaps. These cap the multiple investors are willing to pay.
Oscillation does not just waste cycles. It compounds cost — because each failed crossing attempt makes the next one harder. Trust in the process drops, so the next process introduction meets more resistance. Heroics become the culturally expected response to pressure, so structural authority is progressively harder to establish. The longer a venture oscillates, the more expensive the crossing becomes.
From the inside, both look similar in stable periods. The difference is visible only under real load — and in the direction of the trend over time.
Nine questions return your maturity level across Technology, Organisation and Trust — and flag any oscillation pattern. The Diagnostic Sprint goes inside to name the binding constraint and define the system decisions required to cross it and hold.