Deep-tech ventures rarely stall because nothing is improving. They stall because improvement is uneven. The SSMF makes that imbalance visible — and names the dimension that's holding everything back.
Read horizontally: how each dimension evolves. Read vertically: whether the venture is maturing coherently or whether one dimension lags. The lagging dimension is the binding constraint — naming it is the first act of diagnosis.
| L1 · Initial | L2 · Managed | L3 · Defined | L4 · Adaptive | |
|---|---|---|---|---|
| Technology | "We'll clean it up later."Prototype-centric. Ad-hoc development. Technical debt accumulates invisibly. Cadence slows under the weight of decisions made for speed. | "If we ship faster, we're scaling."Technical coupling. Reactive delivery. Architecture limits scale. Local acceleration hides systemic fragility. | Architectural runway. Designed for growth.Parallelism is safe. The system absorbs change without losing coherence and cadence. | Continuously optimised.Open interoperability. Scales without redesign. Other teams extend it autonomously. |
| Organisation | "Speed means we're aligned."Decisions through founders. Heroic coordination. No system behind the people. Alignment based on individuals doesn't scale. | "Process equals maturity."Formal process, implicit decisions. Delivery depends on heroism. Coordination cost moves from architecture into the org chart. | Delivery without heroism.Coordination at scale. Explicit decision systems. Escalation is the exception, not the default. | Adaptive governance.Scales without refounding. Leadership multiplies. The system onboards its own successors. |
| Trust | "It works because you know who to call."Personal trust. Fragile at distance. Breaks when key people leave. Trust debt accumulates invisibly. | Trust in people, not process.Strong internally, opaque externally. Institutional buyers can sense it but can't verify it. The trust runway hasn't been built. | Structural, evidence-based.Selling reliability, not potential. Assurance artifacts any procurement team can verify — independently of any relationship. | Trust as system property.Self-reinforcing. Survives change in people. The system maintains the trust record continuously. |
Each level is a qualitative shift in how the venture behaves under pressure — not an incremental improvement in process.
The self-deceptions at each level are the signal: the rationalisation founders reach for when the dimension is lagging but the pressure to keep moving is high.
"Architecture is not about structure; it determines whether future options expand or collapse."
Maturity here is measured as the system's ability to absorb change without losing coherence and cadence. The binding question at each level is whether the architecture is accumulating debt or building runway.
"We'll clean it up later" — but later compounds, and cadence slows under accumulated technical debt.
"If we ship faster, we're scaling" — but coupling grows faster than throughput, and local acceleration hides systemic fragility.
"We can fix it later by adding more integrations" — but integration amplifies whatever the architecture already is. Acceleration exposes constraints; it doesn't remove them.
"If technical architecture defines system boundaries, organisational architecture defines authority boundaries — and misaligned authority creates the same fragility as misaligned interfaces."
Deep-tech systems fail usually at the decision level, not just the technical level. The patterns of founder routing, heroic recovery and informal override are the organisational equivalent of technical coupling.
"Speed means we're aligned" — but alignment based on individuals doesn't scale.
"Process equals maturity" — but process without clear decision rights only increases latency. Coordination cost moves from architecture into the org chart.
"Everyone is responsible" — but when everyone owns it, no one does. Scaling is not only about what the system can do; it is about who is allowed to decide.
"Trust is the least visible and most decisive dimension — and it has two faces that mature and fail differently."
Treating the two faces as one is the most common reason this dimension is mismanaged. The transition from personal trust to systemic and structural trust is what separates fragile growth from scalable growth.
The system is not predictable enough to be trusted by default, so people compensate with heroics, escalations and checks. "It works because you know who to call." Once trust becomes scarce, scaling becomes political.
Credibility built deliberately ahead of need: the evidence, predictability and delivery discipline that let institutional buyers rely on you before a relationship exists. Without it you win the demo and lose the deployment.
The most important scaling step is not prototype to product. Many ventures look mature enough to scale — and then fall back into Level 2 behaviour the moment pressure hits.
Founders override decisions. Teams renegotiate commitments informally. Escalations bypass structure. Execution returns to heroics. This is not a failure of intent — it is a failure of structural design.
The L2→L3 crossing makes three things explicit that at L2 remain implicit, personality-dependent or urgency-driven:
Clear inputs, outputs and quality thresholds between teams — so coordination doesn't require constant mediation.
Explicit decision rights and escalation paths that hold under pressure — not just in calm periods.
Deadlines and goals as reliable contracts — not negotiable intentions that depend on who's watching.
A venture adds process but reverts to heroics under pressure. More planning cadence, more governance rituals, more formal roles — for a while it looks more mature. Then pressure hits and the system snaps back.
The signal: the same decisions keep re-escalating, the same people keep getting pulled in, the same commitments keep slipping. Not because the team is weak — because the structure isn't load-bearing.
"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."
Nine questions, roughly ten minutes. The questions enter through behaviours you actually recognise — not framework abstractions. Answer for where you are, not where you aspire to be. The output is your per-dimension profile and the binding constraint that determines the right first move.
Each question describes a situation your organisation faces. Select the answer that best describes what actually happens — not the ideal version. The result gives you a per-dimension maturity level, names the binding constraint, and flags any oscillation patterns.
The self-assessment converts recognition into a conversation. What follows is defined by what the diagnosis reveals — not a predefined package.
Nine questions return your maturity level across Technology, Organisation and Trust — and name the binding constraint and any oscillation pattern. The front door to the conversation.
Four weeks. A complete SSMF assessment across all three dimensions with the full depth of the reference. Names what breaks next, sequences the moves, and defines the system decisions the venture needs to make before the next scaling event locks in the wrong foundation.
Follows the diagnostic. A focused engagement on the specific constraint the diagnosis named — architecture, integration, organisation or trust. Fixed-fee, scoped to the sprint. The diagnostic defines what this is; the sprint crosses it.
Ongoing strategic counsel through the scaling transition, or embedded scaling leadership: helping run the L2→L3 crossing, not just advising it. One to two engagements at a time. Defined by what the diagnostic and domain sprint uncover, not by a predefined scope.
Posts and short essays as the practice develops — the same arguments worked out in public, before they're settled enough for this page.
Deep-tech doesn't scale through tools, methods, or talent alone. It scales through maturing systems. A system-level model for escaping the Scaling Trap — and the foundation everything on this page builds from.
Read on LinkedInFor a few weeks, OKRs and governance rituals feel like Level 3. Then pressure hits, founders override the formal process, and the system snaps back. Level 2 protects speed through informality. Level 3 protects scale through structure.
Read on LinkedInDelivery still happens, milestones are met — but only certain engineers can manage the technical debt, and escalations move faster than processes. It works because you know who to call. That's trust debt, and it's quietly compounding.
Read on LinkedInThe self-assessment is the front door. A diagnostic sprint is the first paid engagement — and the starting point for every long-term relationship.