Deep Tech Briefing is the weekly independent intelligence for decision-makers operating across the Industrial Frontier.

Each edition turns fragmented signals across frontier sectors into market context, allocation implications, strategic watchpoints, and the clarity required to compound knowledge into capability.

Subscribe now

2026 has been a year in which the financing architecture around Deep Tech has become harder to ignore.

Companies are raising larger rounds, entering public markets, expanding manufacturing capacity, and building infrastructure whose capital requirements extend well beyond the traditional venture cycle. Yet one part of the capital stack remains notably thin.

Less than one-tenth of the disclosed funding raised by European Deep Tech companies this year came in the form of debt.

It is a European data point, but the question it raises is global: what conditions would allow debt to play a larger role in Deep Tech?

This week, The Big Idea asks whether the answer lies in stronger guarantees and more specialized lenders—or whether debt simply belongs to fewer stages, assets, and business models than the market often assumes.

Subscribe now

Beyond this, the edition maps more than 40 milestones across AI interconnects, battery storage, autonomous logistics, post-quantum security, robotics, quantum validation, advanced nuclear systems, fusion magnets, photonic networks, critical-mineral recovery, synthetic fuels, and distributed AI infrastructure.

The macro layer follows with the forces shaping market access: Europe’s Cyber Resilience Act, industrial access to research infrastructure, the UK’s proposed £1 billion pension-backed scale-up fund, Australia–Japan quantum cooperation, the Philippines’ emerging launch market, asset-level economics for industrial AI, and new regulatory pathways for gene-edited crops.

Finally, the edition then closes with 10 startups selected for how closely they map to this week’s most consequential frontier shifts.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Deep Tech’s Debt Desert

9.2%. Less than one-tenth of the disclosed funding raised by European Deep Tech companies in 2026 came in the form of debt.

The number comes from Tech.eu’s latest 2026 funding snapshot. It is a European data point, but the question it raises is global: what conditions would allow debt to play a larger role in Deep Tech? Do we need better indicators, stronger guarantees, more specialized lenders—or should we accept that debt applies only to certain stages, assets and business models?¹

For those immersed in Deep Tech, these questions have become a recurring part of the conversation. They surface when founders consider dilution, when investors build capital plans for industrial scale, and when policymakers look for ways to mobilize private capital. This week’s data offers a useful occasion to examine them more closely.

One possible response is to reach for a “new menu”:

Read more

Subscribe now

This week, I sat down with Tobias Egle, Senior Associate at Fine Structure Ventures. We explored how advanced materials are becoming increasingly critical to photonics, why foundry compatibility and manufacturing risk matter as much as laboratory performance, how photonics startups can shorten lengthy development cycles, and which customer and foundry commitments provide credible early validation.

Key takeaways from the episode:

BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE

Materials Are Reshaping Photonics

Photonics is becoming a critical part of the infrastructure required to move increasingly large volumes of data. Within that stack, three areas stood out throughout our conversation: lasers, modulators, and packaging.

Each depends on materials, but a compelling solution does not begin with the material itself. It begins with the performance constraint the material can remove.

For instance, a modulator converts an electrical signal into an optical one. Conceptually, the function is simple. Strategically, it influences two of the most important metrics in optical interconnects: energy per bit and bandwidth density.

Energy per bit measures how much energy is required to encode information into the optical domain. Bandwidth density reflects how much information can be pushed through the optical pipeline.

This is where innovation can become commercially meaningful. A new material creates value when it enables better performance at a point in the stack where the industry is actively seeking faster and more energy-efficient solutions.

The material is not the end product, it is what allows the component to address a critical system-level constraint.

Performance, however, is only one side of the challenge. The material must also be turned into something that a semiconductor fab can integrate into its process and manufacture at high yield.

Raw Materials, Supply Chains, and Markets

Photonics bottlenecks do not begin only at the device or fabrication level. In some cases, they extend all the way back to the availability of the underlying materials.

Indium phosphide

Indium phosphide is a key active material for producing lasers, which are expected to become increasingly important as industry roadmaps move toward co-packaged optics.

The challenge is that indium is generally obtained as a co-mined material rather than through a standalone supply chain. This means that the bottleneck can extend beyond wafer production to the availability of the raw material itself.

This illustrates a broader principle in deep tech: a system-level bottleneck can originate far upstream. Even when the need for more devices is clear, growth may still depend on access to specialized materials and reliable sources of supply.

Beyond data centers

AI data centers are a major market for photonics, but they are not the only environment in which new materials and components can create value.

Biosensing presents a different set of requirements. Raw performance may be less important than the ability to integrate photonic components into a broader biological or sensing application.

Quantum technologies can also provide an early proving market.

These applications may require extremely low optical loss because every lost photon can affect performance. Volumes may remain limited, but customers can be willing to pay for components that meet unusually demanding specifications.

Defense can serve a similar role for technologies based on specialized processes. This sector may be more willing to support the transition from laboratory production to an early manufacturing process.

From Lab to Manufacturable Component

A working laboratory device is only the beginning of the company-building process. For a photonics startup, the real challenge is turning that device into a component that can be manufactured at high yield, qualified within a process, and supported by a clear data sheet, proven reliability, and a viable supply chain.

First, a startup should not focus on selling an “innovative material.”

Customers buy a laser, modulator, or other component with a defined data sheet, proven reliability, and a supply chain capable of supporting production.

The material may create the underlying performance advantage, but the component is the commercial product.

This distinction shapes the entire business plan.

The fabless path

A startup will generally aim to follow a fabless model, except in the rarest cases, when it secures the resources required to build a specialized fabrication facility.

However, fabless does not make process transfer a simple external expense. Transferring a process to a foundry is a multi-year engineering program that should be treated as a central part of the company’s roadmap.

The journey often begins in a university research facility, where the first device is fabricated.

The next step is usually a multi-project wafer run at a commercial foundry, where components from several customers are pooled to reduce the startup’s tape-out cost.

This gives the startup its first chip from a commercial foundry, which it can measure and iterate on while improving foundry compatibility.

Iteration speed becomes a strategic advantage

The difficulty lies in the time between iterations.

A startup may wait six to nine months, or longer, between tape-out and the return of fabricated material. Once the device is measured, the team must revise the design and begin the cycle again.

These long cycles can cause a startup to get stuck, particularly because it is unlikely to be a priority customer for the foundry.

One way to reduce the turnaround time is to parallelize development.

The company may tape out at two different foundries or organize parts of the engineering process so that several activities advance at the same time.

The goal is to shorten the turnaround time between tape-out, receiving the fabricated material, measurement, and redesign.

For a photonics startup, the ability to shorten this manufacturing feedback loop can therefore become a strategic advantage.

Subscribe now

The Foundry Needs a Credible Volume Story

A foundry does not evaluate a startup only on the quality of its technology. It also evaluates process and contamination risk, future wafer volume, and the opportunity cost of committing engineering hours and tool time.

From the foundry’s perspective, the central question is whether the startup can eventually translate into meaningful wafer volume.

The foundry ultimately wants to understand whether the process could translate into wafers per month, how many, and whether it could eventually use a significant share of the line’s capacity.

This is why relationships and industry credibility matter. A professor, advisor, or early executive with foundry experience can help the startup gain attention and become a higher priority for the foundry.

New materials can create contamination risks

A new material can threaten the integrity of an existing process. For instance, a metal in one layer may diffuse into an adjacent layer and degrade the device’s performance.

Materials such as gold, lithium, or other metals that could contaminate a CMOS-adjacent line may trigger a detailed contamination review.

Where a contamination risk is identified, the foundry may require quarantine tooling, separate wafer carriers, and strict handling protocols.

In other words, for a foundry, the concern is that a contaminating element could compromise the broader manufacturing process and affect the performance of the resulting chips.

This is why few foundries may be willing to accept the risk of introducing such materials into a CMOS-adjacent line.

The right partner may not be a leading foundry

A tier-2 or tier-3 foundry may be more willing to experiment, particularly if it can dedicate an older line or separate equipment to the process.

Such a foundry may accept the risk in the hope of commercializing a technology that could become an important future opportunity.

Even then, the commercial logic must be strong.

Every hour spent supporting an experimental process is time that could have been allocated elsewhere.

The startup must therefore present a credible path toward meaningful wafer volume that can justify the foundry’s engineering hours, tool time, and process risk.

Building an Investable Roadmap Before Full-Scale Production

In photonics, development cycles can last many years—potentially around five years before a qualified and yielding process reaches production. During that time, competing technologies continue to improve.

A startup therefore needs more than a marginal advantage. A useful rule of thumb is the potential to deliver at least a tenfold improvement in a metric that matters to the customer.

The relevant metric will depend on the specific use case. Ideally, the improvement should be even greater.

The technology must still be compelling by the time the process is qualified, yielding consistently, and ready for production.

Early validation must involve real commitment

A letter of intent may indicate interest, but on its own it provides limited evidence of demand. Stronger validation appears when a customer or foundry commits resources.

A paid evaluation or pilot agreement is more credible because it involves payment or the dedication of engineering hours and fab runtime. A development agreement with defined milestones, clear success criteria, and a well-scoped statement of work is stronger still.

A strategic investment from a customer can reinforce that signal further.

The common element is a customer with the skin in the game. The most credible early agreements show that the partner is willing to commit money, engineering hours, fab runtime, or a conditional purchase commitment.

For investors, this demonstrates more than market interest. It can show that the technology is beginning to connect technical progress, manufacturing execution, and a credible path toward commercial adoption.

Disclaimer

All materials published by The Scenarionist are provided solely for informational and educational purposes. They do not constitute financial, legal, or tax advice, nor do they constitute a recommendation, offer, or solicitation to buy or sell securities, crypto assets, or any other assets. The Scenarionist strives to provide accurate information but does not guarantee that its materials are complete, current, or free from errors, and assumes no liability for any reliance placed on them. Any external partnership or sponsored content will be clearly identified as “Brought to you by.” Unless otherwise disclosed, the companies and technologies mentioned do not sponsor The Scenarionist and are not included in its investment holdings. Artificial intelligence tools may be used for operational support and content refinement.

Subscribe now

Deep Tech companies are usually described through the milestones still ahead: qualification, demonstration, certification, industrialisation, factory build-out, or recurring deployment. This perspective can overlook an equally revealing stage, when the technology has already become valuable to a specific counterparty even though the wider business has yet to reach its intended volume, utilisation, or delivery cadence.

At that point, the company may already have something meaningful to offer. A buyer can purchase a component that fits inside an existing system, material for a formal qualification process, engineering work around a full-scale demonstrator, access to a specialised asset, scientific capacity applied to a defined programme, manufacturing know-how, delivered industrial performance, or a claim on output that will become available after new capacity has been built.

The distinction matters because these early forms of demand carry consequences beyond the first inflow of cash. They influence which work must be completed before payment, who finances the remaining development, where technical and operating responsibility sits, and how much flexibility the company retains as it grows. Two announcements carrying similar headline values can therefore represent markedly different positions and execution burdens.

This analysis examines ten models with case studies spanning space, aerospace, advanced materials, industrial heat, quantum computing, biotechnology, carbon removal, and low-carbon manufacturing.

Subscribe now

Together, the cases show how early demand can strengthen qualification, production discipline, technical evidence, infrastructure utilisation, technology-transfer capability, financing visibility, and confidence in future delivery. It can also concentrate the organisation around bespoke requirements, long-duration obligations, capital-intensive assets, or relationships that become difficult to unwind.

The purpose is to understand how value begins to form before scale and how these early choices influence the company developing around the technology. A final comparison brings the ten models onto common ground, examining what is being purchased, when cash may enter, what capabilities may accumulate, and which risks remain as the company moves towards repeatable delivery.

From here onward, the full analysis is reserved for Premium Members.

1. Early Contracts as Operating Decisions

Read more

Deep Tech Briefing is the weekly independent intelligence for decision-makers operating across the Industrial Frontier.

Each edition turns fragmented signals across frontier sectors into market context, allocation implications, strategic watchpoints, and the clarity required to compound knowledge into capability.

Subscribe now

2026 has been a year in which AI infrastructure commitments have expanded into extraordinary physical quantities: gigawatts of capacity, billions of dollars of hardware, and data-center campuses built around the future requirements of frontier models.

This week, AMD agreed to provide the systems behind up to two gigawatts of Anthropic’s future infrastructure, alongside an investment that could reach $5 billion.

The scale is notable. But the structure behind it invites a broader reflection on the way capital, customers, suppliers, and infrastructure commitments are beginning to reinforce one another. That reflection matters today because such commitments are increasingly influencing valuations and investment decisions across semiconductors, cloud platforms, data centers, power systems, and private capital.

Subscribe now

This week’s Big Idea examines how those layers are becoming connected—and what that may reveal about the signals the market is using to measure the AI buildout.

