Why DeepTech companies fail even when the science works

Every DeepTech founder works for years to reach the same moment. The science finally works. The prototype runs to spec. The team has crossed a threshold the wider market has not yet seen. And the founder, having poured years and most of their identity into reaching this point, makes a quiet assumption that turns out to be wrong. They assume the technology will now speak for itself.

It rarely does. The breakthrough is one thing. The commercial opportunity it unlocks is another. Investors, customers, even the team that helped build it can usually grasp the science. What they cannot see, without the founder doing the work to show them, is the business that could be built on top of it. The founder, surprised, blames the market for being slow when the cause is closer to home.

Hailey Eustace, founder of Commplicated, puts it sharply. More than half of DeepTech companies fail within five years, not because the technology let them down but because the founder did. They could not communicate the company well enough, to enough people, to keep it alive.

This is the discipline many DeepTech founders learn too late. And the audience they most often forget is already inside the building.


Communication is a CEO discipline, not a marketing function

The reflex of most DeepTech founders is to treat ‘comms’ as something to outsource. Hire a PR firm when an announcement is due. Bring in a marketing consultant for the website. Founders trained as scientists or engineers often regard communication as a downstream activity, performed by someone else, on the foundation that the technology has already done the hard work.

This reflex is wrong. Communication, in Eustace's framing, is the discipline that touches every part of building a DeepTech company: how the founder articulates the mission to investors, the value to customers, the strategy to the board, the priorities to the team. None of these are marketing tasks. They are CEO tasks. They sit at the centre of whether a DeepTech company survives the long gap between scientific validation and commercial reality.

Geoffrey Moore made the same argument three decades ago in Crossing the Chasm. Technically excellent products lose to commercially clearer ones because their founders cannot bridge the gap between the technologists who build and the pragmatists who must buy. As we have argued before, the founders who get this right build trust as a kind of technology in itself.


The root cause is founder inexperience, not neglect

Founders who fail at this rarely fail through neglect. They fail because they have never done it before.

Most first-time founders have never been responsible for the simultaneous communication needs of multiple stakeholder groups. They have managed peers, perhaps a small team in a prior role, perhaps a research group in a university. None of that prepares them to tell consistent, calibrated, audience-appropriate stories to investors, customers, the board, the team, and the wider market all at once.

Chris Braun, writing for CEO Coaching International, makes the operating reality plain: different stakeholder groups need different cadences and different formats, because "what works for one doesn't work for all." Each audience reads a different rhythm. Each expects a different level of detail. Each is offended by being treated like another.

The founder learns this in real time, while running everything else. The result is that almost every first-time founder is communicating badly with at least one critical stakeholder group at any given moment. They just rarely know which one.


The internal team is the audience founders most under-serve

External audiences feel urgent. Investors call. Customers email. Journalists chase. The internal team is in the office, available, and (the founder assumes) already aligned.

That assumption is the failure.

MIT Sloan's study of more than 2,000 IPO companies found that founder CEOs are systematically worse than hired CEOs at incorporating knowledge from their leadership teams. The conviction that built the company blinds the founder to signal already inside the building. The team raises a concern. The founder hears noise. The pattern recurs until the talented people decide it is easier to leave than to keep being unheard.

Internal communication failure does not look like silence. It looks like assumption. The founder assumes the team knows the strategy, the priorities, and what is coming next. The team usually does not. We have argued previously that the founder is the company's product in its earliest years. Inside the company, the founder is also its narrator. Stop narrating, and the company loses the plot.


Why DeepTech is the extreme case

Three things make DeepTech the sharpest version of this problem.

The first is the length of the R&D cycle. A team eighteen months between funding milestones, with no revenue and no user metrics, has none of the constant reassurance that a SaaS team gets from weekly active users and monthly cohort retention. The team needs to be reminded, explicitly and repeatedly, why their work matters and what progress looks like in a context where the product is not yet generating revenue. The founder who assumes the technical milestones speak for themselves leaves the team to manufacture meaning in the silence.

The second is the technical-commercial language gap inside the founding team itself. Research-trained engineers and commercially oriented co-founders genuinely speak different languages. The CEO who cannot translate between them creates a permanent fault line that the rest of the team feels even when the founders pretend it does not exist.

The third is the isolation of building something few people outside the company understand. That isolation cascades from the founder to the team. If the CEO does not communicate the mission with conviction, the team absorbs the founder's private self-doubt rather than the founder's public belief.


The tell-tale signs

A peculiarity of UK early-stage practice belongs at the top of the list. Institutional investors at Seed and Series A often push to install a non-executive chair earlier than is common in US venture practice. The legitimate reasons for a chair (a large board to manage, multiple major investors to coordinate, complex governance to navigate) all come later in a company's life. At Seed stage, the most likely reason is that the investor has a concern about the founder, and that concern almost always has communication at its root.

Nobody says this out loud. The role is dressed in experience, network and sector gravitas. The implicit understanding is that the chair will quietly develop the CEO into a more effective communicator and serve as conduit until they do. This sets up the wrong dynamic, even if the intentions are sincere. A founder who seeks development should choose their own executive coach; on terms they control. A founder who has development imposed through a chair appointment is at risk of being managed by their cap table, not coached by it.

Beyond the chair signal, the broader symptoms of communication failure show up in their own right, regardless of whether any board intervention has yet been contemplated. Uncertainty about priorities within the leadership team. Investor demands for updates that should be arriving routinely. Departures the founder cannot explain. A rumour mill in overdrive whenever bad news is in the air. Treating these as separate HR or investor relations problems misses the cause. They are all communication problems.


Horowitz's rule applies harder in DeepTech than anywhere else

In The Hard Thing About Hard Things, Ben Horowitz's operating manual for founder-CEOs and still the most cited more than a decade on, two observations deserve to be pinned to every DeepTech founder's wall.

The first concerns trust. Horowitz argues that the amount of communication a company needs is inversely proportional to the trust inside it. When trust falls, the founder must compensate with more communication, not less. The first-time founder's instinct is the opposite. They go quiet when things get hard, on the assumption that silence buys time. It does not.

The second is more uncomfortable. In post-mortems of failed companies, Horowitz observes, you will routinely find that "many employees knew about the fatal issues long before those issues killed the company." Read that sentence slowly. The team often sees it first. The founder is often the last to say it out loud. That's why astute Boards will push for exit interviews of key leavers.

Both observations apply with more force in DeepTech, where technical risk is harder for non-specialists to evaluate, milestone slippage is more common, and the founder's conviction is the gravity holding the team through the years before commercial validation. A founder who waits for certainty before communicating will communicate only when it is too late.


In summary

Most companies whose technology was working fail because the founder could not communicate the company well enough to keep it alive. The cause is rarely neglect; it is inexperience at managing investors, customers, the board and the team all at once.

The failure shows up inside the building first, where the team stops saying what it thinks long before any external stakeholder notices. The strongest UK signal that investors have already noticed is the early non-executive chair appointment, dressed in governance language and quietly carrying the brief no one wants to name.

Communication is not a marketing function the founder can delegate. It is the discipline on which the company depends.

So: do the people who work for you still tell you what they actually think? And would you recognise the answer if they did?

 
Let's talk.