The Scenarionist Premium is designed to make you a better Deep Tech Founder, Investor, and Operator. Premium members gain exclusive access to unique insights, analysis, and masterclasses with the wisdom of the world’s leading Deep Tech thought leaders. Invest in yourself, and upgrade today!

Subscribe now

Deep Tech venture design often doesn’t start from an unmet customer need, but from a technology with enabling potential.

A new material. A novel manufacturing process. A scientific discovery. A proprietary algorithm. A new approach to energy conversion, sensing, computation, biology, or industrial production.

Something becomes technically possible that was previously impossible.

This is the source of Deep Tech’s extraordinary potential. It is also the source of its strategic challenge.

A new technology rarely points toward a single specific product, customer, or market. It often enables multiple possibilities.

It may improve performance in one application, lower costs in another, shorten a critical process somewhere else, or make an entirely new outcome possible in a market the founding team had never considered.

That broad spectrum is often presented as an advantage.

The company accumulates use cases, customer conversations, and technically plausible directions. Each one appears to confirm that the opportunity is larger than initially imagined.

However, a broad optionality creates value only when the company knows what to pursue now, what to preserve for later, and what conditions must be true before the next move becomes rational.

Multiple applications may point to scale and larger markets. They can also fragment attention, accelerate cash burn, and impose significant opportunity costs.

The question is not simply where the technology can be used. It is where it can create an advantage powerful enough to change a customer’s decision and durable enough to support lasting value capture.

Subscribe now

The logic of this piece

So, in Deep Tech, what matters most when building a strong competitive advantage?

Deep Tech is industry-specific and product-specific. The dynamics of a semiconductor company are not those of a mining technology, a medical device, or an advanced materials venture.

Still, some strategic considerations travel across sectors. In moments of company creation, market entry, or strategic pivot.

This was the starting point that inspired this piece.

The answer does not lie in technology alone. It may depend on the business model, distribution agreements, access to customers, control of critical resources, or the company’s position within the value chain.

Drawing on the experiences and conversations collected over time, as well as the lens developed through direct engagement with people operating in the field, I have organized the piece to provide some curated food for thought.

The objective is to move from broad technological optionality to the strongest competitive edge around which a company can build a coherent and durable advantage.

Each section includes practical questions for founders and investors working through market selection, product direction, strategic pivots, and venture design.

From here onward, only our Premium Members can keep reading.

Read more

The Scenarionist Premium is designed to make you a better Deep Tech professional. Premium members gain exclusive access to unique insights, analysis, and masterclasses with the wisdom of the world’s leading Deep Tech thought leaders. Invest in yourself, and upgrade today!

Subscribe now

Deep Tech companies rarely fail for one reason alone.

Sometimes the science does not work. Sometimes the market is not ready. Sometimes the cost curve is worse than expected. Sometimes the first application is wrong. Sometimes the technology is real, but the customer cannot adopt it. Sometimes the company raises money around a roadmap that reality refuses to follow.

But across the conversations I have had with founders, investors, operators, and industry experts in Deep Tech, one pattern keeps coming back.

Deep Tech companies also fail when the wrong people own the wrong problems at the wrong time.

At first, this may sound like an organizational issue.

I don’t think it is.

It is a company-design issue.

A Deep Tech startup is not simply a lab with a pitch deck attached to it. And it is not a software company with a longer technical roadmap.

It is a fragile system where scientific risk, market risk, operational risk, financing risk, and governance risk begin to interact very early.

Subscribe now

At the beginning, the company is still mostly the team.

There is no mature organization to absorb ambiguity. There are no established processes to compensate for unclear ownership. There is no predictable commercial engine, no industrial machine, no stable deployment motion, and often no meaningful revenue.

What exists is a small group of people trying to turn a technical insight into a company that deserves to exist.

A young Deep Tech company can have a CEO, a CTO, advisors, investors, and a few impressive profiles, while still leaving the most important risks under-owned.

It can look strong from the outside and still be fragile inside.

An interesting way to frame this issue is to ask:

“Which critical jobs have to be owned for the plan to succeed?”

That is the question I want to explore in this piece.

Not the generic statement that “team matters.” Everyone says that.

The more useful question is how the team actually functions when it has to translate science into product, product into adoption, adoption into delivery, delivery into economics, and economics into a fundable company.

That is where Deep Tech teams win or break.

The Framework We’ll Follow Today

