You Don't Need a Better VP of Sales. You Need an Architect First.

Two companies hire a sales leader on the same day. Same pedigree, same quota, same stellar recommendations, the same calibre of person by any measure you would put on a scorecard. One of those hires has roughly an eighty-three percent chance of working out in year one. The other has thirty-four. And the difference between them has almost nothing to do with the person in the chair. And more often than founders expect, it has almost nothing to do with the product either.

What separates the two is what was waiting when the leader arrived. The company sitting at eighty-three percent already had a documented, working sales process in place. The one at thirty-four expected its new leader to build that process from scratch while carrying the number from day one. One inherited a blueprint to improve. The other got a blank page and a deadline.

Over the last year, I've been mulling on that gap because it turns the conversation I keep having with founders on its head.

A lot of the Founder / CEO's I talk to are on their third sales leader. A few are on their fourth. The story barely changes between them. We hired someone impressive, from a company everyone respects, with numbers we couldn't argue with. Eighteen months later we're back where we started, writing the job spec again and trying to figure out what we keep doing wrong. The conclusion they reach is nearly always the same. We must keep picking the wrong people.

That conclusion is comforting. It's neat. It keeps the accountability of the failed hire on the candidate. But it's also wrong, and it's one of the most expensive mistakes a growing company can make.

The number is brutal, and it's consistent

Start with how long these leaders actually last. Analysis of fourteen thousand executives by Pave, written up by SaaStr, puts the average tenure of a CRO or CMO at 1.8 years, the shortest of any role in the C-suite. For context, the average CEO in the same dataset lasts 4.3 years. Harvard Business Review, looking at more than a hundred and fifty B2B organisations, lands close by at twenty-five months for the chief revenue officer, and finds annual turnover for the role running at roughly a third every year.

It gets sharper at the early stage. Jason Lemkin's much-quoted look at eighty SaaS startups, which he's honest enough to call unscientific, found that around seventy percent of first-time VPs of Sales don't make it to the twelve-month mark. Not underperform. Don't finish the year.

And replacing them rarely fixes the thing it was meant to fix. The same HBR research found that sixty-two percent of companies saw their growth rate stall or decline in the year after a CRO change, with median growth slipping from 15.5 percent to 11.7 percent. The reset button turns out to be wired to the floor.

If the same role fails this often, across this many companies, the pattern isn't living inside the people. It's living inside the conditions we hand them. This isn't a hiring problem. It's a system problem.

Two different jobs wearing the same title

The market sells one role, the VP of Sales, and quietly expects it to do two very different jobs at once.

There's the architect, who designs the blueprint. The ideal customer, the way a deal actually moves, the qualification discipline, and above all the connective tissue between marketing, sales and customer success so the whole journey hangs together. And there's the builder, the GTM operator, who lays the blocks. Hires the reps, runs the motion, coaches the calls, closes the business. Both of them, all the while, are handed the number and told to deliver it this quarter, whether or not the first job was ever done.

These aren't points on a single spectrum of seniority. They're different skills, drawn from different instincts. The architect thinks in systems and sequence. The builder thinks in momentum and people. Asking one hire to be both, immediately, under a board's quarterly gaze, is asking for the thing that fails two times out of three.

That eighty-three against thirty-four isn't a talent story. It's a job-design story. The blueprint is either there before the builder arrives, or the builder is quietly asked to be an architect on the side, at night, while the number ticks. And the number keeps climbing. The Bridge Group found that revenue-leader quotas rose by more than seventy percent between 2022 and 2024, even as deals took longer to close and fewer reps hit target. We raise the bar and take away the ladder in the same breath.

The research even tells us where the strain shows. Leaders coming out of large, well-run organisations are trained to optimise a system that already exists. Drop them into a scale-up with no system, and the very experience that made them impressive starts working against them. They reach for the support functions, the clean data and the established process that made them effective, and find none of it there. We read that as the person failing. More often it's the environment failing to receive them.

Accountability without authority

There's a second fault that makes all of this worse. The chief revenue officer is handed the most legible number in the business, revenue, but rarely the authority that runs across the whole customer journey. Marketing reports elsewhere. Customer success reports elsewhere again. So the one person carrying the clearest KPI controls only the middle third of the system that produces it.

Maximum accountability, minimum control. We've designed the role so that the person under the most pressure has the least ability to fix the things actually causing it. Then we're surprised when they leave. Mostly, though, we don't wait for them to. HBR's work suggests around seventy percent of CRO departures are initiated by the company, not the executive. These leaders aren't walking out. They're being shown the door of a room they were never given the keys to.

What this isn't

I want to be careful here, because the honest version of this argument I believe is more useful than the convenient one.

Sometimes the leader genuinely is the problem. Leadership IQ's work on twenty thousand hires found that most failures came down to attitude rather than skill, and that holds at the top as much as anywhere. And a wide analysis of more than eleven thousand revenue leaders by Jeremey Donovan found that people moving from big companies into smaller ones weren't, on average, any less successful, as long as the move was a sensible one. So this isn't a simple tale of pedigree, and it isn't an excuse for a poor hire.

The truthful position is that structure and talent reinforce each other. A weak system will defeat a strong leader. A strong system won't save the genuinely wrong one. My argument is only that the first half of that sentence is wildly under-diagnosed, and the second half gets all the attention.

The order of operations is the whole point

If the blueprint is what separates eighty-three percent from thirty-four, then the blueprint has to come first. Not the hire.

That's the work we do. We install the revenue operating system before the company spends another year and another half-million on its fourth attempt at the same role. We map how the revenue motion actually runs, connect the customer journey from lead to prospect to customer to advocate so no single leader is asked to carry the whole of it alone, and put a leadership OS around it — like our ManagementOS or our RevenueCouncilOS — that gives the team one honest, shared view of how customers really move through the business.

Get the sequence right and the next builder you hire walks into eighty-three percent conditions instead of thirty-four. Draw the architecture first, then bring on a builder who can spend all of their attention on execution, rather than half of it sketching the map they're being judged against. The role stops being a coin toss.

So before you write that job spec again, ask a harder question than who. Ask what you're handing them. A blueprint, or a blank page. If it's a blank page, the next hire will fail for exactly the same reason as the last three, and it'll have nothing to do with how good they were.

If that sounds like your business, I'm always happy to talk and share some of our customers stories about implementing a RevenueOS in their companies.