The Second-in-Command Role in Founder-Led Companies

The second-in-command is the senior executive who sits directly below the founder and runs a large share of the business day to day. The title varies: chief operating officer (COO), president, general manager, managing director, or "integrator" if the company uses the language of the Entrepreneurial Operating System (EOS). The title matters less than the job. This person takes over the part of running the company that the founder has been doing by default, so the founder can spend time elsewhere.

In a founder-led company, that handover is harder than it sounds. The founder usually built every function by hand, still holds the final say on most decisions, and may not be sure what they actually want to give away. That's why this role fails so often, and why it deserves a clear definition before anyone is hired or promoted into it.

What the second-in-command actually does

At its core, the role covers four kinds of work:

• Running operations. Turning the founder's direction into a working rhythm: plans, budgets, meetings, deadlines, follow-through.
• Integrating functions. Making sales, delivery, finance, and people work as one system instead of four separate fiefdoms.
• Holding the team accountable. Being the person executives answer to on results, so accountability doesn't depend on the founder's mood or availability.
• Absorbing decisions. Deciding the things that currently queue up waiting for the founder. A delegation of authority matrix is how those limits get written down.

Notice what's not on the list: vision, culture, and the biggest external relationships. In most founder-led companies those stay with the founder, at least at first. The second-in-command usually exists so the founder can do more of that work and less of everything else.

No standard job description

The first thing to understand about this role is that there is no single version of it. In a Harvard Business Review article on the COO role, Nate Bennett and Stephen Miles argue that asking what makes a great COO is like asking what makes a great U.S. vice president: the answer depends entirely on the CEO. The role takes the shape of the person above it and the company around it.

For a founder, that cuts two ways. It means you have freedom to design the job around what you need. It also means a vague hire is nearly guaranteed to disappoint, because two people can both be called COO and be doing completely different work.

Common shapes of the role

A widely used typology sorts COOs into seven kinds. This list follows a Shortform summary of Cameron Herold's book The Second in Command, which sets out the seven types and supplements them with Bennett and Miles's HBR research:

These types aren't exclusive, and one person can be a mix. But the list is useful as a diagnostic. If you can't say which of these you're hiring for, the role is probably underspecified. The "heir apparent" type is the one that connects most directly to founder succession, and it's the one most often assumed rather than agreed.

The visionary and integrator version

A second popular model comes from EOS. In that framework, the founder is typically the "Visionary" and the second-in-command is the "Integrator." EOS Worldwide describes the integrator as the person who has the ability to manage daily issues as they come up and to integrate the major functions of the business (sales and marketing, operations, and finance) into one harmonious group. The Visionary, on the other hand, is described as the one who generates ideas and creative solutions.

A later EOS Worldwide page on the two roles describes the integrator as the leader who runs the business day to day and holds the leadership team accountable, and says the two are partners: neither is the other's boss. That framing is useful because it tells the founder what they're agreeing to. In this model the second-in-command isn't an assistant or a deputy. They are closer to a co-leader who owns a defined territory.

Be careful with the model, though. It's a proprietary operating system with its own vocabulary, and the visionary and integrator labels aren't universal management terms. Use them if they help. Don't treat them as established research.

The Adizes version

A third lens comes from Ichak Adizes. His PAEI model sorts management work into four roles: Producer, Administrator, Entrepreneur, and Integrator, as the Adizes Institute describes in its leadership assessment. Many founders are strongest at producing results and spotting opportunities, which map to the Producer and Entrepreneur roles. A second-in-command is often hired to cover the Administrator and Integrator work that the founder has less appetite for (an observation about common practice, not an Adizes finding). For how a company's needs from its leaders shift as it grows, see the Adizes corporate lifecycle.

Why founders create the role

Founders usually reach for a second-in-command for one of five reasons:

1. Capacity. The founder is the bottleneck. Decisions queue, projects stall, and the founder's calendar is full of operational work.
2. Capability gap. The founder is good at starting and selling, and less good at systems, process, and people management.
3. Succession. The founder wants a trusted successor to emerge, or wants the company to survive without them.
4. Credibility. Lenders, investors, or acquirers want to see a management team that can run the business without the founder.
5. Risk. The company has too much riding on one person. See key person risk.

