Last week, I argued that capital can enlarge a company without making it more capable. A large financing round creates choices, but it does not create the operating architecture required to make those choices well. The related question is what happens to information and decision-making as the company grows.
We encounter this question both as investors and as board members. Frontier tech companies are unusually dependent on the quality of their decisions because their principal risks cannot be separated neatly. A technical decision may alter the regulatory pathway; a commercial commitment may impose a new manufacturing architecture; a financing decision may determine which scientific milestones can be reached before the next round. The people closest to each problem rarely possess authority over all of it.
In the early years, the founder holds these elements together. They carry the history of the technology, the reasons behind previous compromises and the relationships on which the company depends. This concentration of knowledge is initially a competitive advantage. If the company grows successfully, however, it can become one of its most important constraints.
Photo by Benjamin Child on Unsplash
The founder becomes the company’s most expensive queue
A founder’s early centrality is usually rational. They possess more context than anyone else, recognise hidden dependencies and can resolve disagreements without convening a constitutional assembly. In technical companies, they may also be among the few people capable of evaluating both the science and the commercial compromise under consideration. The organisation learns to route difficult decisions towards them because doing so produces better answers.
It continues after the volume of decisions has exceeded any individual’s capacity. The founder then becomes a queue: highly intelligent, strategically important and increasingly responsible for the latency of the entire system. Around a board table, this often appears as a discussion about workload. The proposed remedies include better meeting discipline, an executive assistant or the delegation of routine tasks. These measures can provide relief, but they do not address why decisions continue travelling upwards.
Usually, authority has been delegated without being specified. Managers are told to take ownership but remain uncertain which trade-offs they are permitted to make, so they seek approval. The founder, frustrated by the absence of initiative, intervenes and often improves the immediate decision. The organisation learns that escalation remains the safest procedure. A few repetitions are enough to establish the culture. The founder must eventually move from answering the greatest number of important questions to designing how important questions are answered. We have found this to be one of the hardest transitions in company building: it sounds like a promotion, but often feels like a loss of control.
Decision-making needs an architecture
Pushing decisions downwards does not mean treating every decision alike. Choices that alter the technical architecture, capital structure, regulatory exposure or survival of the company deserve senior attention. Reversible operating decisions generally need speed. A scaling organisation should make the distinction explicit: where does authority sit, when is consultation required, and what conditions trigger escalation? Without this architecture, “empowerment” remains an attractive word attached to a system of informal centralisation.
This is especially important in frontier tech companies, where decisions regularly cross functional boundaries. Engineering may understand what can be built, regulatory may understand what can be approved, commercial may understand what customers will buy, and finance may understand what the company can afford. None possesses the complete answer. The objective is not to remove the founder from consequential decisions but to ensure that the organisation can integrate these perspectives without asking the founder to arbitrate every disagreement.
A board can help by examining the flow of decisions rather than only their outcomes. Which decisions repeatedly arrive late? Which ones return to the founder after apparently being delegated? Where do teams wait because several people can object but nobody can decide? These questions reveal more about operating capacity than another discussion of organisational charts. Authority does not exist because a box appears beneath someone’s name. It exists when the organisation knows which decisions that person can make and expects those decisions to stand.
Reality deteriorates as it travels upwards
At twenty people, a founder can observe much of the company directly. At two hundred, they observe representations of it. Investors and boards are one step further removed. Information arrives through dashboards, management meetings, board materials and conversations that have already passed through several layers of interpretation. No deliberate deception is required. Each layer removes some uncertainty, sharpens the explanation and makes the situation slightly more suitable for presentation.
Good news travels rapidly because it is easy to deliver. Bad news waits for confirmation. A technical delay remains manageable until the recovery plan fails; a customer concern remains anecdotal until procurement stops responding; a hiring problem remains temporary until the preferred candidate joins a competitor. Hope, indispensable to entrepreneurship, begins performing tasks for which evidence would be more suitable. This matters particularly in frontier technology, where technical uncertainty cannot be managed through optimism. Biology remains indifferent to investor updates. Manufacturing yield does not improve because the quarterly narrative requires it. Regulators have yet to adopt the venture industry’s preferred relationship with deadlines.
As board members, we contribute to this filtration through our own reactions. If the person raising a problem is treated as its source, the organisation learns quickly. Future problems will arrive with more context, better formatting and less time remaining to solve them. We therefore try to distinguish bad outcomes from bad operating behaviour. Bad news raised early, accompanied by serious analysis and a clear owner, indicates that the information system works. Bad news concealed, minimised or repeatedly presented without ownership indicates that it does not. A board should react very differently to the two. Reality eventually enters the room; the only variable is how much time and capital have been spent before it does.
A dashboard is not an operating system
Scaling companies tend to acquire metrics at roughly the same time they acquire managers. Each manager needs information, each function needs objectives, and the board would reasonably prefer not to govern by anecdote. The result can be a large quantity of increasingly precise data describing an organisation that remains difficult to control. We do not need every board pack to contain more information; we need it to make the essential information harder to avoid.
Are the few trajectory-defining outcomes moving? What currently prevents them from moving? Who owns the constraint? Which decision is required, and from whom? Useful visibility does not attempt to create a perfect representation of the company. It shortens the distance between reality and action. A technically comprehensive dashboard can conceal as much as it reveals if the central risk appears on page forty-seven, surrounded by measures that are improving.
The same standard applies to meetings. A recurring meeting should make decisions, allocate resources, remove constraints or review commitments. The discipline is almost embarrassingly simple: meetings end with decisions, owners and dates, and the next meeting begins with the commitments made previously. Actions should not disappear into minutes that demonstrate excellent administrative hygiene but no institutional memory. Accountability is created less by intensity than by recurrence. What matters is not the dramatic intervention after a missed milestone, but the expectation that every commitment will return to the room.
What we believe an investor can usefully do
The venture industry has stretched the expression “hands-on” until it encompasses almost every form of investor behaviour short of remaining entirely absent. At Entropia Capital, operational involvement has a more specific meaning. Frontier tech companies’ principal constraints often span science, governance, regulation, industrial execution, capital formation and geography. Solving one component in isolation may not alter the company’s trajectory.
A European technology may require Asian manufacturing capability, Gulf infrastructure capital or North American commercial access. A technically successful company may remain unfinanceable because its governance, leadership structure or regulatory sequencing is unintelligible to the investors required for the next stage. An apparently substantial commercial opportunity may be strategically wrong because the company cannot deliver it without fragmenting its core platform. Our role is not to occupy the founder’s chair from a safer distance, nor to provide a collection of introductions and describe the resulting email traffic as value creation. We try to identify the transition that matters, assemble the relevant resources around it and remain involved until the company has materially changed state.
Sometimes this means assisting with senior recruitment or governance. Sometimes it means restructuring the financing logic around the real technical milestones. Sometimes it means connecting European science with Asian industrial capability, Gulf capital or American commercial access. And sometimes it means arguing against an attractive expansion because the underlying system cannot yet absorb it. The work varies because the constraints vary, but the principle does not: our involvement should make the company more capable and, eventually, less dependent on us. This is what we mean when we describe ourselves as blue-collar investors and operators. The phrase implies work, proximity to the constraint and the mildly inconvenient possibility of being judged by a visible result.
Building an institution
A company becomes an institution when the quality of its decisions no longer depends on one person being present in every consequential conversation, and when reality can travel upwards without being made comfortable along the way. The founder remains essential, but their leverage increasingly comes from designing the system rather than operating every part of it.
The board has a role in that transition. It should help make choices clearer, bad news safer to disclose and commitments harder to forget. It should bring perspective without creating another layer of management, and support the founder without preserving a form of dependence that the company has already outgrown.
At Entropia Capital, we believe the same test applies to the investor. Our work should leave behind better decisions, clearer ownership and greater operating capability, not simply a longer list of meetings in which we participated. Capital can finance the organisation. Building the institution requires something more demanding: an honest view of reality, a deliberate architecture for decisions and the discipline to make both survive beyond the people who created them.
The distinction between having governance structures and having genuinely independent governance is crucial. A board cannot challenge management if management controls everything the board is allowed to see.
The most unsettling question here is also the most useful: does the system surface uncomfortable truths automatically, or must someone risk their career to expose them? Too many organisations quietly depend on individual courage.