SaaS companies add functions in almost the same order every time, which makes the structure predictable in a way that is genuinely useful for planning: engineering, then sales, then customer success, then marketing operations, then finance, then people, then security and compliance when the first enterprise deal asks. What varies is the headcount at which each arrives and how many managers the whole thing implies. This page is the order, the triggers and the arithmetic. On the worked example 120 people at a span of seven imply 15 managers, 105 individual contributors and four layers.
The order functions arrive in, and why it rarely varies
Engineering and sales exist from the start. Customer success arrives with the first renewal cohort. Marketing operations arrives when lead volume outgrows one person's spreadsheet. Finance moves from contractor to employee somewhere near a hundred people. People operations arrives when the joiner rate passes about two a month, and security and compliance arrive the first time an enterprise buyer sends a questionnaire. Each one is triggered by an event you can see coming a quarter out.
What each addition does to the manager count
Every new function starts as one person and becomes a group of about seven before it needs a manager. Headcount divided by the span plus one is the total: 15 managers at 120 people, 20 if the span drops to five. The planning question is not whether to hire the manager but whether the function is at seven people yet, and that is a number rather than a judgement.
Where the structure usually goes wrong
Two failures repeat: a function leader hired before the function has anybody in it, which produces a manager with no team and a chart with a gap; and a function grown to fifteen people with no internal layer, which produces a leader who cannot name what half their team did last week. Both are visible in the arithmetic before they are visible in the company.
Questions people ask about saas organizational structure
How many people before we need a head of people?
Usually when joiners and leavers pass about two a month, which on the worked example's 28 changes a year is close. Before that it is a part of somebody else's role.
Should engineering and product be one function or two?
Two lines, one leader, at this size. Splitting the leader too early creates the coordination problem the split was meant to solve.
Does the structure differ for B2B and B2C?
The functions are the same; the weight differs. B2B adds customer success and solutions engineering earlier, B2C adds support scale and lifecycle marketing earlier.