Sales Enablement Was Never Going to Fix Your Revenue Problem

Sales enablement makes your sales team better at selling. Training, content, tooling, methodology. It works, and it is worth doing.

What it cannot touch is anything living between two teams. The handover from marketing. The definition of a qualified lead that three departments fill in differently. The forecast nobody believes. The customer who churns because service never knew what sales promised.

By the time a company is past about sixty people, those are the problems, and no amount of sales training fixes them because none of them belong to the sales team. That gap is what Revenue Operations covers.

What RevOps covers

RevOps is the set of processes, people and technology that manage revenue generation across the whole cycle rather than one team's part of it. In practice that means:

• Lead generation
• Customer acquisition
• Customer onboarding
• Contract management
• Pricing and quoting
• Sales performance management
• Billing and invoicing
• Customer relationship management

Note where that list goes. It does not stop at the sale, and it includes two things sales enablement never touches: billing, and what happens after someone becomes a customer.

The differences that matter

The two get confused because they share end goals. Side by side they are not close.

	Sales enablement	RevOps
Focus	Individual reps and their performance	Every stage of the revenue cycle
Functions	Sales training, sales tools, sales method	Training, tools and process for every team that touches revenue, including finance and IT
Goals	Sales productivity: more qualified leads, better win rates, shorter time to close	Sales productivity plus total revenue growth, with marketing and service working to the same targets
Scope	Resources and training for the sales team	Marketing, sales and service operations together
Team structure	Sits inside sales, usually a Sales Enablement Manager reporting to the Head of Sales	A cross functional team, usually a Revenue Operations Manager reporting to the Chief Revenue Officer
Tools	CRM, marketing automation, training platforms	The same, plus analytics and business intelligence across the full cycle
Process	Linear: give the sales team what it needs	Data driven, with an analysis step that reads across departments
Key metrics	Leads generated, pipeline progress, close rate	Those, plus customer satisfaction, retention and service usage
Results	Better sales productivity	Better sales productivity, and revenue growth across the funnel

Why this shows up at 60 to 200 people

Under about fifty people, one sales team and one marketer sit near each other and the handover happens by conversation. It is inefficient and it works.

Somewhere past that, three things happen at once. The teams stop overhearing each other. A service or customer success function appears, and it has its own view of the customer. And the reporting gets formal enough that people start comparing numbers, which is when everyone discovers the numbers do not match.

That is the moment RevOps becomes an actual job rather than an idea, and it is also the moment sales enablement stops being the answer, because the problems are now in the joins.

What it gives you that enablement cannot

You can see the whole cycle. Where leads come from, how they move, what closes them, why customers stay. When marketing generates volume and sales does not close it, you get to find out whether that is a lead quality problem or a qualification definition problem, instead of two teams each being certain it is the other one.

You can find the time sink. If reps are spending their week on admin, that is visible and fixable, usually by changing how records get created rather than by asking them to work harder.

The forecast improves. Not because RevOps is clever about prediction, but because it makes historical data comparable, and a forecast built on inconsistent stage definitions was never a forecast.

You see churn coming. Behaviour across marketing, sales and service in the one record is what lets you name the accounts at risk this quarter rather than explain them next quarter.

One note on the Australian context

No regulator covers RevOps and no law defines it, so treat every category level claim about it carefully, including ours. There is no compliance reason to do any of this.

The closest useful Australian number is AI adoption, because most of the RevOps tooling being sold right now is AI-branded. The Australian Bureau of Statistics put around 12 per cent of Australian businesses using AI in 2024-25. Among medium businesses it was 22 per cent, against 3 per cent in 2021-22, and among large businesses 35 per cent, against 9 per cent. Those are the ABS figures on business adoption of AI.

Read that next to any RevOps playbook written for the US market. Australian mid-market companies are earlier on this curve, which means a lot of that advice assumes a data team, an analytics engineer and a tooling budget you do not have. The sequencing has to be different even when the destination is the same.

How to make the shift

Five steps, and the first one is the one people skip.

1. Decide what the revenue goal actually is

A number, with a period attached. Everything after this gets prioritised against it, and without it you end up improving whatever is easiest to improve.

2. Look honestly at what you have

Do marketing and sales work to the same definitions. Are your tools current, and do they give you the numbers you need. Does your team have the skills to run this. Expect the answers to be uncomfortable. Every company we look at has gaps here, including the ones with good numbers.

3. Name the gaps

Usually some combination of: sales cannot see what marketing sees, the two have different goals, nobody talks across the handover, and nobody can follow a customer through the whole journey.

4. Plan the fixes in order

Process first, tools second, training third. Automating a broken handover just makes it break faster.

5. Ship it and watch the numbers

This is ongoing rather than a project with an end. The thing you fix in March will need revisiting when the team changes in September.

Where to start

Pick the one number your teams disagree about most and trace it back to the properties and process behind it. That single exercise usually finds the gap, and it gives you a reason people accept for changing how records get created.

If you want the longer version, there is the full explainer on what RevOps is and the current 2026 HubSpot RevOps guide. Once it is running, the eight KPIs worth tracking is where to look next, and the automations to have in place before the new financial year covers the practical build.

This is most of what our RevOps and HubSpot work is. If you are trying to work out whether you need a RevOps function or a better sales enablement programme, tell us which numbers your teams argue about and the answer is usually obvious from that.