You've had the meeting. It went well — or so you thought. Your contact was attentive, asked good questions, said the technology was "very interesting." They asked you to send additional documentation. You sent a detailed technical memo the next morning.

Three weeks passed. Then a month. Then silence.

This is one of the most common experiences in deeptech commercial development. And it is almost never about the technology.

What happened in that room after you left matters more than what happened while you were in it. Understanding it changes everything about how you prepare, what you say, and what you ask for at the end.

The primary filter: risk, not opportunity

Investors and industrial buyers use fundamentally different decision frameworks. An investor evaluates upside. An industrial buyer evaluates risk.

This is not a small distinction. It is the entire logic of the relationship.

A director of R&D or process engineering at a large industrial company is not compensated for finding the next breakthrough technology. They are compensated for meeting their targets, not disrupting their operations, and being able to justify their decisions to their management hierarchy. Every engagement with an external startup represents, from their perspective, a potential source of delay, cost overrun, or internal political difficulty.

This doesn't mean they won't engage. It means they evaluate everything through one lens: what is the worst-case scenario here, and can I survive it internally?

Your job is not to sell the upside. Your job is to make the downside feel manageable.

What builds confidence

Four signals consistently move industrial buyers toward engagement.

Specificity of use case. Vague application areas signal that you don't understand their world well enough to be a useful partner. A sharply defined use case — "reducing batch rejection rates in API manufacturing at TRL 5-6, targeting a 15% improvement over 12 weeks" — signals that you've done your homework. Industrial buyers are pattern-matchers. They need to quickly answer "is this for me?" If your framing is too broad, the answer defaults to no.

Honest assessment of your development stage. Counter-intuitively, admitting limitations builds more trust than obscuring them. Industrial buyers have seen enough startups claim readiness that wasn't there. A founder who says "we're at TRL 4, we can do X but not yet Y, and here is what a collaboration would allow us to validate" is far more credible than one who says "our technology is ready for industrial deployment." The first is someone they can work with. The second is someone they'll need to manage.

Evidence that you understand their constraints. Show that you know how their industry works — procurement cycles, validation requirements, internal approval processes, regulatory context. You don't need to know everything. But demonstrating that you've thought about the integration challenge, not just the technical performance, signals that you can be a usable partner. Not just an interesting research project they'd never know how to bring inside.

A concrete, bounded first step. The single most common reason an industrial conversation stalls is that there is no clear next action. "Let's stay in touch" is not a next action. A proposal for a 6-week feasibility study at a defined scope and cost is. Industrial buyers who are genuinely interested need something specific enough to bring back to their management. Give them that, or the meeting produces nothing regardless of how well it went.

What triggers a quiet exit

Some signals consistently push industrial buyers toward silence — not a direct rejection, which would at least be informative, but the kind of progressive non-response that leaves founders wondering what went wrong for months.

Disruption language. Telling an industrial director that your technology will "disrupt" their industry is telling them their current processes are wrong and their colleagues' decisions are about to become irrelevant. Even if it's true, it is not useful. Industrial buyers are not looking for disruption. They are looking for improvement that fits inside their existing structure and that they can justify to the people above them.

Mismatched ambition. A pitch that opens with "€40 billion addressable market" and "10x performance improvement" is a pitch built for investors. To an industrial buyer, it signals that you are thinking about a future that has nothing to do with their operational reality. They have a problem to solve in this fiscal year, within their current budget, within their operational structure. Meet them there first.

No internal champion. This one happens invisibly, and it's the most dangerous. After your meeting, your contact needs to go back to their team and explain why they spent time with you — and potentially why they want to take it further. If you've given them nothing specific to say — no clear use case, no defined deliverable, no bounded first ask — they cannot make the internal case. The deal doesn't die in your meeting. It dies in the conversation they have about you when you're not there.

Overstating readiness. If you claim your technology is ready for industrial deployment and it isn't, the pilot will expose it. Industrial buyers talk to each other. The cost of being caught overstating your readiness is not a lost deal — it's a damaged reputation in a community that is smaller and more connected than it appears from the outside.

The internal champion problem

Most startup founders think of an industrial deal as a two-party negotiation. It isn't. It is a multi-party internal process on the buyer's side, in which you have no visibility and no control — unless you've deliberately equipped your contact to manage it on your behalf.

After your meeting, the person you spoke to faces a choice. They can advocate internally for moving forward, or they can let it fade into their backlog of "interesting things that went nowhere." The difference between these two outcomes is almost entirely determined by how clearly you've defined what "moving forward" means, and how easy you've made it for them to propose it.

A good industrial pitch ends with a very specific ask: not "let's explore working together" but "would it make sense to run a 4-week technical assessment on a sample set from your process, scoped to X, at a cost of Y?" That question gives your contact something to do. Something specific enough to budget, to schedule, to propose upward.

Without it, the most enthusiastic meeting in the world produces the same result as a polite rejection: nothing moves.

What "very interesting" actually means

An industrial buyer who says "this is very interesting" is often, in reality, saying something more specific: "I don't see a reason to dismiss you, but I also don't see a reason to commit right now." The interest is real. The urgency is absent. And without urgency, industrial organisations do not act.

The way to create urgency is not to pressure. It is to identify, early in the conversation, what the specific trigger for action would be on their side — a timeline, a regulatory milestone, a production constraint — and to frame your offer explicitly in relation to that trigger.

"Very interesting" becomes a partnership when the industrial buyer can answer the question their management will ask: why now? Your job is to give them that answer before they leave the room.