Beyond this, the edition maps more than 80 milestones across semiconductor architecture, industrial robotics, autonomous transport, AI security, photonic networks, battery storage, advanced nuclear, fusion engineering, textile recycling, bio-based chemicals, orbital infrastructure, industrial water, and critical-material processing.

The macro layer follows with the forces reshaping the market: defence-material traceability, resilient clean-tech procurement, civil nuclear market access, faster autonomous-systems acquisition, public AI infrastructure, space regulation, synthetic-content transparency, science funding, and industrial-policy coordination.

The edition then closes with 10 startups selected for how closely they map to this week’s most relevant frontier shifts, from autonomous logistics and multi-domain defence software to AI materials discovery, perovskite solar, optical switching, and room-temperature quantum memory, followed by 10 Data to Track to sharpen situational awareness before these signals become obvious.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

The AI Compute Loop Eats Its Own Tail

Investors may be treating financially dependent AI commitments as independent evidence of demand.

AMD will supply the systems behind up to two gigawatts of Anthropic’s AI infrastructure while investing as much as $5 billion in the customer and reportedly exploring support for some of its future data-center leases.¹–³

If supplier capital helps finance the buyer whose orders then drive the supplier’s growth, some of the industry’s most impressive demand signals may be considerably less independent than they appear.

Read more

Subscribe now

This week, I sat down with Vincent Berk, Partner at Apprentis Ventures. We explored how AI is broadening the software-builder base and reshaping cybersecurity, why domain expertise is becoming increasingly important as software moves into specialized industries, what creates a defensible moat when products are easier to reproduce, and how founders should think about team composition, technical validation, enterprise sales cycles, and focused go-to-market execution.

Key takeaways from the episode:

BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE

AI Is Expanding Both the Cybersecurity Surface and the Builder Base

Artificial intelligence is changing cybersecurity in two opposite directions.

1. On one side, it is making software easier to build. Founders, operators, and industry experts can now create applications faster, even when they do not come from traditional software backgrounds. This is especially relevant in industrial and highly specialized markets, where the most valuable opportunities are often understood by people with deep domain expertise rather than by generalist software teams.

2. On the other side, the rapid expansion of software is increasing the number of systems that must be protected. A company builds software, someone finds a vulnerability, and another company develops a way to detect or mitigate it. AI does not change that fundamental dynamic, but it simply accelerates it.

More software means more vulnerabilities

AI can support high-quality software development when it is used inside disciplined engineering processes. But companies are also producing more code under tighter timelines, with growing pressure to launch and iterate quickly.

The issue is not simply whether AI-generated code is better or worse. The deeper problem is volume. More software means more applications, integrations, permissions, and potential failure modes.

The concern is therefore not only the quality of individual applications, but the expansion of the software base. When tighter development timelines contribute to lower software quality, the security risk increases further.

Authentication failures, poorly designed permission systems, and unexpected software behavior can all become entry points. As software becomes more embedded in industrial operations, vehicles, infrastructure, and physical systems, those weaknesses can affect more than data. They can affect how the underlying business operates.

AI accelerates vulnerability discovery

AI is also making it faster to search for weaknesses.

A security researcher can inspect software, test common failure modes, and look for vulnerabilities. AI can perform many of the same activities at much greater speed. It may not always be better than an experienced expert, but it can repeat analytical processes across far more code and far more systems.

This increases the overall capacity to search for software weaknesses and accelerates the ongoing cycle of software development, vulnerability discovery, and the creation of new detection and mitigation methods.

The result is a much larger effective workforce capable of searching for weaknesses. Vulnerabilities that might previously have remained undiscovered for longer can now be identified more quickly.

This makes cybersecurity increasingly relevant across a growing range of industries, particularly as AI becomes more deeply integrated with the physical world.

More specifically, as software becomes easier to create, it is moving deeper into sectors that were previously less digitized. Security depends on understanding how a system is supposed to work, what should be permitted, and what kinds of failure are possible.

In increasingly specialized software markets, that knowledge often comes from direct industry experience. Therefore, the people who understand those sectors may be particularly well positioned to become cybersecurity founders.

Domain Expertise Is Becoming the New Entry Point

Cybersecurity is often treated as a field reserved for founders with deep technical backgrounds. That assumption is becoming less reliable.

As AI lowers the barriers to building software, founders with strong industry knowledge can move closer to product creation. They may not have spent years writing code, but they understand how a specific process, system, or market is supposed to work.

That knowledge matters because cybersecurity begins with failure modes.

A security problem emerges when a system behaves in a way that should not be possible. An authentication process fails. A permission is too broad. A piece of software accepts an unexpected input. A device communicates with something it should not trust.

To identify those risks, a founder needs more than general technical ability. The founder needs to understand the operating model behind the system.

Security is embedded in the domain

Every cybersecurity solution is built around an implicit model of normal behavior.

To protect a system, a company must know which actions should be allowed, which should be restricted, and what kinds of behavior indicate that something has gone wrong.

In highly specialized industries, those answers are often not obvious to outsiders.

A founder who understands a particular industrial process may be better positioned to identify domain-specific failure modes that outsiders may not immediately recognize.

The same principle can apply across traditional industries, industrial operations, IoT systems, and connected vehicles.

As software becomes more specific to individual industries, security is likely to become more specific as well.

The market may therefore produce more point solutions: focused products designed to address a particular failure mode, workflow, or operational environment rather than broad platforms attempting to secure everything.

This specialization reflects how software itself is evolving. Bespoke applications can create equally specific security requirements and failure modes.

The New Moats in Cybersecurity

As software becomes easier to build, defensibility becomes harder to prove.

A product may be technically impressive and still become easier to reproduce as software development becomes more accessible. General technical knowledge alone is therefore less likely to provide a durable advantage.

A useful way to frame defensibility is through three elements: process, problem, and people.

Process, problem, people

A process moat comes from knowing how to discover, detect, operate, or solve something in a way that is not obvious from the outside.

A problem moat comes from understanding how a complex system behaves in the real world. This often requires substantial experience with the specific conditions, constraints, and failure modes of that environment.

A people moat comes from trusted relationships. Early-stage products are rarely perfect. Founders need customers who are willing to test incomplete solutions, provide feedback, and tolerate mistakes. Access to those first users can create the initial validation that a startup needs before the market is ready to trust it more broadly.

This is why relationships within a specific industry can be strategically important. They can provide the early access and trust required to test a product, make mistakes, and validate the initial solution.

Real-world performance is a critical test

One of the first differentiators to examine is also one of the simplest: whether the product works outside the lab.

Many cybersecurity solutions are convincing in concept. They combine data sources, identify a suspicious pattern, and appear capable of detecting an attacker.

The difficulty is whether the same approach works inside a real enterprise.

Networks are larger, more fragmented, and more complex than test environments.

A system may perform well on one computer or a small dataset and fail when it must analyze vast numbers of devices, identities, data streams, and connections.

As in the physical world, scalability is therefore part of defensibility.

Team Composition and AI’s Limitations

The quality of a cybersecurity startup depends not only on its technology, but also on the composition and dynamics of its founding team.

At the pre-seed stage, the ideal team is usually small. The conversation suggested a founding team of more than one person and, ideally, no more than three.

However, what matters most is not the number of people. It is how well they work together.

The founders should know one another well enough to challenge assumptions, expose weaknesses, and disagree without damaging the relationship.

They should be able to call out one another’s flaws while maintaining enough focus and trust to work effectively together.

Strong founding teams often combine 3 capabilities.

1. The first is imagination. A team can benefit from someone capable of seeing possibilities beyond the current product: new applications, larger markets, and different ways the technology could evolve.

2. That energy must be balanced by execution. Another member of the founding team needs the executive discipline to reduce the number of possibilities and return the company to its immediate priorities. The team may see ten interesting directions, but it still needs to decide which customer, problem, and market it is building for today.

3. The third capability is domain expertise. At least one founder should understand the industry and the problem deeply. This has become more important as software development has become easier. When the ability to build is less scarce, the quality of the problem insight becomes more valuable.

At its core, technical capability alone is not enough. The team also needs to understand the market it is entering and the specific problem domain in which the product must operate.

AI is powerful, but not universally effective

The same discipline is required when evaluating the role of AI inside the product.

New technologies often appear capable of solving almost any problem before their limitations become visible. AI is still passing through a similar phase.

It is remarkably effective at generating language, knowledge, and code. It can compress a large amount of information into a relatively small model and produce useful output across many different subject areas.

Cybersecurity, however, often depends on a different type of reasoning.

A security system may need to connect a series of failed login attempts with a later successful login, determine whether those events are related, and compare them with behavior across other machines, users, and applications.

That becomes difficult when the events occur far apart in time or across different data sources.

An experiment may work across three controlled data streams. A large enterprise may contain hundreds of thousands of data streams generated by computer systems, identities, and pieces of software.

The technical challenge is not merely identifying an unusual event. It is correlating disjointed events across time and across systems at enterprise scale.

This is where many AI-based cybersecurity products face their real test.

A compelling demonstration may rely on a novel prompt that works in a controlled laboratory environment. That does not prove the solution can identify the same patterns inside a complex enterprise.

Investors therefore tend to look beyond the “AI layer”. The central question is whether the founders have solved the core problems of correlation and scale within their particular problem domain.

AI can help founders build software faster and can assist in developing algorithms to address these problems. But it does not remove the need to understand the underlying architecture of the problem.

The more credible cybersecurity startups are therefore likely to combine an effective founding team, deep knowledge of the problem domain, and a realistic understanding of what AI can and cannot do.

Subscribe now

Cybersecurity Go-to-Market Strategy

A technically strong cybersecurity product does not become a scalable company simply because the problem is real.

Adoption is slow because customers rarely deploy a new security solution across the entire organization from the beginning. They start with a limited test.

They want to know whether the product solves the problem, whether it works inside their environment, and whether it continues to perform as usage expands.

Only after those questions are answered does the customer buy more.

This is the logic of land and expand.

A startup enters through one site or another limited deployment, then grows after the product has demonstrated that it works and scales.

Founders need to reflect this reality in their financial planning. Even when the product works and scales, it may take 12 to 18 months before the company begins to see meaningful traction.

The ideal customer profile must be narrow

Cybersecurity founders can easily begin with an unfocused assumption: everyone has the problem, so everyone can be a customer.

That may be broadly true, but it is not focused enough to support an effective go-to-market strategy.

A startup needs a precise ideal customer profile and a clear understanding of the individual buyer inside that organization.

The company should know who owns the problem, how it will earn that person’s trust, and how it can get in front of the same buyer repeatedly.

Without that focus, the message becomes too broad to attract anyone in particular.

Customer size also matters. Selling to a small company can take as long as selling to a large enterprise because both customers will want to test whether the solution works and scales before expanding its use.

The difference appears after the first deployment.

A small customer may have limited room to expand. A large enterprise can roll the same product out across more locations and at a much greater scale. The initial sales effort may be similar, but the economic opportunity within the larger customer can be significantly greater.

This makes customer selection part of the business model.

Partners cannot replace founder-led sales

Another common assumption is that a reseller or systems integrator will solve distribution.

The logic appears attractive. The partner already has customers, so it should be able to add the startup’s product to its portfolio and generate sales.

In practice, large integrators may already carry vast numbers of products. They have little incentive to invest time in understanding an unknown solution unless they believe it can generate meaningful volume.

The vendors most likely to receive that attention are usually the vendors that are already large.

An early-stage startup should therefore retain control of its initial go-to-market rather than assuming that a partner will create demand and sell the product on its behalf.

Partners may play a role, but founders should not expect them to create the company’s initial traction.

Precision marketing over broad visibility

The same discipline applies to marketing.

Broad brand marketing is a weak substitute for a focused strategy built around a defined ideal customer profile and buyer persona. Trade shows, advertising, public relations, and sales development are only tools.

Their value depends on whether they reach the person responsible for the problem.

The more useful question is not what percentage of the budget should go to marketing. It is whether the company is “shotgunning or sniping.”

A broad outreach approach begins with a generic budget allocation. The company buys ads, attends large conferences, and hires sales representatives without knowing precisely where its target buyer spends time.

A precision approach begins with the target buyer.

The founder identifies the person responsible for a specific security issue inside the type of company the startup wants to serve.

The next step is to understand where that person reads industry news, exchanges ideas, attends meetings, and builds trust with peers.

Sometimes the right channel will be a focused conference. It may instead be a smaller industry group, a standards meeting, a technical community, or a specialized publication.

The most valuable environments are often those in which buyers validate products among themselves.

A cybersecurity company may begin winning customers inside one vertical not simply because the product appears suited to that industry, but because the security professionals within that vertical know one another, meet regularly, and create internal validation.

Once that pattern becomes visible, the company can focus on the places where those conversations happen.

The marketing budget should follow that insight.

Travel, events, articles, advertising, and sales development should be selected according to their ability to reach a known buyer.