There are many ways to discuss teams in Deep Tech. We could talk about founder-market fit, leadership style, hiring, culture, governance, or incentives.

All of those matter.

So in this piece, I want to look at the team question through three practical angles, drawing on a curated narrative built from the conversations collected so far.

The goal is to build a sharper language for asking better questions: who owns which risk, where does misalignment begin, and how can the team fine-tune itself before small gaps become expensive.

Subscribe now

1. What Winning Teams Get Right

Before an early-stage Deep Tech company has a real organization, it usually has a small number of people carrying a large number of tasks.

Costs begin on a clear date. Revenue, instead, arrives on an uncertain one.

That is why roles must be defined.

However, team dysfunctions tend to show up in a few recurring ways. Across our work, a few patterns keep appearing:

Read more

The Scenarionist Premium is designed to make you a better Deep Tech Founder, Investor, and Operator. Premium members gain exclusive access to unique insights, analysis, and masterclasses with the wisdom of the world’s leading Deep Tech thought leaders. Invest in yourself, and upgrade today!

Subscribe now

Dear Friends,

There is a question in Deep Tech that often appears much later than it should.

At first, it sounds like an operational question.

Something to discuss with the technical team, the COO, the supply chain people, the contract manufacturers, the equipment vendors, or whoever is responsible for turning prototypes into something that can actually be delivered.

But the more I speak with founders, investors, and operators across Deep Tech, the more convinced I become that this is not really an operational question.

It is a company-design question because, among other things, it affects:

• How much capital the company needs.

• How fast it can reach the market.

• How much margin it can capture across the value chain.

• How defensible the business becomes.

• How much control it has over quality.

• How dependent it becomes on partners.

• How credible it looks to customers.

And, consequently, the roadmap it follows and the type of company it ultimately becomes.

However, over time, markets change, supply changes, and regulation changes. That makes the manufacturing decision an evolving scenario that becomes true when the evidence catches up — a kind of Rubik’s Cube where several dimensions have to fit together within a specific window of time.

One recurring pattern across geographies and sectors is that the manufacturing conversation tends to become too binary, too quickly.

1. On one side, there is the asset-light instinct.

Stay flexible. Preserve capital. Leverage partners. Avoid building steel too early. Do not become a factory before the market is ready.

2. On the other side, there is the control instinct.

Own the process. Protect the know-how. Learn faster. Improve yield. Control quality. Do not let a third party become the place where the real manufacturing intelligence accumulates.

Both instincts are reasonable. And both can be dangerous.

A Deep Tech company that builds too early can trap itself in fixed costs before demand is real.

It can raise expensive equity to finance equipment, facilities, operators, permitting, and working capital, only to discover that customers are still testing, still qualifying, still comparing, still waiting.

But a company that outsources too casually can create a different kind of problem.

It may lose the learning loop that makes the product better. It may hand over know-how before it knows what is truly proprietary. It may become dependent on a partner that does not move at startup speed. It may struggle to control quality, cost, or yield.

This is the real pain.

Deep Tech companies are often told to scale, but not always given a clear way to decide what scaling should mean.

• They are told to be capital-efficient, but also to prove they can deliver.

• They are told to avoid CapEx, but also to show a credible path to commercial production.

• They are told to leverage partner relationships, but also to protect their moat.

• They are told to move fast, but also to build trust with customers who cannot afford supply risk.

And so the manufacturing question becomes a place where many unresolved tensions collide.

It is not just: “Should we build a factory?”

It is:

• What does the customer actually need to believe before adopting this product?

• What part of the value chain creates the real advantage?

• Is demand strong enough to justify capacity?

• Would CapEx create capacity?

• Can partners help the company move faster without absorbing the knowledge that makes it valuable?

That is the kind of decision logic I want to unpack in this piece.

Spoiler alert: There is not one answer.

A robotics company, a semiconductor company, a battery company, a bio-manufacturing company, an aerospace company, and a photonics company will not make the same manufacturing decision.

But they often face the same underlying trade-off.

They have to decide what to build, what to outsource, and what to delay.

And they have to make that decision asap, before the market, the board, the customer, or the next financing round forces the answer.

So this piece is not a manifesto for asset-light Deep Tech.

And it is not a defense of asset-heavy Deep Tech either.

It is an attempt to lay the first brick of a more useful decision language, grounded in hundreds of conversations with people doing the work in the field.

In my view, this is not a Hamlet problem of “to build or not to build.”

