Five RevOps Fixes to Ship Before You Hit £5M ARR

The five RevOps fixes worth shipping between £1M and £5M ARR are lead scoring built from closed-won data, one agreed attribution model, lifecycle stage exit criteria enforced by workflow, deal stages named after buyer actions, and renewal risk surfaced 120 days out. Each one builds in HubSpot inside a single sprint.

Five fixes below. Each names the property, workflow trigger and report type you need, and each has a first move you finish inside one sprint.

They cover the five failures we see most in portals between £1M and £5M ARR: scoring built on form fills, three competing versions of the pipeline number, lifecycle stages set by hand, deal stages named after your process instead of the buyer's, and renewal risk surfacing with 30 days left. None of them shows up as a line in your P&L. All of them show up as reps working the wrong accounts, a forecast nobody believes, and a board pack that disagrees with the CRM.

Start with fix 3. Some of the others depend on it, and the sequencing at the end explains why.

If you are under £1M ARR, this is more machinery than your revenue motion needs yet. Build the definitions, skip the automation, come back when volume makes manual work expensive.

How do you build a lead score your sales team will trust?

Build it from the properties that separate your closed-won deals from your closed-lost ones, and nothing else.

What breaks

An MQL defined as "downloaded an ebook" passes volume to sales. Two quarters later reps ignore the queue entirely and the handoff has no credibility left.

The build in HubSpot

• Work in the Lead Scoring app under Marketing, not the old score property. HubSpot's legacy scoring stopped updating on 31 August 2025 and there was no automatic migration, so any workflow still reading the old property is making decisions on frozen data. HubSpot's lead scoring documentation covers the current tool. Contact scores need Marketing Hub and deal scores need Sales Hub, so check what your portal carries before you design the model.
• Build fit and engagement as separate scores rather than one blended number. Fit uses Job title, Number of employees, Industry and Country. Engagement uses pricing page views, repeat sessions inside 30 days, email link clicks and meeting booked. One number tells you a record is warm. Two tell you whether it is warm and worth having.
• Add negative criteria. Free email domains, competitor domains, student and job-seeker titles, unsupported regions. Without these the score drifts upward and stops separating anything.

We have written the full build on the current tool, including what to do if your legacy score is still frozen in place, in our complete HubSpot lead scoring setup guide.

• Contact-based workflow, enrolment trigger on both scores crossing their thresholds. Actions: rotate record to owner, create a task with a due date of one working day, send an in-app notification to the owner.
• Stamp a custom date property when the threshold is crossed. You need it later to report on time to first touch.
  
  

Your first sprint

Sit with two reps. Pull the last 20 closed-won and 20 closed-lost deals and list the contact and company properties present at deal creation. Take the three with the widest gap between the two sets. That is your v1 model. Refine after 90 days of data.

How you know it worked

MQL to SQL conversion rate split by score band, in a custom contact report grouped by score. If the top band converts at the same rate as the middle, the model is doing nothing.

A score nobody acts on is a reporting exercise. The routing, the SLA and the feedback loop that make it real are covered in the MQL to SQL handoff most HubSpot portals get wrong.

How do you stop three teams reporting three different pipeline numbers?

Pick one attribution model, write the definition down, and report from that model alone.

What breaks

Marketing reports pipeline generated. Sales reports pipeline closed. Customer success reports expansion. Three views, three numbers, and a weekly revenue meeting spent arguing about whose is right.

Arguing about the number is usually a symptom. If you want to find where revenue is leaking before you rebuild the reporting, start with finding the real revenue bottlenecks in your SaaS funnel.

The build in HubSpot

• Check your deals are associated to contacts first. Attribution reporting reads the association, so a portal full of orphaned deals will return a clean-looking report built on a fraction of your revenue.
• Pick one model and write the definition down. Original source and Original source drill-down 1 for demand credit, with multi-touch revenue attribution reports on top if you are on Marketing Hub Enterprise.
• Stamp source onto the deal at creation. Deal-based workflow triggered on Create date is known, copying the contact's Original source and drill-down values into custom deal properties. The deal then keeps its source even when the contact gets re-attributed later.
• Build one dashboard: deal funnel report by stage, pipeline created by source, win rate by source, average days to close by source.
• Write the agreed definition into the dashboard description field so nobody rebuilds a rival view six weeks later.

Your first sprint

Forty-five minutes with the sales and marketing leads in one room. Agree what "pipeline created" means, deal created date or entry into a specific stage. One definition, written down, applied everywhere.

How you know it worked

Count the numbers challenged in the weekly revenue meeting. Target zero inside a month.

What are lifecycle stage exit criteria, and how do you enforce them?

A lifecycle stage exit criterion is a property test that has to be true before a record moves on. If you cannot write it as a filter in HubSpot, it is not a definition. It is an opinion.

What breaks

Stages set manually, moved backwards, skipped under pressure. Every funnel conversion report built on top of them is fiction, including the one in your board pack.

The build in HubSpot

