HubSpot

HubSpot CRM built around the process you already sell with.

I start with how your company sells and serves customers today, and configure the portal around that. Pipeline, data model, automation and reporting get set up, whatever sits in spreadsheets and the old system comes across, and the team learns the portal on a finished configuration. I work with B2B companies in Poland and abroad.

Book a call
HubSpot

Six areas an implementation covers.

Implementation

Sales process in the CRM

Pipeline, stages with exit criteria, deal properties, tasks and reminders. A salesperson opens a view with today's work on it, not a table of everything.

See Sales HubAudit

Marketing and lead capture

Forms, lists, campaigns, emails and landing pages, wired into a report that shows where an enquiry came from. Handover to sales is defined and visible in the portal.

See Marketing HubMigration

Customer service and tickets

Ticket queue, categories, owners and escalations. Case history sits on the customer record, so sales can see what happens after the contract is signed.

See Service HubRetainer

Data and record structure

Companies, contacts, deals and the associations between them. Properties get created for the reports that have to exist, not the other way round. Deduplication and data hygiene rules apply from day one.

See Smart CRM

Reporting and forecast

Dashboards for the board and for the team, built on fields somebody actually fills in. A report nobody can maintain does not go into an implementation.

See Data Hub

Content and AI inside the portal

Blog, pages and knowledge base in Content Hub, and alongside them the AI tools inside HubSpot: summaries, search across communication history, drafted replies.

See Content Hub
HubSpot

Workshop. Configuration. Data. Go-live and training.

01Discovery

Process workshop

I walk through sales and service as they run today, including the steps done outside the system. Output: a process map, the list of what goes into the implementation, and the list of what stays for later.

02Scope

Portal configuration

Pipeline, properties, views, automation and reports set up around the agreed process. I show the configuration as it goes in, not at the end, so corrections land early.

03Build

Data migration

Field mapping, deduplication and an import into a test environment. Record counts get checked on both sides before production is touched. Customer history comes across with the record.

04Stay

Go-live and team training

Switching to production is a separate, deliberate decision. Training on the finished configuration follows it, and after the first weeks of real use there is a review of whatever needs correcting.

HubSpot

An implementation stands on your process, your data and the team that uses it.

Configuration

Process before configuration

The workshop starts with how the company sells today, including the steps people do outside the system. A portal configured around a textbook process serves a sales motion this company does not have.

Automation

Data moved, not retyped

Whatever sits in spreadsheets, inboxes and the old CRM comes across with field mapping and deduplication, in a test environment before production. Customer history travels with the record.

See migrations from other CRMs
Reporting

Scope agreed up front

The workshop ends with a list of what goes into the implementation and a list of what stays for later. Without the second list an implementation spreads across everything the portal can do.

Migration

A team that works in it

An implementation ends with training on the finished configuration, on the company's own data. A portal nobody knows how to use is a licence cost with nothing coming back.

See training
Not sure where to start?

Want to see what scope on your portal looks like?

A quick call - what I'd expect to find, what an engagement would cover, what falls in the quote.

Contact me
Contact

Let me hear about how your sales runs today.

On the call I go through how many people sell, where the data lives and what leaks because of it. A work email address and a topic are enough to book it.

Starter offer

An audit day or a training day to start working together.

Both have a fixed scope and take one working day. I quote a larger project only once I know what is really in it.

HubSpot8 hours

HubSpot portal audit day

  • Half an hour with leadership on the one number the company cares about
  • A read-only pass through the portal
  • Twenty minutes with each team member, up to four people
  • A document with fixes priced in hours, plus an hour to walk through it
Book a call about the auditSee the audit scope
AI in business8 hours, online

AI training day for your team

  • Six blocks in one day
  • Opening with leadership, 30 minutes
  • Hands-on work with the model on your team's materials
  • Recording and a starter kit for every role
Book a call about the trainingSee the training programme
HubSpot

Questions that come up on a first call. > Questions written the way a buyer asks them on a call. The Polish page uses People Also Ask phrasings from the Polish SERP; those do not carry over to English search, so they are not ported.

How much does a CRM implementation cost?

Two things worth counting separately. The HubSpot licence, paid monthly to HubSpot, depends on the hubs and the number of seats. The implementation is my work: workshop, configuration, data migration, reporting and training. I quote the implementation after the process workshop, because before it any number would be a guess. One sales process with a data migration and training is a project measured in weeks.

Is a CRM hard to use?

HubSpot is one of the easier systems in its class and sales teams pick it up quickly. The difficulty comes from somewhere else: a portal configured around a process the company does not run. That is why the work starts with a workshop on the process and ends with training on the finished configuration, on your own data, rather than a link to documentation. After the first weeks there is a review, and whatever people work around gets fixed.

Which HubSpot licence should we take?

It depends on the process, the number of people and what has to happen automatically. I pick it in conversation, after going through the process, and say plainly which paid features you will actually use. Licence prices are not on this page, because they depend on how the account is put together.

We already have HubSpot and it is a mess. Do we rebuild it?

An audit of the portal first, then the decision. Part of the configuration can usually be saved, and a rebuild from zero often costs more than sorting out what is already there.

What happens to the data in our old system?

It comes across with field mapping and deduplication, together with contact history. The import runs in a test environment first, and record counts get checked on both sides before production.

Who maintains the portal after go-live?

Two ways. The team takes it over, because after training somebody in the company understands the configuration. Or I stay on portal care in an agreed number of hours per month.

Do you also do work outside HubSpot?

Yes. I connect the systems a company already runs, automate processes, and bring AI into the team's daily work. Those are two separate service lines and they also run in companies without a CRM.

Related services

What clients usually pair with this.

Portal Audits

A structured review and a prioritised fix list.

See portal audits

CRM Migrations

Clean cutover from Pipedrive, Salesforce, Zoho, and more.

See CRM migrations

Trainings

Hands-on training on your portal, with your data.

See trainings

Automations & Integrations

HubSpot integrations and cross-stack process automation.

See automations
HubSpot

The portal gets built around the process that already works in your company.

<p>On the call I walk the road from enquiry to signed contract and find the places where it jams. Afterwards you have a scope with what is worth doing first and what can wait.</p>

Contact meBook a call