A better way to frame the question is:

“Which parts of manufacturing are strategic enough to own, which parts can be handled through partners, and which parts should remain flexible until the market gives the company permission to build?”

That is where the real strategy begins.

Subscribe now

The Decision Nodes We’ll Walk Through

There are many ways to approach the manufacturing question in Deep Tech. (Personally, I have identified at least 3 useful angles, and I suspect I will return to the others in future pieces…)

For this deep dive, I chose to start with these 5 decision nodes because, across the paths I have listened to and collected so far, they seem to be the most useful starting point for building a sharper lens on a decision that can shape the entire company.

For each section, I have also included practical questions and scenarios collected along the way through real-world conversations, meant to serve as a framework to help you generate sharper questions and stress-test your business plan — whether you are a founder discussing the path with your team or an investor helping a company think through the trade-offs from a different angle.

1. Product-Manufacturing-Market Fit

Read more

That may sound obvious. But in practice, many founders still approach customer discovery as if the main question were, “Do customers want this?” In deep tech, that question is usually too small. A company may want it. An engineer may admire it. A pilot partner may agree to test it. And yet nothing moves. Not because the technology is weak, but because the path to adoption is still unclear.

Subscribe now

✨ This is the Premium Edition of The Scenarionist. Unlock the full experience by becoming a Premium Member!

The Scenarionist Premium is designed to make you a better Deep Tech Founder, Investor, and Operator. Premium members gain exclusive access to unique insights, analysis, and masterclasses with the wisdom of the world’s leading Deep Tech thought leaders. Invest in yourself, and upgrade today!

Subscribe now

This guide is written for deep tech founders who are trying to understand markets that do not behave like software markets.

In such sectors, the challenge is often less about discovering whether a user finds a product interesting and more about understanding whether an organization can qualify, adopt, scale, and continue to buy a new technology over time.

The guide uses the phrase customer discovery broadly. In this context, customer discovery includes application discovery, buyer and stakeholder mapping, validation of adoption criteria, pilot learning, and ecosystem sensing.

That broader framing tends to be more faithful to the realities of chemistry, advanced materials, industrial equipment, and other sectors in which technical performance alone rarely determines commercial success.

Subscribe now

Why Deep Tech customer discovery works differently

A scene familiar to many deep tech founders begins with a real technical breakthrough and an awkward commercial conversation.

A team leaves the lab with a membrane that performs better, a coating that lasts longer, a catalyst that reduces energy use, an excipient that improves delivery, or a process platform that changes yield and purity.

The early reactions are often encouraging. Prospective customers may say the work is impressive. Investors may say the science looks promising. Yet the company still struggles to answer what sounds like a deceptively simple question: where, exactly, should this technology enter the market?

That question tends to remain unresolved because most mainstream customer-discovery advice was built for businesses in which the product is easy to demonstrate, the user can test it quickly, and adoption is relatively low risk. In software, a founder may often learn a great deal from a short conversation, a trial, or a lightweight pilot. In deep tech, the situation is usually more layered. A buyer may not be the user. An engineer may shape the specification without controlling the budget. A quality team may stop the project long after a commercial champion has expressed enthusiasm. A pilot may create useful technical evidence while revealing almost nothing about who will authorize scale-up. In other words, the learning task is broader than simple demand sensing.

This broader view is reflected in the U.S. Department of Energy’s Adoption Readiness Levels framework, which is explicitly designed to complement Technology Readiness Levels.

The ARL framework describes commercialization as an exercise in identifying and addressing adoption risks early and often. It evaluates not only technical promise but also issues such as market acceptance, resources, and license to operate. That distinction is particularly important in hard-tech sectors, because a technology may be technically mature and still be commercially fragile if the adoption pathway is unclear.

The same idea appears in Vanessa Chan’s work on materials commercialization. In a 2025 lecture at MIT, she emphasized that new materials frequently begin at the start of the value chain and therefore depend on adoption by multiple downstream actors before they can become mainstream.

That may sound obvious to people inside hardware or materials science, but it is surprisingly easy to forget when founders are surrounded by software analogies.

A product does not move from invention to adoption simply because a market ‘likes’ it. It moves when enough actors in the chain can understand it, test it, trust it, and fit it into existing or newly designed systems.

Established industrial firms tend to behave accordingly. They often build application centers, technical centers, innovation centers, pilot facilities, and co-creation environments because they know that customer discovery in their world is not a single interview problem.