If the company cannot identify that buyer with precision, it has probably not completed enough market research.

A realistic financial and go-to-market model should therefore account for long sales cycles, focused customer selection, direct access to the buyer, and the gradual economics of land and expand.

Disclaimer

Please be aware: the information provided in this publication is for educational purposes only and should not be construed as financial or legal advice or a solicitation to buy or sell any assets or to make any financial decisions. Moreover, this content does not constitute legal or regulatory advice. Nothing contained herein constitutes an offer to sell, or a solicitation of an offer to buy, any securities or investment products, nor should it be construed as such. Furthermore, we want to emphasize that the views and opinions expressed by guests on The Scenarionist do not necessarily reflect the opinions or positions of our platform. Each guest contributes their unique viewpoint, and these opinions are solely their own. We remain committed to providing an inclusive and diverse environment for discussion, encouraging a variety of opinions and ideas. It is essential to consult directly with a qualified legal or financial professional to navigate the landscape.

Deep Tech Briefing is the weekly independent intelligence for decision-makers operating across the Industrial Frontier.

Each edition turns fragmented signals across frontier sectors into market context, allocation implications, strategic watchpoints, and the clarity required to compound knowledge into capability.

Subscribe now

A seed-stage company is usually defined by what it has yet to build: its team, technology, customers, and operating system.

This week, a robotics company entered the market from a very different starting point.

The headline is difficult to ignore: a unicorn at seed.

Yet the more important question is not how much capital the company raised. It is what had already happened before the financing was announced.

Subscribe now

This week, The Big Idea examines a less visible route through which deep tech companies can enter the market—and what it could mean for founders, investors, corporations, and the institutions where technical capability is built.

Beyond this, the edition follows more than 50 developments across defence, robotics, quantum, energy, semiconductors, industrial biotechnology, advanced manufacturing, and AI infrastructure.

Capital continued to move toward physical systems, but the most valuable evidence came from execution: major contracts, operating deployments, customer orders, regulatory progress, production scale-ups, and strategic infrastructure commitments.

The macro layer maps the policies and institutions influencing the next stage of industrial growth, including new support structures for energy, semiconductors, defence technology, critical minerals, and compute infrastructure.

The edition closes with 10 companies to watch across robotics, energy, quantum, defence, advanced materials, and industrial biotechnology, followed by 10 Key Data points highlighting the scale, production capacity, and operating evidence behind this week’s most consequential developments.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Subscribe now

The New Route to a Seed Unicorn

This week, a robotics company came out of stealth with $300 million in seed capital and a $1.1 billion valuation. The headline is striking: a unicorn at seed. Yet the more consequential signal may lie in how the company reached that starting point—and whether its formation suggests that the next generation of deep-tech companies could emerge through a different institutional route.

Read more

Subscribe now

This week, I sat down with Sabrina Sasaki, Partner at Monozukuri Ventures. We explored how scientific founders can move from laboratory validation to industrial adoption, why milestones must reflect the physical complexity of the product, and how Japan’s manufacturing ecosystem can support international commercialization through pilots, co-development, and strategic partnerships.

Key takeaways from the episode:

BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE

Physical AI Becomes Investable When Hardware Meets Industrial Reality

Physical AI is often discussed as the next frontier of artificial intelligence: a world in which machines can perceive, interpret, and act within physical environments.

But from an investment perspective, the category cannot be reduced to smarter robots or more capable automation systems. Its real significance lies in the convergence of hardware, software, data, manufacturing, and industrial adoption.

Hardware gives an AI system access to the physical world. Sensors allow it to observe. Actuators allow it to respond. Robotic systems allow it to perform tasks. Yet the hardware alone does not necessarily create a defensible company.

A growing part of the value comes from what happens after the physical interaction has been captured.

Software must interpret the information generated by the system, identify which signals matter, and convert those signals into useful operational decisions. In industrial environments, this may mean supporting predictive or preventive maintenance, or helping operators understand what action should be taken next.

This must shape the logic of venture building.

A hardware startup cannot assume that engineering complexity will automatically translate into commercial differentiation. The technology must be connected to a broader system of data, intelligence, and business value.

At the same time, the company must demonstrate that the technology can perform effectively in real customer environments, not only under controlled laboratory conditions.

That requires more than a working prototype. It requires a team capable of learning from customers, adapting to uncontrolled environments, financing capital-intensive milestones, and choosing partners that reduce rather than increase execution risk.

A Prototype Is Not Yet a Commercial Solution

Deep tech companies often begin in laboratories, research institutions, or highly controlled engineering environments.

That is where the underlying science can be tested. It is where researchers can isolate variables, measure performance, and demonstrate that a technical concept is possible.

This work is necessary. But it can also create an incomplete sense of validation.

Researchers naturally speak with other researchers. They encounter similar technical problems, use a common vocabulary, and operate within environments that share many of the same assumptions.

A new component or system may therefore receive strong interest from other universities, laboratories, engineers, or designers building specialized prototypes. Those early users may understand the technical achievement immediately.

The difficulty is that validation inside this community does not necessarily prove that a large industrial customer has a commercially meaningful problem.

A technology can be valuable to another research team and still have a limited path toward broader commercial application.

Leaving the controlled environment

The transition becomes particularly difficult when the technology involves robotics, physics, chemistry, or industrial automation.

Inside a laboratory, the founders can control the environment. They can determine how the system is positioned, which variables are introduced, and how each experiment is conducted.

A customer environment operates differently.

Conditions may change, unexpected variables may affect the system, and the founders may no longer be able to control the experiment in the same way.

Field robotics makes this gap especially visible. A machine that performs perfectly under controlled conditions may behave very differently when the environment around it changes continuously.

The same applies to materials and chemical systems. Physical and chemical processes may behave differently when they are moved from a controlled laboratory into a real customer environment.

This is why a perfect laboratory prototype is not necessarily close to a commercial product.

One purpose of early customer engagement is not simply to receive confirmation that the technology is impressive. It is to discover which assumptions fail once the system enters the real world.

Building toward the commercial problem

At the earliest stages, the startup may not be able to build the version that a large corporation will ultimately purchase.

That final product may require too much capital, too much time, or too much engineering work. The level of maturity and performance expected by the customer may be impossible for a young company to achieve immediately.

The startup still needs to demonstrate progress.

An effective approach is to identify shorter milestones that move the technology closer to the commercial need.

A second version of the prototype may improve one critical part of the system. Each milestone can test and improve part of the solution while showing customers that the technology is advancing.

These steps do not constitute full commercial traction. They show that the company is learning in the right direction.

Investors need evidence that the founders understand the gap between what currently exists and what a customer will eventually pay for.

They also need to see that the team can break that gap into milestones that are technically credible and appropriate to the scale and resources required by the product.

Learning from customer feedback

One of the hardest transitions for scientific founders is learning how to respond to negative feedback.

Positive feedback is comfortable because it confirms the original hypothesis. It reinforces the value of the science and supports the idea that the founders are building the right solution.

Negative feedback can be especially useful.

It may reveal that the customer does not experience the problem in the way the founders expected. It may also challenge the original assumptions about the application or show that the solution needs to adapt to what the market requires.

The point is to apply the same willingness to test assumptions to the market.

Founders can treat customer interactions as another source of evidence. They can test assumptions, examine contradictions, and adjust the product when reality does not support the original design.

Subscribe now

Milestones Must Match the Scale of the Product

It is difficult to discuss comparable roadmaps for physical AI or industrial deep tech. The capital required to develop a sensor is not comparable to the capital needed to build a large robotic infrastructure system.

An actuator can sometimes be prototyped using existing components. A new tunneling platform, energy system, or aerospace product may require substantial resources before a credible minimum viable product can even exist.

The investment stage alone does not determine what progress should look like. The scale and technical nature of the product are equally important.

At pre-seed, the team is the main evidence

The initial market thesis may change. The use case may evolve. The founders may discover that their differentiation is different from what they originally believed. Customer conversations can redirect the product, and early experiments can expose limitations that reshape the entire company.

For that reason, pre-seed investment is often primarily an assessment of the founders and the relationship among them.

The important questions concern how the team works under pressure, how responsibilities are divided, and how the founders respond when experienced people challenge their assumptions.

Accelerators, mentors, and advisors can be useful partly because they create this pressure. They force founders to explain why the company is different, where the value comes from, and what evidence supports their claims.

The purpose is not simply to improve the pitch. It is to observe whether the founders can process criticism without becoming defensive or losing conviction.

Early-stage company building requires both.

A team must be confident enough to pursue an uncertain technical vision and flexible enough to change when the evidence demands it.

Seed stage

By seed stage, investors expect more than a scientific concept, but what counts as meaningful progress varies widely.

For a component company, it may be possible to build multiple prototypes, test them with customers, and improve the design relatively quickly.

Off-the-shelf parts may reduce development time, and the startup may be able to reach a functional demonstration with limited resources.

For a company developing a more complex infrastructure technology, each prototype may be expensive. The company may need specialized equipment, large testing environments, or physical installations before it can prove that the system works.

The first few units can cost disproportionately more than later production.

The relevant question is whether the company has defined milestones that reflect the scale of what it is building.

A credible plan must show what can be learned from each unit of capital. It must explain which technical risks will be retired, which assumptions will be tested, and how each development stage brings the company closer to a product that customers can adopt.

Japan’s Industrial Ecosystem and Opportunities for Startups

Japan remains an attractive environment for industrial and manufacturing technologies because much of its competitive strength exists below the level most founders initially see.

International entrepreneurs usually recognize the country through its large consumer brands. They know the automotive companies, electronics groups, and industrial names that became symbols of innovation during previous decades.

But many of those companies built their products through networks of highly specialized suppliers.

Small and medium-sized manufacturers developed deep expertise in specific materials, components, processes, and production techniques. In many regions, clusters formed around a narrow category of industrial capability.

Their specialized knowledge and manufacturing capabilities may be valuable resources for startups to access.

Industrial customers rarely behave like early adopters

A corporation will not normally accept technical risk simply because the startup is ambitious. Industrial companies are generally unwilling to take risks on behalf of startups, particularly when evaluating solutions for business-critical environments.

The required quality level is therefore much higher.

This is particularly important when working with large manufacturers, whose reputation has been built around rigorous quality control.

A startup cannot approach these companies with the expectation that they will tolerate an unreliable product while it develops.

Before pursuing a serious industrial relationship, founders must understand the quality standards against which their technology will be evaluated.

Corporate interest does not necessarily indicate commercial progress

Many large companies are still learning how to work with startups. Their internal processes may move slowly. Decision-making authority may be unclear.

The innovation team may be interested in the technology without controlling the budget or business unit required for adoption.

On the other hand, an early-stage company has limited time and limited capital.

A large corporate conversation can appear strategically important because the brand is recognizable and the potential contract seems significant. The startup may invest months in meetings, technical discussions, custom requests, and internal presentations.

Yet the relationship may not move the company toward its real milestones.

Therefore, before achieving product-market fit, identifying meaningful use cases, securing sufficient financing, or developing a stable product, extensive corporate engagement could become a distraction.

This does not mean founders should ignore large companies until they are fully mature. They can begin building the relationship earlier.

They can educate potential partners, share product developments, communicate new use cases, and keep relevant stakeholders informed about fundraising and technical progress.

The distinction is between nurturing a relationship and depending on it.

Conversely, once the startup has reached a greater level of maturity, the conversation with a corporate partner can become more productive.

A company with a stronger product, credible customer use cases, and a clearer market position is better prepared to engage with an industrial corporation.

Before reaching that point, founders can keep potential partners informed about the company’s progress, applications, customers, and fundraising activity without relying on them to drive the startup’s immediate milestones.

This is especially important because some corporations may not fully understand how to work with companies that have not yet reached product-market fit.

The objective is to pursue industrial partnerships at a stage when they can genuinely support the company’s development.

The Right Industrial Partnership Depends on What the Company Needs

There is no single model for working in industrial B2B markets. The right structure depends on the technology, the resources required to build it, and the strategic importance of the market.

For advanced materials and semiconductor companies, collaboration with an established manufacturer can be highly valuable. These startups may need equipment, laboratories, process knowledge, and production infrastructure that would be unrealistic to recreate independently.

A larger industrial partner may already possess the machinery and technical teams required to test the technology at a different scale.

In those situations, co-development can create interesting opportunities.

The startup contributes a new technical approach. The manufacturer contributes facilities, production knowledge, and the ability to translate the concept into a repeatable process.

The challenge is negotiating partnerships that allow both sides to test and develop the relationship effectively.

One option is to begin with a limited agreement that allows both parties to test the relationship. The collaboration may run for a defined period to understand whether the technical work and working dynamics are effective.

This can reduce uncertainty.

Both sides can use this period to understand whether the collaboration works and whether it can support further technical development.

The purpose of the initial relationship can be to create evidence.

