A SaaS org chart changes shape three times on the way from twelve people to two hundred, and each change is triggered by headcount rather than by strategy. Engineering splits before anybody plans it, customer success appears the quarter after the first renewals, and revenue operations arrives when sales and marketing stop agreeing on numbers. This page is what the chart looks like at each of those three stages and the arithmetic underneath: on the worked example a company of 120 at a span of seven needs 15 managers and four layers, and the top four leaders reach 228 people within three.
Seed, roughly twelve to thirty people
Two layers: founders and everyone else. Engineering is one group, go-to-market is one group, and finance is a contractor. Four leaders at a span of seven reach 28 people, which is why this shape holds right up to the edge of thirty without inventing a manager. The chart's job here is to show what each person owns rather than who they report to, because everybody already knows the second part.
Series A, roughly thirty to a hundred people
The middle appears. Engineering splits into teams with leads, sales splits into new business and account management, and the first non-founder function leader is hired. At 100 people and a span of seven that is 13 managers, and three layers reach 228, so the chart still fits inside four. This is the stage where the chart starts being wrong between reorganisations, because changes now happen weekly rather than monthly.
Series B, a hundred and fifty people upward
Functions get their own internal layers and the dotted lines multiply: designers embedded in product teams, revenue operations serving both sales and marketing, security serving engineering and legal. On the worked example that is 43 dotted lines on a 140-person company, 2.4 for every manager, and about $2,428 a month of standing check-ins. The chart is now a directory or it is out of date.
Questions people ask about saas org chart
How many engineers per manager in a SaaS company?
Six to eight is what most run, which is where the worked example's span of seven comes from. Below five the manager writes code and manages badly; above nine the one-to-ones stop happening.
When does customer success get its own leader?
Usually the quarter after renewals become a number somebody is accountable for, which is typically past thirty people and always before a hundred.
Where does revenue operations sit?
Under whoever owns the number, with dotted lines to the functions it serves. It is the clearest example of a role the solid line cannot describe on its own.