They are not just selling. They are learning how the market learns. This guide is built on that observation.

It starts from a simple idea: some of the most useful customer discovery models for deep tech can be distilled from commercialization patterns visible across deep-tech markets, including industrial incumbents, hard-tech pioneers, and category-defining scale-ups.

Not copied literally, but translated. These companies have spent years learning how new technologies move through qualification, stakeholder alignment, pilot work, and ecosystem formation. Their contexts are different from those of startups, but the commercial logic is often highly reusable.

The five models are:

Read more

When software eats the world, it leaves the crumbs of physical production to others. But in 2025, some of the savviest deep tech upstarts are instead feasting on those “crumbs” – building factories, mastering hardware processes, and turning heavy infrastructure into high-ground advantage. In an era when supply chains became strategic choke points and capital flooded back into industry, manufacturing is no longer a dirty word in venture. It’s a secret weapon. Welcome to the arena of manufacturing moats, where steel and silicon trump code.

Subscribe now

Why? Because if you control the hard infrastructure, you control the market entry point. When you run the fab or the test-stand or the pilot plant, you dictate the pace of innovation and the flow of product. It’s defensive tech in its most literal form: concrete, cleanrooms, cryogenics.

This isn’t theoretical. It’s deeply practical – and it’s playing out right now across domains from semiconductors to quantum to energy.

In this analysis, we’ll explore how a handful of real worlds startups have built “moats” out of manufacturing and what that means for investors and founders seeking durable advantage in deep tech.

Subscribe now

Each section dives into a different “factory stack” – from ultra-high vacuum chip fabs to cryogenic quantum foundries to megawatt-scale energy lines – to illustrate how physical infrastructure can become a repeatable edge. By the end of this analysis, you’ll have a clear, pragmatic understanding of how and why hard infrastructure can act as a high-impact moat.

Whether you’re evaluating a quantum chip venture or plotting an aerospace factory, the goal is to equip you with a mental model for when building in-house manufacturing is not just a costly line item but a strategic imperative. In a time when nations and corporations alike are scrambling for technological self-reliance, the startups that literally build their advantage may define the new winners.

✨ This analysis is reserved for our Premium Members.

To read on, unlock The Scenarionist Premium today.

Becoming a Premium Member gives you full access to our archive of deep tech intelligence, case studies, and strategic guides – all grounded in independent research and exclusive insights from the front lines of technology and venture.

Subscribe now

1. Introduction — From Asset-Light Dogma to Industrial Edge

Read more

Subscribe now

Deep tech startups face a harsh reality: moving from lab prototype to industrial scale isn’t just a bigger project – it’s a different universe.

Unlike software ventures, which can iterate rapidly and cheaply, deep tech companies must pour capital into physical infrastructure, supply chains, and hardware long before revenue flows [1].

This is the notorious “valley of death” in deep tech, where technology readiness alone isn’t enough, and the difference between success and failure comes down to strategy, financing structure, and execution precision [2].

In 2024, U.S. construction spending on new manufacturing facilities hit a record $238 billion – a sign of massive scale-up efforts underway – yet many of these projects will falter if their first Capex investments don’t pave the way for cheaper follow-ons.

Subscribe now

For investors and founders, the first industrial asset (be it a pilot plant, production line or hardware rig) is often a make-or-break bet.

Get it wrong, and you burn through capital on a one-off facility that still leaves too many questions unanswered. Get it right, and every dollar after can go into replicating and scaling a proven design, rather than reinventing the wheel.

So, in today’s industrial build-out, most deep-tech companies don’t stall on physics—they stall on replication and financing. The first plant absorbs the capital; the second never gets cheaper.

This report dives into the strategies and tactics to flip that script—engineering and planning the first industrial asset so every subsequent unit is faster, cheaper, and genuinely lender-friendly.

We examine the engineering patterns (spec freeze, copy-exact boundaries, modular envelopes), the operational themes (instrumentation and ramp-up practices), and the capital stack that shifts spend from invention to replication.

We draw lessons from climate, energy, and advanced manufacturing teams that turned Plant #1 into a repeatable product—where they standardized and where they deliberately left room to learn.

By the end, you’ll have a grounded strategy to move from FOAK risk to NOAK economics and to recognize the conditions under which Capex truly becomes a growth engine.

1. First-of-a-Kind vs. Nth-of-a-Kind: The Power of the Learning Curve

