Why deep tech support systems are structurally designed to sustain themselves — not the technologies they claim to serve
And How The Founders Are the Product
The Part Nobody Admits Out Loud
There is a conversation that happens in corridors, over coffee, between people who have spent real time inside deep tech programmes. Founders who have been through multiple cohorts. Programme managers who started with genuine intent. Funders who keep seeing the same pattern repeat.
The conversation goes something like this:
“The outcomes don’t match the effort. And everyone knows it. But the programme keeps running.”
It keeps running because the people inside it need it to keep running. Not necessarily out of cynicism. But because the structure they are operating within rewards continuation, not conversion. Activity, not outcome. Visibility, not industrial deployment.
This is not a local problem. It is not a problem that more funding solves, or that better management fixes, or that a new cohort of founders will finally overcome.
It is a structural problem. And it has a structural solution.
The Label Justified the Budget. The Budget Built the System. The System Protects the Budget.
When deep tech became the policy priority — and it became one quickly, as AI enthusiasm started colliding with the recognition that software alone does not build industrial capacity — money followed.
Public programmes were funded. Accelerators were launched. Incubators rebranded. Technology transfer offices expanded. A new category of support infrastructure materialised, staffed by people hired to deliver it, measured by metrics inherited from the programme generation before.
This is where the structural problem begins. Not in the people. In the sequence.
When you hire staff to run a programme, those staff need the programme to continue in order to have jobs. When you measure a programme by activity outputs — cohorts completed, founders supported, investor meetings facilitated — those staff will produce activity outputs. When the programme’s renewal depends on its reporting, and the reporting measures activity rather than outcome, the programme will become very good at generating reportable activity.
None of this requires bad intent. It requires only that people respond rationally to the incentive environment they are placed in. Which they do. Always.
What Gets Measured Is What Gets Built — And It Is Not the Technology
Here is the mechanism, stated precisely.
A programme is designed with a mandate — support deep tech ventures, accelerate commercialisation, build industrial capacity. That mandate is translated into KPIs. Those KPIs are inherited, almost universally, from one of two sources: the consumer startup ecosystem, or public grant reporting requirements. Neither was calibrated for deep tech development timescales.
So the KPIs look like this:
Follow-on funding secured.
Investor meetings held.
Cohort completions.
Spinout entities created.
Media mentions.
Pitch event participations.
Jobs created within mandate period.
These are not outcome indicators. They are activity proxies. They measure what is happening inside the programme. They do not measure whether what is happening inside the programme will produce industrial market outcomes at the timescales deep tech development requires.
But here is the critical part: they shape behaviour.
When a programme rewards follow-on funding secured, founders optimise for investor readiness — narrative development, pitch polish, network density — rather than for evidence depth and technical reproducibility. When a programme rewards cohort completions, programme managers fill cohorts — including with ventures that are programme-experienced rather than technically substantive. When a programme rewards spinout entity creation, TTOs create entities — regardless of whether those entities have the foundation to survive without continued programme support.
The measurement system does not passively observe the programme. It actively constructs it.
And what it constructs, progressively, is a programme optimised for its own metrics.
Which are not the metrics of industrial conversion.
The Budget Flows to the Intermediary — By Design
There is a political economy to this that makes it more durable than it should be.
Public and semi-public funds move more easily into programme infrastructure than into direct technology support. The reason is structural: programmes generate accountability artefacts. Reports. Event documentation. Cohort lists. Participation certificates. KPI dashboards. These are easy to produce, easy to audit, easy to present to oversight bodies, and easy to use as justification for renewal.
Direct technology support — funding a founder to move a material from TRL 3 to TRL 5 over eighteen months — is harder to document in ways that satisfy quarterly reporting requirements. The evidence that matters is scientific and industrial. It does not fit neatly into a programme reporting template.
So the budget flows to the intermediary. Not because the intermediary produces better outcomes. Because the intermediary produces better paperwork.
The result is a layer of infrastructure — incubators, accelerators, TTOs, programme offices — that sits between public funding and the technologies it is nominally meant to support, consuming a substantial share of that funding in its own operation, and justified by metrics that measure its operation rather than its effect.
In the UK alone, one recent analysis estimated the publicly funded TTO and accelerator infrastructure costs in the order of £300 million annually. As documented in the UK version of this in forensic detail — the equity stakes, the deal timelines, the budget flows, the spinout numbers that don't survive scrutiny. The data is damning. But the more important question is not what the numbers show. It is why the system keeps producing them.
Against that expenditure, the sector’s own data shows spinout activity heavily concentrated in a handful of institutions, with the majority of deep tech companies building themselves entirely outside the formal support system. The 66% who never went through a TTO. The founders who didn’t wait six months for a licence negotiation. The people who just built something.
The system is not failing to reach them. It was not designed for them. It was designed for the metrics it reports.
This Is What the Compounding Looks Like — Before It Becomes Visible
What makes this particularly difficult to address is the temporal structure of the damage.
The KPI configuration is set at programme design. The behavioural adaptations it induces begin immediately — but they are invisible in early reporting, because the metrics look fine. Founders are attending workshops. Investor meetings are happening. Cohort numbers are healthy.
The structural distortion accumulates underneath. Founders are being trained, implicitly, to optimise for programme participation rather than industrial readiness. The selection mechanism is progressively filtering toward ventures that perform well in programme contexts — which is not the same as ventures that will convert industrially. Capital is being mis-sequenced: equity conversations opening before the evidence base can support them, because the programme’s KPIs reward funding signals over validation milestones.
By the time the consequences are visible — stalled Series A rounds, ventures in grant-dependent survival, technologies that never reached deployment — the causal chain runs back years. And the standard attribution is wrong: the failure gets assigned to the venture, or to market conditions, or to the inherent difficulty of deep tech.
Never to the programme structure that shaped the trajectory.
This is the accountability gap that makes the system self-perpetuating. The damage is real. The cause is invisible within the reporting architecture. The programme renews.
What the Relief Looks Like — And Why It Has to Start Before Execution
If you are running a programme, funding one, or designing the next mandate — this is the section that is actually for you.
Not because what follows is a framework to adopt or a methodology to implement. But because the structural leverage point is specific, and it is earlier than most institutions think.
The measurement architecture that determines long-term programme outcomes is set before execution begins. Before the first cohort is selected. Before the first reporting cycle runs. Before the first behavioural adaptation has a chance to become structurally embedded.
Once execution starts, each reporting cycle under a misaligned KPI configuration induces adaptations that compound. Founders learn what the programme rewards. Programme managers learn what renewal requires. The system learns to produce what it is measured for. And each cycle makes the correction more expensive — not because the problem grows linearly, but because the behavioural patterns it induces become harder to reverse.
The window in which structural realignment is both possible and low-cost is pre-execution.
What that realignment requires — specifically, which indicators need to shift, in which sequence, and against which baseline — is what distinguishes a programme structurally capable of producing industrial outcomes from one that is not.
That question has a measurable answer. But the determining variables are typically embedded before the first cohort is ever selected. It is not the same answer for every programme. It depends on the TRL range of the intake, the mandate horizon, the capital and industrial architecture of the ecosystem the programme operates within, and the behavioural incentives the current KPI configuration is already creating.
Getting that answer — before the next mandate cycle locks in — is the intervention point.
The Three Levels at Which the System Reproduces Itself
The self-perpetuating quality of structurally misaligned programmes is not accidental. It operates at three distinct levels, each reinforcing the others.
These dynamics are not merely cultural or organisational. They produce predictable behavioural adaptation patterns across founders, programme operators, capital allocators, and institutional reporting structures.
Over time, those adaptations compound into measurable shifts in venture selection, capital timing, evidence sequencing, and industrial conversion probability.
In other words: programme KPI architectures do not simply measure ecosystems.
They shape their outcome distributions.
The structural leverage point is specific, and it is earlier than most institutions think... read below: