Why Frontier-Tech Companies Need a Mission-Critical Operating System: Brian Garrett of Crosscut Ventures on the Age of Bits-Enabled Atoms

The next generation of consequential technology companies will not be built through software alone. They will combine artificial intelligence, advanced manufacturing, specialized hardware, energy systems, physical infrastructure, and complex supply chains to solve difficult problems in the physical world.

These companies need more than exceptional engineers, committed founders, and sufficient capital. They need an organizational operating system capable of coordinating highly specialized teams, managing interdependent work, learning from imperfect information, and maintaining execution discipline when the consequences of failure are significant.

That is one of the clearest implications of a Tech Scenes conversation between Collective Genius founder Jeff Martin and Brian Garrett of Crosscut Ventures.

Garrett described a major shift in where technological and economic value may be created. In his view, the software age is giving way to what he called an “AI-driven, bits-enabled atoms” paradigm. Software and artificial intelligence will remain essential, but they will increasingly enable physical products and systems in advanced manufacturing, advanced materials, energy, power, space, and defense.

The shift from software alone to intelligent physical systems changes more than the product. It changes how the company must operate.

The Frontier-Tech Shift Is Also an Organizational Shift

Crosscut Ventures began in 2008 with a commitment to helping catalyze the Southern California technology ecosystem. Garrett, Rick Smith, and Brett Brewer recognized that a meaningful innovation flywheel was beginning to form in the region, even though institutional capital had not yet fully embraced Los Angeles as a major technology market.

The timing was difficult. Crosscut raised its first capital shortly before the global financial crisis and then had to build through an environment in which additional fundraising became extremely challenging. Garrett continued operating companies while the firm built its early investment record.

Over time, Crosscut established an institutional platform and invested across several technology categories. Garrett eventually found himself moving deeper into space, defense, energy, power, advanced manufacturing, and other physical-world technologies.

As he described it, he went down the frontier-technology rabbit hole and was not interested in coming back.

That evolution was not simply a change in investment category. Garrett saw a concentration of talent emerging from companies such as SpaceX, Anduril, Tesla, and other Southern California technology organizations. These experienced operators were not leaving successful companies to build minor product extensions. They were setting out to address enormous problems in manufacturing, energy, space, defense, and national infrastructure.

Garrett’s job, as he described it, was to follow the talent.

The founders and operators entering these markets brought a different level of ambition. They were combining artificial intelligence with mechanical engineering, advanced materials, autonomous systems, new manufacturing methods, and redesigned supply chains. They were questioning assumptions that had constrained established industries for decades.

But the more technically ambitious the company becomes, the more organizationally demanding it becomes as well.

A frontier-tech company may need to align scientists, engineers, manufacturing leaders, government-relations specialists, commercial teams, finance leaders, supply-chain partners, regulators, and investors. Each group brings different expertise, timelines, risks, and definitions of success.

Without a shared operating system, the organization can become a collection of brilliant but disconnected specialists.

Mission-Driven Is Not the Same as Execution-Ready

Garrett observed that frontier-tech founders tend to be more mission-driven than many of the founders he encountered during earlier technology cycles.

They are not merely pursuing an attractive market. Many are attempting to strengthen domestic manufacturing, develop new energy sources, improve national security, reduce dependence on vulnerable supply chains, or expand what is possible in space.

That mission can become an enormous organizational advantage. It attracts people who want their work to matter. It creates resilience when the product is difficult to build. It gives customers, employees, investors, and partners a reason to believe in what the company is attempting.

But a powerful mission does not automatically create an organization capable of executing it.

A founder may clearly understand the technological future and still struggle to translate that future into coordinated work across the company. The leadership team may agree that the mission matters while disagreeing about the sequence of priorities required to achieve it.

Engineering may optimize for technical performance while manufacturing optimizes for repeatability. Product may push for additional capabilities while finance focuses on runway. Business development may pursue customer opportunities that create entirely new technical dependencies. Government customers may introduce requirements that affect design, compliance, production, and delivery.

Everyone can be working hard in service of the same mission while still moving in different directions.