Building something that’s never been built before is inherently expensive. A first-of-a-kind (FOAK) facility – whether it’s a fusion reactor, a battery recycling plant, or a biomanufacturing line – almost always costs far more than later copies of the same design. The reasons range from lack of scale economies to unforeseen engineering challenges.

But a well-known phenomenon in industrial technology offers hope: the learning curve. With each doubling of cumulative production, the unit cost of a new technology tends to fall by a constant percentage, known as the learning rate. Solar panels, for instance, have exhibited a ~20% cost reduction for every doubling of installed capacity, and lithium-ion batteries around an 18–19% reduction. In other words, the more you build, the cheaper and more efficient it gets to build the next one. This isn’t automatic magic – it’s the result of learning by doing, process improvements, and economies of scale.

The trick for deep tech startups is to harness this effect even at small scales. You want your FOAK project to generate the knowledge and processes that make your nth project cheaper by design.

Consider advanced nuclear reactors: the U.S. Department of Energy projects that repeat deployments (“Nth-of-a-kind”) of next-gen reactors could reduce capital costs by 40% compared to the prototype plant. That kind of cost decline can be transformational – turning an unviable project economics into a profitable venture – but it only happens if the lessons of the first build are captured and applied.

Yet history shows that cost declines are not guaranteed. In fact, an MIT study of nuclear plant construction found a sobering result: in some cases, nth-of-a-kind units were more expensive than the first, due largely to “soft” indirect factors.

Each new project had to relearn lessons or adapt to new local conditions, causing scope creep and design changes that erased expected savings. The takeaway? Standardization is key.

The MIT researchers concluded that sticking to a standardized design and avoiding site-specific redesigns is critical to realizing cost reduction – recommending strategies like offsite modular fabrication and assembling plants from factory-made subcomponents. If every new build is treated as a bespoke project, you forfeit the learning-curve benefits.

In contrast, look at industries that obsess over replication. The semiconductor sector offers a famous example: Intel’s “Copy Exactly!” strategy. Beginning in the 1980s, Intel perfected its chip fabrication process in one facility, then duplicated it precisely across its fabs worldwide [3][4].

Engineers would replicate even seemingly trivial variables – the type of floor tiles, the humidity and cleanroom protocols, even the color of workers’ gloves – to ensure that a fab in Arizona produced chips indistinguishable from those in Oregon [5][6]. This fanatic standardization paid off by eliminating

Read more

The hot rounds; the 2 a.m. ‘Are we in?’ texts.

You can hear the market breathing hard again, elbows out, repricing the future by the hour. Artificial intelligence is, at once, the most capital-hungry technology of the last generation and the most prosaic story in enterprise software on the factory floor.

One side of the market looks like sovereign project finance; the other looks like a classic, sweaty block-and-tackle: tickets closed faster, denials overturned, scrap reduced, days sales outstanding pulled forward.

We have been here before. Platform shifts inflate expectations faster than cash flows can catch up, public markets get skittish, and venture cyclicality begins to feel like a law of nature.

Every so often, however, the market rediscovers a wedge—an operating model that turns exuberance into earnings.

In mobile, it was distribution moats and payments; in cloud, it was usage-based pricing and land-and-expand. In AI, the wedge increasingly looks vertical, not horizontal. The portfolio is a barbell: at one end, eye-watering frontier-model rounds that concentrate risk; at the other, industry-specific AI that converts domain constraints into defensible software margins.

Gravity well: the skyscraper phase

Start with the gravity well. Anthropic raised $13 billion at a $183 billion post-money, tripling its March mark, with an annualized revenue run rate crossing $5 billion in August and Claude Code alone pacing at a $500 million run rate.

Demand reportedly topped $25 billion, with a syndicate that blended crossover giants and Middle Eastern capital. The subtext is capital intensity: building frontier models now resembles hyperscale infrastructure, with cash burn measured in data centers rather than headcount.

For venture funds without compute contracts in their back pocket, these rounds are both thrilling and binary. Either the model providers keep compounding and compress downstream margins, or they reset and everything from late-stage marks to secondaries reprices. It is a skyscraper—rare, expensive, impossible to ignore. But skyscrapers do not make a city livable for everyone; they define the skyline for a handful of owners.

Unless you can secure model supply chains, bargaining power in the cloud, and global distribution leverage, the platform layer is a spectator sport.

