Get your team using HubSpot.

HubSpot only pays off when the team uses it. I train each team on their own records, strip out what gets in their way, write down how it all works and train someone in-house to run it.

He takes something that seems complex and breaks it down into human language.
Noel Halligan Founder, NOCO Hair, award-winning Bristol salon

HubSpot training and adoption means your team uses the portal properly and can run it without outside help. I'm an independent HubSpot Gold Solutions Partner. I run role-based training on your own data, record Loom walkthroughs, write plain-English documentation and train an admin to own the portal. Training is included in every project.

How it works, in detail

Why do teams stop using HubSpot?

When a team avoids the CRM, it's usually because the CRM is asking more than it gives back. Forty fields on a deal, half of them irrelevant. A view that doesn't show what a rep needs before a call. Reports nobody looks at, so nobody sees the point of keeping the data up to date.

So the first question is whether you've got a training problem or a design problem. If the portal is built around how the team works, training sticks. If it isn't, the fix starts with a review.

I'd always take a simpler build that the whole team uses over a clever one that only a couple of people understand. That's usually where I push back on scope.

How does the training work?

  • Role-based sessions. Sales, service, finance, marketing and leadership each get what they need, not a tour of every menu.
  • On your own records. People practise on deals, tickets and customers they recognise.
  • Recorded. Every session is recorded so new starters can catch up without another session.
  • Loom walkthroughs of the jobs people do every week: logging a call, moving a deal, raising a quote, closing a ticket. Short, and easy to find later.
  • Help inside the apps. Custom apps I build carry an in-app "How does this work?" guide, so people can check without leaving the record.
  • Across time zones where your team is spread out, with sessions scheduled around each region's working day.

What it looks like in practice

A global team trained on a new process at a manufacturer

For a UK-headquartered manufacturer, I rebuilt years of product test history in HubSpot and built the tools to generate customer test reports from it. Then I trained their global team on the new testing and reporting process. They also have a private documentation site covering how it all works.

A go-live training pack for a multi-region support team

When an international tech firm moved its support desk from Zendesk to HubSpot Service Hub, the team needed to be ready on the day, across three continents. I built a go-live training pack and a separate explainer for support agents, and ran sessions across time zones. On go-live day I supported each team as it came online, in London, New York and Sydney, across one very long day.

A reporting workshop for a London immersive art studio

I rebuilt a London immersive art studio's revenue reporting around line items and billing schedules. Then, instead of staying the person who builds their reports, I ran a workshop with five of their team on building their own. The team agreed a set of core reports, shared data conventions and an internal owner for data quality. See the revenue reporting work.

Admin enablement: who owns HubSpot after the project?

When nobody owns the portal, fields pile up, someone builds a workflow that clashes with another one, and a year later it needs sorting out again. So every project ends with a named owner, trained to look after it.

  • What's been built and why, written down: objects, properties, pipelines, workflows, integrations and reports.
  • What's safe to change. Adding a dropdown option or a report is fine. Changing a property that a workflow or integration depends on isn't, and the documentation says which is which.
  • How to test a change, in a sandbox where you have one, before it reaches live data.
  • A short routine: a monthly check of duplicates, unowned records and failed workflows.
  • Where to look when something breaks, including what each integration does when it fails.

Documentation people will actually read

Documentation is short and in plain English. A one-page guide per role, a reference of what each property and pipeline stage means, and the Loom library. For larger portals I publish it as a private documentation site behind a login, so there's one place to look.

What happens after the project?

If you have to call me every time you need a new report or a dropdown option, I haven't done the job properly. I'm happy to stay on for the harder work, such as new integrations, custom apps or the next phase. The everyday running of HubSpot should sit with your team.

Training is part of every implementation and rebuild. It's also available on its own if someone else built your portal and your team never really got to grips with it.

My business has grown from the depth of knowledge Peter brings. We mapped out our customer journey and brought in AI tools to make it flow far more smoothly. He takes something that seems complex and breaks it down into human language.
Noel HalliganFounder, NOCO Hair, award-winning Bristol salon

Questions people ask

Why won't our sales team use HubSpot?

Usually because it costs them more time than it saves: too many fields, views that don't show what they need, and no payoff for keeping it up to date. Fix those first and the training sticks.

Do you train on our own data or a demo portal?

Your own portal, on your own records. People remember what they did on a deal they recognise. Sessions are recorded so new starters can watch them later.

Can you train someone to be our HubSpot admin?

Yes. I hand over what's been built, what's safe to change, what isn't, and how to test changes before they go live. The aim is that you don't need to call me for routine changes.

Is training included in your projects?

Yes. Every implementation and rebuild includes training and documentation, and you own all of it. Training can also be booked on its own for a portal someone else built.

How do we know if adoption is improving?

Look at what the team actually does in HubSpot: records updated, deals moved through stages, required fields filled and reports opened. I set up a simple view of that, so you're not relying on how people feel about the system.

Where to next

Want a team that actually uses it?

Book a short call. Tell me who uses HubSpot, who avoids it and who owns it, and I'll tell you what I'd do first.

Book a call