Start by understanding what the business needs HubSpot to do, who relies on it and where the current setup gets in the way. Use that context to review the system and agree a prioritised roadmap before making changes.

Start with the business.

Taking over HubSpot can leave you with a long list of unfamiliar properties, pipelines and automations. The first useful question is what the business depends on the system to do. A setup that looks untidy may still support an important process; a tidy-looking one may leave the team working around it.

Choose a few important journeys to understand, such as a new enquiry becoming a customer or an existing account approaching renewal. Ask what should happen, what information people need and how they know the work is complete.

  • What are the business priorities that HubSpot should support?
  • Which teams rely on the information, and for which decisions?
  • Where is work delayed, repeated or happening outside the system?

Listen to the people using it.

Talk to the people doing the work as well as those responsible for the outcome. A report owner, a salesperson and a customer service colleague may describe the same process very differently. Those differences are useful evidence.

Ask someone to walk through a recent example. Follow the handover between teams, notice where information is added and record any spreadsheets or other tools involved. Keep the intended process and the actual process visible so you can discuss the gap.

A useful question

“Show me the last time this happened. What did you do next, and where did you find the information you needed?”

Review what is already there.

Use those journeys to focus the review. Look at the records, properties, pipelines, reports, connections and automations relevant to the work. Record what is useful alongside what needs attention. A list of things to remove is not, by itself, an audit.

Before changing an unfamiliar automation, understand its purpose and the people or processes relying on it. Where workflows are available in the account, their revision history can help explain what changed, when and by whom. Use the current HubSpot documentation for the tools available in your subscription.

HubSpot: view and revert workflow changes

Turn the findings into a roadmap.

Describe each finding in terms of the business impact, the proposed action and any decision needed before work can begin. A missing handover, for example, needs agreement on responsibility as well as a technical change.

Group the work into quick wins, focused tasks or larger phases. Make dependencies visible and agree the scope and priorities before delivery. At Aventine, discovery informs a shared roadmap that the client reviews and signs off before we move into the agreed work.

  • What needs attention first, and why?
  • Which decisions or dependencies could hold up delivery?
  • How will you check that each change has addressed the original problem?
The takeaway

Questions first. Changes second.

A useful starting point is a clear account of how the business works today, what gets in the way and what the team has agreed to improve.

Related service

Our HubSpot audits connect the business context with a review of your setup and a roadmap for what comes next.

Explore audits & roadmaps