The real job: a predictable revenue engine
The classic Series B trap is running revenue with a purely sales-driven operating system: everything converges on closing, and the other functions line up behind it. Whether you come from sales, marketing, consulting, ops or product, the challenge is the same: building a revenue-driven organisation.
Marketing, Sales, CS and RevOps answer for the same number, with the same definition of pipeline, the same ICP and the same customer journey. It is no longer a question of closing. It is a question of predictability: a forecast the board can defend, a pipeline nobody disputes, and NRR run as a revenue engine rather than as a support centre.
That engine does not build itself. It is built through the four to six leaders you place under you, and that is where everything is decided: 40 to 50% of leadership hires fail within 12 months at Series B. Rarely for lack of skill. Right profile, wrong timing, an organisation that is not ready, a scope that was never settled.
What triggered your role
A CRO usually arrives when three signals show up at the same time:
- Revenue growth slows down or becomes unpredictable.
- Marketing, Sales and CS no longer speak the same language: disputed leads, weak conversion, rising churn.
- The organisation is outpaced by its own growth: dozens of sales reps need to be hired and trained, and nobody owns the plan.
Most often, this happens between €10M and €40M ARR. Below that, a Head of Sales or a Head of Revenue is usually enough, with a possible move to CRO within 12 to 24 months. The classic mistake is to wait for growth to stall: hiring and ramping a sales rep takes 6 to 9 months, so capacity has to be planned 12 to 18 months ahead.
What you inherit when you arrive
A CRO being appointed means the company is already at Series B, between €10M and €40M ARR. Nothing has to be built from scratch, everything has to be scaled.
You take over a sales team of ten AEs or more, led by a Head of Sales who is at capacity. A marketing team that generates pipeline, but nobody agrees on its quality. A compact CS team that protects retention without owning expansion. A RevOps function that runs the CRM and the dashboards, with a forecast still made by feel. Everyone does a good job in their own silo. Nobody answers for the same number.
Your mission: scale without losing predictability. Your direct reports are not foundation builders. They take over an existing scope and scale it.
The GTM team by ARR stage
Here are headcount orders of magnitude across three ARR stages. Read them as ceilings, not targets: average deal size, sales cycle and the number of countries all move them, and efficiency pulls them down (see below).
| Function | Under €10M | €10M to €40M (Series B) | Over €40M (Series C+) |
|---|---|---|---|
| Sales (AEs) | 3 to 6 | 8 to 15 | 20 to 35 |
| SDR/BDR | 1 to 2 | 3 to 6 | 8 to 15 |
| Customer Success (CSMs) | 1 to 2 | 4 to 8 | 10 to 18 |
| RevOps | 1 (generalist) | 1 to 2 (strategist + technical) | 3 to 5 |
| Marketing (demand gen) | 1 to 2 | 3 to 6 | 8 to 15 |
| Target total GTM headcount | around 10 to 12 | 20 to 35 at most | 50 to 90 |
Efficiency: fewer heads, more leverage
At Series B, the board no longer rewards headcount. It looks at what every euro burned and every GTM employee produces: burn multiple (net burn divided by net new ARR), ARR per employee, payback. An org chart that lines up many people for the same ARR is hard to defend.
Market benchmarks point the same way. ARR per employee, calculated on the company's total headcount and not only on GTM, is around €155,000 at the median between €5M and €20M ARR, and around €240,000 between €20M and €50M. GTM teams are now 21 to 43% smaller than they used to be at the same ARR. A CRO who presents an org chart built on the old ratios gets challenged on exactly this ground.
AI is speeding this up. It has already made CS teams more compact, and it compresses first-level tasks in marketing, RevOps and prospecting:
- Marketing: format adaptation, translation and first-level SEO no longer need the same workforce. The team focuses on what remains human: ABM for Enterprise, strategic events, mastery of demand gen tooling. In the 3 to 6 people shown for Series B, there should be no junior executors. These are "Marketing Product Managers": highly senior people who can run AI agents, analyse attribution data and orchestrate budgets, not write blog posts by hand.
- SDR/BDR: targeting, enrichment and sequences are being automated. A more compact and more senior team feeds the same number of AEs.
- Customer Success: usage alerts let each CSM follow more accounts. In Enterprise, the CSM spends their time on business alignment and expansion, not on support.
- RevOps: no need for manual data entry. A senior profile configures workflows and frees up sales time.
The consequence for your hiring: favour senior, high-leverage profiles over volume, and treat the table above as a ceiling.
Sources for the market benchmarks: Aleph x Benchmarkit, SaaS and AI Performance Benchmarks 2026 (small samples per band); ICONIQ Growth. Amounts converted to euros and rounded.
What this changes for your hiring:
- Under €10M: no CRO yet, a Head of Sales leads the team, from 3 to 5 sales reps. A RevOps Manager becomes useful once the sales team passes 5 people.
- €10M to €40M: the team goes beyond 8 to 10 AEs and the scope widens. This is the stage of the CRO, the VP Sales, a Head of CS (or a VP Customer Success & Expansion if the scope grows) and a Head of RevOps. The VP Channels & Alliances arrives once direct sales are running.
- Over €40M: several regions, several time zones. The Head of RevOps runs a multi-region team.
NRR: the number that judges you in front of the board
If ARR is the CEO's compass, NRR (Net Revenue Retention) is the CRO's arbiter. A good gross revenue retention (GRR) proves the product works. An NRR above 100% proves the installed base grows by itself, without a euro of new acquisition.
Market benchmarks are more modest than most people assume: the median for B2B SaaS is around 101 to 102%, with GRR around 91%. The top quartile sits around 108 to 110%, and 120% or more is the exception. NRR rises with average deal size, but only modestly: around 98% below €10K ACV, 102 to 104% between €10K and €215K, 106% above €215K.
Three ways to read it in front of your board:
| NRR level | Reading | What it means for you |
|---|---|---|
| Below 100% | Red zone | Churn is outrunning expansion. Hiring more AEs in this context means filling a leaky bucket: retention comes before sales capacity. |
| 100% to 110% | In the market | Expansion offsets attrition, but the machine does not outperform. This is where the median sits. |
| Above 110% | Top quartile | The best exceed 120%, often driven by a Land & Expand strategy in Enterprise. This is the number that wins over top-tier funds. |
A high NRR is not a customer support metric, it is a GTM deliverable. It requires marketing to source an ICP with strong expansion potential, RevOps to deploy automatic alerts based on product usage, and the commercial scope of expansion to be locked down between CS and Sales (see mistake 3).
What this changes for your hiring: look at your NRR before approving an AE plan. Below 100%, the Head of CS and the Head of RevOps come before the VP Sales.
Sources for the market benchmarks: Aleph x Benchmarkit, SaaS and AI Performance Benchmarks 2026 (2025 data); SaaS Capital, 2025 B2B SaaS Retention Benchmarks (more than 1,000 private B2B SaaS companies). Amounts converted to euros and rounded.
Head of Sales or VP Sales: when do you switch?
Your question is not whether you need a sales leader. It is which one. The two roles are not alike.
The Head of Sales is the right choice when you have 3 to 5 sales reps and a sales cycle that is starting to repeat. They optimise a motion that already exists: they hire, coach and structure. Below 3 reps, it is too early.
The VP Sales is the right choice when you pass 8 to 10 Account Executives (AEs), the board expects 2x growth over 12 months and your Head of Sales is at capacity, having already validated the ICP and the motion. Another strong signal: nobody can say any more how many reps need to be hired to double revenue, while the board asks for an org chart and a defensible forecast. Below 8 AEs, it is too early. The tipping point: the question moves from "how do we do better?" to "how do we do 3x?".
The mathematical signal: span of control. A normal human being cannot coach, steer and run intensive pipeline reviews with more than 7 to 8 direct reports. As soon as your sales team goes past 8 AEs reporting directly, coaching time per head collapses. That is the exact signal to move from a Head of Sales (who coaches individuals) to a VP Sales (who can build intermediate management layers, such as a Mid-Market Team Lead and an Enterprise Team Lead).
International often decides. As soon as you open a territory outside France, the scope becomes that of a VP Sales, even with a team that is still compact.
The trap: hiring a VP Sales when you need a Head of Sales. You then pay for a strategic role that the company is not ready to fill.
The three profiles that fail at 9 months
You will meet them in interviews. They all have the right CV.
The VP from a global software vendor
Why they fail: they arrive with a playbook designed for a company that already has worldwide brand recognition. At Series B, even in Enterprise, you still have to build the tools, take the knocks and call customers yourself. They spend six months asking for budget, wanting to hire intermediate layers and producing slides. The verdict at 9 months: zero Enterprise pipeline created, a frustrated team, and a refrain: "the product is not up to US standards".
The Founding CSM promoted to VP Customer Success & Expansion
Why they fail: they are often the company's first CSM, excellent at caring for the customer relationship and putting out fires. But at Series B, when KAMs are removed and an NRR quota is put on CS, they cannot run a P&L, build a pricing strategy or negotiate against a procurement team. The verdict at 9 months: GRR is fine, expansion is at zero, NRR falls below 100%.
The "logo hunter" Head of Alliances
Why they fail: they spend their first six months signing cosmetic partnerships with big consultancies or tech players, and posting on LinkedIn. A signed agreement does not generate a single euro of ARR. Without an internal organisation to train, run and motivate the partners' sales reps, the channel stays empty. The only indicator that counts is Partner-Sourced ARR entered in the CRM and validated by Sales, not the number of agreements signed. The verdict at 9 months: 15 partnerships signed, €0 of Partner-Sourced ARR.
The three mistakes CROs make
Mistake 1: hiring the VP Marketing too late. The reflex is to believe that adding Enterprise AEs is enough to sign contracts. The AEs arrive without leads, prospect blindly, then leave. Marketing prepares the ground before them, not after.
Mistake 2: looking for the unicorn in Sales. The trap is wanting a VP Sales who holds the rigour of Enterprise cycles (MEDDPICC) in one hand and the velocity of SMB volume in the other. These are two different mental software stacks. The CRO has to choose their priority battle.
Mistake 3: leaving the CS / Sales scope unclear. If nobody says on day one who owns renewal and who owns expansion, Sales thinks it is CS and CS thinks it is Sales. Your strategic customers fall through the cracks at renewal time.
The rule of thumb to settle it:
- Velocity / SMB model (ACV under €30K): 100% CS. Customer Success owns all of NRR (retention and upsell). The cost of aligning a salesperson is not profitable.
- Hybrid / Mid-Market zone (ACV between €30K and €75K): the model is collaborative. The CSM owns renewal at unchanged terms and spots expansion signals. As soon as an upsell opportunity is detected or a price renegotiation opens, a salesperson (AE or AM) steps in to lead the financial close.
- Enterprise model (ACV over €75K): the CSM is the sole guarantor of product adoption and delivered value. Commercial negotiation, pricing defence and the closing of amendments are carried by a dedicated Account Manager or by the original AE (Land & Expand). You do not ask a CSM, who guards the relationship and the value, to fight an annual stand-off against a procurement team.
What a failed direct report costs
Take a VP Sales who fails at 12 months: €1M to €2M of missed revenue, 30 to 50% turnover in the team, €150K to €250K to replace them. In total, between €1.5M and €2.5M. And it is you the board questions, not the person you hired.
The hiring order that works at Series B
Once the CRO is in place, their direct reports are VPs, except RevOps, which stays Head of RevOps, and CS, where the Head of CS remains the norm (see below). Each one takes over an existing scope and scales it. Each step feeds the next: pipeline before the sales reps who close it, sales reps before customers to protect, a proven direct engine before the indirect one. The months are indicative, the dependencies are not.
Day 90 goal: make the number predictable (months 1 to 3)
The VP Marketing takes over the demand gen team and its channels, and scales pipeline to the volume and source mix the Enterprise plan needs. They arrive before the VP Sales.
The Head of RevOps takes over the CRM, dashboards and reporting run by the RevOps Manager, and makes the forecast defensible in front of the board: shared definitions, review cadences, quotas, territories. Orders of magnitude for a good RevOps function: more than 95% opportunity completion, a forecast-to-actual gap under 10%. This is not a Salesforce admin: if they spend their time fixing the CRM, the role is badly defined. The signals that you need one: AEs spending more than 1h30 a day on non-sales tasks, nobody owning data quality, a forecast made by feel.
Day 180 goal: scale direct sales and retention (months 3 to 6)
The VP Sales takes over the team built by the Head of Sales and scales the team, the territories and the hiring plan, including markets outside France. They are most often hired from outside: the Head of Sales generally has neither experience of European or US markets nor of managing managers. They arrive with a pipeline already fed and a reliable forecast.
The Head of CS, or the VP Customer Success & Expansion takes over the CSM team and the renewal book, and carries NRR as a quota: retention, renewals, expansion. With AI, CS teams are far more compact than ten years ago, so the Head of CS remains the norm. You move to a VP when the scope grows: taking over tasks previously handled by AMs, taking over IT support (helpdesk) on top of customer success, managing extended follow-the-sun teams. They arrive in parallel with or just after the VP Sales, so that every new Enterprise customer is onboarded through well-run processes.
Beyond day 180: open the indirect channel (month 6 onwards)
The VP Channels & Alliances takes over the first partnerships, run ad hoc until then, and turns them into Partner-Sourced ARR. They arrive once direct sales and delivery are running smoothly, not before.
How to defend the Head of RevOps in front of the board
The board almost always pushes to hire the closers first. Here are three arguments to defend a Head of RevOps before the VP Sales:
- The forecast is your first deliverable to the board. Without shared definitions or a review cadence, you present a number you cannot defend.
- New AEs are hired against quotas and territories. Without clean data, the VP Sales sizes them blind.
- The hidden cost already exists. AEs spending more than 1h30 a day on non-sales tasks lose nearly a fifth of an 8-hour day. On a team of 15 AEs, that is nearly three full-time positions, which you are not paying for on top and which you recover before hiring new ones.
The message to the board: before adding capacity, recover the capacity you already have.
A lean structure: group roles without leaving a function orphaned
Five leadership roles under a CRO are not hired in one go. Most scopes already exist and move up a level, they are not created. And these functions have to exist, but not necessarily under five distinct titles:
- Customer Success: a Head of CS is enough as long as the scope stays CS. A VP Customer Success & Expansion absorbs account management, even the helpdesk, when the scope grows.
- SDR/BDR: they report hierarchically to the VP Sales through a dedicated manager, to align with closing. Governance of their targeting, however, is co-led with Marketing. In Enterprise, leaving SDRs to the sole metric of call volume produces prospecting in a vacuum. Marketing must equip them with intent data and ABM (Account-Based Marketing) playbooks. The SDR is the armed wing of Demand Gen.
- Channels & Alliances: the role is hired last, and only once direct sales and delivery are running.
One rule is not negotiable: every function has a named owner, even if the title is shared. A function without an owner is mistake number 3.
Job profiles for each role
For each role in the sequence, our job profile details the missions, the profile, the compensation, the right time to hire, the evaluation scorecard and the interview questions. The detailed job profiles are currently available in French only.
The job profiles are currently available in French.
- VP Marketing / CMO (in French)
- Head of Growth (in French)
- RevOps Manager (in French)
- Head of RevOps (in French)
- Head of Sales (in French)
- VP Sales (in French)
- Head of Customer Success (in French)
- VP Customer Success & Expansion (in French)
- Head of Channels & Alliances (in French)
Frequently asked questions
About
This playbook comes from the recruitment assignments of 20M, a search and RPO firm specialising in Sales & GTM, founded by Thibault Martin.
20M supports scale-ups and tech SMEs in France and Europe on the hires that weigh on revenue: salespeople, Go-to-Market experts and leaders (Head of, VP, CRO). Two ways of working: executive search for a specific role, and RPO to structure a growing team.
The benchmarks in this document (ARR thresholds, hiring order, failing profiles) come from those assignments, not from a theoretical study. They are meant to be tested against your own context, which is the purpose of the conversation offered below.