It should demonstrate that the companies can build something together and provide a basis for deciding whether a deeper partnership makes sense.

International commercialization considerations

Opening an operation in another country consumes management attention and financial resources. It also requires the company to commit significant time and organizational effort to that market.

A local presence becomes rational when the company’s strategy is genuinely tied to a specific ecosystem.

This may be the case when partners are essential to manufacturing, when the country is a core customer market, or when local grants and industrial partnerships can materially accelerate the business. In other situations, a local representative or commercial partner may be sufficient.

In other words, the operating model should follow the company’s real dependency.

For instance, an established industrial partner can provide the infrastructure and capabilities needed to manufacture the product while helping control manufacturing risk according to established standards.

This can unlock resources that would be difficult for the startup to obtain independently. Moreover, public funding may become more accessible when the company has a credible plan to manufacture locally with a respected partner.

Furthermore, a manufacturer that already serves customers in other Asian industrial economies may become a route into those ecosystems.

But the value of these options depends on how well the partnership model aligns with the company’s strategy and technological needs.

A semiconductor component, an advanced material, or a complete robotic system require different resources and different forms of collaboration.

In conclusion, the company must begin with a clear understanding of what it needs from the partner, what it can develop independently, and how the relationship will help it reach the next stage of commercial development.

Disclaimer

Please be aware: the information provided in this publication is for educational purposes only and should not be construed as financial or legal advice or a solicitation to buy or sell any assets or to make any financial decisions. Moreover, this content does not constitute legal or regulatory advice. Nothing contained herein constitutes an offer to sell, or a solicitation of an offer to buy, any securities or investment products, nor should it be construed as such. Furthermore, we want to emphasize that the views and opinions expressed by guests on The Scenarionist do not necessarily reflect the opinions or positions of our platform. Each guest contributes their unique viewpoint, and these opinions are solely their own. We remain committed to providing an inclusive and diverse environment for discussion, encouraging a variety of opinions and ideas. It is essential to consult directly with a qualified legal or financial professional to navigate the landscape.

Deep Tech Briefing is the weekly independent intelligence for decision-makers operating across the Industrial Frontier.

Each edition turns fragmented signals across frontier sectors into market context, allocation implications, strategic watchpoints, and the clarity required to compound knowledge into capability.

Subscribe now

Deep tech markets are often described through inventions: a better reactor, a more capable autonomous system, a new battery chemistry, or a manufacturing process that removes an old constraint.

But technologies do not scale through technical merit alone. They also need contracts, factories, working capital, and financial institutions able to understand long development cycles and strategic risk.

This week, The Big Idea begins there.

Nine governments are working toward a multilateral, sovereign-backed bank for defence, security, and resilience, with the ambition to mobilise up to £100 billion. Yet the real signal is not only the scale of capital it could unlock, but the possibility that it begins to define what becomes bankable across allied defence markets—shaping which companies can finance production, inventories, contracts, and supply-chain expansion before the wider market fully adjusts.

Subscribe now

Beyond this, the edition maps more than 50 company milestones across the deep-tech landscape—from fusion, defence autonomy, and advanced nuclear to energy storage, AI infrastructure, and the industrial systems turning emerging technologies into scalable businesses.

The most revealing developments increasingly appear beyond the laboratory: in criticality, certification pathways, offshore endurance, commercial offtakes, operating batteries, pilot factories, and foundry-compatible processes. Together, they show a market learning to distinguish technical promise from dependable industrial capacity.

The macro layer follows the institutions shaping that transition, from critical-minerals finance and AI assurance to isotope production, cybersecurity infrastructure, naval procurement, aviation rules, and semiconductor talent.

The edition closes with 10 companies to watch across fusion, defence autonomy, industrial water, wildfire intelligence, semiconductors, and long-duration storage, followed by 10 Key Data points highlighting this week’s most consequential shifts and sharpening situational awareness.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Subscribe now

A World Bank for Defence

A new financial institution can shape a market long before its balance sheet becomes large. The decisive influence often begins with eligibility rules, credit memoranda, and covenants that define which risks qualify for capital. Defense technology currently lacks a common underwriting language across allied markets, leaving similar companies exposed to different interpretations by ministries, banks, and investors. The bank announced in Ankara may become the place where that language starts to harden.

Read more

Welcome back to Rumors, The Scenarionist’s pattern-recognition column for the deep tech frontier—where emerging micro-trends across companies, technologies, and capital are connected into category-level signals.

Subscribe now

This is the ninth edition of Rumors. If you are new here, the premise is simple: most important deep tech categories do not announce themselves cleanly. They appear first as scattered signals—a financing here, a technical milestone there, a founder leaving an incumbent, a new buyer pain point, a strange wedge that does not yet fit the standard market map.

Rumors is where we connect those fragments.

This edition looks at atomic-scale process control in advanced semiconductor manufacturing.

The driver is the process margin. As fabs move toward High-NA EUV, GAA, backside power, CFET roadmaps, 3D memory, and advanced packaging, more value is being created inside structures that are thinner, taller, deeper, and harder to measure. A few Ångströms of variation in line edge, film thickness, etch profile, overlay, or buried geometry can become a yield, cycle-time, or ramp problem.

Inside, four early-stage startups are mapped and analyzed across metrology, etch-based pattern refinement, atom-beam lithography, and in-tool sensing.

Beyond it, the edition examines why this control layer is becoming relevant now, how the fab’s error budget is changing, which process steps are absorbing more economic pressure, and what market metrics matter when evaluating tools that sit close to yield.

It also looks at the signals coming from incumbents and advanced-node ecosystems — lithography, etch, metrology, deposition, research hubs, foundries, and memory players — to understand where the existing tool stack is already moving.

Finally, the edition closes by assessing the main adoption risks for atomic-scale process control inside the fab, from tool performance and workflow integration to cost of ownership and incumbent response.

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

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Read more

Deep Tech Briefing is the weekly independent intelligence for decision-makers operating across the Industrial Frontier.

Each edition turns fragmented signals across frontier sectors into market context, allocation implications, strategic watchpoints, and the clarity required to compound knowledge into capability.

Subscribe now

2026 has been a year in which quantum companies have started to move more visibly into public markets. The latest example came just this week with IQM, and that is a peculiar signal in itself: a sector once defined mostly by labs, roadmaps, and national strategies is slowly gaining public benchmarks.

But this week, The Big Idea enters the quantum world from a different angle: the security work required because of it.

If quantum computing becomes powerful enough to reshape chemistry, materials, optimization, and simulation, then the digital economy also has to prepare for what quantum can do to the security assumptions underneath today’s systems.

That is the Quantum-Safe question. And this week offers fertile ground to think it through, because a live-system signal suggests that post-quantum infrastructure is beginning to move from standards language into something that can be tested, inspected, and eventually compared.

Subscribe now

Beyond this, the edition maps more than 40 milestones across defense autonomy, physical AI, inference silicon, energy storage, photonic networks, robotics, PFAS systems, orbital servicing, nuclear proof points, fusion conversion, manufacturing scale-up, direct air capture, data-center power, advanced materials, and silicon-photonics tooling.

The macro layer follows with the forces reshaping the market: defence budgets, unmanned-systems governance, SMR fleet logic, semiconductor diplomacy, LEO satellite cooperation, steel policy, university commercialization, and Mexico’s nearshoring map.

The edition then closes with 10 startups selected for how closely they map to this week’s most relevant frontier shifts, from autonomy and AI infrastructure to energy resilience, industrial remediation, carbon removal, and next-generation power, followed by 10 Data to Track to sharpen situational awareness before these signals become obvious.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Subscribe now

The Post-Quantum Clock Is Ticking

Quantum computing carries one of the more compelling promises in deep tech. Better materials discovery, richer molecular simulation, faster optimization, new methods for drug design, and more efficient modeling of complex industrial systems all sit within the broad opportunity set. The technology could eventually make certain hard problems less expensive to solve and give manufacturers, energy companies, pharmaceutical firms, and logistics networks a new layer of computational advantage.

Yet that upside also creates a practical security question that is becoming harder to postpone, and this week, post-quantum cryptography received a small but visible market signal:

Read more

Subscribe now

This week, I sat down with Sean Mitchell, co-founder and former CEO of Movidius, the fabless semiconductor company acquired by Intel in 2016. Drawing on his founder journey, we explored what it takes to navigate market uncertainty, customer evidence, capital constraints, and timing when building in complex semiconductor markets.

Key takeaways from the episode:

BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE

Start With a Technical Conviction

In 2005, the Movidius founding team was not simply looking for a startup idea in semiconductors. It was looking at a structural inefficiency in computing.

A growing class of workloads was poorly served by existing architectures. Traditional processors could execute instructions quickly, but for these workloads, much of the system’s effort was consumed moving data rather than performing useful computation.

That distinction mattered. The opportunity was to ask whether a different architecture could make these workloads dramatically more efficient.

This was the original conviction behind Movidius: emerging applications would require a more efficient way to process data-intensive workloads, especially as these workloads moved toward constrained computing environments such as mobile devices.

The founders believed that a specialized architecture could lift performance dramatically by reducing the inefficiencies embedded in general-purpose computing.

At the time, however, the market was not yet obvious.

This is an uncomfortable but common starting point in deep tech.

In semiconductors, advanced materials, robotics, energy systems, and other frontier technologies, the sequence is often less linear. The technical capability may precede the market category.

The founder may see that a new capability is becoming possible before customers have a precise language for how they will buy it, integrate it, or prioritize it.

It means the team has to manage two different forms of uncertainty at the same time.

• Can the team actually build what it believes is possible?

• Where will this capability first become urgent enough to justify adoption, and in what product form?

That is where strategic discipline begins: knowing which part of the company’s logic must remain stable and which part must remain open.

• A founder who becomes too attached to the first market hypothesis may force a powerful technology into the wrong application.

• A founder who treats the technical thesis as infinitely flexible may lose the very insight that made the company worth building in the first place.

For Movidius, the stable element was the belief that data-intensive computation needed a more efficient architecture. The open question was the entry point. The first commercial application had to be concrete enough to test the company’s assumptions against real customers, real constraints, and real purchasing behavior.

This is a subtle but important lesson for deep tech builders. The first market map is rarely the final one. Its purpose is to create a disciplined path into reality and to clarify what must become true in the world for a technical enabler to become a solution customers urgently need.

Proof Before Product

In deep tech, customer discovery often fails because it is treated as an interview process rather than a proof-building process. A founder approaches a large customer and asks: “What problems do you have?”

The question sounds customer-centric, but in practice it usually produces incomplete answers.

The customer may not yet have a concrete way to map an emerging capability onto its own problems.

The people in the room may not own the most important problem. Or the real constraint may sit somewhere between R&D teams, product teams, executives, and other decision-makers up the organization.

This is especially true in semiconductors.

A chip company cannot simply ask the market what to build and expect a clean answer. The development cycles are too long, the integration risk is too high, and the product-definition stakes are too large.

Customers need to see enough evidence to believe the architecture is credible before they will invest the time required to explain what they truly need.

The way through is to bring proof before product.

That proof can take different forms: a simulation, a prototype, a test chip, a performance target, or a technical demonstration that shows a credible piece of the future system. It does not need to be the final commercial product. It does need to be concrete enough to change the quality of the conversation.

The company’s early experience reflected this pattern.

For more than a year, the team worked through a technology feasibility phase before customer engagement became very active. As the architecture started to show promise, the founders could approach potential customers not with a blank page, but with evidence.

They could show a direction of travel and make the technical claim concrete enough to be tested in discussion. They could give sophisticated technical buyers something specific to evaluate.

That changed the customer conversation.

Instead of asking customers to imagine an abstract capability, the team could frame a more useful discussion: this is what the architecture appears able to do; this is the kind of performance it can deliver; this is not yet the final product, but it suggests a path.

The difference is subtle but decisive. Customers often cannot describe the future in the abstract. But they can react intelligently to a credible, tangible proof point.

They can say whether a performance level is meaningful, whether an interface is missing, whether integration would be painful, or whether a use case is commercially relevant.

In that sense, early technical proof is a customer discovery tool. It also helps reveal which customers are merely curious and which customers are serious.

Serious customers will give a challenge. They will define a performance target. They will describe a specific workload. They will expose a constraint that must be solved before adoption becomes possible.

For founders, this is one of the most valuable signals in the early commercial process. A precise technical challenge is much more useful than a simple expression of interest. It means the customer has moved from passive interest to active evaluation.

Some of the strongest conversations in the company’s journey emerged when customers could articulate the problem clearly, saying something along these lines: “If the technology can run this workload at this level of performance, then we are interested.”

That kind of statement gives the team a target, a reason to allocate engineering resources, and eventually a form of evidence that investors can understand.

This matters because in deep tech, market risk and technical risk are intertwined.