This is why frontier-tech companies need more than inspiration. They need alignment around where the company is going, what must happen next, who owns each result, how progress will be measured, and how the organization will respond when assumptions change.

Mission creates commitment. Organizational execution converts that commitment into progress.

Frontier Technology Is Often Mission-Critical Technology

Many frontier-tech companies are not only mission-driven. Their products are also mission-critical.

During the Tech Scenes episode, Garrett discussed a company developing directed-energy technology designed to stop drones. He noted how immediate the need for such a capability had become as autonomous and unmanned systems played a larger role in modern conflict.

A product like that cannot be evaluated only by whether it is innovative or whether the market is large. It must work under demanding real-world conditions. Range, reliability, manufacturing capacity, operational integration, response time, cost per use, and field performance all matter.

Similar conditions exist throughout frontier technology.

A satellite component must operate after launch. An energy system must produce power safely and consistently. A defense platform may need to perform in an environment where failure creates immediate consequences. A manufacturing process must produce repeatable quality, not simply a compelling prototype.

Mission-critical performance places greater demands on the entire company. Product, engineering, manufacturing, finance, regulatory, sales, operations, and supply-chain teams cannot function as separate islands. Each depends on the others.

The organization must operate as a coordinated team of teams.

Physical-World Innovation Increases Coordination Complexity

Conventional software companies can often release an early product, observe how customers use it, correct defects, and deploy another version relatively quickly.

Frontier-tech organizations do not always have that flexibility.

A hardware design may require expensive tooling. A material may need extensive testing. An energy system may face safety and regulatory requirements. A satellite component must survive launch and operate in an environment where repair may be impossible. A defense system may need to perform reliably under extreme conditions. A manufacturing process must produce consistent quality, not simply an impressive demonstration.

These constraints create more dependencies across the organization.

A product decision can affect manufacturing costs. A supply-chain delay can change a customer commitment. A regulatory requirement can alter the engineering roadmap. A capital decision can affect production capacity. A design improvement can create new testing needs and push back delivery.

The company therefore needs a shared operating picture.

Leaders must be able to see which critical objectives are on course, where dependencies exist, what risks are emerging, and which decisions require cross-functional involvement. Teams need enough visibility to coordinate without waiting for the founder to personally connect every function.

This is organizational intelligence: the ability to transform information from across the company into shared understanding and coordinated action.

Without it, the company may have tremendous amounts of data but little common awareness. Different teams see different parts of reality. Problems remain local until they become organizational. Decisions are made without understanding downstream consequences.

In a mission-critical organization, that fragmentation is not merely inefficient. It creates execution risk.

First-Principles Product Thinking Requires First-Principles Organizational Design

Garrett described frontier-tech founders as clean-slate thinkers who are often willing to ignore the history of an industry and redesign the solution from first principles.

They do not accept that something must be built a certain way simply because it has always been built that way. They reconsider the product, materials, manufacturing system, supply chain, and economics.

That same first-principles discipline should be applied to the organization.

Many founders unintentionally inherit disconnected operating habits from conventional startups, large technology companies, government programs, academic research environments, or traditional manufacturers. Each leader arrives with a different idea of how planning, decision-making, meetings, metrics, and accountability should work.

The engineering leader may bring one system. The manufacturing leader brings another. The commercial leader introduces a third. The founder becomes the interpreter connecting all of them.

This can work while the company is small. Everyone remains close to the founder, information moves informally, and major decisions can be made through constant interaction.

It becomes much less effective as the company scales.

The organization needs a shared system that preserves the expertise and autonomy of each function while creating common habits for alignment, planning, visibility, decision-making, and learning.

This does not mean forcing every team to perform identical work. It means giving every team a common language for how the company operates.

Frontier-Tech Companies Need a Team-of-Teams Model

A frontier-tech organization cannot function as one large, undifferentiated team. Its work is too specialized.

Engineering needs technical depth. Manufacturing needs operational control. Commercial teams need customer awareness. Finance needs capital discipline. Regulatory and government teams need fluency in environments that may be unfamiliar to the rest of the company.

Each team must retain its expertise and decision-making capability. At the same time, those teams must operate as parts of a larger system.

That is the essence of a team-of-teams organization.

