HubSpot portal audit with a list of fixes

The engagement

One audit. Concrete output. Stands on its own.

Portal audit

The HubSpot Portal Audit

Typically 2-3 weeks

A structured review of an existing HubSpot portal. I look at how the platform is actually being used, and map what's working against what's quietly costing your team time, deals, or attribution accuracy.

You get a written scorecard, a prioritised fix list with effort estimates, and a 90-minute readout with whoever needs to be in the room. No code changes inside the audit - the audit is the diagnosis, not the surgery.

Written scorecard across six dimensions
Prioritised fix list with effort estimates
90-min readout with recording
Recommended 'do this first' sequence
Audit fee credits against follow-on work (30 days)

HubSpot

Access. Review. Document. Walk-through.

01Call

Access

A read-only user in your portal is enough to start. I agree up front what I may look at and what stays closed.

02Audit

Review

A day of work in the account: process, data, automation, reports, integrations, licence use. Findings are written down as they appear, with the evidence next to each one.

03Readout

Document

The findings become a prioritised list with effort estimates. No finding goes in without a number or a record I can point at.

04Call

Walk-through

A call to go through the list, agree what matters and what does not, and settle who does what. Whatever I correct on that call goes into the document.

HubSpot

Six areas I go through.

Data layer

Sales process and stages

Pipelines, stages and whether a stage describes something that changed on the buyer's side or something the salesperson did. Stages that describe internal activity make time-in-stage meaningless.

Workflows

Data and hygiene

Duplicates, records without owners, companies without a single associated contact, properties nobody fills in. Half the custom properties in a mature portal usually come from a CSV import where a column did not map.

Sales motion

Automation and workflows

What runs, what overlaps and what nobody can explain. Automated tasks that pile up unclosed are noise, not process, and they are the easiest thing to find in an audit.

Reporting

Reports and whether they tell the truth

I take the reports the board looks at and check whether the data can even reach them. A funnel report counting from a middle stage quietly drops every record that arrived by import or migration.

Integrations

Integrations and data flow

What each integration writes, in which direction, and what it overwrites. An integration that overwrites a manual entry can destroy the credibility of a report on its own.

Security + cost

Licence and adoption

Which paid features the company pays for and does not use, and who has not logged in for weeks. That is a cost conversation grounded in the account, not in opinion.

Starter offer

An audit day or a training day to start working together.

Both have a fixed scope and take one working day. I quote a larger project only once I know what is really in it.

HubSpot8 hours

HubSpot portal audit day

Half an hour with leadership on the one number the company cares about
A read-only pass through the portal
Twenty minutes with each team member, up to four people
A document with fixes priced in hours, plus an hour to walk through it

Book a call about the audit See the audit scope

AI in business8 hours, online

AI training day for your team

Six blocks in one day
Opening with leadership, 30 minutes
Hands-on work with the model on your team's materials
Recording and a starter kit for every role

Book a call about the training See the training programme

HubSpot

Questions that come up on a first call.

Do we need an audit or training?

If the reports disagree with what the team says, or nobody can explain why a workflow exists, start with the audit. If the configuration holds up and people simply do not use it, book training instead.

What exactly do we get at the end?

A document with the findings in priority order, an effort estimate for each fix, and a call to go through it. It is written so your own team can execute it.

Do we have to give you access to the portal?

Yes, read-only is enough. An audit from screenshots would be guesswork, and the interesting findings sit in places screenshots never show: import history, workflow enrolment, association counts.

How long does it take?

The audit itself is a day of work in the portal. The document follows, and the walk-through call is scheduled with you. No dates get promised before I have seen the account.

How is this different from a free health check?

A free check tells you something is wrong. This one names what is wrong, what it costs today and how many hours the fix takes. The difference is whether you can act on it the same week.

We already know our portal is a mess. Can we skip the audit and rebuild?

You can, and sometimes that is right. Usually part of the configuration is worth keeping, and a rebuild from zero costs more than sorting out what is there. A day of looking first makes that a decision instead of a bet.