Fractional Sales Leadership: When It Pays

There is a stage where almost every B2B company makes the same mistake. Two to ten million in revenue, twenty to fifty people. Two or three sellers, one person in marketing, maybe a key account manager. Everyone operational, no teams, nobody in between. Too big for the founder to run sales on the side. Too small to justify a full C-level and VP layer.

So the decision gets postponed until it pays for itself. And in the meantime revenue runs on the hope that operational people will structure themselves.

The question that follows is almost always the same: at what revenue do I need a sales leader? That is the wrong question, and this article explains why — and which question decides instead.

The no-man's-land between two models

The band between two and ten million is not a waypoint. It is its own operating mode. Below it, the founder still runs sales, or two or three people do it alongside their day job. Above it, a VP layer already exists — head of marketing, head of sales, head of customer success. In between, that layer is missing, and the mistakes it would have caught are expensive precisely because nobody notices them.

This is the part worth naming plainly: it is not a talent problem and not a market problem. It is a structural vacuum, and it gets more expensive with every additional hire, not cheaper. Adding another seller to an organisation with no leadership layer buys more activity without more accountability.

Manuel Hartmann, founder and CEO of SalesPlaybook, describes this stage in his LinkedIn newsletter Diary Of A CRO. His observation from working with growth-minded smaller companies: they do not fail on the market, they fail because there is no structure and no clear process across sales, marketing and customer success. That is his assessment rather than a survey — but it is the diagnosis the whole model question follows from.

From the LinkedIn newsletter Diary Of A CRO by Manuel Hartmann.

Why a revenue threshold does not work as a trigger

"Above X million you need a sales leader" sounds like a rule and is not one. Two reasons undo it.

First, the revenue figure says nothing about the organisation. One business with ten people may have grown over years, carry a lean payroll and run a very comfortable margin. Another with identical revenue funds thirty people and is structurally thin. Same number, two entirely different situations — and two entirely different answers to the leadership question.

Second, geography distorts the maths. An experienced sales hire in the Zurich area costs a multiple of what the same role is paid in Berlin. A threshold that holds for Munich is wrong for Zug. Anyone running DACH off a single number is miscounting one of the two markets.

The quotable version: revenue tells you how big a company is, not how much its sales organisation needs leading.

The quota test: the question that replaces the revenue question

There is a question that holds, and it points at the role rather than at the company: does this leadership role own a measurable share of company quota — with the team already in place?

That also settles what the role has to be. Sales leadership at this size builds structure that does not depend on individual star sellers: clear process across sales, marketing and customer success. But building structure at this size does not mean drawing slides in an ivory tower. The role is fully operational and strategic at once — closing important deals with the team, sitting in the meetings that matter, carrying project management across go-to-market.

Which produces the sharpest line in this article, and it is the one that protects the reader from an expensive mis-hire: anyone who only orchestrates, without carrying part of the number themselves, is too expensive at this company size. A leader who pours pipeline on top instead of building the system underneath is not a leader. They are an expensive senior seller.

The four models compared

There are four answers to the leadership question, and in two of the four a fractional arrangement is explicitly not the right one. What separates them is not price level but where the cost sits on the balance sheet, how long the role takes to bite, and how easily the decision can be undone.

On cost, one framing that is explicitly an estimate and not a market rate: in the same newsletter edition Manuel Hartmann puts a full-time role at this level in the six figures per year, all-in — and notes that many companies do better with the right scope than with that fixed block. That is his experience, not a surveyed benchmark, and your own calculation will turn on local pay levels anyway.

The evidence for the second row is a published case study. At Cito exactly this situation was the starting point: "A staffing gap: A temporary vacancy in the Head of Sales role, combined with the founders' limited capacity as they managed many issues beyond Sales." The engagement was modular, moving with the phase rather than with a contract, and the result was achieved in less than six months. That is the property a full-time hire cannot reproduce: the scope follows the stage.