The objective is not central control over every decision. It is coordinated autonomy. Teams should be empowered to operate within their areas while remaining aligned to shared company priorities and visible to the functions that depend on them.

For this to work, the organization needs clear answers to several questions.

Why does the company exist? Where is it going over the next several years? What must be true by the end of this year? Which organizational capabilities need to be built during the next quarter? Which metrics reveal whether the company is learning and progressing? Who owns each result? Which decisions can be made within a function, and which require broader organizational input?

When these answers remain implicit, coordination depends on individual relationships and founder intervention.

When they become visible and regularly reinforced, the organization can move with greater speed and confidence.

Commercialization Is an Organizational Challenge

Garrett’s frontier thesis extends beyond the invention of new technology. He is particularly interested in whether technologies can cross the difficult gap between technical promise and commercial scale.

In the episode, he discussed the importance of modular, mass-manufacturable systems in energy and power. The underlying belief is that frontier technologies need viable production economics, repeatable manufacturing, and a path to commercialization.

That requires more than building a working prototype.

The company must connect technology development to production, customer demand, capital requirements, pricing, delivery, and long-term economics. It must decide which capabilities to build internally, where to use partners, how to sequence investment, and when the organization is ready to scale.

These are cross-functional organizational decisions.

A company can have a successful technical demonstration while remaining unprepared to manufacture, deliver, support, and improve the product at scale. Investors and boards may see technical progress without realizing that the organization lacks the operating capacity required for commercialization.

An organizational operating system makes that capacity more visible.

It connects the long-term destination to the one-year plan, the one-year plan to quarterly objectives, and quarterly objectives to the weekly work of the organization. It creates a cadence in which technical, operational, commercial, and financial information can be reviewed together.

The result is not certainty. Frontier technology will always involve uncertainty.

The result is a company that can learn and adapt intentionally rather than react after problems become unavoidable.

What a Mission-Critical Operating System Must Accomplish

A mission-critical operating system must begin with alignment. The organization needs a clear mission, a tangible long-term direction, and an agreed definition of success for the year ahead.

It must then create focus. The company cannot pursue every technically interesting opportunity or respond to every potential customer request. It needs to identify the small number of capabilities and outcomes that matter most during the current period.

It must establish accountability. Every important objective, result, decision, and dependency needs clear ownership. Accountability should create confidence and empowerment, not bureaucracy.

It must create organizational visibility. Teams need to understand how their work connects to the larger mission and where their priorities intersect with the work of other functions.

It must support disciplined communication. Meetings should surface relevant information, resolve important issues, and produce decisions and action. They should not become repetitive status exchanges that consume the time required to execute.

Finally, the system must help the organization learn. Frontier-tech companies operate with incomplete information. Their plans will evolve as technical results, market signals, customer requirements, and regulatory conditions change. The organization therefore needs regular moments to review assumptions, identify lessons, and adjust course.

These capabilities are central to Peak OS and to the organizational principles explored in Peak Teams.

Collective Genius has facilitated Peak with Crosscut and some of its portfolio companies. That work does not need to be the center of the Crosscut story, but it demonstrates a willingness to invest in how founders and teams operate—not only in the technologies they are building.

No organizational system can eliminate the risks of frontier technology.

The purpose is to ensure that technical uncertainty is not compounded by avoidable organizational confusion.

The Companies Building the Future Must Also Build Themselves

Garrett’s thesis about “AI-driven, bits-enabled atoms” points to a future in which technology becomes increasingly embedded in the physical systems on which society depends.

That future will be built by founders with extraordinary ambition, technical teams capable of challenging long-held assumptions, and investors willing to support difficult work over long timelines.

But it will also be built by organizations that know how to execute.

The companies that win the frontier era will not necessarily be those with the most compelling early demonstration. They will be the companies that can repeatedly turn technical insight into coordinated action, manufacturing capability, customer value, and organizational learning.

They will preserve the speed and conviction of a startup while developing the discipline of a mission-critical organization.

They will understand that the technology and the team cannot be separated.

A company building the next generation of energy, manufacturing, space, or defense technology is also building the organization that must bring that technology into the world.

That organization needs an operating system of its own.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?