[Test] The five questions that stop deep tech deals at Investment Committee

The partner meeting went well. The VC leaned in, asked smart questions, said they were "really excited about the technology." Maybe they asked for the data room. Maybe they said they'd "take it to the team." You left feeling good.

Then nothing happened.

Here's what you didn't see. Two days later, that partner walked into their Investment Committee and presented your deal to a room of colleagues whose job is to find the reasons not to invest. The partner is your champion. They want this to work.

But IC is a stress test, a layer of risk management, and the wisdom of the crowd. Your champion has to defend your company against questions you never heard, in a room you were never invited into.

Most deep tech deals don't die in the pitch meeting. They die here, because the champion couldn't answer the questions that the rest of the committee asked.

These are the 5 questions that consistently stop deep tech deals at IC. They share a common feature: none of them are about whether the science works.

1. "Who's going to sell this?"

The IC looks at the founding team and sees 3 brilliant scientists. Maybe a CTO who built the prototype, a CSO who published the research, a CEO with a PhD and a vision. Deeply credible on the technology.

Then someone on the committee asks: who is going to pick up the phone, walk into a procurement meeting, negotiate a contract, and close a deal?

The answer "we'll hire a commercial lead after the raise" is one of the most common responses. It tells the IC that the most critical capability the business needs to reach revenue doesn't exist yet, and the founders are asking investors to fund the search for it.

The most common fallback from the IC is simple: "you're too early" or "come back for the next round."

What changes the dynamic: a co-founder or early hire with genuine commercial experience already on the cap table. A signed LOI or pilot agreement that demonstrates someone on the team can sell. An advisory board member with relevant distribution relationships who is actively engaged, not decorative. A well-thought-out position description for the commercial hire with promising candidates already in conversation.

The IC needs to see that the path from technology to revenue has a champion who has done this before.

2. "What's the path to revenue and how difficult is it?"

Deep tech founders often present markets that are real but brutally hard to enter. The product requires customers to change suppliers, retool processes, retrain staff, or adopt entirely new workflows. Sometimes the product is genuinely better. But "better" is not the same as "easy to buy."

The IC is asking 3 sub-questions at once.

Do customers exist who will pay for this, or does the market need to be educated and created? What are the switching costs (financial, operational, psychological) for the target customer? Is the pricing model clear, tested, and defensible, or is it a placeholder the founders will "figure out later"?

A TAM slide answers none of these. What answers them is evidence of real customer engagement: pilot agreements, pricing conversations, letters of intent. Or at minimum, documented customer discovery that demonstrates founders have sat across from buyers and heard what they'd actually pay and why they'd switch.

If the path to revenue requires the market to change its behaviour before you can sell, the IC will price that difficulty into their assessment. Most early-stage funds won't underwrite it.

3. "What happens when a well-funded incumbent decides to do this?"

This question isn't about whether an incumbent is doing it today. It's about what stops them doing it in 18 months once you've proven the market exists.

Deep tech founders tend to answer with patents. Patents are necessary but rarely sufficient. A well-funded competitor with an existing customer base, distribution infrastructure, and a team of engineers can often design around a patent, acquire the technology, or simply outspend a startup on go-to-market. The IC knows this. They've seen it happen.

What the committee wants to hear is a defensibility story that goes beyond IP.

Feedstock advantages that can't be replicated easily. A production process with a learning curve that creates a meaningful head start. Regulatory approvals or certifications that take years to obtain. Customer contracts with lock-in periods or real integration depth. Specific partnerships that an incumbent would have to build from scratch.

The best answer to "what happens when an incumbent enters" is: "by the time they do, we'll be here, and here's specifically why that position is hard to reach."

4. "What are the unit economics at scale, now and 5 years down?"

In deep tech, the gap between pilot economics and production economics is not a rounding error. It can be an order of magnitude.

A process that works beautifully at bench scale with hand-selected inputs and controlled conditions may produce entirely different cost structures at commercial scale with variable feedstock, real logistics, maintenance cycles, and yield rates.

The IC isn't asking for a perfect forecast. They're asking whether the founders have done the work to understand their own cost structure deeply enough to model it credibly at scale.

The difference between a founder who says "we expect costs to come down with volume" and a founder who presents a detailed bill of materials, identifies the specific cost drivers that change at scale, and shows the sensitivity analysis around each one: that difference is the distance between a deal that gets funded and a deal that doesn't.

The "5 years down" dimension matters because deep tech often involves capital-intensive scaling. The IC needs to see the trajectory, not just the snapshot. What does the cost curve look like as you move from first plant to second plant, from first market to adjacent markets? Where do the step-changes in margin come from, and what assumptions drive them?

5. "How and when will we make our money back, and what is an acquirer or investor paying for at exit?"

This is the question founders are least prepared for, and the one that matters most to the people writing the cheque. It's the question the championing partner gets asked most often.

A VC fund has a finite life. LPs expect returns within a defined window. Every investment decision is a bet on whether the capital deployed will generate a return that justifies the risk and the opportunity cost.

Deep tech compounds this because the time to revenue is often longer, the capital requirements are often larger, and the exit landscape is often narrower than in software.

The IC is asking: what does the exit look like, realistically? Who acquires a company like this, and what are they paying for: the technology, the customer base, the team, the regulatory position? Will it solve a burning problem for the acquirer, or is this a nice-to-have? And if this is an IPO trajectory, what are the revenue and margin benchmarks that make that credible?

Founders who can articulate the return thesis signal a level of commercial sophistication that most deep tech founding teams lack. "This is a big market" doesn't do it. "Here is how a fund investing at this valuation, at this stage, gets to a return that works for their portfolio" does.

It tells the IC that this founder understands the investor's problem.

The common thread

None of these 5 questions are about whether the technology works. By the time a deal reaches IC, the technology credibility has usually been established. The partner wouldn't bring a deal they didn't believe in technically.

What the IC is stress-testing is whether this is a business. Whether the founders have the commercial range to turn a scientific advance into a venture-scale company.

The founders who raise successfully aren't the ones with the best slides. They're the ones who have already had their deal stress-tested against these questions before the real IC, and built the evidence to answer each one before they're in the room.

If you discover your belief gaps in a room you'll never enter, it's too late.