The most expensive title change in software is the one where a company promotes its VP of Sales to Chief Revenue Officer and nothing else changes.
The comp changes. The business card changes. The expectations on the board slide change. But the job — the actual work the person does every day — stays exactly the same. Eighteen months later, the board is asking why growth is stalling, the CEO is quietly running a search, and a talented executive is wondering what happened.
I've watched this movie more than once. The plot twist is always the same: everyone involved — the CEO, the board, and usually the executive — believed the CRO role was a bigger VP of Sales job. It isn't. It's a different job that happens to sit near the same org chart real estate.
If you're a sales leader eyeing the CRO seat, or a CEO trying to decide whether your VP of Sales is ready for it, the most useful thing I can offer is a clear map of what actually changes. Because the difference isn't scope or seniority. It's the nature of the work itself.
Running the Trains vs. Building the Tracks
Here's the metaphor I use when I'm trying to explain the difference.
Running sales is keeping the trains running on time. The forecast call happens every Monday. Pipeline gets reviewed by stage and segment. Deals get inspected. Reps get coached. Quota gets attained — or it doesn't, and you diagnose why. It's a demanding, high-skill job, and when it's done well, it's a beautiful thing to watch. The trains arrive when the schedule says they will.
Leading revenue is deciding where the tracks should go. Which markets do we serve next? Which customers should we stop serving? Do we need a partner motion, a product-led motion, an enterprise motion — and in what proportion? Where do we put the next station? What do we do when the city grows in a direction the current map never anticipated?
Both jobs matter. A railroad with brilliant routes and late trains goes bankrupt. But so does a railroad with perfectly punctual trains running to towns that emptied out a decade ago.
The VP of Sales runs the trains. The CRO is accountable for the map.
And here's the part that trips people up: the better you are at running trains, the more the organization rewards you for staying in the locomotive. Every quarter you make the number by personally inspecting the top twenty deals, you reinforce the muscle that will eventually hold you back. Nobody taps you on the shoulder and says, "Stop driving — go survey the territory." You have to make that shift yourself, usually before anyone gives you permission.
What Actually Changes: Six Dimensions
I came to the CRO job by an unusual route — I was a CMO when I took over the full revenue engine, and a CEO before that — which means I got to observe the VP-of-Sales-to-CRO transition from the outside, repeatedly, before living the role myself. Watching who made the leap and who didn't, the differences showed up in six places. This is the framework I'd put in front of anyone deciding whether they're looking at a real CRO role — or evaluating whether they're ready for one.
What actually changes between the VP of Sales job and the CRO job — dimension by dimension.
Scope. The VP of Sales owns a function. The CRO usually owns more — though not always the same "more." In some companies the CRO holds sales and RevOps. In others, sales and customer success. In my case at GoTo, the role included the full marketing organization, which is part of why I took the title Chief Commercial Officer. The defining trait isn't a specific org chart; it's that the role spans functional boundaries. If the "CRO" role you're looking at owns sales and nothing else, read the next dimension carefully — because scope alone doesn't make the job.
Time horizon. A VP of Sales lives in the current quarter, and should. The pipeline that closes in ninety days was built in the last two; the job is converting it. The CRO has to hold the current quarter and the model four to eight quarters out — because the decisions that determine next year's growth (capacity you hire now, segments you enter now, pricing you change now) all have lag times longer than a quarter. If every hour of your week is spent on deals closing in the next ninety days, you're running trains no matter what your title says.
Financial ownership. This is the dimension I'd argue matters most, and the one most sales leaders are least prepared for. A VP of Sales owns a bookings number. A CRO owns the economics of growth: what it costs to acquire a customer and how fast that cost pays back, what retention does to the durability of the base, how the mix of new business and expansion shapes the revenue model the CFO presents to the board. The conversation shifts from "did we hit the number?" to "is the machine that produces the number worth what we're paying for it?" If terms like CAC payback and net revenue retention live in your peripheral vision rather than the center of your dashboard, that's the gap to close first.
Key relationships. The VP of Sales manages down and across: the team, the deals, the partners in marketing and product. The CRO's most important relationships point up and sideways — the CEO, the CFO, the board. That's not politics; it's the job. The CRO is the person the board holds accountable for the growth story, which means the CRO has to be able to stand in front of investors and defend the model, not just report the quarter. I'll say more about the CFO relationship in a future piece, but the short version: if the CFO doesn't trust your math, you don't really own revenue.
Success metric. A VP of Sales is measured on attainment. A CRO is measured on whether growth is durable and efficient — which sometimes means making decisions that hurt attainment this quarter. Walking away from a segment with great win rates but terrible retention. Slowing hiring when the unit economics say the model isn't ready to scale. Attainment tells you whether the trains ran on time. It tells you nothing about whether the railroad is going anywhere worth being.
Decisions owned. Here's the cleanest test. The VP of Sales owns execution decisions: territories, quotas, deal strategy, hiring against an approved plan. The CRO owns three things the VP of Sales doesn't: the go-to-market model (which motions, which segments, in what mix), the organization design (what the revenue org should look like, not just who fills the boxes), and the long-term growth strategy (where growth comes from in years two and three, not just quarters two and three). If those decisions are being made above you, you're not the CRO — whatever the card says.
Why Great VPs of Sales Fail as CROs
The uncomfortable truth is that the failure rate isn't driven by weak performers getting over-promoted. It's driven by strong performers whose greatest strengths turn into blind spots. Three patterns come up again and again.
Heroics over systems. The best sales leaders I know got there partly through heroics — the quarter saved by personally taking over the big deal, the relationship rescued at 11 p.m. It's a real skill. But heroics don't scale across an organization of hundreds, and a CRO who solves problems by diving in is a CRO who isn't building the system that prevents the problems. The trains run on time only when the train-master is in the station — and that's not a railroad, that's a hobby.
Over-rotating to the deal you can see. Sales leaders are trained to chase the visible: the pipeline in the CRM, the deal at the committee stage. The CRO's most consequential problems are invisible at deal level. Win rates can be excellent while the segment quietly churns out the back door. The current quarter can be safe while the capacity plan guarantees a miss in three. Deal-level instinct, applied to system-level problems, produces confident answers to the wrong questions.
Treating marketing and CS as adjacent rather than owned. This one shows up even when those functions don't formally report to the CRO. A new CRO from the sales track tends to keep operating as the head of sales who now attends marketing's QBR — pushing for more pipeline, more leads, more air cover, as a customer of those functions rather than an owner of the system they all belong to. The CRO who wins is the one who treats the entire revenue engine — including the parts staffed by people who have never carried a quota — as one machine with one set of economics. I came up through both sales and marketing, and I can tell you the view is completely different when you stop thinking of the other function as "them."
None of these patterns is a character flaw. Each one is a strength that was never re-examined when the job changed. Which is exactly the point: the job changed.
The Honest Counterpoint: Sometimes the Trains Are the Job
Now let me argue against myself, because there's a version of this article that's dishonest by omission.
Some companies don't need a track-builder. A company with strong product-market fit, a proven motion, and a clear runway may need exactly one thing from its revenue leader: flawless execution at increasing scale. Keep the trains running, make them faster, add cars. In that situation, a "CRO" who spends their time redesigning the go-to-market model is solving a problem the company doesn't have — and neglecting the one it does.
There are also companies that hand out the CRO title as a retention device or a recruiting sweetener, with no intention of expanding the decisions the role owns. That's not inherently sinister. But you should know which job you're being offered.
So before you take a CRO role — or covet one — ask the questions that reveal the actual job underneath the title. Who decides which segments and motions we invest in? Who owns the design of the revenue organization? When the long-term growth model gets debated, am I in the room as the author or the audience? If the honest answers point up the org chart, you're being offered a train-running job with a CRO title. Take it or don't — but take it with your eyes open.
There's no shame in being a world-class operator of a proven model. Some of the highest-impact revenue leaders I know are exactly that. The career risk isn't being a train-runner. It's being a train-runner who believes they were hired to build tracks, or a track-builder hired into a job that only wants the trains run.
Where Do You Operate Today?
Twelve questions across the six dimensions that separate running sales from leading revenue. Answer for how you actually spend your time — not how your title says you should. Takes about three minutes. Nothing is stored or sent anywhere.
Be honest with yourself here, because the org chart won't be. Titles lag reality in both directions: there are VPs of Sales quietly doing CRO work, and CROs who have never stopped being VPs of Sales. The assessment above is designed to tell you where you actually operate — not where your title says you should.
Building Tracks Before You Have the Title
If you've read this far and concluded you're a train-runner who wants to build tracks, here's the good news: almost everything that distinguishes a CRO can be practiced before anyone gives you the role. The executives who get the job are almost always the ones who started doing parts of it early. Five places to start:
1. Own a cross-functional metric. Pick a number that no single function controls — net revenue retention, CAC payback, pipeline conversion end-to-end — and become the person who understands it best in your company. Cross-functional metrics force you to learn how the whole machine works, and they make you visible to the people who own the whole machine.
2. Build CFO fluency. Ask for thirty minutes a month with your finance partner and have them walk you through how the revenue plan is actually modeled — the assumptions, the sensitivities, what the board pushes back on. The vocabulary of unit economics is learnable, and it is the single highest-leverage language an aspiring CRO can acquire. Boards and CEOs trust revenue leaders who speak finance. It's not optional.
3. Cross the functional line, deliberately. If you've grown up in sales, get real exposure to marketing or customer success — a shared project, a rotation, a joint planning cycle you volunteer to lead. If you're a marketing leader reading this, the same advice points the other way: get closer to the number, ideally by owning one. The CRO role belongs to people fluent in both languages, and fluency only comes from immersion.
4. Write a point of view on the model — not just the plan. Once a year, write down what you believe about your company's go-to-market: which segments deserve more investment, which motion is under-built, where the model breaks in two years. Share it with your CEO. Most functional leaders never do this. The ones who do are signaling, in the most concrete way possible, that they think like owners of the map.
5. Practice the longer horizon. Carve out protected time — even two hours a week — for the questions with multi-quarter lag: capacity, ramp, segment economics, pricing. The current quarter will fight you for every minute. Losing that fight occasionally is how train-runners stay train-runners.
None of this requires permission, a new title, or a bigger team. That's precisely what makes it credible. When the CRO conversation eventually happens — at your company or someone else's — you won't be asking them to bet on potential. You'll be showing them tracks you've already built.
The railroad metaphor has one more thing to teach. In the golden age of railroads, the companies that died weren't the ones with the worst trains. They were the ones who thought they were in the train business when they were actually in the transportation business — who kept optimizing schedules while the world built highways around them.
Revenue organizations face the same trap. Running this quarter's motion flawlessly is necessary, and it is not sufficient. Someone has to be accountable for where the tracks go next. That's the job. Whether it's your job is a question worth answering honestly — and I hope this gave you a better map for doing it.