HubSpot audit vs process assessment: which one do you actually need?

A HubSpot portal audit tells you what is wrong with the system: duplicate records, conflicting workflows, reports that don't reconcile. A process assessment tells you why it got that way, by looking at how work moves between the people who use it. If you have inherited a messy portal you probably need both, and the order matters. The audit shows you the symptoms; the assessment finds the causes, so the fixes stick.

Centralise's process assessment is Assess. This article explains what each one covers, where a portal audit stops, and how to tell which you need.

What does a HubSpot portal audit cover?

A portal audit is a technical review of the system as it stands. A thorough one checks data quality (duplicates, incomplete records, contacts and companies with no owner), property sprawl, workflows that are broken, overlapping or undocumented, pipeline and stage set-up, reports and dashboards, users and permissions, and whether integrations are syncing what they should.

You get a list of issues, usually ranked, with technical recommendations against each. For anyone who has inherited a portal, that list is worth having. It turns a vague sense that things are a mess into something specific you can show leadership and work through.

Where does a portal audit stop?

It describes the system. It can't explain the business behind it.

Take a common finding: six workflows set lifecycle stage, and two of them conflict. True, and worth fixing. What the audit can't tell you is why six workflows exist. Usually it is because marketing, sales and customer success each work to a different definition of a qualified lead, and each team built automation to match its own. Delete four workflows without agreeing one definition and somebody builds a fifth within the quarter.

Or take quotes. The audit finds a pile of quotes that were sent and never followed up, with the deals still sitting in the pipeline. The obvious recommendation is a workflow that creates a follow-up task. But if nobody chases because the rep assumes finance takes over once a quote is sent, and finance assumes the rep owns it until signature, the workflow just creates tasks nobody completes. The fix is agreeing who owns the follow-up. Only then is a task worth automating.

What does a process assessment cover?

A process assessment takes a top-down view of how work moves across the whole revenue engine: lead to close, sale to delivery, and renewal and expansion. It looks at the records in the portal, but treats them as evidence about how people work rather than as the thing to be fixed.

That means talking to the people doing the work, not just the people who manage them. It means following a deal across team boundaries, finding what lives outside the CRM (the spreadsheet finance keeps, the inbox where renewals are tracked), and asking where each number in the board pack really comes from.

The output is a set of findings, each backed by evidence, and a prioritised plan that separates what you can fix with what you have from where investment is justified. Some of the most useful recommendations need no technology at all.

Portal audit vs process assessment: side by side

Signs you need the process view

A portal audit is often enough. These are the signs it won't be.

Reports start arguments. The pipeline figure from sales and the revenue figure from finance don't match, and the first part of every leadership meeting goes on working out whose number is right. [LINK: Article 3] covers where that gap usually starts.

Handovers need chasing. Delivery finds out about a new client from a calendar invite, then spends the first call asking questions sales already asked.

Work gets done twice. Account managers rebuild the client's history from email. Marketing exports lists to a spreadsheet because the segments in HubSpot can't be trusted.

You have fixed the same thing more than once. The duplicates were cleaned up last year. They're back.

Nobody can explain why something exists. A property, a workflow, a pipeline stage. It was there when you arrived, and turning it off feels risky because you don't know what depends on it.

If you recognise yourself in that list and you inherited the portal, none of this is a judgement on you. Portals that grow without governance end up here, whoever is running them. Patching from the inside is usually how they got this way. What you need now is a system you can stand behind, and decisions you won't have to undo later.

How Centralise does it: the audit first, then Assess

We start with a free revenue audit at audit.centralise.com. It asks how your revenue engine works today and gives you a report on where it is under strain. You keep the report whatever you decide next.

If you go on to Assess, the audit becomes the starting point. Assess takes three weeks, costs £4,000 excluding VAT for every company, and produces four outputs: the Brief, which agrees scope and outcomes; the Landscape, which shows how work moves today and is reviewed by the people who do it; the Report, with findings and the fix for each; and the Roadmap, which sets out what to change first. Your portal records are examined throughout as evidence, so the technical findings sit inside the process picture rather than in a separate list.

Assess ends at the Roadmap, and you keep every output whether or not you work with us afterwards.

FAQs

Is a HubSpot audit enough?

It is enough when the problems are technical and contained, such as a broken integration, a permissions mess or a reporting fault. If the same issues keep returning, or leadership has stopped trusting the data, an audit will tell you what is broken without telling you why, and the fixes won't hold.

Can I fix it with what I have?

Often, at least in part. The Roadmap separates the changes you can make with your current set-up from those where further investment is justified, so you can see both before committing to anything.

Will an assessment tell me to buy more HubSpot?

Not by default. Assess is about the process first, and its recommendations include fixes that need no technology at all. Where the Roadmap does point to investment, it shows the evidence and assumptions behind it so you can judge it yourself.

Who needs to be involved?

A sponsor who agrees the Brief, plus the people who do the work day to day: reps, operations, delivery, and finance wherever quotes and billing are part of the picture. They review the Landscape before any analysis starts, so the findings rest on something they recognise.

Start with the audit

The free revenue audit is the quickest way to see where your revenue engine is under strain, and it forms the starting point of Assess if you go further.

Start the free revenue audit or find out more about Assess.