• Define each stage as a rule with a property test behind it. MQL becomes: fit score above threshold, engagement score above threshold, Number of employees above your floor, Industry within your target list.
• One contact-based workflow per transition, using Set property value on Lifecycle stage. Remove manual edits from the process.
• Know how backwards movement works before you design around it. HubSpot tools only move the default Lifecycle stage property forward, and setting an earlier stage means clearing the value first, which is where most portals lose their history. HubSpot documents this behaviour in full. Handle genuine resets through a workflow that clears the value and writes a logged reset reason property, never by letting users do it by hand.
• Report stage-to-stage lag using the Date entered [stage] and Date exited [stage] calculated properties HubSpot writes for you. The latest-time and cumulative-time versions need Professional or Enterprise.
• Build the rejection path. Sales sets Lead status to Unqualified with a required Disqualification reason dropdown. A workflow returns the contact to nurture and pushes the reason back to marketing.

Your first sprint

Write the one-line rule for each stage in a shared doc. Get both leads to sign it. Build the MQL workflow first and leave the rest until the definition survives two weeks of real traffic.

How you know it worked

Share of contacts whose lifecycle stage was last set by a workflow rather than a user. Above 95% and your funnel reporting means something.

Should deal stages be named after your process or the buyer's?

The buyer's. A stage should describe something you watched a buyer do, not something your team completed.

What breaks

Stages named after your internal process leave reps guessing where a deal belongs. Stage probability becomes decoration and the forecast becomes a feeling.

The build in HubSpot

• Rename each stage after an observable buyer action. Discovery completed. Technical validation booked. Business case shared with economic buyer. Commercials agreed. Contract out for signature.
• Rename, do not delete and rebuild. Each stage carries a public label your reps see and an internal value used by integrations and reporting, and the internal value is fixed when the stage is created. Deleting stages to start again costs you your historical reporting.
• Set conditional stage properties per stage under Settings, Objects, Deals, Pipelines: next step, close date, and the decision maker attached through a labelled association.
• Set stage probability to your observed win rate from that stage, then recheck it every quarter against the deal stage funnel report.

Stage probability set from real win rates is what moves a forecast from feeling to method. We set out the benchmark and what breaks it in what good forecast accuracy looks like.

• Hygiene workflow: enrol deals where Last activity date is more than 14 days ago and the stage is not closed. Create a task for the owner and notify their manager.
• Build a report on time in current stage. Stuck deals should surface before the forecast call, not during it.

Your first sprint

Pull closed-won deals from the last two quarters and mark the earliest date each buyer action appeared. Rename your stages to match what you find. Resist adding a stage.

How you know it worked

Stage-to-stage conversion in the deal funnel report, plus the share of open deals carrying a close date in the past. The second number is the honest one.

When should renewal risk show up in your CRM?

A hundred and twenty days before the renewal date, while the decision is still open.

What breaks

Customer success learns an account is leaving with 30 days on the clock. By then the decision is made and you are negotiating an exit, not a renewal.

The build in HubSpot

• Create a renewal pipeline on the Deal object, separate from new business. A workflow creates the renewal deal on closed-won, with the close date set to the contract end date.
• Filter the renewal pipeline out of your new business pipeline reports. A renewal deal carries an Amount, so leaving it in inflates pipeline created and makes every conversion rate below it look worse than it is.

Renewal deals are also where net revenue retention goes wrong. The three reporting errors we find most often are in three reasons your NRR is wrong in HubSpot.

• Add company properties: Renewal date, Health score, Last QBR date, Product usage tier. Feed usage from your product database through a data sync integration or a scheduled import.
• Date-based workflow enrolling 120 days before Renewal date. Creates a task for the CS owner, moves the renewal deal into its first stage, notifies the account team.
• Risk trigger: company-based workflow on Health score below your floor, or no logged activity in 45 days. Creates a ticket in a churn risk pipeline with an SLA attached.
• Report renewal deals by stage and close date month, filtered by health score, on the same dashboard as new pipeline. Net revenue retention and new business belong in one view.

Your first sprint

Get contract end dates into a Renewal date property on the Company object. A spreadsheet import is fine for v1. You need the dates before any of the automation earns its keep.

How you know it worked

Share of renewals with a logged CS touch 90 or more days before close date.

Which order should you build these RevOps fixes in?

Fix 3 first. Lifecycle definitions sit underneath your scoring model and every funnel report you own, so building either one before the definitions are agreed means rebuilding both.

The same sequencing logic applies to automation more broadly, which we set out in RevOps automation in 2026: what lean teams should build first.

Then 1, then 4. Scoring feeds the MQL rule you have written. Deal stages give you a forecast worth reading.

Then 2, because attribution reporting is only trustworthy once the stages beneath it are enforced.

Then 5, which stands alone and delivers the fastest commercial return of the five if you have renewals inside the next two quarters.

Sequencing is the part teams skip, and it is the part that compounds. Each build produces something the next one reads: a definition, a score, a stage, a source. Out of order, every one of them gets rebuilt the moment the layer underneath it changes. In order, the work holds and you build it once.

Where to start

If you recognise three or more of these five, our ROC RevOps Audit gives you a health check across the portal and a prioritised roadmap splitting quick wins from foundations, so you know which of these to build first and what it is worth. It takes two weeks and you keep the roadmap whether or not you work with us after it.

If you have already identified the work and need senior hands to build it alongside your team, Fractional RevOps is the embedded version. Right-sized, in your portal, shipping in sprints.

FAQs