The reason matters because it shapes the job. A second-in-command hired to relieve capacity needs authority over operations. One hired for succession needs exposure to the board, the customers, and the strategy. One hired for credibility needs a track record the outside world can see. Mixing the reasons without saying so is one of the main ways the role goes wrong.

How the role fails

Most failures come from the same few causes. None of them are really about the person.

The founder won't actually delegate

The role is created on paper, and the founder keeps making the same decisions. The new executive has the title but not the authority, so the team keeps going around them to the founder. Within a year, the executive concludes that the job isn't real and leaves.

The scope was never written down

Without a defined territory, the second-in-command and the founder drift into overlap and conflict. Who owns pricing? Who approves hires? Who talks to the biggest customer? If the answer is "it depends," it will be settled by whoever is louder.

The type is wrong for the need

A change agent is hired when the company needed an executor, or a mentor is hired for a founder who doesn't want mentoring. The seven types above exist because these roles are genuinely different, and a mismatch is hard to fix.

The founder wanted a clone

Some founders hire someone like themselves. But the point of the role is usually to cover weaknesses, not duplicate strengths. A second-in-command who thinks and decides exactly like the founder adds capacity but not capability.

The team doesn't accept the role

If long-serving employees still treat the founder as the only real boss, the new executive can't lead them. The founder has to visibly route decisions through the new role, and say so to the team.

The unspoken succession question

If the second-in-command expects to become CEO and the founder has no intention of stepping aside, resentment builds fast. And if the founder expects the role to produce a successor but the executive has no interest in the top job, the plan fails quietly. Say which it is, early.

How to define the role

A good definition is short and specific. Before hiring or promoting, write down answers to these questions:

If you need a starting point for the written scope, a chief operating officer job description template lists typical responsibilities. Adjust it to match the answers above, not the other way around.

Hire, promote, or split

The role can be filled in three main ways, each with trade-offs:

• Promote an insider. They know the company and the people. The risk is that they're used to being a peer or subordinate, and the founder may keep treating them that way.
• Hire an outsider. They bring fresh experience and a clean start. The risk is cultural mismatch and a long ramp-up. Outsiders also tend to expose how much the founder's knowledge was never written down.
• Split the work. Some companies spread the duties across two or three leaders (a head of operations, a head of finance, a head of people) before naming a single number two. This works when no one person is ready for the full role.

Whichever route you take, treat the first year as a trial with explicit checkpoints. The point isn't to test the executive. It's to test whether the design of the role works.

How the role relates to succession

The second-in-command and the successor aren't the same thing, and mixing them up causes trouble. A second-in-command can be a great operator and never want, or be right for, the CEO job. A successor can be someone several levels below.

There are three common patterns:

1. The operator, not the successor. The role is permanent and the company knows the CEO will come from elsewhere. This is the clearest arrangement, and it's fine.
2. The heir apparent. The role is explicitly a preparation for the top job, with a timeline and a plan. This needs a candid conversation about what the founder will actually do once they step back, a theme covered in founder succession.
3. The bridge to an outside CEO. The second-in-command runs operations while the company decides whether to look for a new chief executive, as discussed in hiring an external CEO.

Even if you never name a successor, a capable number two lowers your exposure if the founder is suddenly unavailable. That's one reason the role keeps appearing in plans to reduce dependence on a single person. For the related question of who sits in the rest of the leadership team, see the management team below the founder.

Key Facts: The second-in-command role

• The role goes by many titles (COO, president, general manager, integrator). The job is defined by the scope the founder gives it, not by the title.
• Bennett and Miles argue that what makes a great COO depends entirely on the CEO, much as with a U.S. vice president.
• Cameron Herold's The Second in Command describes seven COO types: executor, change agent, mentor, other half, partner, heir apparent, and MVP.
• In the EOS model, the integrator manages daily issues and integrates sales and marketing, operations, and finance.
• EOS Worldwide describes the visionary and integrator as partners, with neither the other's boss.
• In Adizes' PAEI model, Integrator is one of four management roles, alongside Producer, Administrator, and Entrepreneur.
• Common failure causes: the founder won't delegate, the scope isn't written down, the type is wrong for the need, or the succession expectation is never stated.

Related reading

• Management Team Below the Founder
• Founder Succession
• Delegation of Authority Matrix
• Hiring an External CEO
• Key Person Risk
• Systems-Dependent vs People-Dependent Business
• Chief Operating Officer (COO) Job Description