Skip to content

The HubSpot core

HubSpot onboarding services: set up properly, for the way you actually sell.

HubSpot is bought. Now somebody has to set it up properly. We run a guided build of the hubs you have paid for, module by module with your team in the room, delivered remotely for teams in the UK, the US, Australia and South Africa. You work with the engineer who builds it.

A named specialist replies within one working day.

What are HubSpot onboarding services?

A guided setup of the HubSpot hubs you have licensed: data model, pipelines, lifecycle stages, core automation, reporting and role based training, run module by module with your team over four to eight weeks. HubSpot’s own onboarding teaches you the product. Ours configures it to the way you sell.

What you get

What HubSpot onboarding includes.

  • A data model that matches your business

    Objects, properties, associations and required fields agreed before anything is built. We check users, teams, currencies and every default property first, because a duplicate field is a reporting bug nobody sees for months.

  • Pipelines and lifecycle stages

    Deal stages with exit criteria, and lifecycle stages that mean the same thing to marketing and sales. Required fields sit on stages, not on record creation, so the forecast is protected without slowing anyone down.

  • Core automation

    Lead routing, handoffs and task creation, built to the process agreed in the scoping workshop rather than to the demo, so nothing ends up as automation nobody owns.

  • Reporting from day one

    Dashboards for the meetings you actually run, built on the data model rather than bolted on afterwards.

  • The team using it

    Training by role against your real records, not a sandbox, plus a written way of working and a check in two weeks after go live.

  • Delivered in your hours

    Workshops and training run live in your working day. Configuration happens in ours, so the work moves forward overnight from your side.

Which hubs

Which hubs we onboard.

We scope to the hubs and tier you own, and tell you plainly if something you want needs a higher one. New customers in EMEA now buy one edition for the whole portal, but the work is still done one area at a time, and the data model is built once for all of them.

  • Smart CRM

    The data model, properties, associations, teams, permissions and data hygiene that everything else depends on.

  • Sales Hub

    Pipelines, deal stages and exit criteria, sequences, quotes, forecasting and the sales dashboards leadership uses.

  • Marketing Hub

    Lifecycle stages, lead scoring, forms, email, campaigns and attribution reporting that ties marketing to pipeline.

  • Service Hub

    Ticket pipelines, help desk, SLAs, and the handoff from sales to service.

  • Content Hub

    Website and landing pages on HubSpot CMS, built so your team can change a word without a developer.

  • Data Hub

    Data quality tools, data sync and the automation that keeps records clean.

Scope and shape

Scope and shape.

Every engagement is scoped properly before it starts. This is the shape of a typical one.

Typical duration
Four to eight weeks Driven by how many hubs and how clean the data is
Who has to be in the room
A decision maker, plus one person per hub The single biggest cause of overrun is nobody being able to approve a process
What you supply
Current data, current process, access Messy is fine. Undocumented is fine. Absent is the problem
How it is delivered
Remotely, in sessions in your working hours One named engineer owns the build, and everything is written down
What it is not
A migration or a rescue Coming off another CRM is Migration. An existing portal in trouble is Portal rescue

Free, and yours to keep

Find out what is actually wrong with your portal.

An automated audit of ownership, pipeline hygiene, data quality and admin access. The findings are yours whether you engage us or not.

  • Portal health
  • Workflow audit
  • Data hygiene

Run the free audit

10,000 credits buys one of

HubSpot-sent emails
666
Workflow actions
3,333
AI service conversations
200
AI content pieces
10

How it runs

Scope. Configure. Train. Check back.

  1. 01

    Scope

    One workshop per hub to agree the process before we build to it, with a decision maker in the room.

  2. 02

    Configure

    Data model, pipelines, properties, automation and reporting, built in your portal and shown to you in increments.

  3. 03

    Train

    Sessions by role against your real records: sellers, marketers, service agents and the admin who will own the portal.

  4. 04

    Check back

    Two weeks after go live we look at adoption and fix what people are avoiding, rather than reminding them to use it.

Remote delivery

HubSpot onboarding across time zones.

We are based in Cape Town and deliver remotely. South Africa runs on UTC+2 all year with no daylight saving, which overlaps well with the markets we serve.

United Kingdom and Ireland
One to two hours apart Almost a full shared working day
US East Coast
Six to seven hours behind Cape Town Our afternoon is your morning, which is when workshops and training run
US West Coast
Nine to ten hours behind Sessions in your early morning, or a regular late slot we agree
Australia
Eight to nine hours ahead Sydney and Melbourne. Our morning is your afternoon

Already know you need this?

Skip the audit. Book 45 minutes.

Tell us what is going on and we come to the call having already looked at it. If we are not the right fit, we say so.

Before you ask

The questions we get on this one.

We already did HubSpot onboarding with HubSpot. Why would we do this?

HubSpot’s onboarding teaches you the product. Ours configures the product to your business. They are different jobs, and the second one is where portals usually fail.

How long does HubSpot onboarding take?

Four to eight weeks for most teams, depending on how many hubs you are onboarding and how clean the data is. A build that spans multiple hubs, teams or regions with integrations and migration is a full implementation, typically eight to sixteen weeks.

What is the difference between HubSpot onboarding and HubSpot implementation?

Onboarding configures the hubs you bought to a process that is already reasonably clear. An implementation designs the architecture first, because there are enough moving parts that building straight into the admin screens would create problems you only discover at reporting time.

Can you onboard us if we are in the US, UK or Australia?

Yes. We deliver remotely from Cape Town. Workshops and training are scheduled in your working hours and configuration happens in ours. The UK is one to two hours apart, the US East Coast six to seven hours behind, and Sydney eight to nine hours ahead.

Can you do one hub now and another later?

Yes, and it is usually cheaper that way. The data model is done once and holds for every hub added afterwards.

Do we need Professional or Enterprise?

No. We scope to the tier you own and tell you plainly if something you want needs a higher one, rather than designing around an upgrade you did not agree to.

Why a technical partner rather than a marketing agency?

Most onboarding goes wrong in the same places: a data model nobody designed, lifecycle stages that mean different things to different teams, and automation nobody owns. Those are engineering problems. We write the architecture down before configuring anything, and we measure adoption, not go live.

What happens after go live?

We check back at two weeks and fix what people are avoiding. After that, your team runs it with the documentation, or we run governance with you monthly. Both are fine. Handing over an undocumented portal is not.

Talk to us about hubspot onboarding

Tell us what is going on.

One form, one reply, from the person who would do the work.

  • A reply within one working day
  • From a dedicated specialist, not an account manager
  • A real person reads every message

Rather pick a time now?

Book a call

Protected by reCAPTCHA. We do not sell, share or rent your details.