A customer commitment is only meaningful if the technical requirement is real. A technical milestone is only valuable if it maps to a customer problem that matters. The founder’s task is to connect the two as early as possible.

For semiconductor founders, the lesson is particularly important because the final product may take years, and integration into a customer system may depend on requirements that are easy to miss and expensive to correct. The goal is to convert uncertainty into sharper questions before the most expensive decisions are locked in.

Commitment Is the Signal

An early-stage company needs credibility, revenue, and reference points. But it also has real constraints. Those constraints create scarcity. Used well, scarcity becomes a way to qualify seriousness.

One of the strongest lessons from this case study is that early access to the technology could not be offered casually to every interested customer. It had to be treated as a selective resource.

The company could only support a small number of early adopters, so the question became whether a customer was serious enough to justify that scarce capacity.

The message was no longer simply about inviting customers to try the technology. It became a test of intent: if a customer wanted early or preferential access, the startup needed evidence that the opportunity mattered, that there was a real project behind the interest, and that successful collaboration could lead to meaningful business.

That distinction matters. A letter of intent may be useful in the earliest phase, when the company is still trying to organize market conversations and create basic evidence of interest.

But as the company matures, the stronger signal is when a customer commits something scarce of its own: money, defined volumes, upfront commitments, or a concrete mechanism tied to access, capacity, pricing, or future delivery.

This is where early customer engagement becomes strategic.

The company is building a chain of evidence. A serious customer commitment can help justify an expensive product decision. It can give investors confidence that the market signal is real. It can sharpen technical priorities. It can also create urgency inside the customer organization.

This is why the best early adopters are the customers whose urgency is specific, whose technical requirements are clear, and whose willingness to commit is real. They help define the next proof point.

For a semiconductor company, that distinction is especially important. The move from prototype to production can require expensive decisions, manufacturing-related commitments, packaging and testing work, and long development timelines.

Before making those investments, the company needs a reason to believe that a defined product, built to defined specifications, will matter enough for customers to adopt. A committed early customer can provide that reason.

Product Definition Is a Journey of Precision

Product definition is rarely a single decision made once at the beginning. It is a process of increasing precision. A company may start with a powerful technical conviction: that a new architecture can solve a class of problems existing systems are poorly equipped to handle.

But a technical conviction does not become a company until it finds the right commercial form.

That form is discovered over time, through proof points, customer conversations, integration constraints, capital pressure, and the discipline to keep moving before the answer is fully visible.

This journey brings that lesson into sharp relief.

The team moved through successive stages of learning about which applications mattered, which customers felt the problem most sharply, and which product definition could turn architectural advantage into commercial adoption.

This is especially true in semiconductors because the product does not live alone.

A chip has to fit inside another company’s system: its device architecture, engineering process, cost structure, roadmap, and internal decision-making logic.

Performance matters, but performance by itself is not enough. Adoption depends on whether the technology can become usable inside the customer’s world.

In the case discussed, the company did not arrive at the winning product definition in a straight line. It advanced through stages: feasibility work, early customer engagement, application learning, sharper technical challenges, and eventually customer evidence strong enough to support the next major product direction.

Each stage narrowed the distance between what the architecture could do and where the market most needed it.

The founder must convert belief into evidence, evidence into product direction, and product direction into enough credibility to earn more time.

Staying in the game does not mean waiting passively for the market to catch up. It means learning fast enough, and focusing sharply enough, to keep the company alive while the right opportunity takes shape.

In this case, the decisive turn came around the second major product version, when a concrete customer challenge changed the trajectory of the company.

For founders, the lesson is that each product step should make the company smarter. Each prototype, customer exchange, and technical proof point should reduce uncertainty and sharpen the next decision.

The winning product may not be obvious on day one. It may emerge only after the company has tested entry points, earned customer intimacy, survived capital constraints, and held the technical vision long enough for the market to reveal the right wedge.

That is why perseverance matters: the ability to keep the core conviction intact while allowing the product to become more precise.

The Founder’s Real Job Is to Stay in the Game

Successful companies compress time. From the outside, a company’s journey becomes a clean narrative: a technical insight, a few strategic pivots, a breakthrough product.

Often, the story appears coherent because the ending gives structure to everything that came before it. But that is not how the journey feels from inside the company.

Inside, the path is usually discontinuous. Progress comes in fragments. A test chip works, but the product definition is incomplete. Customers are interested, but not yet committed. Investors are supportive, until the macro environment changes.

The next product looks like the right one, but the company may not have enough capital to reach it.

This is why the central operating problem in deep tech is not only whether the technology can work. It is whether the company can survive long enough for the technology, the market, and timing to converge.

The company’s journey makes that reality unusually clear when, after closing its first institutional round, the team entered a dramatically different funding environment.

Capital became harder to access. Risk appetite narrowed. A semiconductor startup, already facing long development cycles and expensive product milestones, suddenly had to operate under a much harsher assumption: it might not be able to raise again for some time.

That changed the meaning of every decision.

Spending discipline was no longer an operational preference. It became a survival requirement. The company had to focus capital on what mattered most: building the product, selling the product, and creating enough evidence to justify the next step.

Anything outside that core had to be questioned.

This is one of the most important lessons learned along this incredible journey. Vision may attract the first believers, but survival depends on sequencing. The founder must constantly ask:

Sometimes that proof point is technical. A feasibility study. A working prototype. A test chip. A performance demonstration that shows the architecture can deliver what the market requires.

Sometimes it is commercial. A serious customer conversation. A defined workload. A performance target. An upfront commitment. Sometimes it is financial. A new investor willing to underwrite the next development cycle because customer evidence has made the risk more legible.

The founder’s job is to connect these proof points into a path.

That path is rarely elegant. In this case, it included reducing burn, closing offices, laying off people, and facing pressure to sell the company before the founders believed the real opportunity had been built.

The founder’s responsibility is to keep the company moving through that sequence. Not indefinitely. Not blindly. But long enough for the right evidence to appear—and disciplined enough to recognize it when it does.

This is the kind of moment that rarely appears in retrospective success stories with the force it deserves.

^Disclaimer

^{Please be aware: the information provided in this publication is for educational purposes only and should not be construed as financial or legal advice or a solicitation to buy or sell any assets or to make any financial decisions. Moreover, this content does not constitute legal or regulatory advice. Nothing contained herein constitutes an offer to sell, or a solicitation of an offer to buy, any securities or investment products, nor should it be construed as such. Furthermore, we want to emphasize that the views and opinions expressed by guests on The Scenarionist do not necessarily reflect the opinions or positions of our platform. Each guest contributes their unique viewpoint, and these opinions are solely their own. We remain committed to providing an inclusive and diverse environment for discussion, encouraging a variety of opinions and ideas. It is essential to consult directly with a qualified legal or financial professional to navigate the landscape effectively.}

Subscribe now

For most of the last technology cycle, startups and mining lived in different mental universes. One promised speed, iteration, and rapid feedback. The other demanded land, permits, water, power, shafts, roads, tailings, community trust, metallurgical certainty, commodity exposure, and years of patience before the first commercial tonne appeared.

Critical minerals have forced those two worlds into the same room. The result is awkward, productive, and increasingly unavoidable. Mining remains one of the least startup-native activities in the industrial economy, because a mine resists the favorite verbs of venture capital. It rarely iterates quickly. It rarely pivots cleanly. It rarely generates clean early revenue. It requires permission before production, infrastructure before cash flow, and physical proof long before market proof.

Subscribe now

The title question has a deliberately uncomfortable shape. Owning the miner sounds tangible. Owning the bottleneck sounds strategic. In mining, both can be true, and both can become traps. A mine can be an extraordinary asset with reserve life, infrastructure, and optionality through cycles. A bottleneck can be a high-margin intervention with faster time-to-revenue and lower capital exposure. A mine can become a capital sink. A bottleneck can become a pilot that never changes procurement. The useful question sits in the transfer: where does risk move, who accepts the new version of it, and how does that party get paid?

From here onward, only our Premium Members can keep reading.
The full analysis shows how startups are redrawing the boundary between technology provider, mine partner, project company, and future supplier — and which economic indicators reveal whether a mine-adjacent technology is creating real value.

Read more

Deep Tech Briefing is the weekly Independent intelligence for decision-makers operating across the Industrial Frontier.

Each edition turns fragmented signals across frontier sectors into market context, allocation implications, strategic watchpoints, and the clarity required to compound knowledge into capability.

Subscribe now

This week, humanoid robotics enters a new information regime.

Agility Robotics’ planned listing could give the category something it has been missing: a public benchmark. Not another demo. Not another private mark. A live market test of orders, deployments, utilization, safety, manufacturing cadence, RaaS economics, and revenue conversion.

Once a category gets a comparable, everyone else has to reprice around it.

The rest of this edition maps the frontier around that shift: AI infrastructure, semiconductor inspection, defense tech, compute capacity, long-duration storage, nuclear milestones, quantum tooling, water systems, carbon removal, battery factories, advanced materials, geothermal, photonics, and critical-minerals finance.

What Shapes the Market follows the macro layer: sovereign compute, nuclear cooperation, quantum policy, clean-power finance, food security, and AI commercialization.

Then the edition closes with a curated Card List of 10 startups gaining relevance across frontier industries, followed by 10 Data to Track.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Subscribe now

The Humanoid SPAC Test

Agility Robotics’ planned listing could give humanoid robotics its first US-listed public-market reference point for valuation, deployment evidence, and industrial scale.

The humanoid market is getting its first US-listed public comparable. For the past two years, many of the most important arguments around humanoid robotics have lived inside private rounds, customer pilots, strategic partnerships, and boardroom forecasts.

Agility Robotics’ proposed listing would bring those arguments into public valuation, public filings, public operating metrics, and public market memory.

That can change how capital reads the entire category.

Read more

Subscribe now

This week, I sat down with Isaac Sigron, Managing Director at Koch Disruptive Technologies. We explored why advanced packaging has become one of the strategic bottlenecks behind AI infrastructure, how the shift from monolithic chips to chiplets changes both technical architecture and venture design, why component companies in AI can still represent very large markets, and how founders should think about pricing, procurement, and team-problem fit when building in complex semiconductor ecosystems.

Key takeaways from the episode:

BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE

Advanced Packaging Is Reshaping How AI Compute Scales

Understanding advanced packaging requires looking beneath the visible surface of the AI race. Most conversations about AI still revolve around models, applications, and, occasionally, GPUs.

But the ability to scale AI compute depends on a deeper infrastructure foundation: the systems that allow more logic, more memory, more bandwidth, more power, and more connectivity to operate together efficiently.

That is where advanced packaging becomes strategically important.

It is not simply a semiconductor manufacturing detail. It is part of the infrastructure required to make modern AI systems possible.

Around AI compute, the critical questions increasingly involve interconnect, optical connectivity, memory access, networking, advanced packaging, and the physical architecture that determines whether compute can continue scaling.

The challenge is that the old playbook no longer sufficient on its own.

For decades, the semiconductor industry was able to rely on a relatively simple strategic pattern: make transistors smaller, place more of them into roughly the same area, and unlock more capability over time. That pattern shaped how chips were designed, how performance improved, and how the industry thought about progress.

Advanced packaging emerged because that pattern started to run into scaling limits.

From Moore’s Law to Chiplets

A chip, at its most basic level, can be understood as layers of silicon, insulators, and copper arranged to implement logic and memory.

For a long time, progress came from the ability to draw those structures with an ever-narrower pen tip. That was the operational logic behind Moore’s Law in this discussion: increasing transistor density over time.

The industry kept increasing transistor density, and as a result, chips became dramatically more powerful without requiring a comparable increase in physical size.

Compute power, memory capacity, and networking bandwidth all rose by orders of magnitude while the absolute size of the chip did not change significantly.

But as transistors started to get very small, around the sub-10-nanometer range, increasing transistor density became much harder.

As density improvements became harder to sustain at the same pace, one response was to make chips larger. For a while, that helped.

Then yield issues began to appear. As chips became larger, semiconductor defects became more likely because they tend to be proportional to the area of the chip.

At the same time, another pressure was building.

Historically, logic chips and memory chips could remain separate. A logic chip might include some memory internally, but it was primarily built for logic. A memory chip might include some logic, but it was primarily built for memory.

These chips communicated through the motherboard at relatively low interconnect speed. Rising compute requirements changed the intensity of that relationship.

It became increasingly important to bring logic and memory closer together, rather than having them communicate through relatively slow board-level interconnects. The industry needed to move them closer together.

This is the core logic behind advanced packaging.

Instead of building one massive chip, the system can be broken into smaller building blocks, or chiplets. A compute chiplet can be placed close to a few layers of memory, such as high-bandwidth memory.

These components can then be connected through a small interposer, almost like a “very small motherboard”.

The result is a different way to scale.

