Startup org chart, by stage
A startup's org chart changes shape about four times in its first hundred people, and each change is forced by one hire. Here is the same company, Oxbow Software, drawn at ten, twenty-five, fifty and a hundred people: what changed, who made it necessary, and the mistake each stage invites. Every stage downloads as a template.
Ten: everyone reports to a founder Two founders, a handful of engineers, the first salesperson, and someone who does everything else.
Oxbow Software — 10 people
What changed
Nothing yet. The chart exists so that the tenth hire can see it, and so the founders can see that one of them has six reports and the other has three.
The hire that forced it
The first salesperson. Until then every customer was the CEO's; after, someone else owns a number, and the founder has to decide what they own instead.
Watch out for
Two roots. Co-founders who both refuse to draw a line between them produce a chart with no top, and every hire after the tenth learns that decisions have two addresses. One of you is the CEO; draw it.
Twenty-five: the first managers Tech leads under the CTO; a head of sales, product, marketing, success and operations under the CEO.
Oxbow Software — 25 people
What changed
Engineering split into teams with leads, because eight engineers reporting to a CTO who also writes code was six too many. Sales, product, marketing, success and operations each got a head, most of them promoted from the first hires, and the CEO's reports became functions rather than people.
The hire that forced it
The first tech lead. It is the first time a founder gives up a direct report to someone else, and the first time the chart has a middle. The second was the head of sales, who turned the CEO's customers into a pipeline.
Watch out for
Promoting the best engineer to tech lead without asking whether they want to manage. Half of first tech leads step back within a year; draw the role as a lead, keep it close to the code, and let the manager title wait for fifty.
Fifty: managers of managers A VP of engineering beside the CTO, sales in regions, a head of people, and open roles drawn as open.
Oxbow Software — 50 people
What changed
A layer. The CEO's eight reports each run a team of teams now, and the two founders split engineering: the VP of engineering runs delivery, the CTO keeps the platform and the data team. Sales went to regions. People became a function of its own rather than a coordinator inside operations.
The hire that forced it
The VP of engineering. The first executive hired from outside, at a level above people who were there first, and the hire most startups make a year late. The chart shows why: at fifty, twenty engineers under one CTO is a queue.
Watch out for
Eight direct reports to the CEO is the ceiling, and it is already here. The next stage is either a chief operating officer or grouping functions under two or three executives; the chart at a hundred shows the choice this company made.
A hundred: the leadership view Six executives under the CEO, a chief of staff beside her, and every manager's team size in the title.
Oxbow Software — 100 people, leadership view
What changed
The shape folded. Marketing moved under a chief revenue officer, so one person owns the number; success, support and people moved under a COO, so one person owns the operation; finance got an executive of its own because the board asked for one. The CEO went from eight reports to six and a chief of staff.
The hire that forced it
The chief operating officer. Not to run the company, but to take the functions the CEO was managing badly for lack of time and give them a manager. The second was the VP of finance, because a company of a hundred with a finance manager has a board pack nobody trusts.
Watch out for
Drawing all hundred people on one page for the board. The board chart stops two levels down with team sizes in the titles; the full chart is the one HR keeps current. Two charts from one list, not one chart that tries to be both.
The rules that hold at every stage
- The CEO's span is five to eight. Past eight, add an executive or group functions; past ten, the chart is telling you something the calendar already has.
- Draw the next hire as an open role before the offer goes out, so the chart and the plan agree.
- Promote into leads, hire into managers of managers: the first-time leads are usually inside, the first VP usually is not.
- Keep contractors and agencies on the chart as what they are. A startup of twenty-five that looks like twenty is misleading its next investor.
- One founder is the CEO on the chart, whatever the cap table says.
- Redraw when a layer appears, not when a person does. The chart changes shape four times in a hundred people and a hundred times in between; only the four need announcing.
Questions people ask
- What does a startup org chart look like at 10 people?
- Flat: two founders and everyone reporting to one of them, usually engineering and design under the technical founder and sales and operations under the CEO. There are no managers and no layers, which is right; the only structural decision is which founder is the CEO.
- When should a startup hire its first manager?
- When a founder has more than about eight direct reports, which usually happens between fifteen and twenty-five people. The first managers are typically tech leads promoted from inside and a head of sales; the first manager of managers, a VP of engineering, tends to arrive at forty to sixty people and is the hire most startups make a year late.
- How many people should report to a startup CEO?
- Five to eight. At ten people it is everyone who is not the other founder; by twenty-five it is heads of function; by fifty it is eight and at the ceiling. The way past it is a COO or grouping functions under two or three executives, not a ninth report.
- When does a startup need a COO?
- When the CEO is managing functions badly for lack of time rather than lack of judgment: usually somewhere between fifty and a hundred people, when success, support, people and operations each have a head and none of them gets an hour a week. A COO on the chart at twenty people is a co-founder with a title.
- Should co-founders be on the same level on the org chart?
- No. One of them is the CEO and the other reports to them, whatever the equity says. A chart with two roots tells every hire that decisions have two addresses, and the first disagreement proves it. Draw the line; it costs nothing and settles more than it seems to.
- How do you show advisors and investors on a startup org chart?
- Not on the operating chart. Advisors, board members and investors are governance, not reporting lines; the nonprofit and church examples keep their boards on a separate chart for the same reason. A chief of staff, by contrast, is a real role and sits beside the CEO as a staff position.
- Is there a startup org chart template?
- Four, one for each stage on this page, as Excel workbooks and CSVs. Download the one nearest your size, replace the names, add your planned hires as open roles, and import it; the chart draws itself and stays current as the list changes.
Draw the stage you are at, and the next one
Import your list and the engine draws it; add the roles you plan to hire as open positions and it draws the next stage too. Building is free at any size, and the chart stays current as the list changes.