The shift from VP Sales to CRO is one of the most consequential title changes a B2B SaaS company makes. The CRO title implies a broader scope, a different operating cadence, and a different relationship with the CEO and the board. The shift is often made at the wrong time, for the wrong reasons, and with the wrong candidate.
The shortest distinction is that a VP Sales runs the sales team. A CRO runs the revenue function across sales, customer success, revenue operations, and often marketing. The first is a functional leader. The second is a cross-functional executive.
A VP Sales owns the sales team. The role manages sales managers, owns the new bookings number, runs the forecast call, hires and ramps AEs, and partners with marketing on pipeline. The function is paced by the quarterly sales cycle and lives inside a defined operating cadence: weekly pipeline reviews, monthly forecast, quarterly business reviews.
The role reports to the CEO at most companies under 30M ARR. The compensation is structured with a 50/50 or 60/40 base-to-variable split. RepVue and Pavilion data place senior VP Sales OTE between 350K and 600K at venture-backed B2B SaaS companies, with significant variance by segment and stage.
A CRO owns the revenue function. The scope covers sales, customer success, revenue operations, and at many companies marketing. The role reports to the CEO and partners with the CFO on capacity planning, with the board on revenue strategy, and with the product team on go-to-market for new releases.
The function is paced by the annual operating plan, not by the quarterly cycle. CRO compensation is structured similarly to VP Sales but with a lower variable percentage because the scope cannot be tied to a single quarter's bookings. RepVue and The CRO Report place senior CRO OTE between 500K and 900K at venture-backed B2B SaaS companies, with equity often dominating total comp at well-funded scale-ups. The CRO Report tracks the benchmark data.
The shift from VP Sales to CRO makes sense at most B2B SaaS companies somewhere between 20M and 50M ARR. The trigger is when the scope of the role naturally expands to cover customer success, RevOps, and cross-functional planning. Below 20M, the scope rarely justifies the title. Above 50M, the function almost always needs to be cross-functional, regardless of what title it carries.
Bessemer Cloud Index and ICONIQ Growth data both show the median move happens around 30M ARR at well-run companies. Companies that make the move earlier often do it for symbolic reasons rather than scope reasons, which produces a CRO title without the cross-functional reporting line.
The shift is premature when three conditions are present. The first is that the company is below 15M ARR and the sales team is small enough that the VP Sales is still running deals directly. The second is that customer success and RevOps still report to the CEO or COO rather than into the revenue function. The third is that the board is pushing for a CRO hire as a signal to investors rather than as a scope expansion.
Companies that make the shift prematurely produce a CRO title with the scope of a VP Sales role. The candidate they hire arrives expecting the full scope and either expands it informally or leaves within 12 to 18 months. The fix is to wait until the scope justifies the title.
The hardest decision is whether to promote an existing VP Sales into the CRO role or to hire externally. The promotion path works when the incumbent has cross-functional credibility, has built strong partnerships with marketing and customer success, and is ready to delegate the daily sales operation to a new VP Sales.
The external hire path works when the company has hit a growth wall, when the incumbent VP Sales is not the right profile for a scaled role, or when the board has identified a specific gap in operating experience. Bessemer and OpenView surveys show roughly 60 percent of CRO hires at venture-backed companies are external, with 40 percent internal promotions.
The two hardest reporting line decisions at the CRO transition are marketing and customer success. Marketing reporting to the CRO works when the CEO is operationally focused on product and engineering rather than on go-to-market. Marketing reporting to the CEO works when the CEO has strong marketing instincts or when product marketing is a strategic priority for the company.
Customer success reporting to the CRO is the standard pattern past Series B. Reporting to the CEO or COO is more common at smaller companies and at companies with a strong product-led motion. The revenue leaders directory and The CRO Report track the patterns at venture-backed companies.
VP Sales comp is heavily commission-driven, with 40 to 50 percent of OTE in variable tied to the quarterly bookings number. The structure works for a functional role with quarterly accountability.
CRO comp tends to be more weighted toward base and equity, with 25 to 40 percent of OTE in variable. The variable component ties to annual revenue, net retention, and a small set of strategic metrics rather than to quarterly bookings alone. The shift in comp structure follows the shift in operating cadence from quarterly to annual.
The equity differential between VP Sales and CRO is real but smaller than the title would suggest at most companies. The bigger differential is in the equity package timing. CROs hired into a real cross-functional scope at growth-stage companies often negotiate equity refresh grants tied to revenue milestones, which can dwarf the base and variable components over a four-year vesting period.
The Pavilion executive compensation surveys and the ICONIQ Growth scale-up surveys both show the CRO equity package at companies past 50M ARR running 0.5 to 2 percent of fully diluted equity, with the band depending heavily on whether the hire is the first CRO or a replacement.
Four patterns recur in the VP Sales to CRO transition. The first is the symbolic title change without scope expansion, which produces an internal promotion that confuses the rest of the org. The second is hiring an external CRO without a clear scope decision on marketing, which produces an immediate conflict between the new CRO and the existing CMO.
The third is hiring a CRO with deep enterprise sales experience for a company that runs a mid-market or SMB motion, which produces a strategic mismatch and a slow ramp. The fourth is firing the existing VP Sales when the CRO arrives, which loses operating context and produces a sales execution gap during the most fragile period of the transition.
The fix to all four is to write the scope, the reporting line, and the success criteria before posting the role. The CEO and the board should align on the answer before any hiring conversation. The path to CRO guide covers the candidate side of the same transition.
Most B2B SaaS companies make the shift between 20M and 50M ARR, with the median at well-run companies around 30M. The trigger is when the scope naturally expands to cover customer success, RevOps, and cross-functional planning. Below 20M, the scope rarely justifies the title.
Both patterns are common at scale, splitting roughly evenly across public B2B SaaS companies. Marketing reporting to the CRO works when the CEO is operationally focused on product and engineering. Marketing reporting to the CEO works when the CEO has strong marketing instincts or when product marketing is a strategic priority.
External hires are more common, running roughly 60 percent of first CRO appointments at venture-backed companies. Internal promotion works when the incumbent VP Sales has cross-functional credibility and is ready to delegate the daily sales operation to a new VP Sales.
CRO comp is more weighted toward base and equity, with 25 to 40 percent of OTE in variable tied to annual revenue and strategic metrics. VP Sales comp runs 40 to 50 percent in variable tied to quarterly bookings. The shift in structure follows the shift in operating cadence from quarterly to annual.
Hiring a CRO with enterprise sales experience for a company that runs a mid-market or SMB motion. The strategic mismatch produces a slow ramp and often a mutual exit within 12 to 18 months. The fix is to align the candidate profile to the actual motion before the search starts.