The RevOps tech stack in 2026: the skills to hire for

The RevOps tech stack in 2026 is the set of systems that runs revenue from first touch to renewal: CRM, data and enrichment, engagement, conversation intelligence, forecasting, CPQ and billing, commission and customer success platforms, joined by a warehouse and an automation layer. The skills worth hiring for are not tool certificates but the ability to design that system, keep its data trustworthy and change how people work with it.

Most RevOps job adverts still read like a shopping list of logos: Salesforce, HubSpot, Outreach, Gong, Clari. That is understandable, because the tools are what the hiring manager sees every day. But the best RevOps hires we place are rarely chosen for knowing a specific tool. They are chosen because they can look at a messy stack and say what it should do, what it actually does, and what to fix first. This guide sets out what a RevOps tech stack looks like in 2026, the seven skills that separate strong operators from tool administrators, how to test for them, and what those people cost in London and the main US hubs.

What is in a RevOps tech stack in 2026?

Stacks differ by company size and motion, but most software companies between Series A and IPO run some version of the layers below. The tool names are examples, not recommendations. The right-hand column is the point: every layer creates a skill requirement, and most of those requirements are about data and process rather than the tool itself.

Two observations from that table. First, at least half the layers exist to move or reconcile data that already lives somewhere else. Second, almost every AI capability in the bottom row is only as good as the CRM and warehouse rows above it. A RevOps hire who is strong on AI tooling but weak on data modelling will build fast, impressive automations on top of records nobody trusts.

Why did the stack become the hiring problem?

The pressure on RevOps comes from three directions at once: tool sprawl, poor data, and buyers who increasingly prefer not to talk to sellers.

On sprawl, Salesforce's fifth State of Sales survey (7,775 sales professionals, fielded in 2022) found that sales teams used about 10 tools to close deals, that 66% of reps felt overwhelmed by the number, and that 94% of sales organisations planned to consolidate their stacks within a year. The same research found reps spent only 28% of their week actually selling. Salesforce's sixth edition (5,500 respondents, published July 2024) put non-selling time at about 70% of a rep's week and found that only 35% of sales professionals fully trusted the accuracy of their organisation's data.

On AI, the 2024 Salesforce data is a useful corrective to the hype. Of the teams that had fully implemented AI, 53% had first consolidated their tech stack and 51% had added data security measures. In other words, the companies getting value from AI did the unglamorous systems work first. That is RevOps work.

On buyers, Gartner's June 2025 survey of 632 B2B buyers found 61% prefer a mostly rep-free buying experience, and 69% see inconsistencies between what a supplier's website says and what its sellers tell them. More of the buying journey now happens in self-serve channels, product trials and digital sales rooms, which means more of the signal RevOps has to capture never touches a sales rep's calendar.

Put those together and the brief for a RevOps hire changes. In 2020 many companies wanted someone to keep Salesforce tidy and build dashboards. In 2026 they need someone who can decide which tools to cut, define the metrics the board will see, design the data flows between product usage, marketing and sales, and put AI to work without breaking any of it.

The seven RevOps skills to hire for in 2026

These are the capabilities we screen for when a client asks for a RevOps manager or head of RevOps. They are listed roughly in the order a stack breaks down if they are missing.

1. CRM architecture and data modelling

This is the foundation. Can the candidate explain how accounts, contacts, leads, opportunities and contracts should relate in your business? Do they know when to use a custom object and when that creates technical debt? Can they design ownership, territory and stage fields so that reporting works without manual clean-up? A strong operator talks about data models before dashboards. A weak one talks about the dashboards they built and cannot explain where the numbers came from.

For Salesforce shops this usually means hands-on administrator-level depth, even in a leadership hire, because a head of RevOps who cannot read a flow or a validation rule will struggle to manage the people who build them. HubSpot shops need the equivalent understanding of objects, associations and lifecycle stages. Candidates who have run both are useful at companies considering a migration.

2. Data and analytics literacy beyond the CRM

The most important number in a software business, net revenue retention, usually cannot be calculated from the CRM alone; it needs billing data. Pipeline attribution needs marketing automation and product usage. As a result, RevOps hires increasingly need working SQL, an understanding of how a warehouse and a modelling tool such as dbt fit together, and the discipline to define a metric once and use it everywhere. They do not need to be data engineers, but they need to be able to brief one and check their work.

3. Forecasting and capacity planning

Forecasting is where RevOps earns credibility with the CRO and CFO. The skills are mathematical as much as technical: pipeline coverage by stage and segment, historical conversion rates, sales cycle by deal size, and the difference between a roll-up of rep judgement and a statistical forecast. Capacity planning sits next to it. A strong candidate can work backwards from a revenue target to the number of ramped account executives needed, the pipeline each needs, and the marketing and SDR output that implies.

4. Compensation plan design and administration

