Built for then
There’s a moment in most scale-up (ie post-startup) businesses when someone — usually not the founder — looks around and realizes the company is juggling two operating systems at once. The old one, built for speed and founder judgment and improvisation. And the new one, which doesn’t exist yet but which the business desperately needs.
That moment is usually when I get the call.
Startups work the way they do for a reason. When you’re small, speed is survival. Process is overhead. The founder’s judgment is faster than any committee, and their relationships are the business. A ten-person company can operate on vibes and trust and a shared sense of mission because the founder is in the room. They set the tone, resolve the conflicts, make the calls. Everyone is close enough to the center that the warmth reaches them. Vision, strategy and company motivation are grounded in the founder’s ideas, principles and goals.
This is not a bug. It’s the feature. It’s what lets startups move in ways that established competitors cannot. The chaos is productive. The improvisation is creative. The founder’s fingerprints on everything are a form of quality control.
The problem is that none of it scales.
Before going further — founders deserve real credit. Getting a company to $10 million in revenue, or to the point where private equity comes knocking, or to the moment when a sale becomes possible, is a genuine achievement. It requires courage, personal sacrifice, and a tolerance for uncertainty that most people simply don’t have. The bravery it takes to start something from nothing, and to keep going through the years when it isn’t working, is not something that gets acknowledged enough in the conversations about what comes next.
But that bravery — and the instincts that went with it — were built for a specific environment. They are 1.0 instincts, and they are exactly right for a 1.0 company. The question isn’t whether the founder was capable. They demonstrably were. The question is whether a 1.0 operating system can run a 2.0 company.
I find it useful to give this a name. Not because naming it solves anything, but because it creates a shared frame of reference for conversations that are otherwise slippery.
I use version numbers — borrowed deliberately from the software world, where a new release isn’t an admission that the last one failed; it’s recognition that the context has changed. Company 1.0 is the startup: fast, founder-led, improvised, personal. Company 2.0 is the scale-up: structured, distributed, process-driven, repeatable. Some businesses glimpse a Company 3.0 on the horizon — the corporate, the publicly listed entity, the division of something much larger.
These aren’t rigid categories. They’re languages. When you can say “we’re a 2.0 business trying to run on a 1.0 operating system,” people understand immediately what the problem is. The version number does what org charts and strategy decks usually can’t: it puts everyone in the same picture.
The instincts of a 1.0 leader — bravery, decisiveness, personal ownership, speed — don’t disappear in a 2.0 company. But they get superseded by a different set of operating characteristics: repeatability, accountability, process, delegation, trust, empowerment. These aren’t personality traits so much as features of a different operating system. A company that has them can distribute decision-making across layers without losing coherence. One that doesn’t will keep pulling every decision back to the top.
Most founders build companies that, in some important way, serve their own vision of what work should be. That’s not criticism — it’s observation. The culture reflects the founder’s values, their hours, their tolerance for ambiguity, their relationship with hierarchy, often rooted in their deliberate rejection of how larger companies operate. In a company of eight, that’s fine. When it’s eighty or two hundred, the founder’s personal operating preferences have become an organizational structure, and not everyone chooses to work inside someone else’s lifestyle.
I’ve worked with founders who confused intimacy with accountability. Who built organizations so centered on their personal authority that there was no real management layer — just the founder, and then everyone else. Who took pride in being accessible to everyone, which sounds healthy until you realize it meant decisions couldn’t happen without them. Who genuinely believed that the creative chaos that produced the product was the culture, not a side effect of being small.
The transition to a scale-up requires something most founders don’t see coming: the company has to become, in meaningful ways, less like them.
A scaling business needs distributed decision-making. It needs leaders in the second and third layers who can operate with real authority, not just execute instructions. It needs process — not bureaucracy, but repeatable approaches to recurring problems, so that institutional knowledge lives somewhere other than one person’s head. It needs a management layer that can hold the culture without the founder being in every room.
None of that comes naturally to someone who succeeded precisely because they didn’t need any of it, or worse, believed those things stifled agility and growth.
The scale-up executive — whether that’s still the founder or someone brought in alongside or eventually instead — needs to be comfortable with indirectness. With hearing about problems that have already been partially solved by the time they surface. With trusting that the judgment calls happening three layers down are sound, because the system has been built to make them sound. That’s a fundamentally different relationship with the organization than the one that built it.
Some founders make this transition. Many cannot, or not fully. The ones who struggle tend to do so not because they’re incapable, but because they’re being asked to change their relationship with something that is, in a real sense, personal. To let the company become less theirs. That’s harder than any operational challenge I’ve encountered.
What gets talked about less is the employee problem.
The people who joined early were selected for startup traits. They were the ones who could work without structure, tolerate ambiguity, follow the founder’s instinct into uncertain territory. They were rewarded for improvisation. They learned — often without realizing it — to read the founder’s mood, to bypass whatever process existed because the founder preferred speed. They built careers on being close to the center of gravity.
These are not scale-up skills.
In a scaling business, the ability to improvise can become an allergy to process. Closeness to the founding team can become a political currency that newer, often more capable people simply can’t earn. The “we figure it out together” culture can become cover for the absence of genuine accountability. The founding team’s loyalty to each other — forged in the early days when it was all that held the company together — can become a ceiling.
Some early employees make the transition. They’re the ones who understood that their value was in what they could do, not in who they knew. Who were curious about the next stage rather than defensive of the one that made them. They’re often among the most valuable people in the building.
But many don’t — not because they’ve failed, but because they were optimized for something that no longer exists. The reconditioning is possible, but it requires honesty: about what’s changing and why, and about what the old behaviors actually were. Leadership has to model the new way rather than just demand it. You can’t ask people to operate differently while the founder is still running on 1.0 instincts.
The companies that navigate this transition well tend to do one thing differently: they name it.
Not just “we’re growing.” Something more specific. We are moving from Company 1.0 to Company 2.0. The operating system is changing. What made us successful here will not, by itself, make us successful there. Here is what 2.0 looks like. Here is what it asks of you.
They have an honest conversation — sometimes uncomfortable — about what the startup required and what the scale-up requires. They separate what was essential from what was incidental to being small. They acknowledge that the people who built the company may not be the people who take it to the next stage, and they treat that as an organizational challenge rather than a question of loyalty.
What I’ve seen, more than once, is this transition failing not because the company lacked talent or strategy, but because nobody said clearly that the transition was happening. The founder kept operating as a founder. The early team kept operating as a startup. And somewhere in the middle, the company that needed to emerge got stuck between the company that existed and the one it was trying to become.
Naming it is not the solution. But it’s where every solution I’ve seen has started. There’s a related question that sits underneath all of this — not just how the company operates, but what it’s now for. That’s the subject of the next piece.