What RevOps Actually Is, and Why Most Companies Get It Wrong

Ask three teams in the same company how many deals are open right now and you will get three numbers. Marketing counts what it handed over, sales counts what it accepted, finance counts what has a signature on it. Nobody is lying and nobody is right, because no agreed definition of a deal exists anywhere in the building.

That is the problem revenue operations exists to fix. Everything else people say about RevOps sits downstream of it.

What RevOps actually is

Revenue operations, RevOps for short, is the work of getting marketing, sales and service running off one set of records, one set of definitions and one set of numbers.

In practice it is unglamorous. Agreeing what "qualified" means and writing it down. Deciding which system owns the customer record. Turning the handoff between two teams into a step in software instead of a message somebody has to remember to send. Then reporting on all of it in a dashboard the three teams read together instead of three they read separately.

HubSpot's definition covers the same ground. One thing worth saying plainly, though: no regulator, standards body or professional association defines RevOps. There is no compliance test to pass and no legal definition to appeal to. It is a way of organising a company, so the version you get depends entirely on who does it.

The company this is written for

Most RevOps advice online is written for American software companies with 400 staff and a dedicated ops team. That is not the Australian mid-market.

The Australian Bureau of Statistics counted 68,325 actively trading businesses employing 20 to 199 people at 30 June 2026, plus 5,366 employing 200 or more. So roughly 74,000 Australian businesses are large enough to have separate marketing, sales and service teams, out of 2.81 million trading businesses in total.

That is the population this piece is for, and most of the ones we walk into have nobody whose job title contains the word operations. The pattern is usually the same too: three teams keeping three sets of books on the same customers, forecasts that never reconcile, and leads going cold in the gap between two people who each thought the other had it.

Why most companies get it wrong

They start at the end.

The usual sequence runs: notice the reporting is bad, buy a reporting tool or hire someone with RevOps in their title, ask for a dashboard, discover the dashboard is wrong, blame the tool. The dashboard was wrong because the records underneath it were never given a shape.

We learned how much the order matters on a build for The Agency, an ASX listed real estate group recruiting agents across five states. HubSpot was already in place, with roughly 48,000 contacts accumulated in it, and the whole thing was producing no pipeline at all. The CRM was fine. What did not exist was the structure underneath it: none of those contacts had a type, a territory, an income tier or a consent position anyone could stand behind, and without those four things nothing can be scored, nothing can be segmented and nothing can be sent.

So the build ran in a fixed order. Nothing could be scored until a contact had a type, nothing could be sent until consent was real, and nothing could be reported until the first four stages were running. Skip a step and the one after it produces a number nobody believes. The full case study walks through all five stages.

The second mistake is treating RevOps as a hiring decision. A dedicated team is one option. The other is naming one person in marketing, one in sales and one in service who own the definitions between them and meet fortnightly. In a 60 to 200 person business that second version usually works better, because what you are short of is agreement, not capacity.

What it is actually worth

Money, two ways.

The first is the work you stop doing by hand. Building the same monthly report by copying figures out of three systems. Chasing a rep for a close date. Re-typing a form submission into the CRM because the form was never connected to it. Automating that in a 100 person business does not make anyone redundant, it gives you back the days those jobs eat, and those days go into work that produces revenue.

The second is deciding on figures instead of instinct. When marketing and sales data sit on the same records, you can see which lead source actually closes, and stop spending on the one that only produces enquiries. You can also see how long deals sit in each stage, which is usually where a forecast goes wrong.

What a RevOps build actually touches

Three things, in this order: your processes, your systems, and the people who own them.

Processes, which means definitions

What counts as a marketing qualified lead. Who owns a contact after the first call. Which deal stages exist and what has to be true before a deal moves into each one. This is the part that sounds like admin and decides whether anything else works. Done properly it shortens the sales cycle, brings customer acquisition cost down and improves retention, because fewer people fall through the cracks between two teams.

Systems, which means the boring build