When full-time is the right answer

This section is here so the article does not read as a sales pitch. A full-time hire is the better choice in two cases, and both are nameable.

The first is volume. When the job genuinely fills a person — several teams, a hiring plan of its own, ownership beyond sales into marketing and customer success — then a part-time scope stops being an advantage and becomes a ceiling. The second is predictability. With a clear one-to-two-year outlook you can carry a fixed cost block, because you know what it is set against.

And the counter-calculation belongs in the picture even though it is uncomfortable. A full-time role at this level is a fixed block that stays on the balance sheet through a weak quarter. On top of that sits mis-hire risk, which at this company size costs more than salary: it costs a year of sales development. That risk, not the price, is the actual reason the fractional model is attractive during a transition.

People or software — and why that framing is wrong

A second debate runs alongside the model question, and both extremes in it are wrong.

"People only, no systems" no longer works at this size: running sales, marketing and customer success without clear process is simply not fundable. A tool stack that holds is a precondition — in our own delivery that means HubSpot as the shared source of truth, because otherwise neither pipeline nor the handoff between marketing and sales can be checked. But "all code, no people" is just as naive, because trust in B2B scales person to person.

The division of labour that holds is unspectacular: AI takes research, documentation and process — the trust work stays with people. In the conversation behind that newsletter edition, Patrick Kohler expects the human factor to come back more strongly rather than disappear — "we buy from people". For the leadership question that means a system does not replace a leadership layer. It makes one verifiable.

Which number steers, and which one misleads

Sales leadership juggles a dozen metrics — lead volume, pipeline, deal velocity, win rate, retention. The temptation is to get lost in them. The hierarchy is simpler than it looks.

Revenue is a lagging indicator. It is the consequence of action, not the action — which makes it useless as a steering metric. What actually gets steered sits earlier, and the most important leading indicator is a valid pipeline: not an inflated one, not a wished-for one. Underneath it sit two things, and the second is the real work: a tool stack that simply holds as a standard, and capability, reliability and discipline in the team.

The way to spot missing structure is an uncomfortable question: how do you tell correlation from causation in your people's behaviour? One rep runs four hundred automated activities a week and not one conversation. Another closes the largest deal in company history because the customer had little alternative, not because of the rep. A third loses the largest existing account without doing anything wrong. Without structure and accountability, nobody knows who actually drives revenue. That is not a metrics problem — it is precisely the gap a leadership layer closes.

Cadence: why a quarter is no longer a valid test period

The old rule was that when something is not working, you give a person or an initiative a quarter to show whether it bites. That logic no longer holds, for people or for markets. See a problem only after ninety days and you have lost three months — and in a faster market the constraint is not the team, it is the leadership that watched too long.

The remedy is unspectacular and regularly mistaken for micromanagement: short, fixed check-ins instead of quarterly reviews. Three questions are enough — what is the goal this week, what went well and what did not last week, and where does each person stand with their own obstacles. That is not control, it is constant communication. The difference from micromanagement is directional: it is about clarity and help, not justification.

One note on appetite for change, because it decides whether such a mandate succeeds. Change arrives either as an initiative from the top or because market pressure has become unavoidable — a competitor making a jump, or organic growth that suddenly stalls. In a market where the old way still works, change is hard to push through. And the biggest time sink is then not the technology but the persuasion: bring the management team along first, then the wider team.

The question that comes before all the others

In the end the model is not the deciding factor. There are two ways to bring in sales leadership, and on paper they look identical.

One: you bring someone in because you want the change yourself. Then a leadership layer can genuinely lift the company into its next size bracket. The other: you bring in someone "who is good at this" so that you do not have to change anything — and still expect people, process and market direction to move. The second only buys time until the market makes the decision for you.

So before choosing a model there is a question for the management team itself, and it is the most honest test in this article: am I prepared to change my own behaviour when this role arrives? Answer yes and the table above is usable. Answer no and you save the money — under all four models.