Advanced packaging helps address the yield problem because smaller chiplets are easier to manufacture than one very large chip. It also helps address the memory problem because compute and memory can be placed much closer together. That proximity increases bandwidth and reduces the power lost in moving data.

The tradeoff is that the structure becomes much more complex and costly. That complexity is precisely why the field is technically and commercially interesting, and why it is becoming an important design space for compute architecture.

The new frontiers of packaging innovation

Across the conversation, several areas emerged as frontiers of advanced packaging innovation:

1. One is the ability to build larger interposers and larger panels that can host more chiplets. The goal is to create bigger and more powerful compute and memory blocks by allowing more chiplets to sit together inside the package.

2. Another major frontier is 3D memory stacking. Putting memory next to compute was already a major step. Putting memory on top of compute would be a more radical version of the same principle. The technical logic remains the same: bring memory closer to logic, increase bandwidth, and reduce the inefficiency of data movement.

3. A third frontier is optical connectivity. The industry is trying to move optics closer and closer to the compute itself. Compute remains electronic, but the need to move data efficiently across systems creates a push to bring optical connectivity inside the package or near it.

4. The last one points toward modular chiplet architectures. If chiplets can be designed, reused, and amortized across multiple projects, the economics of semiconductor development may begin to change.

Startup Archetypes and Venture Logic in Advanced Packaging

Advanced packaging is an unusual market for startups. On one hand, it is a relatively new field. On the other hand, it is deeply controlled by large incumbents.

Only a small number of companies can execute advanced packaging at scale today, and in some parts of the market there may effectively be only one or two players with true scaled capability.

That creates a difficult but compelling environment for venture-backed companies.

Across the conversation, we explored several potential startup archetypes, each approaching advanced packaging in a different way.

The first archetype is the company that uses advanced packaging innovation to build a product.

In this case, packaging innovation is embedded inside the product strategy rather than sold as a standalone process capability. The packaging innovation matters, but it is tied to a specific product and a specific performance outcome.

The second archetype is the company that develops a piece of the process.

These startups solve problems that must fit into the broader advanced packaging ecosystem. They might work on thermal management, optical waveguides inside the interposer, or more efficient ways to deliver power into the package.

For these companies, the central question is how they fit inside the ecosystem. A component can be technically impressive and still face challenges if it cannot be integrated into the way the industry actually builds systems.

A third potential archetype is more forward-looking.

These are companies that reimagine architecture and business model at the same time. They are not simply improving a process step or building a product on top of an existing model. They are asking whether advanced packaging could make a different semiconductor business model possible. Chiplets are one example of this logic.

In this model, customers may be large semiconductor companies or AI infrastructure players building the larger systems into which those chiplets are integrated.

Pricing, Procurement, and Win-Win B2B Deals

A new compute architecture does not automatically turn into closed deals.

In semiconductor infrastructure, many strong technical ideas encounter the reality of procurement. Customers may be willing to evaluate new technical approaches, but they can be conservative when it comes to unfamiliar commercial structures and business models.

That means founders need to be pragmatic. If a business model is new, it may need to be presented in a form the customer already understands.

For instance, the founder can change the economics. An option could be to offer a discount because the startup plans to amortize the development cost across multiple projects rather than charging one customer for the entire burden.

In exchange, if the customer scales, the startup participates in the upside through per-chip economics.

Still, the objection will come. Customers will worry about margin stacking. They will ask whether the startup is inserting itself into the economics and making the final product more expensive. They will compare the model with alternatives and test whether the new structure actually benefits them.

There is only one real answer. The math has to work.

If the customer would be better off paying a different commercial structure, then that option should be available. If the chiplet-based model is better, the founder must prove it with numbers.

The customer has to see that the proposed structure improves the economics of their project. This is the discipline behind a B2B win-win deal.

A business model built on extracting more value from the customer without improving the customer’s position may look attractive in a pitch, but it is unlikely to work in negotiation. The right model works because both sides benefit.

Team-Problem Fit

The deepest venture lesson from advanced packaging is not only about chips. It is about team-problem fit.

Innovation comes in waves. When a real problem emerges, multiple teams often identify it at roughly the same time.

In a world where technical information moves quickly and industry bottlenecks become visible across ecosystems, it is rare for only one team to see a major opportunity.

In other words, innovations arrive in waves because constraints arrive in waves.

This is especially true in advanced packaging.

When many companies are attacking the same problem, that can be a good sign. It often means the problem is real.

But it also changes the investor’s question. The question is not simply whether the problem exists. The question is which team is best suited to solve it.

That is team-problem fit.

The strongest founders are not necessarily the ones with the most interesting technology in isolation. They are the ones whose experience, insight, relationships, technical fluency, and market understanding match the specific problem they are trying to solve.

This matters because advanced packaging is a field where founders must deeply understand the industry context.

They must understand dependencies. They must understand supply-chain challenges, customer behavior, capital requirements, integration pathways, and the pace at which real adoption can happen.

The challenges often begin when a team develops an impressive solution in a lab or technical environment, and only later starts searching for something to do with it.

The technology may be real. The engineering may be difficult. The invention may be elegant. But that is not the same as a company.

A strong startup needs a problem that matters enough, a customer that understands the pain, a path into the value chain, a business model that works, and a team that can navigate the realities between invention and adoption.

This mistake is not limited to pre-seed companies. It can appear even at later stages. Teams can spend years building excellent technology and still be working hard to find the right use case.

In hardware and semiconductor markets, that is a particularly expensive way to learn.

Success depends on whether the company is positioned around a bottleneck that matters, whether the solution creates economic leverage, whether customers can adopt the model, and whether the founding team has the right fit with the problem.

In conclusion, advanced packaging is a technical field, but not only a technical one. It is a test of venture design, market timing, capital discipline, and commercial vision.

Disclaimer

Please be aware: the information provided in this publication is for educational purposes only and should not be construed as financial or legal advice or a solicitation to buy or sell any assets or to make any financial decisions. Moreover, this content does not constitute legal or regulatory advice. Nothing contained herein constitutes an offer to sell, or a solicitation of an offer to buy, any securities or investment products, nor should it be construed as such. Furthermore, we want to emphasize that the views and opinions expressed by guests on The Scenarionist do not necessarily reflect the opinions or positions of our platform. Each guest contributes their unique viewpoint, and these opinions are solely their own. We remain committed to providing an inclusive and diverse environment for discussion, encouraging a variety of opinions and ideas. It is essential to consult directly with a qualified legal or financial professional to navigate the landscape effectively.

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,

I’m back with a new piece in the 30 Lessons Learned series on Deep Tech.

After the recent pieces on execution and exit strategy, this naturally sits between those two points.

In Deep Tech, scale-up is one of the most difficult and fascinating parts of the venture-building journey.

It is the moment when a company stops proving that something can work once and starts proving that it can work repeatedly, economically, safely, and reliably.

It is where the lab meets the factory, where the pilot meets the customer’s operating reality, and where technical performance has to become throughput, yield, margin, quality, delivery, and trust.

Of course, scale-up is difficult to generalize.

It does not look the same in semiconductors, energy, advanced materials, robotics, mining, aerospace, or biomanufacturing.

Each sector has its own bottlenecks, qualification cycles, capital needs, regulatory paths, customer behaviors, and operating constraints.

But even if the details change, some questions, moves, and challenges keep coming back.

That is what pushed me to write this piece.

As always, the result is not a definitive map of every possible outcome.

It is a curated and distilled set of lessons learned along the way.

If you build, back, or study Deep Tech, I think these lessons will help you ask sharper questions about scale-up design — and maybe avoid discovering too late that the company you built is not as easy to scale as you once assumed.

Subscribe now

Lesson 1

Repeatability is the first language of scale.

Scale-up begins when a company stops proving that the technology can work once and starts proving that the system can make it work repeatedly.

Can the company deliver the same result across batches, sites, operators, customers, and time? One successful build can still hide a fragile process. Scale requires documentation, supplier qualification, inspection, training, quality systems, and process control. The question is no longer whether the best engineer can make the product work once. It is whether the company has built a system that can make it work without extraordinary effort.

Lesson 2

The first plant should be a learning machine.

Every production run should make the next one smarter.

The first industrial plant needs to support early production, but its deeper job is to teach the company how production really behaves. It should reveal process windows, labor requirements, supplier performance, quality controls, customer specifications, working capital needs, and unit economics. If the first plant creates volume but not learning, it is underperforming its most important role.

Lesson 3

The techno-economic model should challenge the company before the market does.

The best models do not make the story look investable. They reveal whether the business can survive contact with scale.

Techno-economics does more than support fundraising. It forces the team to connect technical assumptions to CapEx, OpEx, pricing, revenue, and margin. It shows which variables matter most, which improvements actually change the business, and where the company is most exposed.

Lesson 4

Read more

Welcome to Edition N^o 116 of Deep Tech Briefing.

The Scenarionist’s weekly intelligence layer on what you need to know, understand, and track to win in deep tech: company milestones, market shifts, and macro forces reshaping outcomes, competitive position, capital allocation, and critical decisions.

Deep tech markets rarely announce themselves at the moment they become obvious. They turn earlier: when a regulator creates a path, when a site becomes financeable, when a buyer commits before scale, or when a technical result changes which risks still matter.

This week, the signal comes from fusion. The Big Idea examines whether a first-of-a-kind licensing milestone is more than administrative progress — and whether the first company to show regulators how to evaluate a new fusion system may gain an advantage before the first commercial megawatt arrives.

Subscribe now

Beyond fusion, this edition follows the same pattern across world simulation, AI coding infrastructure, security data lakes, long-duration storage, captured-carbon chemistry, edge AI, rack-scale inference, robotics, orbital operations, quantum systems, circular battery materials, green ammonia, advanced nuclear siting, commercial satellite servicing, low-input agriculture, purified phosphoric acid, mycelium protein, rocket manufacturing, AI data-centre power, mineral carbonation, textile recycling, high-temperature composites, optical interconnects, semiconductor materials, post-quantum security, and maritime defense.

The market-shaping layer tracks the institutions moving around those technologies: critical-mineral diversification, grid tariffs for large loads, privacy rules for AI-era data, biotechnology patent reform, nuclear-deterrence planning, evolving radiology AI regulation, and environmental data infrastructure.

Finally, the edition closes with 10 key data points to know — from billion-dollar valuations and long-duration storage to quantum access, robotic task performance, AI infrastructure, and behind-the-meter power.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Subscribe now

Has Fusion Reached a De-Risking Milestone?

A first-of-a-kind licensing milestone is not the end of the risk curve. It is evidence that the curve is beginning to bend.

For the first time, a fusion company says it has received the state licenses needed to build toward commercial power-plant operations.₁

A license does not generate electrons. But it can change the way capital perceives risk. And in regulated markets, the first license is never just a license.

What if the first durable moat in fusion is not plasma performance, but

Read more

Subscribe now

This week, I sat down with Steve van Zutphen, former CEO of Magpie Polymers, acquired by Italmatch Chemicals in 2017, and current CEO of Swan-H.

Drawing on his experience building and leading Magpie Polymers, Steve joined us for a practical conversation about what it really takes to build a business around an advanced material.

We explored why a scientifically credible application can still be the wrong market, how technical founders can improve customer discovery, why industrial sales is fundamentally a process of reducing risk, and how pricing, pilots, and customer collaboration shape the path from laboratory validation to market adoption.

Key takeaways from the episode:

BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE

Find a market that is willing to pay

The first key takeaway from the conversation is that a technology can solve a real problem and still struggle to become a viable business.

At first, the polymer seemed naturally suited to wastewater treatment and pollution control. It could selectively capture metals, and the environmental need was easy to understand.

The team met potential customers, attended trade shows, received samples, and ran tests. Companies were interested enough to engage, but those conversations did not develop into a clear path to paying customers.

This is an important distinction for advanced materials founders.

A customer may be willing to discuss a technology, test it, or provide feedback without being willing to pay enough.

The problem was not the technology, but the economics of the application. By entering this market, the startup was effectively asking customers to pay more for a better way of managing an existing expense.

That did not mean the market had no value. It meant that the commercial dynamics worked against premium pricing.

For an early-stage chemical company, this is a difficult position.

The company is still producing limited volumes, and manufacturing costs are relatively high. It’s rarely ready to compete through large volumes and low prices.

It needs applications where small quantities of product can create enough value to support healthy margins. This is where product design and market positioning become critical.

Moving from waste management to value recovery

The opportunity became more attractive when the company shifted its focus from removing unwanted metals to recovering valuable ones.

The underlying technology did not need to change substantially. Its core function remained the same. What changed was the customer’s reason to buy.

In a pollution-control application, the polymer helped manage a liability. In precious-metal recovery, it helped recover an asset.

Gold, platinum, and palladium leaving a production process are not simply contaminants. They are materials with a clear value. Recovering them can create a measurable economic return.

This made the commercial proposition much easier to understand.

