Deep Tech Demo Days End. The Commercialisation Work Does Not.
Deep tech demo days end with a full room and a round of applause. The competition has a winner. The programme has photographs for its annual report. Six months later, the founder is still trying to find someone at the corporate who can approve the next test.
I think this is one of the more expensive habits in deep tech support: we make the moment of connection highly visible, then leave the continuity of the relationship largely to chance.
Competitions can fund useful work. Demo days can open doors. But if we want to evaluate a deep tech innovation programme, the closing ceremony is a peculiar place to stop looking.
What deep tech demo days leave unresolved
A jury can assess a proposition against its criteria. An investor can request a follow-up meeting. Neither action establishes that an industrial customer can qualify the technology, integrate it into production or allocate a budget to buying it.
Consider a materials venture that wins a competition and meets a potential industrial partner at the final. The technical team likes the result. Procurement needs supplier evidence. Quality requires a different test protocol. Nobody has agreed who pays for that work.
The introduction was useful. The unresolved problem is now coordination across people with different responsibilities. Another pitch rehearsal will do very little for it.
This is where counting introductions, finalists and investor attendance can give a programme an impressive account of activity while leaving its commercial contribution unclear.
What Central Perk understood about continuity
In my latest essay, I borrow an unlikely reference point from Friends. Central Perk has no matchmaking software, selection panel or prescribed networking outcomes. People simply have somewhere to return.
The useful feature is the low cost of continuing a relationship. New information arrives. Earlier assumptions can be challenged. A conversation can resume without everyone having to reconstruct its history.
Deep tech needs that function. A shared pilot facility, recurring technical review or buyer working group may provide it. The furniture is optional. Someone retaining the context and taking responsibility for the next decision is rather less optional.
The awkward conversation comes after the stage
A pitch rewards a coherent account of where the venture is going. Working together eventually requires an honest account of what is blocked.
The corporate's strategic interest may have no operating budget. The investor's fund may be unable to finance the industrialisation path. The founder may need fewer pilots and more capacity to deliver the ones already agreed.
These are difficult things to say when everyone is performing readiness. They become easier to discuss when the relationship can survive a disappointing result or a change of plan.
That is why programme evaluation needs to examine what happens between the formal milestones. In my independent programme evaluation and design work, I examine how selection criteria, incentives, support and decision responsibilities connect to the outcomes being claimed. The practical question is what should change before another cycle repeats the same friction.
A continuity check before the next programme cycle
For programme owners and institutional funders, I would start with five questions:
1. What continued? Identify substantive interactions after the competition or demo day, and what those interactions made possible.
2. Who owned the next decision? Establish whether there was a named person with authority, a defined evidence requirement and a realistic route to a budget.
3. What changed for the venture? Look for access to testing, facilities, customers or procurement that materially affected its next step.
4. What knowledge survived? Check whether technical context and commitments remained accessible when a mentor, corporate champion or programme manager moved on.
5. Which relationships stopped, and why? A useful intervention may clarify that there is no fit. Keeping every connection alive is no more sensible than counting every introduction as progress.
This is a starting point for investigation. It is not proof that a programme caused an outcome. That requires examining what would plausibly have happened without the support.
Continuity needs an open door
There is an uncomfortable detail in the Central Perk metaphor: the regulars always seem to get the sofa.
Stable relationships can become closed networks. Transparent entry routes, explicit allocation criteria and outside challenge matter, especially where public resources are involved. We should be able to preserve trust and accumulated knowledge without turning access into a reward for already belonging.
Before commissioning another competition or demo day, I would want to know where participants can go when the next difficult decision arrives. If the answer is another application and another explanation from zero, the ecosystem is repeatedly paying to forget.
I explore the relational infrastructure behind this argument, and what to do better to foster cross-sectional market entry for scientific innovation in E.cosystems Need a Central Perk, Not Just Another Stage. For shorter analyses of the decisions connecting science, commercialisation, capital and policy, you can receive the ARISE Decision Brief by email.
Independent commentary. Not affiliated with or endorsed by the producers or rights holders of Friends.
Kommentare