Commercialising Deep Tech Part 2: Discovery (Finding a market)
Commercialising Deep Tech Part 2: Discovery (Finding a market)
Words Liam Nolan
March 17th 2025 / 8 min read
Google Glass is considered one of tech’s biggest failures of the past few decades. Representing a huge leap forward in augmented reality, Google Glass was on the market for just over six months before being discontinued.
Whether it was the eye-watering price tag, its undesirable design, or its notable privacy violations, critics say the product was doomed from the start. By the time they pivoted towards enterprise—with potential applications across manufacturing and healthcare, to name a few—it was too late. At its core, Google launched their product without a buyer in mind, and paid the price.
There’s a common wisdom around venture building with regards to customer discovery: start with the problem, and build your technology to solve that problem. That way you can be confident that 1) you are solving a genuine problem, and 2) those people who feel the problem will pay for your solution.
The challenge with deep tech is that it flips this on its head—you start with the breakthrough technology, then have to find a big enough problem that your technology can address. Discovery in deep tech, therefore, isn’t about building for your ideal customers: it’s about taking your technology and finding out if there’s a convincing application that solves problems.
In our Commercialising Deep Tech series, we’re exploring the opportunities and challenges that founders face when trying to build, fund, and scale deep tech businesses. In this article, we explore customer discovery when you’ve already got a breakthrough technology, helping founders answer the fundamental question—am I solving a clear problem, or am I just building innovation for innovation’s sake?
Previous articles in the series:
Interested in receiving more insights like this ? Subscribe to our newsletter and join 20,000+ founders, investors, and innovators
Subscribe hereDeep Tech Discovery: Why is it much harder?
Finding a market for deep tech comes with considerable challenges.
Commercial considerations, like customer discovery, don’t always come naturally to deep tech founders. Technologies aren’t developed with buyers in mind, and putting the tech to one side can feel like a distraction from the main task at hand. Take OpenAI, which existed for several years as a non-profit research lab before first commercialising through an API, and then ChatGPT.
A common mistake is that breakthrough technology is not necessarily the same as a ‘product’ or a ‘solution’. So while the breakthrough itself can feel like success, it’s worth remembering that success in research doesn’t equal success in the market.
Deep tech is often a ‘building block’ technology, foundations for other applications to build on top of. In some ways, this presents an opportunity: deep technologies may have dozens of use cases with plenty of problems to solve, a narrative that investors will warm to (it increases your market size and future potential). But it can also be a distraction—customers don’t buy ‘horizontal’, they want to see specific applications that solve problems for them.
Category creation can be a double-edged sword. Being novel is advantageous but not unequivocally beneficial—there’s no existing market, no existing competitors, and therefore no existing customers. This makes market mapping much harder, requiring considerable work to think about who you are solving for and what you are offering an alternative to (not as simple as ‘doing X cheaper/faster than Y’).
If there’s no existing solution, this may mean your customers don’t even know about the problem. It might be hard to fathom a solution that doesn’t exist yet, and they may just take the problem as a given. As the old adage goes—before cars existed, if you’d asked people what they wanted, they would have said ‘faster horses’.
Deep Tech Discovery: Finding your problem to solve
General advice for customer discovery is that you need to work out 1) who’s the customer, 2) what’s the problem, and 3) what’s the technology? With deep tech, you know what the technology is, but you need to find the other two.
One of the key goals of deep tech discovery is determining what direction you’re going to take your technology in in order to figure out how you’re going to productise it and make it “easy to buy”. We coach founders to use a ‘recursive strategy’: outlining the series of steps you’ll take to gradually and realistically scale your product).
The Tesla example (taken from Elon Musk’s famous 2006 blog post):
Build sports car
Use that money to build an affordable car
Use that money to build an even more affordable car
While doing above, also provide zero emission electric power generation options.
So while your tech may have dozens of use cases, this is about narrowing them down to a specific but sizable enough problem to start commercialising.
1. Market evaluation
To do this, founders need to start broad and narrow down opportunities very quickly. To find the most promising opportunity, you should identify a number of addressable markets, and evaluate the attractiveness of each market.
In short, you want to find specific but sizable problems. Weigh up a number of factors: value of the market, value of incumbents, as well as penetrability.
We get founders to map out potential customers by using this template and adapting it to factor in specifics for the type of business they’re building. This helps ensure a focus on the most commercially viable path to begin with.
2. Create a value proposition for this market
The next step is to understand your ideal customer profile (ICP) within your chosen market and define a value proposition for your business.
In essence, value propositions fall into three buckets:
Stop you going to prison (e.g. compliance, regulation)
Cut your costs (by doing things more efficiently, with cheaper materials, etc)
Increase your output (by doing things faster, more resourcefully)
Work out which of these you are offering for your ICP. You should do some of this through desk research—starting off with broader industry analysis, before looking at specific companies and looking at their current practices (tools/materials/services they’re currently using, who they’re buying from, what’s this costing them, etc.). For instance, large corporations often make their high-level annual goals public, allowing you to link the benefit of your tech to these.
At this point, your value propositions are nothing more than hypotheses. While you should have done sufficient research, you’re still making assumptions about your customers that you need to test.
3. Pick up the phone
Speaking directly to your potential customers is the tried and tested way of validating your hypotheses. There will be unknowns that your desk research didn’t pick up on; more importantly, desk research doesn’t measure the urgency of your solution, and how desperately (or not) your customers might want it.
Picking up the phone isn’t just about discovery: it’s about starting an open dialogue with your customers, starting to qualify who you might ultimately end up selling to. There’s valuable work to be done here, which you’ll thank yourself for when it comes to GTM and actually trying to close sales.
Who should you speak to?
Part of discovery is working out exactly who you should speak to. In some sense, this is another test in itself—you should set out to test a hypothesis around who sees the most value in your solution (and who has the biggest problem for you to solve). Various stakeholders you might speak to include:
Strategic (e.g. CEOs)—key figures who will help you understand overarching business need for what you are offering, as well as who can manage the risk of using your product
Financial (e.g. CFOs)—stakeholders who understand potential financial hurdles to overcome, such as budgets and procurement processes
Operational (e.g. product teams, line managers)—end users, who will help you understand practical and emotional hurdles (do they care enough, will they integrate into their current workflow or technology stack?)
What are you trying to find out?
Bluntly, you are trying to find out whether they would pay for your solution: as above, is this more than just a technology, is it a product/solution? On top of this, you’re trying to understand why they’d pay for your solution: understanding this motivation will help you sell and identify other similar customers.
Calls should be as unbiased, uninfluencing, non-salesy as possible. Initially, you should be looking to:
Identify the problem—their day-to-day, challenges they face, future trends or changes they anticipate
Identify frequency and intensity—how often does this problem occur, what is most frustrating about it?
Understand current solutions or workarounds—what have you tried using to solve this problem before, have you paid for it or was it a free workaround, did it work, and what happens if you don’t solve this problem?
Validate the value of a potential solution—how important is it that this is easier to solve, how much time or money would it save you, who would you need to consult before trying a new solution?
Your potential customer loves your solution? It doesn’t end here sadly. There are numerous other practicalities and specificities you should be sourcing from these conversations—other influencers on the decision making process, budget authority, approval processes, procurement policies and constraints, etc. Think through the entire end-to-end process that will take your customer to buying your product, and what answers you need to gain to be confident of this.
And beware of false positives. People like to say what they think you want to hear. Potential customers may express enthusiasm without real intent to buy. The key question is: would they pay for it today? And if not, what needs to change?
What happens next?
Discovery can be an exhaustive process, but it’s essential to your future prospects of commercialisation. Without sufficient discovery, you may end up with the most ingenious innovation that no one wants to buy.
It’s also worth bearing this in mind. The validation process for deep tech may be much longer. But once you’ve solved the problem, found people who have that problem, and proved that your technology works, selling to them is much easier. We’ll explore this further down the line—but demonstrates there’s real value in putting in the hard yards at this early discovery stage.
Our next article in the series, we’ll be focused on product development.
Are you building in deep tech?
Find out more about our thesis and where we're building in deep tech.
Find out moreAbout Liam
Liam Nolan is Head of Growth at Founders Factory. Prior to this, he held several growth & marketing roles at JustPark and Zealify, where he was Head of Product Marketing. He also founded his own business in the student accomodation space.
News from the Factory Floor
practical advice
Commercialising Deep Tech Part 2: Discovery
Building technology first, rather than problem first, can mean you build without a buyer in mind. Here’s how founders should approach customer discovery in deep tech
factory news
Investing in Enzidia—leading the bioeconomy revolution with enzymes
Learn more about our latest investment, Enzidia, and how they’re transforming enzyme engineering through synthetic biology, data collection, and machine learning
trends
Commercialising Deep Tech: What makes deep tech different?
In this new article series, we dive into the key differences between deep tech & traditional digital tech, and what that means for the founders