HubSpot implementation
Marketing, sales and service on one contact record
We set up HubSpot so that a contact’s history, from the first form to the last support ticket, sits in one place. That covers properties, pipelines, workflows, forms, data migration, reports and training.
Contact timeline
- Requested a demo on the websiteForm
- Opened the follow-up emailMail
- Deal created and assignedDeal
- Discovery call heldMeet
- Onboarding question answeredTicket
What it is
One platform, several hubs, one database
HubSpot is built around a shared contact database with separate hubs on top of it for marketing, sales and service. The advantage is that every team sees the same record. The risk is that it can do a great deal, and an account set up without a plan fills with unused properties and overlapping workflows. Our job is mostly deciding what to leave out.
- One record per contact and company, shared by every team
- Forms, emails and lists for marketing; pipelines and sequences for sales
- Tickets and a shared inbox for support
- Workflows that connect them, such as handing a lead to sales at the right moment
Dashboard · sample data
- New contacts from forms38+6
- Leads passed to sales14+2
- Open deals21+3
- Open tickets5−2
What we deliver
A tidy account that each team can work in
Data model
Properties, lifecycle stages and associations defined once, with clear rules for who fills in what.
Migration
Contacts, companies, deals and history moved from spreadsheets, a mailing tool or an old CRM, cleaned first.
Sales setup
Deal pipelines, tasks, templates and sequences that match how your salespeople follow up.
Marketing setup
Forms, lists, email templates and consent settings, connected to your website.
Workflows
Lead routing, follow-ups, internal notifications and hand-overs between teams, each documented.
Reports and training
Dashboards per team and training on your own records, with a guide for people who join later.
How a project runs
Decide the model first, then build
- 01
Follow a contact end to end
We trace a few customers from first contact to support and note which team needs which information.
- 02
Design the data model
Properties, lifecycle stages and pipelines are agreed on paper before anything is created in the account.
- 03
Build, migrate, connect
The account is configured, data imported and checked, and the website, email and other tools connected.
- 04
Train each team
Marketing, sales and support are trained separately on their own part, then we adjust during the first weeks.
What we connect to HubSpot
- HubSpot features
- Contacts and companies, Deal pipelines, Workflows, Sequences, Forms, Tickets, Dashboards
- Connected to
- Your website, Gmail and Outlook, Calendars, Invoicing, ERP, Webshop
- Integration
- HubSpot API and webhooks, n8n, Make
We start from what you already have. The list shows what we reach for when something is missing, not tools you must adopt.
Is HubSpot the right CRM?
A good fit when…
- Marketing and sales need to see the same contact history
- Leads come mainly through your website and email
- You want support tickets on the same record as the deal
- Someone on your side will own the account after go-live
Probably not for you when…
- You only need a simple sales pipeline
- Nobody will have time to keep the account in order
- Your sales process is built around projects or production, not contacts
- You want every feature switched on from the first day
Examples
What a CRM build looks like
Illustrative scenarios, not client projects.
Questions about HubSpot
HubSpot or Pipedrive?
Choose HubSpot when marketing, sales and service should work from one record and someone will look after the account. Choose Pipedrive when the need is a clear sales pipeline that the team picks up quickly. We recommend one after looking at how you sell, and write down why.
Which hubs do we need?
Usually fewer than expected. We start from what each team has to do in the first months and recommend the smallest setup that covers it. Adding a hub later is easier than untangling one bought too early.
Are you a HubSpot partner?
No. We are an independent implementer, we do not resell licences and we take no commission. You hold the subscription in your own account.
Can you clean up an existing HubSpot account?
Yes. We audit properties, lists and workflows, show you what is unused or duplicated, and tidy it in agreed steps so that nothing a team relies on disappears.
How is consent for marketing emails handled?
We set up forms and subscription types so that consent is recorded with the contact and unsubscribes are respected automatically. The legal wording is yours to approve with your advisor.
Can HubSpot be connected to our ERP or webshop?
Yes, through its API. Typical connections are orders and invoices shown on the contact, and won deals creating an order in the ERP. We build these with n8n, Make or a small custom service.
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples