Path From RevOps Manager to Director of RevOps: The 18-36 Month Map

You probably noticed it on a Wednesday afternoon. The CRO Slacks you a question about pipeline coverage by segment, you pivot the report in eleven minutes, and you feel that little hit of dopamine when the answer lands. Good Manager. Useful Manager. The Manager who never gets promoted.

The work that got you to RevOps Manager is, almost word for word, the work blocking your promotion to Director. Clean dashboards, fast Salesforce fixes, a forecast deck that holds up under questioning. Most RevOps people stall here, not because they're bad at the job, but because they became too valuable as the analyst-of-record. The CRO has no incentive to take that machine offline by promoting you out of it.

This piece is the candid version of what nobody writes down: what actually changes at Director, the four capabilities that gate the move, the comp bands so you can stop guessing, and an 18-36 month plan that has worked for a fair number of operators I've watched make the jump.

The Report-Builder Trap

Your reliability is the ceiling. Read that twice.

CROs love a Manager who answers any question in 24 hours. They promote a Director who tells them which questions to stop asking. Those are different jobs, and the Manager job is the one that pays you to never grow past it.

Here are the concrete signs you're stuck:

• More than 40% of your week is ad-hoc requests. (Track it for two weeks. Most stalled Managers are at 55-65% and didn't know.)
• You're the only person in the org who can rebuild the pipeline coverage report from scratch.
• Your calendar has zero strategy blocks. Every hour is reactive.
• The CRO praises you in skip-levels using words like "responsive," "reliable," "knows where the bodies are buried." None of those words show up in Director job descriptions.
• You've been a "Senior Manager" for 18+ months and the conversation about Director keeps getting deferred to "after this quarter."

If three of those land, you're in the trap. The trap isn't a performance problem. It's a positioning problem, and the fix is structural, not effort-based. Working harder digs you in deeper.

What Actually Changes at Director

Three real shifts. Skip the platitudes about "strategic thinking" and "leadership." Here is what's literally different on a Tuesday.

Own the systems strategy, don't just maintain it. A Director sets the 24-month tech stack roadmap covering CRM, CPQ, enrichment, attribution, conversation intelligence, and the BI layer. You decide what gets renewed, what gets ripped out, and what gets bought next. That usually means approving $200K-$800K in annual tooling spend, defending the line items in the CFO's annual budget review, and owning the integration architecture between systems. A Manager files tickets against the stack. A Director designs the stack.

Manage 2-4 ICs. Typical Director team: one or two RevOps analysts, a Salesforce admin, sometimes a data engineer or a deal desk lead. Your output is now their output. The first time you ship a strategic project where you didn't touch the keyboard, you'll feel like a fraud. That feeling is the job. Get used to it.

Broker conflicts between CRO, CFO, and CMO. Territory disputes, MQL definitions, comp plan math, forecast variance fights, attribution wars. The Director is the neutral operator with the data. You will sit in rooms where the CRO wants aggressive territory expansion, the CFO wants cost discipline, and the CMO wants credit for pipeline they sourced. Your job is to bring the numbers, propose the trade-off, and get all three to nod. If you pick a side, you become a partisan, not a Director.

That third one is the one most Managers underestimate. It's also the capability that compounds the fastest.

The Four Capabilities That Gate the Promotion

Print this. Score yourself honestly. If you can't put a "yes" next to all four within 18 months, the title isn't coming.

Score yourself 0, 1, or 2 on each. Zero means "no real evidence." One means "started, not landed." Two means "I have the artifact, the email, the named project."

A Manager who scores 5 of 8 is a strong internal candidate. A 7 of 8 gets the job. Anything under 4 and you're optimizing the wrong thing. Go ship one of these capabilities before having the comp conversation.

Comp Reality (US, 2026)

Don't optimize blindly. Here are the bands I see across mid-market and growth-stage SaaS, gathered from offer letters, recruiter conversations, and a few public benchmarks. New York and the Bay Area run 10-15% higher; remote-friendly offers cluster around the midpoint.

A few notes the recruiter usually doesn't say out loud.

The Director jump usually requires a company change OR a CRO change at your current company. New CROs build new orgs in their first 90 days, and that's when Director slots open. Internal promotions to Director at the same company under the same CRO happen maybe 30% of the time. If your CRO has been there 2+ years and there's a Director above you who isn't moving, your fastest path is external.

OTE for RevOps Directors is usually 60-70% base, 30-40% variable. The variable is tied to revenue attainment, not your individual KPIs. That's a feature, not a bug. It forces you to think like a revenue leader, not a project manager.

The equity refresh at Director is the single biggest delta. A Senior Manager refresh at a Series C company might be $30K-$60K over four years. A Director refresh at the same stage runs $150K-$400K. That gap is the actual reason to push for the title rather than the +$25K base bump.

A Short Script for Asking Your CRO About the Director Path

You'll need to have this conversation. Don't drift into it sideways during a 1:1. Book a dedicated 30 minutes. Use a version of this:

"I want to make sure we're aligned on my next 18 months. My read is that the gap between Senior Manager and Director here is owning the systems roadmap, building a small team, and showing up in exec rooms with a point of view. I'd like to walk you through how I'd close each of those, and hear from you what else matters. If there's a path to Director here in the next 12-18 months, I want to earn it. If there isn't a Director slot in the plan, I'd rather know now so we can talk about how I keep growing."

Three things this script does. It names the capabilities so you both work off the same scorecard. It puts a timeline on the table without ultimatums. And the last sentence is the one that matters. Most CROs respect candor about the alternative being a quiet exit. The ones who don't are telling you something useful.

Don't use this script in your first six months in the seat. Earn the right to it by shipping one strategic project first.

The 18-36 Month Plan

Months 0-6: Audit and Reclaim Time

Track every block of work for two weeks. Use whatever time tracker you can stomach. Bucket into: ad-hoc requests, recurring reports, strategic projects, people work, meetings.

Most Managers find ad-hoc + recurring at 65-75%. Your target by Month 6 is ad-hoc under 25%. You get there with three moves:

• Templatize the top 10 ad-hoc requests. Build a self-serve dashboard or saved view for each. Send the link instead of pivoting fresh.
• Push back on requests that don't have a decision attached. "What will you do differently if I pull this number?" is a fair question. Half the time, the answer is "nothing" and the request dies.
• Pick one strategic project for the year. Territory redesign, attribution rebuild, comp plan overhaul, CPQ migration. Something with a six-figure dollar impact that survives the year-end review.

By Month 6, your CRO should know which strategic project is yours and your calendar should have at least four hours of unbroken strategy time per week.

Months 6-18: Ship the Project, Borrow the Person

Land the strategic project. The whole project. Not "phase one done, phase two on roadmap." Land it, write the post-mortem, present the impact to the leadership team in dollar terms.

Hire or borrow one person. If you can't get headcount, find an analyst on another team who needs a stretch project and co-own them with their manager for a quarter. The capability you're building is "I made someone else more productive at my craft." You can demonstrate that without a direct report on paper.

Start showing up in CRO staff meetings with a point of view, not a status update. Pick one recurring agenda item (pipeline review, forecast review, QBR prep) and own the narrative slide. Walk in with a recommendation, not a dashboard.

Months 18-36: Build the Case (Internal or External)

By Month 18, you have evidence. The strategic project is shipped, the person you developed has shipped their own work, you're a named voice in exec meetings. Now you decide.

Internal path. Write a two-page systems roadmap covering the next 24 months: what you'd buy, what you'd retire, what team you'd build, what business outcomes you'd target. Hand it to your CRO with the script above. If the answer is "yes, here's the plan to get you to Director by Q4," you're done. Execute and collect the title.

External path. Start a quiet search. Talk to two recruiters who specialize in RevOps placements. The title bump usually comes faster outside, and the comp delta is real (see the table). The risk is rebuilding political capital from zero. Worth it more often than not, but go in with eyes open.

A surprising number of operators do both in parallel for a quarter and let the offers force the conversation. That's not unethical. It's how the market actually clears.

The Trap Reframed

The person who gets promoted to Director isn't the best report-builder in the room. It's the operator the CRO trusts to make a $500K tooling call without checking in. It's the person who can sit between Sales and Marketing on a Tuesday and make both sides feel heard. It's the one who hires an analyst on Monday and ships a territory redesign by the end of the quarter.

Stop being indispensable in the chair you're in. That indispensability is the chain. Start being obvious in the chair above, the one where someone else builds the report, and you decide which reports the company should care about in the first place.

The promotion is a different job. Not a bigger version of this one. Treat it that way and the next 18-36 months will move faster than you expect.

Learn More

• A Day in the Life of a RevOps Manager
• Your First 30/60/90 Days as a New RevOps Manager
• Pipeline Hygiene That Finance Trusts
• Revenue Operations Manager Job Description