The customer was no longer being asked to pay primarily for the management of a waste-related cost. The customer was being offered a way to recover value that was already being lost.

Precious-metal recovery also matched the realities of an early-stage materials company much better.

The startup did not need to sell enormous quantities of polymer for the product to matter. Small volumes of a high-value specialty material could support an economically attractive application.

This supported a low-volume, high-value business model.

The broader lesson is that the first market should not be chosen only because the technology can work there or because the need appears important. It should be chosen because the economics fit the company’s current capabilities.

Let the customer talk

Another interesting insight from the conversation was how the team conducted its early customer meetings.

If the founder speaks for most of the meeting, the company may leave without learning the most important things: how the customer’s process works, where the real problems are, and whether solving them is important enough to justify testing a new technology.

The arrival of an experienced salesperson changed the way these meetings were conducted.

The salesperson did not need to understand the chemistry better than the scientists. The value came from knowing how to guide the conversation.

Instead of explaining the product at length, the team began asking simple questions:

• How does the production process work today?

• Where are materials being lost?

• Which steps are expensive or unreliable?

• What has the customer already tried?

These questions helped uncover problems that would never have emerged from a traditional technical presentation.

A productive meeting is therefore not one in which the founder explains everything perfectly. It is one in which the customer shares enough information for the startup to understand whether there is a real opportunity.

Let the problem come before the product

The order of the conversation matters. In the case discussed, the sales team created space for the customer to describe where value was being lost in the process.

Once the problem was clearly understood, the technology could be introduced as a potential solution.

This approach changed the direction of the sale.

In other words, the startup is not asking the customer to test an interesting new material without context. It is proposing a possible solution to a problem the customer has already described.

This makes the next step easier. A pilot is no longer a generic experiment. It becomes a practical test of whether the technology can reduce a specific and measurable loss.

However, as discussed in the conversation, scientific expertise does not automatically make someone effective in sales.

Scientists are trained to explain ideas clearly, and demonstrate technical depth. Customer discovery requires a different skill set: listening, asking useful questions, and waiting before proposing a solution.

For an advanced materials startup, adding commercial experience can therefore be as valuable as adding technical expertise.

Customer adoption means managing risks

Industrial customers do not evaluate a new material only by asking whether it performs better. They also ask what could go wrong if they adopt it.

From the founder’s perspective, the value of the product may seem obvious. The material can reduce costs, recover more value, improve efficiency, or solve a meaningful technical problem.

But the customer sees the decision from a different angle.

An industrial process may not be perfect, but it is already running. Introducing a new material means changing part of an existing system, and that creates risk.

The downside often matters more than the upside

In the discussion, an example helped illustrate the dynamics of adoption in industrial B2B markets. A factory manager may be interested in a solution that reduces costs by 10%. However, if the same solution causes the production line to stop for two days, the loss can be far greater than the expected savings.

This is why the potential benefit and the potential risk do not carry the same weight.

For Deep Tech founders, this helps explain why a technically superior product can still face resistance.

The customer may understand the technology perfectly well. The hesitation may come from the fact that the operational risk has not yet been reduced enough.

This is why it is so important for the startup to understand how the material behaves inside the customer’s full process.

The customer wants to know that solving one problem will not create another, potentially larger one elsewhere in the system. The more the startup understands the customer’s process, the more credible its case becomes.

De-risking comes before price

One of the most useful points from the conversation is that, once the solution has been sufficiently de-risked, price often becomes less central in technical B2B sales.

Customers may spend relatively little time negotiating the final price compared with the time required to evaluate whether the solution works reliably without disrupting the process.

This does not mean price is irrelevant, but before discussing small differences in cost, the startup has to build confidence.

The customer needs evidence that the material performs consistently, fits into the existing process, and does not introduce risks that are difficult to manage.

Once that confidence exists, the commercial conversation becomes much easier.

The broader lesson is that industrial adoption is rarely driven by performance alone. It is driven by the combination of measurable value and acceptable risk

Pricing and business models

As we’ve discussed many times on this channel, for a Deep Tech startup, the question is not only how much to charge. It is also what the company should sell.

In advanced materials, this is particularly important.

The offering may be the chemical itself, a machine that doses it, a packaged system, or a service built around the result. Each option creates a different level of operational complexity, resource requirements, and customer support.

The most attractive model on paper is not always the most practical one for an early-stage company.

Selling a product is often a practical choice.

The customer can receive the chemical and introduce it into the process directly. In some cases, the startup may also provide a machine that doses the material.

This can be useful during early adoption because it gives the company more control over how the product is used and allows it to work more closely with the customer.

The machine does not necessarily need to be built internally. A specialist supplier can manufacture it, while the startup focuses on the chemistry that makes the system valuable.

The equipment supports adoption, but the chemistry creates the margin

The conversation drew a useful distinction between the economics of the machine and the economics of the material.

Industrial equipment can often be sold with a relatively conventional margin. The machine helps the customer adopt the technology and gives the startup greater control over the application.

But it is unlikely to be the main source of long-term value. The chemical is different.

Its price has to reflect more than the cost of manufacturing a kilogram of product. Years of R&D, testing, application development, and customer work sit behind that material. A simple cost-plus approach can therefore be misleading.

Moreover, at the beginning, founders may focus too heavily on maximizing the first sale.

For an early-stage startup, acquiring a first and then a second customer can matter more than maximizing the revenue generated by a single account.

That matters because early revenue is not just cash. It is proof that the commercial model may be repeatable.

The broader lesson is that pricing decisions should support company building, not just short-term revenue. They should also help the company reach the next customer, prove repeatability, and move toward a business that can scale.

From the lab to the customer site

Product design does not always have to happen entirely inside the startup. In the case discussed, much of the learning about how to use the material happened directly at customer sites.

This created a practical division of tasks.

The startup focused on mastering the production of the polymer. The customer helped validate how the material could be used inside a real industrial process.

This allowed the startup to retain control over material production while developing the application in the customer’s operating environment.

On-site development

The process began with small lab tests. Customers sent samples from their operations, and the team used them to see whether the polymer worked with real process materials.

If the results were promising, testing moved to the customer’s facility.

The team brought small mobile pilot units to the site. Testing could then move to larger or custom-built systems to evaluate the product at a greater scale.

This created a step-by-step path from lab testing to industrial use.

• The lab showed that the chemistry worked.

• On-site testing showed that it worked under the customer’s actual operating conditions.

The larger system helped the customer determine whether the technology could work at a larger scale.

Moreover, working at the customer’s site meant sharing part of the learning process.

The customer became familiar with the product and developed direct experience with how it worked and which risks needed to be managed.

The co-development phase therefore did more than validate performance. It reduced uncertainty and reduced adoption risk.

By the time the customer considered a larger-scale purchase, the decision was no longer based only on the startup’s claims. The product had already been tested inside the customer’s facility.

Deciding whether to charge for early trials

The conversation also highlighted a difficult strategic decision: whether and how much to charge for early trials.

Charging for early testing or co-development work can help the startup cover its costs. But insisting on full payment may slow the project and delay progress with the customer.

At the same time, the startup has a strong interest in entering the customer’s facility and moving the project forward, even if that sometimes means progressing without charging the full cost.

A practical solution could be to share the investment.

The company can explain what the test will cost and ask the customer to contribute. The payment may cover part of the project, for instance, or later be converted into a discount on a full-scale purchase.

The exact structure can vary. What matters is that both sides have something invested in the process.

The startup needs to protect its limited capital, but the long-term objective is not to build a business around fees from early-stage collaborations. It is to reach full-scale adoption and recurring sales.

Learning to filter the wrong opportunities

The final takeaway from the conversation is that not every customer project deserves the same attention. A CEO must therefore stay focused on the right opportunities.

Early-stage startups can easily become excited by any sign of interest. A customer mentions a technical problem, and the team immediately begins designing experiments around it.

But some projects are more valuable than others.

One customer may have a real problem that needs solving. Another may offer a project only because the startup has repeatedly asked for one. A third may present a challenge that has already been tested many times and may not be realistically solvable.

The first meeting is not enough.

Founders should avoid becoming overly optimistic, let the discussion settle, and see whether the customer still has the same problem the following week.

The broader lesson is that advanced materials startups need to protect their time and focus as carefully as their capital. A promising conversation is not yet a commercial opportunity. The strongest opportunities are those in which the customer has a genuine problem and the startup can realistically solve it.

Disclaimer

Please be aware: the information provided in this publication is for educational purposes only and should not be construed as financial or legal advice or a solicitation to buy or sell any assets or to make any financial decisions. Moreover, this content does not constitute legal or regulatory advice. Nothing contained herein constitutes an offer to sell, or a solicitation of an offer to buy, any securities or investment products, nor should it be construed as such. Furthermore, we want to emphasize that the views and opinions expressed by guests on The Scenarionist do not necessarily reflect the opinions or positions of our platform. Each guest contributes their unique viewpoint, and these opinions are solely their own. We remain committed to providing an inclusive and diverse environment for discussion, encouraging a variety of opinions and ideas. It is essential to consult directly with a qualified legal or financial professional to navigate the landscape effectively.

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

Welcome to Edition N^o 115 of Deep Tech Briefing.

The Scenarionist’s weekly intelligence layer on what you need to know, understand, and track to win in deep tech: company milestones, market shifts, and macro forces reshaping outcomes, competitive position, capital allocation, and critical decisions.

In this edition, the Big Idea asks what happens when a critical industrial input is no longer purchased shipment by shipment, but produced inside the customer’s own operation.

The immediate case begins with a single unit operation inside rare-earth recycling. The larger question reaches much further: when a supplier moves onsite, does the customer gain independence, or enter a deeper and more durable relationship with the technology provider?

Subscribe now

Beyond it, this edition moves across sovereign radar intelligence, physics AI for engineering, AI-native industrial robotics, second-life batteries, sodium-ion storage, autonomous freight, commercial e-fuels, photonic-chip manufacturing, compact fusion, distributed quantum computing, and deep-sea geothermal.

The market-shaping layer follows the infrastructure around those technologies: public guarantees, cyber standards, faster defence permitting, classified market access, public demand for specialised AI hardware, and new research and technology-transfer pathways.

Finally, the edition closes with 10 key data points to know — from a valuation above €10 billion and 465 Wh/kg at stack level to 100 repurposed EV battery packs entering an industrial storage system.

Enjoy the read!

Deep Tech Briefing is available for Premium Members

By joining The Scenarionist Premium, you also unlock access to exit analyses, case studies, rumors, exclusive lessons, scalability frameworks, and hard-earned insights from more than 100 Deep Tech founders and investors.

Subscribe now

When On-Site Recovery Replaces Consumables, Who Captures the Value?

Most industrial systems are built as lines. Materials enter, processes transform them, products leave, and waste moves elsewhere.

Each stage depends on a network of external relationships: energy providers, chemical suppliers, logistics operators, water systems and waste contractors.

That arrangement is often efficient. Specialization allows each participant to do one thing well, while the plant avoids having to reproduce every capability internally.

But what happens when one of those relationships becomes unavailable, unreliable or simply no longer economical?

This is what makes the collaboration between

Read more

Subscribe now

This week, I sat down with Anil Achyuta, Partner at Energy Impact Partners, for a practical look at the battery sector from the perspective of founders building across the value chain — from materials, cells, manufacturing processes, and packs to grid storage, EVs, and robotics.

We explore why battery startups are difficult to build in a capital-efficient way, how demand is shifting across end markets, what makes cell manufacturing so industrially demanding, and why a promising material is rarely enough unless it can survive scale-up, qualification, and real customer adoption.

Key takeaways from the episode:

BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE

The Battery Market Is Being Rewritten by Demand, Not Chemistry Alone

The battery market is shaped by chemistry, materials science, manufacturing capability, and electrochemical performance. But before any of those dimensions can become investable, there has to be a strong enough market pull. Without demand, even a strong technical breakthrough can remain trapped at the level of promising experimentation.

Batteries sit inside larger industrial systems. They are an input into electric vehicles, grid storage, robotics, consumer electronics, defense systems, and many other applications.

This matters because different markets move at different speeds.

They have different qualification requirements, different cost sensitivities, different safety expectations, and different levels of tolerance for new technology. A breakthrough that looks compelling in one application may be irrelevant, too expensive, or too difficult to qualify in another.

Grid storage

One of the clearest sources of demand today is grid storage.

The reason is structural. Power systems are under pressure. AI-related energy demand is growing. Grid upgrades are becoming more important.

Countries and regions around the world are building large amounts of renewable energy, and renewables create a basic systems problem: generation does not always arrive when demand needs it.

Batteries become part of the infrastructure that makes renewable power more useful, and more compatible with the needs of a modern electricity system.

For founders, this creates a different kind of market environment.

However, utilities and grid operators can be slow-moving customers. They care deeply about reliability, safety, and long-term performance. But the underlying demand is real, and that matters.

