Blog

RevOps

Hire a RevOps manager, or bring in a consultant first?

Hire a Revenue Operations (RevOps) manager once the growth target, the funnel definitions and the forecast method are agreed. Bring in a consultant first when they are not. A hire carries out decisions. A consultant helps the leadership team make them, builds what they need, and hands over.

I have led more than 50 Revenue Operations projects across EMEA and Australia, and some version of this question comes up in most first calls. This guide is for the CEO or founder who decides, and the revenue leader who makes the case. It covers the signs that the setup has fallen behind, the questions I ask a founder who is about to hire, and when outside help is worth the money.

What are the signs your revenue engine has outgrown its systems?

The clearest sign is a leadership team that argues about the numbers instead of acting on them. Marketing reports one pipeline figure, sales another, and the board stops trusting the forecast. In companies of 20 to 200 people the symptoms tend to arrive together.

  • The forecast misses in both directions. Stage definitions vary by rep, so the pipeline number is an opinion.
  • Leads go quiet at the handoff. Marketing counts a lead as qualified, sales picks it up days later, and nobody owns the gap.
  • The CRM records the past. Reps update it the night before pipeline review, and the real reports live in spreadsheets.
  • Too much depends on one person. When the founder or a long-serving sales manager goes on leave, reporting stops.
  • A new leader cannot get a straight answer. A new CRO asks for conversion by stage and is told it will take two weeks.

None of these is a CRM problem on its own. They are what it looks like when the operating model was built for 15 people and the company is now 60, with three teams and a target the old setup cannot carry.

What does a first RevOps hire walk into?

A first RevOps hire can only carry out decisions that have already been made. In many growing companies those decisions are still open, and nobody has the data to close them.

One company I worked with had about 70 people, no outside funding and a Salesforce team of two or three. They brought us in because rep productivity and profitability had stalled. The Salesforce team kept the system running. Nobody owned how the process worked or how to improve it.

My first question to the CEO was where the business was heading and what success looked like. He told me the target was last year’s revenue plus a little more, because that felt like good motivation. When I asked to see how the business worked today, the next gap appeared: conversion by stage, time to close and revenue per rep were either not captured or not trusted.

They needed to make a decision and had nothing to make it with. More reps or another Salesforce specialist would have added cost and left revenue per head where it was. A RevOps manager hired into that seat would have spent the first months building reporting before anyone could agree on what to fix.

What should you ask before you hire a RevOps manager?

Start with why you need the role at all. Revenue Operations is a support function: it makes marketing, sales and customer success more effective. If those teams are under-resourced, a RevOps manager or a consultancy has little to improve, and the money is better spent on the front line first.

If the need is real, these are the questions I ask a founder who is about to post the job ad:

  1. What will this person be responsible for in the first six months?
  2. Which pain should they take away, in the words your leaders use?
  3. Which systems will they own?
  4. Which targets will they be measured against, and which KPIs show progress?

The answers tell you the size of the job. Sometimes it is a full-time role. Sometimes it is a few days a week, which a part-time or fractional RevOps lead can cover. And sometimes it is bigger than one person: a target to rebuild, a process to design and a build across several systems at once. That is where a consultancy fits.

When is a consultant worth it, and when should you hire instead?

Bring in a consultant when the problem is design and the decision has a deadline. Hire, or wait, when the problem is capacity, when the front-line teams are still under-resourced, or when the operating model works and you need someone to keep the CRM in order.

Two-column graphic titled Bring in a consultant, or hire? listing five situations where an Australian B2B company should bring in a RevOps consultant and five where it should hire or wait.
The one-question test: “what should we change?” is consulting work, “who will do the changing?” is a hire.

Consultancies pay for themselves at the moments the business changes shape faster than its systems: a funding round closes, a new CRO or VP Sales arrives, a RevOps job ad goes up, headcount grows fast, or US expansion starts. Each time, the board or the new leader needs a forecast they can trust within weeks.

Now assume the person you would hire is excellent. They still take months to ramp up, bring one person’s capacity and one person’s range, and need tools, budget and management time to be effective. A consultancy brings a lead consultant who has seen the pattern before, plus specialists for the build, from the first week. An agreement is also easier to change than a role: when the work shrinks or shifts, an engagement can be resized, and a full-time position usually cannot.

There is room for both. A common sequence for a company of 25 to 100 people is a short outside engagement to settle the design, followed by a RevOps hire who inherits a signed-off roadmap rather than a set of open questions. If the plan is already clear and you need someone in the building every day, hire. A good consultancy will tell you so in the first call.

What does a RevOps consultancy actually do?

A Revenue Operations consultancy gets marketing, sales and customer success running on one plan and one set of numbers. The work runs in three stages, and most of the value is decided in the first.

  1. Target first. The one to three year goal becomes this year’s number, then the pipeline, conversion and retention figures that have to hold for it to land.
  2. Numbers second. Stage definitions, lead routing, handoffs and the data behind the forecast are measured against that target.
  3. Then the build. Process, ownership and reporting are redesigned into a roadmap with owners and dates, then built in the system the company already runs, often HubSpot or Salesforce.

At SmoothScale the first two stages take two to four weeks from the first conversation to a signed-off roadmap. In one build I led, we rebuilt the marketing-to-sales handoff around a lead score with three parts: fit to the ideal customer profile; engagement with marketing, the sales team or the product; and recent intent signals that showed a lead was warm. The handover from marketing to sales became far more accurate.

Your revenue leaders keep running their teams. The consultancy designs the system they run on, builds it with them, and hands it over.

What should you ask a RevOps consultant to commit to?

Ask for outcomes you can check without the consultant in the room. If a proposal lists workshops and dashboards with no outcomes, you are buying hours. Put these in the statement of work, with a date beside each.

  • The growth target as operating numbers: new business, expansion and retention, then the pipeline, win rate and cycle time that have to hold.
  • One funnel, one set of definitions, with exit criteria and an owner for each stage, signed off by marketing, sales and customer success.
  • A forecast method the CEO can explain without the consultant present.
  • A baseline of conversion by stage and segment, so you can see what moved in six months.
  • A roadmap with owners, dates and a sequence.
  • A handover plan: who runs this inside the company afterwards, and what they need to do it.

Two things to leave out. A guaranteed revenue number, because a consultant does not control your reps or your market. And a tool recommendation before the process is settled, because the answer will usually be whatever that firm is a partner of.

Frequently asked questions

Who are the best RevOps consultants in Australia?

There is no reliable ranking, and many lists are written by the firms on them. Judge a consultant on whether they start from your growth target, can show a delivered roadmap for a company your size, and will tell you when they are the wrong choice.

How long does a RevOps consulting engagement take?

A diagnostic and roadmap should take weeks. At SmoothScale it is two to four weeks to a signed-off roadmap, with the build following in the sequence the roadmap sets.

Do we need HubSpot or Salesforce before bringing in a consultant?

You need a system of record your teams actually use. A good consultant works in whichever you have. Changing platforms before the process is settled usually moves the problem.

What does RevOps consulting cost in Australia?

It depends on whether you pay for a fixed-scope diagnostic, a monthly engagement or day rates. Compare it with the all-in cost of a hire over the same period. SmoothScale outlines its options on the RevOps consulting pricing page.

What to do next

If two or more of the signs above describe your company, write down next year’s number and the three figures that have to move for it to land. If you can’t, that is the first conversation to have, and it is where we start.

Explore our RevOps consulting process
Ofek Assael

About the author

Ofek Assael is Founder and CEO of SmoothScale, a Revenue Operations consultancy in Sydney for growing Australian B2B companies. He has led more than 50 Revenue Operations projects across EMEA and Australia.