Plumbing vs. Promises: a Darwinian sort

The valuation regime is telling on itself. Private tags at the high end have outpaced what history suggests the U.S. IPO machine can routinely absorb, even on an inflation-adjusted basis.

That is not an indictment of fundamentals so much as an admission that our old exit plumbing was designed for smaller animals. If and when these towers list, the syndicate will have to turn up the water pressure for a building taller than any of its pipes were built to serve.

You can believe in AI’s secular power and still be honest about the plumbing. In Benjamin Graham’s long-familiar framing, the voting machine is working overtime; the weighing machine will have its say later.

Call it a bubble if you like. I would call it a Darwinian sorting mechanism.

And here is the question:

Read more

Big TAM vs. Small Niche: Venture Capital’s Bias

Venture capital, by its very nature, is governed by a power-law distribution of outcomes: a handful of big winners must offset the many that do not succeed. This structural truth naturally encourages a “swing big or go home” mentality.

In practice, many firms apply a simple rule of thumb: the target market should already be substantial — often measured in the tens of billions — to justify the risk.

If the total addressable market doesn’t already measure in the tens of billions, the pitch deck rarely makes it past the first meeting.

While understandable, this way of thinking can make it difficult for ventures focused on narrower or more specialized markets to secure backing.

Subscribe now

Yet history repeatedly shows that large outcomes do not always begin with large markets. Some of the most enduring businesses started in what were, at the time, considered unremarkable niches: Amazon began as an online bookstore, Facebook launched on a single campus, and Intel first produced memory chips before pivoting to processors.

In each case, the company used its foothold to build expertise, relationships, and defensible advantages — expanding outward from a position of strength.

In the world of deep tech and industrial innovation, this dynamic is often even more pronounced.

A novel material or hardware component seldom emerges into a ready-made, multibillion-dollar market. More often, its first adoption occurs in a tightly defined segment where its unique advantages are undeniable. Ironically, an insistence on large upfront markets can lead investors to overlook businesses that may, in time, create an entirely new market or expand a small one into something far larger.

Subscribe now

What is sometimes missed is that capturing a modest market well can yield durable strategic value. A company that becomes the clear leader in a mission-critical niche can maintain pricing power, healthy margins, and deep customer relationships — all of which lay a strong foundation for expansion into related markets. In many cases, such companies ultimately become attractive acquisition candidates for incumbents who rely on their technology to stay competitive.

Owning one mission-critical niche can be immensely valuable: pricing power, sticky customers, steady cash flow, and eventual acquisition interest. A $300 million exit after eight years may feel tame compared to a decacorn dream, but for early backers in at a $20 million valuation, it’s a clean 10–15× with less dilution and far less drama.

Taken together, this structural preference for large initial markets can lead to systematic underinvestment in segments that appear too narrow — yet these overlooked areas may reward those willing to do the patient work.

Subscribe now

A deep-tech company that secures leadership in a focused niche often faces fewer imitators than any successful consumer business might, and with less competition for capital, it can build its position with resilience. By the time mainstream capital notices, these founders frequently hold a commanding lead in talent, technology, and trusted customer relationships.

In this analysis, we’ll look at a series of real case studies — companies that have become meaningful in revenue, funding, or industrial impact without starting in obvious billion-dollar arenas. These cases illustrate a simple but often neglected truth: addressing a “small” problem with care and discipline can yield strong, defensible businesses. And they remind us that opportunity sometimes lies precisely where others have chosen not to look…

Let’s dive in.

✨ This Analysis is Reserved for Our Premium Members

To read it, unlock The Scenarionist Premium today.

Subscribe now

Becoming a Premium Member of The Scenarionist means you also get full access to our complete archive of Deep Tech intelligence, actionable Playbooks, rigorous VC Guides, and founder-ready strategies you won’t find anywhere else — all based on our independent research, original deep dives, and exclusive insights with the world’s top Deep Tech experts.

If you’re serious about Deep Tech and want a real edge in practical knowledge and strategic thinking, The Scenarionist Premium is the one resource you can’t afford to miss.

👉 Join The Scenarionist Premium today — and level up your Deep Tech advantage!

Subscribe now

Owning the Niche, Earning the Multiple

In Deep Tech, the companies that endure often begin in places too narrow, too complicated, or too “unsexy” for the pattern-matching crowd to notice.

HZO, Phononic, and Boston Materials. If there is a lesson here, it is that

Read more

