Moving to HubSpot, or starting again on it? I set it up around how your business sells, serves and reports, with the data foundations HubSpot's AI needs already in place on day one.
Peter helped us onboard to HubSpot, he setup and optimised loads of processes as our business grew. … You couldn't be in safer hands.
Douglas Fairchild Growth Marketing Manager, KeylessData
Objects, properties and associations designed around how you actually sell, then the duplicates and gaps cleaned out.
Data and CRM architectureIntegrate
ERP, help desk and delivery tools talking to HubSpot, so nobody rekeys the same customer twice.
HubSpot integrationsAutomate
Approvals, renewals and handoffs that run on their own, without anyone chasing.
HubSpot implementationApps
Custom cards, app pages and portals, so your team works in one place instead of five tabs.
Custom apps and cardsAI
HubSpot's AI and agents working on data they can trust, plus Claude and ChatGPT set up for your team.
HubSpot AI readinessA HubSpot implementation is the set-up of your portal before your team relies on it: edition and seats, data model, pipelines, data migration, integrations, automation, reporting and training. I'm an independent HubSpot Gold Solutions Partner. Implementations start from about a month and from £3,000, are fixed before starting, and are built AI-ready from day one.
Onboarding gets your team into HubSpot. Users invited and permissions set, email and calendar connected, then a walk through the Hubs, what the objects are, how records are laid out and how to change them, and how the tools work and can be configured. It's showing, not building.
How long it takes varies a lot. One team new to HubSpot is quick. Three teams starting from nothing takes longer. A team already on HubSpot adding a Hub, or moving from Professional to Enterprise, sits somewhere in between. It also depends on how quickly your people pick up new tools. HubSpot is built to be simple to use, which is a big part of why it's so popular, so most teams are working in it within days. For a single team, that can be a week: a few training sessions and an admin session.
Implementation is building HubSpot around your business. Your data, pipelines, integrations and automation, worked out with each team, so the tools in the Hub you're paying for actually work. That's where most businesses need the help.
Most of the portals I'm brought into were onboarded, not implemented. The team was shown how it works, but nobody owned it or had the expertise to build it around the business. Even a good build drifts over time: processes change, people leave and take the knowledge with them, and the data stops being reliable. Once the team stops trusting the CRM, they stop using it.
When I look at an implementation that's gone wrong, the problem usually goes back to the first couple of weeks. The portal was set up on HubSpot's defaults, so contacts, companies, deals and one sales pipeline, and then the business was squeezed into that. A year later the team keeps its own spreadsheets and the board doesn't trust the pipeline.
So I start with how you make money. What you sell, how a deal really moves, what happens after it's signed, what finance needs and what the board looks at every month. The portal gets designed from that, then built. The build itself is quick. Most of the thinking goes into the design, and that's what decides whether HubSpot ends up paying its way.
I use the same order on every project: data first, then integrations, then automation and reporting, then AI, then making sure your people can actually use it. Each layer depends on the one below.
HubSpot has changed how it sells. Instead of buying Marketing, Sales and Service Hub each at their own tier, new customers pick one edition for the whole account (Starter, Professional or Enterprise), then pay for seats and a monthly allowance of credits. Credits pay for AI features, such as Breeze agents and AI actions in workflows.
If you're already on HubSpot, you stay on your current model for now. Renewing or upgrading may give you the option to move across, but it depends on your contract, so it's worth talking it through before you sign anything.
Before anyone talks about upgrading, I make sure you're using what you already pay for properly, where it matters to the business, and that your teams know what's available so they can choose to use it when they need it. If there's a business goal an upgrade would help with, and the return makes sense, then it's worth doing.
If you're weighing up Enterprise, I can show you what it would look like for your business: new objects for the things you track, custom apps on your records, and the automation behind them. Seeing it built around your own process makes the decision much easier.
The questions that usually settle it:
You get a written recommendation on edition, seats and credits before you sign anything. Book a call to talk through which model you're on and what would make sense for you.
Every project is scoped and fixed before it starts. For a fairly light team coming onto HubSpot, it looks like this.
| When | What happens |
|---|---|
| Week 1 | Design and data. How you sell, the data model and pipelines, and your data brought in. |
| Week 2 | Integrations. Email, calendar and forms, then your ERP or other systems as scoped. |
| Week 3 | Automation and reporting, with HubSpot's AI switched on where the data supports it. |
| Week 4 | Training. |
| Then live | With close support while the team settles in. |
Live in about a month, and a team can often start using it in week three. It depends on the business: the quality of your data, how sophisticated the workflows and automation need to be, and how complex the set-up is. An 8-person consultancy using Sales and Marketing Pro to grow is a very different job from a 100-person charity running HubSpot for sales, marketing, support and its website. You'll get the real timeline in writing before anything starts.
HubSpot's AI, Breeze and its agents, reads the records in your portal. It can only be as good as what it finds there. On most portals I'm brought into, getting it working means going back and fixing the foundations first. On a new implementation you can just build them right.
More on that on the HubSpot AI readiness page.
I do the work myself. The person who scopes it designs it, builds it and trains your team.
I design around how you make money. Close date means when it's signed, not when it's invoiced. If revenue lands on billing dates, I build the reporting on line items and billing schedules from the start, because adding it later means going back through every deal.
I build what HubSpot doesn't do out of the box. If your process needs a booking screen, a quote builder or an approvals queue inside HubSpot, I can build it as a custom app. See custom development.
I keep it simple. HubSpot turns a lot on by default. I strip back what you won't use, so the team sees fewer fields and fewer options, and actually fills in the ones that matter.
Zing365 knew they wanted everything on one platform but not whether it was possible. The project covered a CRM migration from Pipedrive, a custom set-up for their training operations, booking data, automated billing and live revenue reporting, with no upgrade to their HubSpot licence. Invoicing became a routine weekly workflow and the legacy licensing went. The full story is in the Zing365 case study.
If you're moving from another system, the migration page covers how history, emails and attachments come across. If you already have HubSpot and it isn't delivering, start with a HubSpot review instead.
Peter helped us onboard to HubSpot, he setup and optimised loads of processes as our business grew. He always had a solution and was a pleasure to work with. I'd highly recommend Peter to anyone looking for support with HubSpot, you couldn't be in safer hands.

From about a month for a fairly light team, and a team can often start using it in week three. A single Hub with a clean import is quick. Several Hubs, a migration and an ERP integration take longer, and what usually adds time is decisions about how the business works, not the build. You'll have the timeline in writing before we start.
New customers now buy one edition for the whole account, with seats and credits, and existing customers stay on their current model for now. Workflows start at Professional, which is where most established businesses I work with are. Custom objects and custom apps need Enterprise. I'll weigh the licence against what the problem is costing you, and only recommend an upgrade when there's a business goal behind it and the return makes sense.
Implementations start from £3,000 and are fixed before work begins, so the number doesn't move. Cost depends mostly on the number of Hubs and teams, how much data is moving and how many systems need connecting. If you're not sure of the scope yet, a review, from £1,000, is the usual first step.
Yes. I map every object and field first, run a test import, check the counts and associations against the source, then run the full move. Zing365 moved off Pipedrive and a legacy booking platform into one HubSpot portal.
Yes. The portal, the data, the documentation and any custom code are yours. Training and documentation are part of every implementation, so your team can run it without me.
Onboarding, theirs or mine, shows your team how HubSpot works. It doesn't design your data model, bring your history across or connect your ERP. If your set-up is simple, onboarding may be all you need, and I'll say so.
Book a short call. Tell me what you sell, how you deliver it and what you're moving from, and I'll tell you roughly what the implementation looks like and how long it takes.