The EV market has become more complex

Electric vehicles remain one of the largest battery demand pools in the world.

The reason is obvious but important: cars require a lot of battery mass. A vehicle can carry hundreds of kilograms of batteries, which means automotive demand creates enormous volume.

When the EV market accelerates, it can pull the entire battery value chain with it, from raw materials to cells, packs, battery management systems, and manufacturing equipment.

But the EV market has also become more complex. Many automakers have explored verticalizing battery manufacturing by bringing it in-house, with the goal of reducing costs and making EVs more affordable at scale. However, a changing policy context and market environment have made some automotive players more cautious.

Robotics is growing fast

Robotics is one of the most exciting emerging demand areas for batteries.

The category is expanding across many forms: delivery robots, sidewalk robots, autonomous systems, lawnmower robots, cleaning robots, specialized industrial robots, and humanoid robots.

That makes robotics interesting, but it’s not yet the same as automotive in volume.

Every Battery Market Has Its Own Performance Logic

In batteries, the right performance profile depends on the application. A consumer device, an electric car, a grid storage system, a drone, and a humanoid robot do not need the same thing from a battery.

Founders often think in terms of superior chemistry or superior materials. Customers think in terms of systems performance.

A founder may believe the company has a better anode, a safer electrolyte, a more energy-dense cell, or a lower-cost manufacturing process.

But the customer wants to know what that improvement means inside the actual product.

• Does the car get more range?

• Does the grid asset cycle longer?

• Does the robot work for more hours?

• Does the cost fall enough to change adoption?

Technical improvement has to translate into a use-case advantage.

Energy density, cycles, safety, and cost

When it comes to performance, electric vehicles offer a useful example.

One of the most important metrics is energy density.

At the simplest level, energy density determines how much energy can be stored per unit of weight or volume. In a car, this connects directly to range. The more usable energy a vehicle can carry without adding too much weight, the more attractive the vehicle can become.

But energy density is only one part of the equation.

Cyclability matters because batteries degrade. Founders and customers need to understand how many times a battery can be charged and discharged over its useful life.

Safety is another core requirement.

Batteries need to operate safely across different conditions, including high and low temperatures. A battery that offers strong performance but cannot meet safety expectations will struggle to earn adoption.

Power density adds another layer.

Some applications need to discharge power quickly, while others may prioritize different performance characteristics. Temperature performance matters as well, especially for systems operating in demanding environments.

Then there is cost.

Cost is not a secondary metric. It is one of the constraints that shapes whether a battery technology can become commercially relevant.

A battery can be technically impressive and still commercially weak if it cannot reach the cost structure required by the market.

In cars, for example, battery cost can represent thousands of dollars per vehicle. The broader vehicle cost then builds on top of that foundation. This is why battery cost has strategic consequences far beyond the cell itself.

Cell Manufacturing Is Where the Value Chain Becomes Industrial

The battery value chain begins with raw materials and extends through processing, active materials, electrodes, cells, modules, packs, battery management systems, and final integration into vehicles, grids, robots, or devices.

Each layer has its own technical requirements and commercial constraints.

This is important for founders because a startup may enter the value chain at one narrow point, but the market will eventually judge whether that point works inside the full system.

From lithium to cells to packs

A simplified view of the battery manufacturing process helps clarify why this market is so demanding.

Lithium first has to be extracted, whether from rock or brines. It then has to be processed and refined into usable forms such as lithium carbonate or lithium hydroxide. These materials enter the manufacturing chain and are combined with cathode active materials and other inputs.

The next step is electrode production.

Materials are mixed and coated onto surfaces through processes such as slurry casting. The coated material is then processed to create uniform layers, often through calendaring, which helps produce thin, consistent electrode structures.

The cathode and anode are prepared separately, with anodes commonly involving graphite and, increasingly, graphite-silicon combinations.

Those components are then brought together with separators and electrolyte. The cell goes through formation, where it is electrochemically cycled and prepared for use. Depending on the format, the cell may be rolled, packaged, tabbed, and assembled into its final form.

But the cell is still not the complete product.

Cells are assembled into modules or packs. Packs require electrical connections, mechanical integration, packaging, and a battery management system (BMS). The BMS acts as the intelligence layer that communicates with and coordinates the behavior of the cells.

Only then does the battery become part of the final system.

For a founder working on one material, one process step, or one component, this process creates a hard reality: the innovation has to fit into and perform across every downstream layer.

A gigafactory is not just a bigger lab

The move from laboratory work to manufacturing is not a linear scale-up. It is a different operating environment.

It requires capital, a manufacturing line, repeatable processes, and the ability to produce cells reliably in the same way over and over again.

One rough reference point from the conversation is that a 10 gigawatt-hour battery manufacturing plant in the US can require hundreds of millions of dollars in capital expenditure, before even considering the operating costs required to keep the facility running.

That figure is not meant to be a precise universal rule. The exact number can vary depending on the project, but it captures the scale of the challenge.

Battery manufacturing is capital intensive because the product is physical, the process is complex, and the market requires reliability at scale.

Owning One Breakthrough Is Not Enough

A team may develop a better anode, a new cathode material, a safer electrolyte, or a novel manufacturing process.

At the scientific level, the breakthrough may be real. It may show impressive performance in early testing. It may even look compelling in techno-economic models.

But batteries are systems.

A founder can be world-class at one component and still be forced to prove performance at the cell level. Customers do not buy an anode in isolation. They need confidence that the full cell will behave reliably and consistently inside the broader battery system.

This changes the company-building journey.

A better anode still has to work inside a cell

Take the example of a silicon anode.

A founder may have a strong technical thesis and compelling data showing that the anode improves performance. But that anode still has to fit into a cell. It has to interact with the cathode, separator, electrolyte, and manufacturing line.

The customer wants to know whether the new material behaves predictably in the full system.

• Does the cell perform reliably?

• Can it be manufactured reliably in the same way every time?

• Does the improvement still hold once it is tested inside the complete battery system?

These questions are the reality of adoption. Every improvement has to be validated inside the system that will carry it to market.

The founder becomes a cell manufacturer without wanting to

This creates one of the most difficult capital efficiency problems in battery startups.

A founder may begin as a materials company. The company’s expertise may be concentrated in one part of the stack.

But to prove that the material works, the founder may have to build cells. To build credible cells, the company may need a manufacturing line, physical infrastructure, and process know-how.

Before long, a materials company starts behaving like a cell manufacturer.

This may not be the founder’s original strategy. It may not be where the company has the strongest expertise. But the market demands system-level proof, and system-level proof often requires physical infrastructure.

That is why battery startups can burn capital even when they are trying to remain focused.

The problem is that the proof required by the customer sits downstream from the original innovation. If the ecosystem does not provide enough external infrastructure to bridge that gap, the startup has to build more itself.

This is one of the reasons the battery sector is so complex.

A company can have a real breakthrough and still face a financing path that looks long, expensive, and dependent on manufacturing proof, customer qualification, and eventual volume.

The missing contract manufacturing ecosystem

One important structural issue discussed is the lack of a strong contract manufacturing ecosystem. A useful way to understand that gap is through an interesting parallel with the biotech sector.

In biotech, capital-efficient company formation became more possible because an ecosystem of contract manufacturers developed around the industry.

A startup did not always need to own every piece of manufacturing infrastructure from the beginning. It could rely on external manufacturing partners for parts of the development and production journey.

That does not make biotech easy. It is a difficult market with its own cycles, risks, and capital requirements. But the presence of contract manufacturing infrastructure changed what early-stage companies could attempt without owning everything themselves.

Batteries do not yet have an equivalent layer at sufficient depth.

If there were a broad network of contract manufacturers for batteries, component-level startups could potentially build in a more capital-efficient way. But today, that layer is not deep enough, and OEMs still need to test and qualify the battery themselves.

This is a structural issue.

If a founder could take a new material to a robust network of contract manufacturers, produce credible cells, and generate the data required for customers, the company-building path would look different. It would still be hard, but the burden of infrastructure ownership would be lighter.

In the absence of that layer, founders have to be much more careful.

They need to know early which parts of the manufacturing journey they must own, which parts they can access through partners, and where the proof of value actually has to occur.

Qualification, licensing, and economics

A battery innovation does not become valuable simply because the technology works. It becomes valuable when the market believes the technology can be adopted, manufactured, qualified, and delivered at scale.

That requires more than technical data. It requires a credible path through customers, production, financing, and time.

This is where battery companies often face long timelines. An important milestones may require years of testing, physical infrastructure, and OEM qualification.

For example, qualification cycles for automotive customers can be very long.

Even a strong technology has to prove that it behaves reliably and safely over time. OEMs need confidence that the cell will perform consistently, not only in ideal conditions but across real-world usage. They have to understand reliability, safety, manufacturability, and integration risk.

This process can take years.

The exact timeline will depend on the customer, application, chemistry, and level of integration, but the strategic point is clear: qualification is a central part of the adoption process.

Licensing often appears attractive in battery materials.

In theory, a company can avoid building massive factories by licensing its technology to larger manufacturers. The model can include upfront payments, milestone payments, and royalties over time. It can seem attractive because it appears to reduce the need for the startup to own the full manufacturing stack.

But licensing only works if the licensed technology reaches volume. Royalties depend on production. If volume does not materialize, neither do the future cash flows. Again, the major economic value often depends on adoption at scale.

Founders Should Think Scale First

One of the most important lessons from the episode is that battery founders should think about scale earlier.

This does not mean every startup needs to build a factory immediately. It does not mean every company should raise hundreds of millions of dollars before proving anything. It means the technical roadmap should be designed with manufacturing reality in mind from the beginning.

A founder cannot afford to treat scale as a later question.

Cell size matters

Cell size matters because it signals how close the company is to meaningful proof.

Coin cells and very small cells may be useful for early experimentation, but they are not enough to establish confidence that a battery technology is moving toward real-world relevance. Investors want to see progress toward formats that begin to resemble real-world relevance.

One amp-hour cells are still small. Moving toward five amp-hour cells begins to create a more meaningful signal. The number may vary by application, but the principle is that founders need to show that performance survives when the system becomes more realistic.

Defense, robotics, and grid

For some founders, the smartest path may not begin with the largest market. A startup may need earlier markets that generate stronger near-term pull, faster feedback, or more credible commercial validation.

Dual-use is one possible path.

In defense, customers may care deeply about speed, performance, reliability, and mission capability.

Some of these buyers may move faster than traditional automotive or utility customers. They may also value differentiated energy systems if those systems create a real operational advantage.

But the key is traction. Investors will want to see evidence that real customers are engaging seriously.

Grid storage can also be attractive, especially because demand is structurally strong. But founders have to recognize that utilities and power customers may move slowly.

Reliability, bankability, and long-term economics matter. The market pull is real, but the adoption process still requires patience and proof.

The broader lesson is that founders should not choose markets only by size.

They should choose markets based on where they can prove value, and generate credible customer signal. A smaller early market with urgent demand may be more useful than a massive market that takes years to validate.

The goal is to sequence ambition correctly.

The battery founder’s real job is to reduce industrial risk

To recap, battery startups are difficult because they sit at the intersection of science, manufacturing, capital, and adoption. A founder has to manage all four.

The science has to be real. The manufacturing path has to be credible. The capital plan has to match the proof points. The customer has to care enough to participate in the journey.

This is why the best battery companies are not built around technical optimism alone. They are built around disciplined risk reduction.

Every milestone should answer a specific question.

• Does the material work beyond the lab?

• Does performance survive in larger cells?

• Can the process be repeated?

• Can the cost structure support the target application?

• Will customers test it?

• Will they pay for it?

• Can the company reach the next proof point without consuming more capital than the opportunity can justify?

The strongest founders will show why the technology matters for a specific market, how it fits into the value chain, what it takes to manufacture, where customer pull is strongest, and which proof points will make the company more investable over time.

That is the reality check.

Batteries remain one of the most important sectors in deep tech. The companies that succeed will be the ones that understand this early. They will think beyond the material, beyond the lab result, beyond the spreadsheet, and beyond the first customer conversation. They will build with the full system in mind.

Disclaimer

Please be aware: the information provided in this publication is for educational purposes only and should not be construed as financial or legal advice or a solicitation to buy or sell any assets or to make any financial decisions. Moreover, this content does not constitute legal or regulatory advice. Nothing contained herein constitutes an offer to sell, or a solicitation of an offer to buy, any securities or investment products, nor should it be construed as such. Furthermore, we want to emphasize that the views and opinions expressed by guests on The Scenarionist do not necessarily reflect the opinions or positions of our platform. Each guest contributes their unique viewpoint, and these opinions are solely their own. We remain committed to providing an inclusive and diverse environment for discussion, encouraging a variety of opinions and ideas. It is essential to consult directly with a qualified legal or financial professional to navigate the landscape effectively.