Who Taught the People Teaching Founders?
A job in the innovation ecosystem can involve years of experience. The question is: experience of what?
How do I evaluate deep tech startup advice before choosing a mentor or accelerator?
Useful deep tech startup advice depends on the decision in front of you: customer qualification, manufacturing, procurement, licensing or financing. The question is not simply whether an adviser is experienced, but what that experience equips them to judge – and whether their judgement can change your route.
A commentary series on entrepreneurship knowledge transfer, essay 1 out of 3.
Key takeaways:
Experience matters. So does context. The article explores why science founders benefit from support that understands the realities of their venture.
Commercialisation needs more than one perspective. Scientific, commercial and institutional experience can bring complementary strengths to a difficult journey.
The right advice can make a consequential difference. The question is not whether founders need advisers, but how expertise helps them move forward in unfamiliar territory.
A public biography never tells the whole story. An exploratory review of twelve organisations reveals varied backgrounds, useful counterexamples and limits to what an outsider can infer.
Better support starts with a more informed conversation. The essay invites founders, advisers and programme leaders to reconsider what meaningful commercialisation support can offer.
What can a scientist considering entrepreneurship learn from the public descriptions of the people advising them?
Team biographies are published with bio-s. I wanted to understand what kinds of responsibility those descriptions make visible – and what a founder can reasonably infer from them.
I have spent enough time around science ventures and the organisations supporting them to become suspicious of one particular word: experience.
It appears everywhere:
Experienced teams.
Experienced mentors.
Experienced innovation professionals.
Usually, the sentence ends before anyone explains what the person has actually had to make happen.
Experience getting a grant approved? Experience qualifying a material for a customer’s production process? Experience advising someone who was trying to qualify a material? Experience organising the event where they met?
All those activities can be useful – at one point in the journey. But they also each produce very different kinds of judgement.
My suspicion was that the ecosystem is better supplied with experience of supporting commercialisation than with experience of being responsible for it. So I started looking at public team biographies, programme descriptions and decision structures. For this series, the focused review covered twelve organisations across Germany, France, the Netherlands and the UK, including university transfer, incubation, venture building and investment.
This was an exploratory reading exercise, not a representative survey. I did not verify every employment history, interview the teams or observe their internal decisions. I wanted to see what an outsider could establish about the expertise behind the promises. The examples below are selected observations from that review, including findings that challenged my starting assumption. They are anonymised, with identifying details generalised, to discuss patterns in public information rather than rate individual organisations. The examples are not a ranking; my professional position and commercial interest are disclosed below.
One thing I found was that my most sweeping version of the suspicion would not survive its own evidence.
Good. Better to discover that before publishing it.
Consider one European investment organisation whose public team biographies describe senior leadership and production responsibilities in industrial manufacturing and energy businesses. At another investment organisation in the review, a senior team member's biography describes strategic sourcing, supplier-related work and make-or-buy decisions in advanced technology industries. These are concrete descriptions of responsibility rather than generic claims of experience. They also place practitioners in senior investment roles.
The absolute claim that industry experience is absent would be wrong. These examples also place practitioners in senior investment and commercialisation roles.
At a university-linked commercialisation organisation, the published backgrounds include industrial deployment and the commercial development of scientific technologies.
These examples point towards a question that goes beyond counting industrial employers on a CV:
Where does the knowledge sit, and what is it allowed to change?
An organisation can employ someone who understands procurement without that person shaping its commercialisation advice. It can also use outside expertise effectively without placing every relevant competence on the payroll. Headcount alone will miss both arrangements. A team photograph tells us who is present. It says very little about whose judgement becomes consequential.
On another university-linked support organisation's public team page, biographies foreground university startup support, funding guidance, innovation consulting and business model development. The leadership biographies describe consulting and roles within the innovation ecosystem.
In these short descriptions, I did not find explicit accounts of responsibility for industrial production, technical purchasing or customer qualification. That observation concerns the information presented on this page; it does not establish the full experience of the people concerned or the expertise available through the wider service.
For me, it raises a broader question: how can public descriptions help founders identify the expertise relevant to their next commercial decision?
An incubation organisation in the review publicly describes a developmental role that combines learning with contributions to startup support. Its stated activities include project analysis, work with founders on commercial positioning and financing, and operational assignments. The organisation also describes support from an experienced team and access to external expertise.
These descriptions show a programme combining professional development with contributions to startup support. They do not, on their own, establish participants’ prior experience, decision-making authority or how their contributions are supervised. I have not assessed those arrangements.
For programmes combining learning and advisory work, I would find it useful to understand which contributions are reviewed, who retains responsibility for recommendations, and when specialist expertise is brought in.
What makes deep tech startup advice relevant to a commercial decision?
The tempting response is to demand that every adviser should previously have built a company. I think that would replace one crude shortcut with another.
A founder who sold a software business may know little about qualifying a coating for aerospace use. A senior industrial executive may understand a mature organisation exceptionally well and still underestimate the constraints of a five-person science venture. A scientist may have excellent technical judgement and very limited understanding of purchasing authority. A transfer professional may understand licensing better than any of them.
Relevant experience depends on the decision. The question is whether someone has encountered the mechanism they are advising on closely enough to understand its constraints, and whether they recognise where their knowledge ends.
I would choose a specialist who says, “I can help you negotiate the licence, but you need someone else to assess manufacturing economics,” seven days a week and twice on Sunday, rather than a generalist who offers to cover both after a two-hour workshop.
The harder question is what happens when relevant expertise conflicts with the programme’s preferred path. I regularly explore that tension in the deep dives and analyses on my Lab-to-Reality-Substack.
Boundaries are a sign of competence. The ecosystem should make them easier to state.
How can founders distinguish customer interest from commercial validation?
Take the familiar instruction to speak to customers. It sounds so obviously sensible that questioning it can make you look commercially illiterate. Yet the useful next conversation depends on what the venture needs to learn.
An engineer might help define the performance envelope. A production manager might identify integration constraints. A quality team might explain the evidence required for qualification. Procurement might establish supplier conditions. A budget holder might reveal whether the supposed problem has any purchasing priority at all.
These people work for the same customer. Their answers are not interchangeable.
Imagine a materials founder returning from a promising discussion with an enthusiastic R&D contact. The contact wants samples and sees several possible applications. An adviser interprets this as customer validation and recommends accelerating the sales narrative. A practitioner familiar with that buying environment might instead ask who owns qualification, what the next test must demonstrate, and whether any business unit has agreed to fund adoption.
This is a hypothetical example. It illustrates the kind of judgement a generic instruction can conceal. The difference is not vocabulary. It is the ability to distinguish an interesting conversation from an advancing commercial decision.
The same distinction applies to scaling. Increasing production volume can expose a different problem from increasing sales. More demand is unhelpful if production variation destroys margins or if every installation requires bespoke engineering. Someone who has lived through those constraints may ask less glamorous questions than someone preparing the next fundraising presentation. The questions can be substantially more valuable.
None of this gives practitioners immunity from being wrong. Experience can become dogma. People can overgeneralise from one company, one market or one unusually favourable period. That is why “has done it before” should qualify someone to contribute evidence, not to end discussion.
The institutional task is to bring relevant experience into a process where assumptions can be challenged. Replacing academic prestige with operator prestige would leave the underlying problem intact.
This is where I think the public information problem becomes more than a communications issue.
Founders are by default looking up to the ecosystem
Nobody owes the internet a complete employment dossier. A short biography may omit precisely the project that would answer my question. Some useful work cannot be disclosed. A website may simply be badly maintained. It would be unfair to turn any of that into a verdict on a person's competence.
But organisations actively asking founders to trust their commercial judgement can make that judgement more legible. They can describe the kinds of responsibility their advisers have held. They can distinguish staff, occasional mentors and decision-makers. They can explain how specialist questions are allocated and how recommendations are reviewed.
For a founder, those are practical buying questions, even when the programme is free. Participation still consumes time, attention and sometimes ownership. Bad sequencing can consume options that no later mentoring session can restore.
A founder does not need a ranking of impressive people. They need to know who can help with the next consequential decision, on what basis, and with what limitations.
I also want to be explicit about my own position. I am a scientist and strategist working on commercialisation decisions. I have a commercial interest in institutions taking those decisions more seriously. That makes it especially important that I apply the same questions to my work.
I should be able to explain what I know from direct work, what I infer from research, and where an industrial specialist is required. A framework does not exempt its author from those obligations. Neither does a strong opinion on Substack.
The standard has to survive being pointed back at us.
My concern, then, is not that a profession of supporting innovation exists. Complex systems need translators, coordinators, lawyers, funding specialists and people who understand institutions. The concern is how easily proximity to an activity can become authority over it.
Working around commercialisation can teach a great deal about commercialisation. It does not automatically teach every part of the work. After enough years, however, “I have supported hundreds of startups” can become an answer to almost any question. It sounds substantial while leaving the causal contribution wonderfully unspecified.
Supported them how? Through which decisions? With which outcomes? What did you learn when your advice failed?
These are reasonable questions for a profession that asks founders to validate everything else.
The strongest defence an institution could offer would be a concrete account of its work: a recommendation revised after manufacturing input; a venture redirected towards licensing; a procurement specialist involved before a pilot was negotiated; an adviser recognising a limit and bringing in someone better qualified. Each would reveal something about how expertise operates.
A page of company logos would reveal something else: access.
The distinction between visible activity and actual contribution also runs through Activity Without Additionality. My Substack analyses take these questions further.
Access can be useful. It still needs to become a contribution.
I cannot tell you from twelve organisations how common the problem is. I cannot tell you that a sparse biography predicts bad advice, or that a strong industrial CV predicts good outcomes.
I can tell you that the public evidence was mixed, and that the mixed evidence made the question more interesting.
There are practitioners. There are careers built primarily inside support structures. There are people still acquiring the experience of entrepreneurship while helping others navigate it. There are detailed biographies and descriptions that tell us very little. Those arrangements deserve different interpretations.
The next step in my thinking was therefore to stop treating experience as a binary possession. I wanted to understand the relationship between knowledge and institutional choice:
Can relevant expertise change the direction of the programme?
Can it challenge the definition of progress?
Can it recommend a route that produces fewer startups or less venture funding and still be considered successful?
That last question matters because an organisation can contain exactly the right people and still give them the wrong assignment.
If the path has already been chosen, the expert may only be there to help founders walk it more efficiently. Their industrial experience becomes a resource for executing the programme's assumptions rather than examining them.
That possibility is harder to detect than an inexperienced adviser. It can come with an excellent team, famous partners and beautifully organised workshops.
Which brings me to the question I now find more uncomfortable than “Who has actually done this?”:
What happens when someone who has done it says the programme is sending the venture in the wrong direction?
Disclaimer: These observations concern public information examined during the September 2026 review. Sources for the anonymised examples were checked on 8 October 2026. They are not assessments of individuals' or organisations' performance or estimates of ecosystem-wide prevalence. The next essay examines the financing destination that programmes may build into their design. Don't miss out
This essay opens the question. On my Lab-to-Reality-Substack, the deep dives and analyses examine how institutional choices, programme incentives and financing destinations shape what ventures are encouraged to become. Subscribe to follow the argument beyond this first essay:
Kommentare