What a HubSpot portal audit should hand you, and why ours costs $100

Search "HubSpot portal audit" and every result is a landing page offering a free one. Fill in the form, book 45 minutes, and a consultant will share their screen and point at things.

That is not an audit. It is a qualification call with a deliverable shaped hole where the deliverable should be.

Here is what the document should actually contain, and the uncomfortable reason a real one is not free.

Why $100 and not free#

A free audit is one of two things. Either it is fully automated, which means it can count properties and flag empty fields but cannot tell you that your deal stages are meaningless. Or it is a sales call, in which case the findings are selected for what they justify buying.

A useful audit requires a certified implementer to spend hours inside your portal forming judgements. That time has a cost. Charging a small amount for it means the findings can be what we found rather than what we sell, and it means we can tell you that half your list is fixable in house without that being a commercial problem for us.

$100, five days, and it is credited against a project if you go ahead. No call is required at any point, before or after. The document arrives and you read it.

The six areas we review#

Data quality. Duplicate rate by object, required fields that are empty on live records, date and currency format consistency, orphaned associations, and properties that exist but have never been populated. The last category is usually the largest and is quietly poisoning your reports.

Pipeline design. Whether deal stages have written exit criteria, whether they are observable by someone other than the rep, stage to stage conversion rates, and how many deals are sitting in a stage past any plausible cycle length. A pipeline where 40% of open deals have not moved in 90 days is telling you something specific.

Lifecycle and routing. Whether lifecycle stages are defined in a way marketing and sales both accept, whether records can move backwards and under what rule, how leads are assigned, and whether any SLA is actually enforced by a workflow or just written on a slide.

Automation. Every active workflow, what triggers it, and the two failure modes: workflows that never fire because their entry criteria cannot be met, and workflows that conflict with each other so the last one to run wins.

Reporting. Which dashboards are viewed and which are not, and for each chart, whether the property behind it has enough history to mean anything. A dashboard full of accurate looking zeros is worse than no dashboard.

Integrations. What is connected, in which direction, what happens on conflict, and whether anyone would notice if a sync stopped. That last question has a surprising answer surprisingly often, and it is the first thing a well built integration solves.

What the document contains#

Eight to twelve pages, structured so it can be acted on rather than admired.

A prioritised fix list. Ordered by impact over effort, not by the order we found things. Each item states the problem, the evidence in your portal, the fix, and what it costs you to keep ignoring it.

A DIY versus outside help split. Every item marked with who should do it. Renaming properties and writing deal stage definitions are yours. A data migration with 31% duplicates is not. We would rather tell you that most of the list is internal work than pretend otherwise.

A one page budget summary. What the outside help items would cost as a project, so you can take a number to whoever approves budgets without scheduling another meeting.

The evidence. Counts, screenshots and the queries behind each finding, so you can verify anything you disagree with.

Who on your side acts on this#

The reason audits sit unread is that they arrive addressed to nobody.

The fix list assigns each item to a role: the RevOps or admin person for configuration and workflows, the sales leader for deal stage and lifecycle definitions because those are business decisions and not settings, and whoever owns data quality for the import and dedup work.

Deal stage definitions in particular are not an admin task. No consultant can tell you what "Qualified" means in your business. That has to be decided internally and then implemented, in that order.

What it will not tell you#

Worth being clear about the limits.

It will not tell you whether your sales process is good, only whether your portal reflects it consistently. It will not predict revenue. And it will not evaluate your team, though the data often has opinions about which parts of the process people are quietly avoiding, which is usually a design problem rather than a discipline one.

What we need from you#

Read only access, or an export if access is difficult. A sentence about what you were expecting the portal to do for you, because an audit with no stated intent is just an inventory.

Nothing else. No kickoff call, no workshop, no stakeholder interviews unless you want them.

Frequently asked questions#

How long does a HubSpot audit take?#

Five business days from access being granted. The document arrives by email. There is no call attached unless you ask for one.

Is the $100 credited if we hire you?#

Yes, in full against any project that follows. If you do not proceed, the document is yours with no restriction, including the budget summary you can use to get competing quotes.

What access do you need?#

Read only access to the portal, ideally including workflows and reporting. If provisioning access is slow, a set of exports covering contacts, companies, deals and workflow definitions covers most of it.

Do you offer free audits for anything?#

Yes, three of them: codebase and architecture review, website performance and SEO, and data and integration review. The HubSpot portal one is paid because it needs a certified implementer's judgement rather than a crawler's output.