The 5-Person Stage: Founder Plus All-Rounders
At five people, you do not need a hierarchy. You need clear ownership. Everyone reports to the founder, everyone wears multiple hats, and the org chart — if you draw one at all — is a flat star with the CEO at the centre.
The useful exercise at this stage is not org chart design. It is a responsibility matrix: who owns product, who owns customer, who owns ops, who owns money. Overlapping ownership is fine — just name one primary owner per function. When something goes wrong, you need to know who to wake up.
The mistake founders make here is treating the five-person flat team as a permanent philosophy rather than a temporary state. “We don't do hierarchy” is a fine principle for a startup. It becomes a liability the moment you hit ten people and no one knows who is making the call.
The 15-Person Inflection: First Managers, First Departments
Somewhere between 10 and 20 people, every founder faces the same reckoning: they can no longer have a meaningful 1:1 with everyone every week. The span of control has exceeded what one person can hold. This is when the first management layer needs to appear.
The typical shape at this stage is three functional clusters — usually Product/Engineering, Commercial (sales + marketing), and Operations — each led by a senior individual who is still 80% hands-on but 20% coordinating others. These are not yet VP roles. They are team leads with manager titles.
CEO
├── Head of Product & Engineering (5 reports)
│ ├── Engineer × 3
│ └── Product Designer × 1
├── Head of Commercial (4 reports)
│ ├── Account Executive × 2
│ └── Marketing Manager × 1
└── Head of Operations (2 reports)
└── Operations Manager × 1Notice the CEO still has three direct reports, not twelve. That is intentional. The job at this stage is to create breathing room — not to build a bureaucracy, but to ensure the founder can focus on strategy and fundraising rather than managing every individual.
The 50-Person Structure: VP Layer and Functional Silos
By the time you hit forty to sixty people, the team lead model breaks. The people you promoted at fifteen are now managing eight to ten people each while still doing individual work. Something has to give.
This is when you formalise the VP layer. Each VP owns a function, a budget, and a headcount plan. They are no longer primarily individual contributors. They are accountable for outcomes, not tasks. Reporting lines should be explicit and consistent — no more informal “everyone knows who to ask” arrangements.
CEO ├── VP Engineering (12 reports) │ ├── Engineering Manager × 2 (6 engineers each) │ └── Head of Platform (2 engineers) ├── VP Product (6 reports) │ ├── Senior PM × 2 │ └── Designers × 3 ├── VP Sales (8 reports) │ ├── Sales Manager × 2 (3 AEs each) │ └── Sales Ops × 1 ├── VP Marketing (5 reports) └── CFO / Head of Finance (3 reports)
The CEO now has five to six direct reports, not thirty. Each VP runs their own team meeting, owns their own OKRs, and makes day-to-day decisions without escalating. The CEO's job shifts from managing people to managing the executive team.
Common Mistakes Founders Make
Promoting too early
Giving someone a VP title at 10 people because you want to retain them creates a political problem at 40. Now you have a VP Engineering managing three people in a company with 15 engineers. Either the title is wrong or the scope never grew to match it. Both outcomes are painful.
Skipping middle management
The instinct to avoid "layers of bureaucracy" often results in a senior manager with 15 direct reports, no time for anyone, and a team that feels unsupported. Middle management is not the problem — bad middle management is. One good engineering manager can make a team of six outperform a team of ten.
Reporting-line chaos from rapid hiring
When you hire fast, new people often end up reporting to whoever interviewed them rather than whoever makes sense structurally. Six months later, you have a growth marketer technically reporting to the CTO and a data analyst reporting to Sales. Fix this proactively — do not wait for it to cause conflict.
Treating the org chart as a one-time document
Startups restructure every six to twelve months. The org chart needs to be a living document, updated after every reorg, departure, or new hire that changes a reporting line. A stale chart is worse than no chart — it actively misleads.
When to Hire a COO vs Promote an Existing Employee
The COO question comes up for almost every founder around the 20-to-40 person mark. The honest answer depends on what is breaking — and what kind of COO you mean.
If the problem is that the CEO is bottlenecked on operational decisions — hiring processes, vendor contracts, cross-team coordination — then a strong Chief of Staff or Head of Operations (often promoted from within) solves the problem for a fraction of the cost and culture risk of an outside COO hire.
If the problem is that the CEO is a product or technical founder who genuinely should not be running go-to-market, an outside COO with commercial experience makes sense — but only if the founder is genuinely willing to cede that authority. A COO with no real remit is expensive and demoralising.
The org chart test: if your proposed COO hire would have more than four VP-level direct reports, you are probably ready. If they would have two, promote internally and revisit in twelve months.
Visualise your startup's team structure
Upload your team list as a CSV and OrgBrief generates a clean, shareable org chart in seconds. Useful for all-hands decks, board updates, investor due diligence, and onboarding new hires.
Related guides
How to Read an Org Chart: Lines, Boxes, and What They Mean
Solid vs dotted lines, span of control, and what org charts leave out.
Org Chart vs Hierarchy Chart: What's the Difference?
Definitions, use cases, and how chart type changes with company scale.
Org Chart Template: Free Excel & CSV Templates for 2025
Ready-to-use CSV templates including a startup format for 10–50 people.