Then the software, and it is more concrete than the word "infrastructure" suggests. On The Agency build it meant 18 contact properties and 34 deal properties, 59 lists typed by audience and territory, one national pipeline, five playbooks for the general managers, and two dashboards feeding 21 reports on GCI pipeline, how long deals sit in each stage, list growth and activity per general manager.

Duplicate records were collapsed and email addresses verified before anything was imported, because scoring a contact that exists three times produces three different answers. Data quality then got reported beside pipeline every month, on the grounds that anything nobody measures decays back to where it started.

People, which means one name per team

Somebody has to own the definitions, and it should be somebody the team already listens to. There is decent evidence that this matters: employees in high-trust organisations show higher levels of productivity, and handing this mandate to people who already have that standing is how it survives the first disagreement about what "qualified" means.

The Australian part nobody budgets for

Consent.

Most RevOps writing treats the marketing database as an asset you own outright. Under the Spam Act, ACMA puts the burden of proof on you: send a commercial electronic message to an Australian address and it is your job to prove you had consent, express or inferred, and every message needs an unsubscribe that works without making the person log in or hand over more details.

Which turns "we have 48,000 contacts" from a number into a question.

On The Agency build, consent took longer than anything else. Each state general manager sent a personal note to a curated list, as a person instead of as a campaign, with a permanent and immediate opt out offered in the first message instead of buried in a footer. Slower than flipping a bulk flag, and the only version that survives scrutiny. It grew the audience they could lawfully market to by 3.4 times.

How to start, in three steps

1. Find the slow bits

• Read your own sales and marketing material the way a buyer would, and work out where they would stop
• List every point where a customer touches you, then mark the ones where the interaction is never recorded, or gets recorded without the fields you would need to report on it
• Pull whatever conversion data you have and find the most common way a lead first arrives

2. Write the plan, and get all three teams to sign it

• Every stage of the funnel has a report, and every gap you found in step one has a name against it
• Go through the software list, retire what nobody opens, and pick the two manual jobs worth automating first
• Write down the definitions and the new processes for marketing, sales and service, then have all three sign them off in the same meeting

3. Build it, then read what the build tells you

• A short business case per change, saying what it does and which number it should move
• The campaigns and follow up sequences the new process needs to run
• Dashboards on the measures you agreed, conversions, time in each deal stage, emails opened, time on page, so the next round of changes has evidence behind it

Our eight RevOps KPIs worth tracking once the basics are in place is the shortlist we would build those dashboards from, and most of them are already sitting in your portal.

What it looks like when it works

The Agency's figures were measured at handover, two months in, against a recruitment cycle that normally runs 12 to 24 months: 44 qualified deals, five agents signed, and a $5M annual GCI trajectory on the record. The build won a Platform Excellence award at the 2025 HubSpot Impact Awards.

Mountway Finance, a mortgage broking business, is the other one to look at. Rebuilding the marketing, content and sales side of their HubSpot produced 210 per cent more new deals over twelve months, with no ad spend at all. Both sit on our work page with the detail.

Neither is a technology story. Clean records, definitions everyone agreed to, a consent model that survives scrutiny, and reporting the whole company reads.

Wrapping Up

RevOps is not a department you have to hire before you can start, and the first move costs nothing. If your three teams have never agreed in writing what a qualified lead is, that is the job. It takes one meeting and one argument, and every dashboard you build afterwards is worth reading.

After that it needs a standing cadence. Whoever owns it meets regularly, goes through what worked, and is honest about what did not, because this work never gets a completion date.

If sales enablement was your last attempt at this, why sales enablement alone was never going to get you here is worth ten minutes. When you want the practical build, the current 2026 HubSpot RevOps guide has the playbook.

Want us in it with you? That is exactly what our RevOps and HubSpot work is. Give us a nudge.

Before any of that, though: go and ask your three teams how many deals are open. If you get three answers, you already know what the first job is.

Subscribe to our YouTube channel for more HubSpot "how-to" guides and tutorials. Follow us on Facebook and join our HubSpot User Group to stay in the loop with the latest HubSpot updates. 

Happy HubSpotting.