In Chapter 1, we explored the concept of “engineering demand” in the deep-tech and industrial innovation world, emphasizing how early commercial signals, partnerships, and structured commitments can de-risk the journey toward building factories. We introduced the idea that meaningful engagement with potential customers and stakeholders should begin long before you pour concrete for your production line.

But how do you turn those early conversations into concrete data and commitments that propel you from lab prototype to a true industrial operation?

The answer often lies in the pilot project—the crucible where you take your lab-validated concept and test it under real-world conditions, bridging the gap between “it works in the lab” and “we can justify building capacity at scale.”

Below, we’ll delve into every aspect of designing, financing, and executing an industrial or deep-tech pilot in a way that not only proves your technology but also generates tangible market traction. We’ll start with the fundamentals of why pilot projects matter, how to select the right partners, and how to structure the pilot with an eye on the final commercial goal. Then we’ll transition into more advanced insights—such as the Adoption Readiness Level (ARL) framework, bridging the dreaded gap between a successful pilot and real market uptake, and eventually moving from pilot lines or microfactories to full-on manufacturing.

Just as in software, where a successful MVP is the stepping stone to scale, in deep tech, the pilot can be the pivot point that converts potential into actual demand.

Done right, this approach can accelerate your journey to production, lock in anchor customers with contractual commitments, and solidify your industrial flywheel—where each successful pilot iteration boosts investor confidence, sharpens market interest, and paves the way for commercial success.

Let’s dive in.

Subscribe now

✨ This Insight is reserved for Premium Members.

By joining The Scenarionist Premium, you’ll unlock full access to this Insight, along with our in-depth Venture Guide Series—a collection of strategic frameworks and case-based insights designed to help you build and back exceptional deep tech companies, and The Deep Tech Negotiation Playbook Series, where we unpack the tactics, levers, and deal dynamics that define successful founder–investor negotiations in complex, science-driven ventures.

Subscribe now

1. Pilot Projects: The Crucible of Demand and Product Fit

I’ll never forget visiting a small robotics startup, fresh out of a top-tier engineering program. Their lab prototype was captivating—an autonomous manipulator that looked like it could go head-to-head with solutions from much larger, well-established companies. Investors were buzzing, convinced this tech had the potential to transform robotic assembly lines.

But when I asked the founders how they planned to test it in a real factory—where dust, downtime, unpredictable shift changes, and complex throughput could throw everything off—they just stared at me, unsure how to respond.

Not long after, a senior partner at a VC firm gave them a dose of reality: “Show us it can run continuously in an actual production environment, and then we’ll talk about a serious round.” That was their wake-up call—a slick lab demo wasn’t going to cut it.

And that’s exactly the purpose of a pilot project: to take your invention out of the clean, controlled lab and drop it into the messy, unpredictable world of real manufacturing workflows.

1.1 The Role of the Pilot Project

A pilot project is the proving ground where a deep tech concept transitions from “this works in the lab” to “this has commercial viability.”

This stage often uncovers hidden pitfalls:

• Performance Gaps: Technologies that shine in the lab don’t always scale linearly. A pilot often exposes performance bottlenecks—whether in production throughput, material durability, or process efficiency.

• Reliability Concerns: Running a prototype continuously for weeks or months reveals reliability flaws that would never surface in a short bench test. This is exactly why major industrial buyers or corporate investors want to see extended runtime data before trusting your solution at scale.

• Economic Feasibility: Even if the core physics or chemistry holds up, industrial partners need to evaluate cost structures, potential ROI, and how easily the technology can integrate into existing workflows without causing major disruptions or budget overruns.

• Investor Confidence: Finally, a pilot backed by tangible metrics and enthusiastic partner feedback becomes rocket fuel for fundraising. One investor friend of mine calls it “the difference between a dazzling pitch deck and a real business.”

Think of the pilot as your minimum viable factory—just on a smaller scale.

If it succeeds, it helps bridge the critical “credibility gap” that often holds back hardware and industrial startups: you’re no longer just an impressive lab experiment—you’re a tested, validated player in the market.

Read more

More importantly, early demand creates alignment. When investors, regulators, and pilot partners all begin to see the same signals—real market interest, credible adoption pathways, well-defined use cases—the road to scale becomes not only clearer, but less risky.

You’re not just building something impressive. You’re building something wanted.

Subscribe now

There’s a scene that plays out quietly—but crucially—across the corridors of industrial innovation.