Comp plans are where RevOps decisions hit people's pay packets, so mistakes are expensive and visible. Look for candidates who have designed or administered plans with quotas, accelerators, crediting and split rules, clawbacks and SPIFs, and who can explain the behaviour a plan design produces. The tool layer (CaptivateIQ, QuotaPath, Everstage and others) matters less than the judgement: a plan the system can calculate but the sales team cannot understand will produce disputes every month.

5. Process design and the deal desk

Quote-to-cash is where sales, finance and legal meet. A good RevOps hire can design approval matrices for discounting, define what a clean order form looks like, set up CPQ rules that stop non-standard deals reaching billing, and run a deal desk that speeds deals up rather than slowing them down. In enterprise-led companies this is often the single most valuable thing RevOps does in its first year.

6. AI and automation building, with governance

This is the skill most hiring managers now ask about first. The useful version is specific: building enrichment waterfalls, routing logic, account research agents, call-summary-to-CRM workflows and data-hygiene automations, then measuring whether they work. The governance half matters as much as the building half. Ask candidates how they evaluate an AI workflow's output, how they stop it writing bad data into the CRM, and what they would not automate. Candidates who can only describe prompts, not controls, are early in this skill.

7. Change management and enablement

Every system change is a behaviour change for someone. The operators who succeed write the documentation, train the teams, sit with managers in pipeline reviews and adjust when adoption is poor. The ones who fail ship a new field, send a Slack message and wonder why nobody uses it. In interviews, ask for an example of a system change that people resisted and what the candidate did about it.

Which RevOps skills matter at which level?

Not every hire needs all seven skills at full depth. The table below maps the emphasis by level and gives indicative 2026 base salary ranges from the TRG GTM salary guide. RevOps roles are mostly salaried, with a 10–25% bonus; see the revenue operations pay tables for detail.

Two points on pay. QuotaPath reported in September 2025 that RevOps pay was rising about 5% a year against a projected 4% average across industries, and that San Francisco and New York professionals earn 20–30% more than the US national average. BoostUp's benchmarks show the effect of company size: median OTE of about $100k at companies under 50 people against $162k above 1,000. In London, Robert Walters' 2026 figures, as reported by Fractional Quest, put heads of RevOps at medium-sized companies at £124k–£186k, which is above our range because titles stretch differently at larger companies. Check scope, not title.

Salesforce admin, systems specialist or RevOps leader: which do you need?

A common mistake is hiring a RevOps leader when the real need is a strong administrator, or the reverse. Use the stage of your stack, not the stage of your funding, to decide.

If the honest answer is all five, start with the head of RevOps but make sure they are a builder, not only an analyst, and budget for an administrator within six months.

How do you test RevOps stack skills in an interview?

Most RevOps interviews are too conversational. Candidates describe projects, the panel nods, and nobody checks whether the candidate did the work or sat near it. The process below takes about the same time but produces evidence.

If you add an AI-specific stage, keep it practical: ask the candidate to walk through an automation they built, show how they tested it, and explain one that failed. The failure story is usually more informative than the success.

Where do RevOps candidates come from?

The strongest RevOps candidates rarely come from one feeder. In practice we see four common backgrounds, each with predictable strengths and gaps.

• Sales operations: strong on forecasting, territories and comp; sometimes lighter on marketing and CS systems.
• Marketing operations: strong on automation, attribution, routing and data hygiene; sometimes lighter on forecasting and deal desk.
• Salesforce or HubSpot consultancies: strong on architecture and implementation across many companies; sometimes lighter on owning outcomes after go-live.
• Finance and FP&A: strong on planning, unit economics and board metrics; usually need support on systems administration.

When you write the brief, decide which gap you can live with. A marketing-ops candidate with a good forecasting story is a better head of RevOps for a demand-led company than a sales-ops candidate who has never touched lead routing.

Is the UK RevOps market different from the US?

The skills are the same; the market around them differs in three ways. First, US hubs pay roughly twice the London figure in their own currency at manager level, so UK companies selling into the US sometimes hire their first RevOps leader in America and later build a London team underneath. Second, UK companies more often combine RevOps with sales enablement or with finance-led planning in a single head-of role, because they hire fewer specialists. Third, the US market has more candidates with deep experience of enterprise CPQ and billing implementations, which matters if you sell large, complex contracts.

For UK hires, London remains the deepest pool, but RevOps is one of the GTM functions most comfortable with remote and hybrid work. See our revenue operations specialism page for the roles we cover, and our salary guide for how location affects pay.

Common mistakes when hiring RevOps

• Writing the job advert around tools rather than outcomes. Logos attract tool specialists; outcomes attract operators.
• Hiring an analyst when the CRM is broken. Analysis on bad data produces confident wrong answers.
• Making RevOps report into sales only, so marketing and CS treat it as a sales function. Decide the reporting line before the search; candidates will ask.
• Under-levelling the role. A head of RevOps who owns the board numbers is a senior hire and is priced as one.
• Skipping the practical exercise. It is the only reliable way to separate people who built the system from people who used it.