Welcome to the 117th edition of Deep Tech Catalyst, the educational channel from The Scenarionist where science meets venture!
This week, we turn to one of the hardest questions in Deep Tech: what it really takes to scale a company when technical ambition collides with manufacturing complexity, cost pressure, and the realities of execution.
I sat down with Nicholas Brathwaite, Founder and Managing Partner at Celesta Capital, to unpack how an operator-turned-investor thinks about speed, scale-up, and the conditions under which a technical breakthrough becomes a business that can actually reach the market at meaningful scale.
Key takeaways from the episode:
⚡ Speed Is the Startup’s Most Defensible Advantage
Startups rarely win on resources. They win when they move faster than larger competitors, and that only happens when speed is treated as a core operating principle.
🧠 Intellectual Density Beats Headcount
In Deep Tech, the real force multiplier is not team size but team quality. Small companies scale best when they are built around concentrated technical depth, judgment, and execution capability.
🏭 Manufacturing Scale Requires Systems, Trust, and Process Discipline
Scaling is not just about adding capacity. It means developing, characterizing, documenting, and transferring processes in a way that allows new products and new manufacturing sites to perform without costly mistakes.
💸 Cost Has to Be Designed In Early
If cost matters, engineers need access to cost information while they are designing, not after the design is finished. Otherwise, the company risks building a product that works technically but cannot support a viable business.
📈 Differentiation Becomes Real Through Pricing Power
Gross margin is not just a financial metric. It is also one of the clearest signals that the market sees the product as truly valuable and hard to replace.
🎯 There Is No Universal Formula for Scale
Timelines depend on the product, the market window, and above all the team. The real discipline is not following a template, but being clear about the objective and building the organization that can execute against it.
BEYOND THE CONVERSATION — STRATEGIC INSIGHTS FROM THE EPISODE
Speed Is the Startup’s Most Defensible Advantage
One of the clearest ideas to emerge from the conversation is that speed is not just an operational preference. It is often the most important competitive advantage a startup has.
That is especially true in Deep Tech, where founders are often solving difficult technical problems under severe resource constraints.
A young company will almost never have more capital, more people, or more institutional reach than the larger incumbents operating in the same space.
However, in many cases, the real competition is not another startup. It is a large, established company with far more resources and the ability to direct hundreds or even thousands of people toward a similar opportunity.
That reality changes the way execution has to be understood.
A startup cannot rely on scale, because it does not yet have scale. It cannot rely on organizational depth, because it does not yet have depth. What it can rely on, if it is well built, is the ability to move faster than larger organizations can.
Speed only becomes valuable when the leadership team genuinely internalizes it as a core belief.
If the founders do not truly believe that speed is one of their greatest advantages, then the organization will not behave accordingly.
Processes will slow down. Decisions will linger. Priorities will blur. And the company will start operating as if it had plenty of time.
That is usually a mistake, for a simple reason: the problems startups choose to solve are rarely invisible to everyone else. Other teams are often working on them too.
In that kind of environment, success is not determined only by whether the idea is strong. It is often determined by how well the company executes, and whether it reaches the market at the right moment.
A startup can have a better technical idea and still lose if someone else gets there first with a solution that is good enough and commercially timed better.
In that sense, speed is not separate from strategy. It is an important part of strategy.
Faster doesn’t necessarily mean having more people.
The conversation also made a more nuanced point about what enables speed in practice. It is not simply intensity. It is not asking a small team to work harder and harder.
It is building what was described as “intellectual density”.
That idea is important because startups are often tempted to think about scaling through headcount. But early on, they do not have the luxury of hiring large numbers of people, and in many cases they should not want to.
What matters more is whether the team contains the critical skills and judgment required to solve the hardest problems quickly and correctly.
Large companies often employ many people while relying heavily on a much smaller group of truly critical contributors.
Startups begin from the opposite condition. They have very few people, so each person has to matter disproportionately. The team has to be dense in capability.
In other words, the goal is concentration of talent.
This is why hiring quality becomes such a decisive lever. When a company is trying to move quickly through difficult technical and operational challenges, average talent is not neutral. It becomes a drag on speed.
The stronger the team, the fewer handoffs, corrections, delays, and organizational frictions it creates.
Execution quality and timing determine who captures the opportunity
What makes this insight particularly relevant to Deep Tech is that many founders are trained to think first in terms of technical validity. The product has to work. The science has to be right. The engineering has to hold up.
But execution is what determines whether that technical progress turns into a real market position.
The conversation framed this very clearly: having a great idea is not enough. What matters is whether the company can execute well enough, and fast enough, to capture the opportunity before someone else does.
In markets shaped by timing and capital intensity before revenue, that distinction can be decisive.
It is how a smaller company can create asymmetry against larger competitors. A useful way to frame the whole idea is through a simple principle:
The fast can beat the big.
Scaling Manufacturing Requires Systems, Trust, and Exceptional People
If speed is a startup’s most defensible advantage, manufacturing scale is where that advantage is tested under pressure.
What came through clearly in the conversation is that scaling manufacturing is not simply a matter of adding capacity. It is a matter of making complex processes repeatable, transferring knowledge without distortion, and doing so in environments where mistakes are expensive and often highly visible.
In that setting, growth is not just about moving faster. It is about moving faster without losing yield, reliability, or operational control.
That distinction matters because many Deep Tech companies underestimate what scale actually demands.
It is easy to speak about expansion in abstract terms. It is much harder to take a new product, a new process, and a limited team and make them work consistently across different sites, different managers, and different operating contexts.
Scale begins long before the factory ramps
One of the strongest insights from the episode is that manufacturing scale really begins upstream, in process development.
Before anything can be deployed broadly, the process itself has to be developed, optimized, characterized, and documented well enough that other teams can implement it successfully.
That is not administrative work. It is part of the core technical effort.
If the process is not understood deeply enough at the source, it becomes very difficult to reproduce performance at the destination.
The example discussed in the conversation makes the point concrete.
Launching a new product across multiple geographies at the same time is not simply a logistics challenge. It requires new process capabilities to be developed centrally, refined there, and then transferred into different factories that must all be able to execute at the required standard.
The burden is even greater when both product and process are new, because the organization is effectively scaling two forms of uncertainty at once.
That is why scale cannot be improvised. The discipline required is cumulative. It comes from doing the work early enough, rigorously enough, that the organization can smoothly move into execution.
The hardest challenge is often coordination across boundaries
The conversation also highlighted a point that is easy to overlook: many of the hardest problems in scale-up are organizational, not purely technical.
When technology teams and factory teams sit in different parts of the organization, the challenge is not only to define the process correctly.
It is also to make sure different groups understand the objective in the same way and can act on it in a coordinated manner. That requires alignment across organizational boundaries, which is often where complexity compounds.
In practice, this means that even a strong central team can become stretched very quickly.
A relatively small group may be responsible for developing the process, documenting it, and then helping multiple sites implement it at the same time.
The bottleneck is not only technical knowledge. It is the ability to transfer that knowledge clearly and support its execution without fragmentation.
This is where scale becomes a management discipline as much as an engineering discipline. The organization has to know who owns what, how information moves, and how accountability is maintained when the work is distributed across regions.
Without that, problems emerge not because the company lacks technical capability, but because its coordination model cannot support the complexity it is trying to manage.
Exceptional people matter more when the margin for error is low
Another key idea from the episode is that manufacturing scale depends heavily on talent quality, especially when the operating model leaves little room for mistakes.
In the conversation, this appeared not as a generic statement about hiring, but as a practical lesson learned under extreme growth conditions.
In a capital-intensive hardware business, there is little tolerance for operational errors.
Yields have to come up quickly. New processes have to work. Product launches cannot be allowed to absorb endless cycles of correction. Under those conditions, average execution is not enough.
That is why the emphasis returned so strongly to the quality of the team.
If the business is trying to do difficult things quickly, then it cannot rely on a large quantity of mediocre capability. It needs unusually strong engineers and leaders who can solve problems, transfer knowledge, and keep execution on track.
This is particularly important in environments where the historical talent base may not have been strong enough for the ambitions of the business.
When the objective changes, the talent model often has to change with it. A company trying to scale advanced processes cannot assume that conventional staffing will be sufficient if the task now requires a much higher level of technical and operational sophistication.
Manufacturing and product teams cannot work as separate worlds
The discussion also offered a useful way to think about the relationship between development and manufacturing.
A product cannot simply be created on one side of the organization and then thrown over the wall to the other.
That model breaks down because manufacturing is not a passive recipient of design decisions. It has to understand the product deeply enough to optimize for performance, cost, reliability, and execution at scale.
And product teams need enough understanding of manufacturing realities to avoid designing in ways that create unnecessary complexity later.
A more effective model is one of overlap and collaboration.
Rather than treating the transition as a clean handoff, the work has to resemble a relay in which both sides run together for a period of time.
That overlap is what allows the manufacturing team to absorb not only the formal process, but also the practical knowledge, constraints, and sensitivities that determine whether scale-up succeeds.
Designing for Cost Before the Market Decides for You
One of the most practical insights from the conversation is that cost discipline cannot be treated as something to solve after the product is built.
In Deep Tech, especially in manufacturing-heavy businesses, founders often concentrate first on technical feasibility and only later turn to economics.
But the discussion made clear that this sequence can be dangerous.
If the company reaches the market with a product that works technically but cannot support a viable margin structure, it may never get the chance to fix the problem.
In other words, the business can run out of room before it runs out of ideas.
That is why cost has to be designed in from the beginning. Not as a finance exercise layered on top of engineering, but as part of the engineering process itself.
Business ambition has to shape technical choices
Simple, but not always obvious: the technology must support a business opportunity, not the other way around. In the operating environments described in the episode, every major initiative had to meet 2 tests:
It had to become meaningful at scale.
it had to improve the economics of the broader business.
A new product or line of business had to justify its place by contributing materially to revenue and by supporting better margins than the baseline business.
That decision-making process is especially relevant in hardware-focused businesses, where margins are lower than in SaaS. If a new initiative cannot scale meaningfully, it will not matter. If it cannot improve margins, it may not be worth pursuing.
This does not mean every Deep Tech company should use the same numerical targets. It means founders need to be explicit about the business they are trying to build.
Growth expectations, margin expectations, and cost structure all need to be thought through early, because they shape technical decisions long before the market sees the final product.
Engineers need access to cost while they are designing
Another great point discussed is that engineers cannot be expected to design for cost if they only discover the cost after the design is complete.
That problem is more common than it should be.
Teams design with the information they have, then pass the work to procurement or finance to obtain quotes, and only afterward realize they have missed the target.
At that point, the organization is no longer managing cost proactively. It is reacting to it.
The episode framed this through a simple comparison: it is like playing a game without a scoreboard and then reading the result in the newspaper the next day. Once the game is over, the information is no longer useful for influencing the outcome.
If cost matters, the engineers need the relevant data while they are making design decisions.
They need visibility not only into the cost of individual components, but also into the architectural consequences of choosing one design path over another.
In many cases, the biggest cost decisions do not come from substituting one part for a cheaper one. They come from the overall structure of the product and the combination of choices embedded in the design.
That is why “cost visibility” is essential: it keeps engineering aligned with the real business objective instead of pursuing the technical challenge in isolation and discovering costly surprises later.
Designing for cost does not mean reducing everything to the lowest possible price.
The point is not to make the cheapest product. The point is to build a product whose cost structure is coherent with the market opportunity, the margin target, and the strategy of the company.
That may still require high performance, strong reliability, and sophisticated technical choices. But it requires making those choices with economic awareness, not in isolation from it.
This is especially important because cost is rarely a single-variable issue. Product architecture, manufacturability, testing, reliability, and supply chain decisions all influence the eventual economics.
Time to market can outweigh perfect cost optimization
There are situations where time to market matters more than perfect cost optimization.
A startup may face a window of opportunity narrow enough that being early is more valuable than reaching the ideal margin on the first version of the product.
If the market is moving quickly, a slower but more economically elegant approach may lose to a faster one.
That trade-off has to be made consciously. It is not enough to say that both speed and cost matter.
The team has to know which objective matters more at that moment, and then organize around it. If speed is the priority, that should be explicit. If cost is the priority, that should be explicit too.
Ambiguity at that level usually creates confusion in execution.
What matters most is alignment between the objective and the system. Engineers need to know what they are optimizing for.
And once that priority is defined, the company has to provide the tools, data, and operating discipline that make it possible to pursue it.
That is the larger lesson here. In Deep Tech, economics do not begin after the technology works. They begin when the company decides what kind of business it is trying to build, what trade-offs it is willing to make, and whether its teams are equipped to design accordingly.
When that discipline is present, cost becomes a lever. When it is absent, cost becomes a surprise. And by the time it becomes a surprise, the market is often already making the decision for you.
Differentiation Shows Up in Pricing Power
A strong product story is not fully validated by technical performance alone. It is also validated by the price the market is willing to accept.
One of the most important points in the conversation is that gross margin is not just a profitability metric. It is also a signal.
If a company claims to have built something meaningfully differentiated, but the business cannot command margins that reflect that differentiation, then the market may be saying something important about how unique the product really is.
That does not mean every company should expect the same margin profile.
Different markets behave differently, and some businesses will always operate under tighter constraints than others.
But the principle still holds: pricing power is one of the clearest external tests of whether a technical advantage is actually being recognized as valuable.
Margin reflects both economics and strategic position
To recap, higher gross margin obviously improves the economics of the business, but it also says something deeper about the company’s position in the market.
If the product is genuinely providing substantial value, then the company should not be afraid to pursue pricing that reflects that value.
In some of the businesses discussed, that means aiming far above the margin thresholds that would be acceptable in a services business or a low-margin manufacturing context.
The goal is not to set an arbitrary number. The goal is to align price with the real strategic importance of what the company is delivering.
That is why margin should not be treated only as an internal planning assumption. It is also a form of market feedback.
A product that customers truly need, and that few others can provide, should be able to support materially better economics than one that is easily substituted.
Founders should not price their products as if they were commoditized.
This is especially relevant for Deep Tech founders coming out of technical environments, where the instinct is often to be conservative in commercial assumptions.
In practice, that can become self-defeating. If a company has built something that creates real competitive advantage for the customer, then it should not automatically price as if it were interchangeable with everything else in the market.
The conversation was clear on this point: when the value is there, the company should try to command the price it deserves.
Of course, that is easier to say than to do. Markets push back. Customers negotiate aggressively. Early commercial relationships are rarely comfortable. But that does not change the underlying logic.
A founder should not begin from the assumption that margin must always be modest. In many cases, the more appropriate starting point is much more ambitious, even if the final outcome lands somewhat lower.
There is a practical reason for this as well.
If a company starts by targeting too little, it can easily end up with a business that looks weaker than it should, not because the technology lacks value, but because the company never tried to capture that value properly.
Pricing power becomes clearest when the product is truly scarce
The most vivid commercial example in the conversation came from a negotiation with a large prospective customer.
The customer pushed hard for a price that could not realistically be accepted.
The response was not to retreat into compromise, but to hold firm based on a clear understanding of the situation: the product was differentiated, no one else had it, and the customer wanted it because it represented a competitive advantage.
That confidence changed the structure of the negotiation.
Once the customer understood that the product would not be priced as if it were generic, the conversation shifted away from pure price pressure and toward exclusivity.
In other words, the real issue was not that the product was overpriced. It was that the customer understood how strategically valuable it was and wanted privileged access to it.
The resolution is telling. Exclusivity was not granted formally, but the customer was offered a different path: it could secure the full capacity of the factory.
That way, the supplier preserved pricing discipline, and the customer got the practical exclusivity it wanted by occupying the available output.
The deeper lesson is that pricing negotiations become much clearer when the company knows exactly how differentiated its product is and refuses to negotiate as if that differentiation were uncertain.
Cost discipline gives the company room to negotiate
This also connects back to the earlier discussion on cost. A company that has designed for cost effectively has more options when it enters a negotiation.
If the underlying economics are strong, the company can choose whether to preserve higher margin or use some of that flexibility strategically.
If the cost base is weak, those choices shrink quickly. The business becomes vulnerable not only operationally, but commercially, because every pricing conversation starts from a position of constraint.
That is why the sequence described in the conversation is important.
First optimize cost. Then use that strength to give the commercial side of the business more room.
That does not mean pricing should be cost-plus. The point is not to anchor value to internal cost alone. The point is that stronger cost discipline gives the company the freedom to negotiate around value without being cornered by its own economics.
In some cases, that means defending price firmly because the product is truly scarce and strategically important. In other cases, it may mean accepting lower margins temporarily because the timing of entry matters more than near-term profitability.
The critical point is that the company should be making that decision from a position of clarity, not drift.
There Is No Formula for Scale, Only a Clear Objective and the Right Team
One of the most grounded points in the conversation is that scale does not follow a universal timetable.
Founders often look for a clean rule: how many months it should take, what milestone should trigger expansion, or what sequence should define the move from product development into real scale-up.
But the discussion pushed back against that view. There is no single rule of thumb that can substitute for judgment.
The timeline depends on the product, the technical complexity, the market window, and, above all, the quality of the team executing the work.
That is why scaling cannot be reduced to a formula. It has to be understood as the result of many layers of experience brought to bear on a specific objective.
Fast execution is possible, but only with the right people
If there is one point that gives substance to the whole discussion, it is that remarkable speed is possible when the team is unusually strong.
There were a few examples shared in the conversation that give a sense of the magnitude involved here.
A company building a complex chip and system business moved from initial funding to tens of millions in revenue in roughly a year and a half. Another company developed and launched a consumer product into major retail in less than a year. A small semiconductor team built an advanced inference chip in about eighteen months with only ten engineers, but those engineers carried an average of around two decades of relevant experience.
These examples are not meant to imply that every company should expect the same pace. They illustrate something more important: timelines are elastic when the team is exceptional.
The speed of execution is not determined only by the complexity of the product. It is also determined by the concentration of experience, judgment, and technical depth inside the organization.
That brings the argument full circle. A startup may never have the largest team, but it can still move with unusual force if the team it has is dense with the right capabilities.
Scale is less about rules than about readiness
Taken together, the discussion leads to a fairly demanding conclusion. There is no generic timeline that defines what fast looks like. There is no universal sequence that can tell every founder when to scale and how long it should take.
What exists instead is readiness.
A company is more ready to scale when it is clear about its objective, when product and manufacturing work in genuine collaboration, when the team is strong enough to solve problems without wasting motion, and when the business understands which variables matter most at that stage.
Under those conditions, speed becomes possible in a meaningful sense. Not because the company is rushing, but because it is aligned.
That may be the most important final reflection from the episode.
Scale is not an abstract milestone waiting somewhere in the future. It is the outcome of disciplined choices made early: who the company hires, how clearly it defines success, how well its teams work together, and whether it treats execution as a true strategic capability.
When those elements are in place, scaling can happen surprisingly fast. When they are not, no rule of thumb will save the company from moving slowly in the wrong direction.
Join The Scenarionist Premium!
Whether you’re an experienced investor leading an established fund, an emerging manager stepping into the field, an angel investor exploring new opportunities, or a founder eager to see the industry from a fresh perspective, The Scenarionist Premium is built for you.
