Mid-market

Every department makes its number, and the company misses.

Scaling a mid-market B2B company gives marketing, sales, customer success and RevOps each a leader, a process and a target. Nobody owns the work between them, and that is where the plan is missed.

The transition

One company, now a set of departments.

In a company like this the Monday leadership meeting has eleven people in it and runs for two hours. Marketing reports pipeline generated against its target and is ahead. Sales reports the pipeline it accepts as real and is behind, because the two teams count a lead at different points. Customer success reports renewals on track; the three accounts at risk sit in a separate deck that finance has not seen. RevOps, created in the spring to settle all this, presents a fourth number and a plan to reconcile the other three by next quarter. The investor on the board asks why the company is below plan when every function is on plan. Nobody in the room has a wrong number. Nobody has the company's.

The last stage carried the model into new teams on the strength of a system. This one hands the system to departments, and each has been given a number it can reach on its own. The work between them was never given to anyone, so it gets paid for in meetings, reconciliations and a second set of spreadsheets, and none of it has a line in the plan.

Signs you are here

Each function has its own number, and they do not add up.

  • Marketing, sales and customer success each count the pipeline at a different point, and each count is reported as the pipeline
  • An ops role was created inside each function this year, and the ops people meet weekly to reconcile each other's reports
  • The forecast is assembled from department forecasts, and the gap between them is settled in a meeting rather than by a rule
  • A process was written down for the first time this year by the team that runs it, and the next team along works from a different version
  • Leadership meetings have grown in headcount and length, and decisions leave them as actions for somebody to coordinate
  • The board asks for predictability, and the answer each quarter is a change to the reporting lines

Four of these true, and no department's report is wrong. The cost sits in getting them to agree, and nobody reports that.

By function

Six departments, six numbers, and the gap between them.

This is the first stage at which every seat is a department with a target of its own. Each target is met inside its boundary, and the leak is the boundary.

  1. SalesA quota: built on marketing's forecast of leads, which marketing built on sales's forecast of conversion
  2. MarketingA target met: pipeline generated on plan, with no line for how much of it sales accepted
  3. Customer SuccessA renewal number: owned by CS, while the expansion the plan counts on from the same accounts is owned by nobody
  4. FinanceFour forecasts: reconciled every month, with no cost line for the reconciling
  5. RevOpsA mandate: to hold definitions the departments have not agreed to
  6. GTM StrategyA plan: the sum of department targets, called the company's
What the next stage demands

Departments that add up to one company.

Specialisation is what this stage buys, and it is worth buying. What the next stage asks is that the specialists add up to one company, on paper and in the numbers.

A number the company owns

Each department measures what it is paid for, so the plan is met by every function and missed by the company. The next stage needs one number above the departmental ones, with an owner whose target is the company's rather than a function's.

Handoffs priced, not only drawn

Every new team adds a boundary, and every boundary adds a wait, a re-entry and a chase on either side of it. The process map shows the arrow. The cost is in what happens at the arrow, and it is paid in the hours of two teams, not one.

The management layer, counted

A new layer of management arrived with the departments, and much of its week goes on carrying information between teams that used to share a room. That time is booked as management. Counted as what it is, the running cost of a structure, it has an owner and can be designed down.

Rules that hold the forecast up

A forecast assembled from department forecasts holds as well as the rules under it, and at this stage those rules are being written for the first time. RevOps can hold them once it is given the company's number to serve rather than a number of its own.

The evidence

Departments, priced in four numbers.

Four published figures for companies between $50M and $100M ARR, the band in which the departments arrive. Each one is a cost of structure that sits in no department's report.

  1. 01

    58%

    Expansion's share of growth ARR at the median for $50M-$100M ARR, up from about 50% in 2023 by the publisher's own comparison. More than half of the plan now depends on the handoff from sales to customer success, and no department's number is that handoff.

    Benchmarkit, 2025 B2B SaaS Performance Metrics Benchmarks, calendar 2024 data, N=81

  2. 02

    23% of revenue

    Median general and administrative spend at $50M-$100M ARR, against 13% above $500M: the structure's own running cost, before the sales, marketing and success budgets. It is the one line that grows with departments rather than with customers.

    ICONIQ, State of Software 2025, quarterly operating data from 127 software companies, 240 company-quarters in this band, median, September 2025

  3. 03

    $240,000

    Median ARR per employee at $50M-$100M ARR, $210,000 at the 25th percentile and $307,000 at the 75th. The gap between the quartiles at this band is close to $100,000 a head, and the hours spent carrying work between departments are paid out of it.

    Benchmarkit, 2025 B2B SaaS Performance Metrics Benchmarks, calendar 2024 data, N=174

  4. 04

    0.9

    Median burn multiple at $50M-$100M ARR, and 2.7 at the 75th percentile, above the 2.0 of the band below it. The median company is close to funding its own growth; a quarter of them burn more per dollar of net new ARR than the worst quarter of the band below, and the difference is structure.

    Benchmarkit, 2025 B2B SaaS Performance Metrics Benchmarks, calendar 2024 data, N=130

The usual entry at this stage

The hours spent keeping departments in step, priced.

Diagnosis

€15,000 flat · two months from the day we get access

Two months inside the functions and between them: how each counts the pipeline, the handoffs between marketing, sales and customer success, the meetings and reports that reconcile them, and interviews with the heads of each department and with the people who carry work between them. The briefing names where the coordination costs money, what it costs in the hours of the people doing it, and which boundary to redesign first. Operation redesigns it after that, with the department heads in the room: €50,000 more if booked within 30 days of the briefing, or €65,000 with the Diagnosis included.

Book a strategy callDetails →

Not sure it is the right one? Compare all five →

FAQ

Before you assume a dashboard will settle it.

We have a RevOps team now. Is this not their job?
RevOps can hold the definitions once the company has agreed them, and that agreement is what is missing. A RevOps team handed a number of its own joins the reconciliation rather than ending it. The Diagnosis reads what each department counts and where the counts part company, so the rules RevOps is asked to hold come from the evidence and not from whichever function argued longest.
What separates this from the expansion stage?
Expansion copies a working model into a new region or team, and the leak is what the copy leaves behind. Here nothing is being copied. The model is being divided into departments for the first time, each with a process and a target of its own, and the leak is the work of keeping them in step. A company can be in both at once; the Diagnosis reads which one is costing more.
Our investor wants predictability. Does a Diagnosis give us that?
It gives the ground a predictable plan is built on. A forecast is as good as the definitions under it, and at this stage each department holds its own. Two months in the records show where the department numbers part from the company's and what the gap costs, and the forecast the board wants is built on that evidence, not before it.
Everyone here is already in too many meetings. How much time does this take from them?
The interviews cover the people who run each department and the ones who carry work between them, and are scheduled into the week they already have. Most of the two months is spent in your CRM, your plan and your reporting, not in your calendar. The meetings worth counting are the ones you already hold to keep the departments in step, and counting them is part of the work.
Get started

On plan in every department, and off plan as a company.

Thirty minutes on how each department counts its number and where the counts part company. If they add up, there is nothing to price, and you are told so.