A young startup has perfected a new material, or a cutting-edge robotics line, or perhaps a breakthrough in biotechnology. The lab tests shine. Investors are intrigued. The vision is clear.
And yet, a question lingers—often too late: who exactly is ready to buy this, and when?

Unlike software, where a few lines of code can launch an MVP, the world of deep tech requires factories, supply chains, and certifications—substantial investments well before the market has truly responded.

This is the first chapter in a two-part series for those building or backing physical, industrial, or scientific technologies—and who want to bake in market traction from the start.

In this first part, we focus on a foundational challenge: how do you engineer demand before you build capacity?
Not through hype or premature commercialization, but by generating meaningful early signals—relationships, partnerships, and structured commitments—that shape your roadmap and reduce downstream risk.

We’ll address strategic questions such as:

• What are the core pillars of demand engineering in industrial innovation?

• How do you convert early interest into tangible signals?

• What frameworks help align technical development with real commercial pull?

• How can regulation act not as a barrier, but as a catalyst for demand?

• And what kind of team structure best supports a demand-led growth strategy in deep tech?

Subscribe now

Why This Matters—Even at the Earliest Stages

If you’re working on something truly new—a next-gen composite, a bioengineered material, a quantum sensor—your instinct may be to stay heads-down until the technology is fully proven. The science comes first. The product second. Then the market.

But in industrial innovation, waiting too long to engage potential buyers can create silent risks.

Markets aren’t passive.
They’re shaped by timelines, procurement cycles, technical standards, and shifting regulatory environments.
And by the time your product is ready, your window might be narrower than you expected.

That doesn’t mean rushing to sell something half-baked.
It means inviting the right stakeholders into the development process early enough that their needs shape your decisions.

It’s the difference between building something for the market, and building it with the market.

Demand in deep tech doesn’t start with a product launch.
It starts with a conversation—with a partner, a future buyer, or a technical champion who sees what you’re building and says, “If you can make this work, we want in.”

✨ This Insight is reserved for Premium Members.

By joining The Scenarionist Premium, you’ll unlock full access to this Insight, along with our in-depth Venture Guide Series—a collection of strategic frameworks and case-based insights designed to help you build and back exceptional deep tech companies, and The Deep Tech Negotiation Playbook Series, where we unpack the tactics, levers, and deal dynamics that define successful founder–investor negotiations in complex, science-driven ventures.

Subscribe now

The Industrial Flywheel: How to Engineer Demand Before You Build Your Factory | Chapter 1.

In the software world, you spin up an MVP, put it in front of users, iterate in quick sprints, and dial up server capacity as traffic grows. It’s all seamless and agile. In deep tech, though, you’re dealing with a different kind of creature. Factories come with colossal price tags and real-estate footprints.

Once you pour capital into constructing an industrial facility—say, advanced robotics lines, microfabrication foundries, specialized chemical or materials processing plants, or biotech labs—you’re suddenly staring down:

• High fixed costs: real estate, specialized equipment, supply chain overhead.

• Long lead times: building a factory could take anywhere from 6 to 24 months, plus extra time for regulatory and environmental approvals.

• Complex risk: your technology might not scale linearly from bench to industrial volumes; pilot data may skip over real-world production quirks.

In software, “move fast and break things” can pan out just fine. If you break the code, you roll back and push a new build. In deep tech, breaking things might set you back hundreds of thousands of euros in advanced materials or specialized experiments. That’s why your iteration cycles run slower—though the principle of early validation is just as crucial.

Deep tech and SaaS might seem like night and day. Software scales on tiny incremental costs; hardware demands a massive upfront commitment. Yet over the last decade, SaaS founders have unleashed a bag of “growth hacks” and operational frameworks geared toward derisking product–market fit and rallying those early demand signals. We can draw inspiration from these strategies—while acknowledging hardware or industrial solutions can’t simply carbon-copy every SaaS go-to-market trick.

One major takeaway from SaaS is continuous engagement with potential users. In deep tech, that can mean staying in tight communication with pilot partners and prospective buyers long before the cement starts pouring on your factory floor.

So how do we systematically engineer that demand?

What if your factory could sell before it exists?

This Insight explores a new approach for modern industrial pioneers—those who don’t just build machines, but engineer momentum. It’s about creating market gravity early, validating real demand, and launching with leverage.

Because before the factory rises, the flywheel has to spin.

Read more