The work
What HubSpot implementation actually involves
HubSpot is a capable platform. The gap between what it can do and what most businesses actually get out of it is almost entirely a configuration and process problem, not a technology problem.
A CRM is only useful if it reflects reality. That means deal stages that map to how your buyers actually progress, properties that your team actually fills in, and pipelines that your forecast can be built on. When those things aren't true, the CRM becomes a filing system nobody believes.
The implementation work I do starts with understanding the revenue function first — the process, the people, the data — and then building HubSpot around that. Not the other way around. The output is a CRM your team uses because it makes their job easier, not because someone told them to.
What's in scope
- CRM architecture and deal stage design
- Pipeline structure and stage criteria
- Properties, views, and data hygiene framework
- Revenue reporting and forecast setup
- Sales sequence and workflow automation
- Marketing to sales handoff configuration
- Team onboarding and adoption
- Integration with outbound tools (Apollo, Clay)
- Dashboard and board-level reporting templates
- Ongoing admin and optimisation
Where it earns its place
Six things HubSpot should be doing in your revenue function
Pipeline management
A pipeline that reflects real buyer progress, with stage criteria your team actually understands and follows. Not a wishlist of open deals sorted by close date.
Forecast accountability
Revenue forecasts built on stage progression and weighted pipeline, not gut feel. HubSpot should make it possible to forecast within 15–20% — most businesses aren't close to that.
CRM data integrity
Properties your team fills in, views that surface what matters, and data hygiene that doesn't require a full-time admin. Clean data is the prerequisite for everything else.
Sequence and workflow automation
Follow-up sequences, task creation, internal notifications, and lead routing that run without manual intervention. The automation that saves time, not the automation that creates noise.
Marketing and sales alignment
Handoff criteria, lead scoring, and lifecycle stage management that means leads don't fall into a gap. Marketing and sales looking at the same data, with a shared definition of what a good lead looks like.
Revenue reporting
Board-ready dashboards showing pipeline health, conversion rates, sales velocity, and team performance. Reporting that earns trust because it's built on honest data.
The diagnostic
Signs your HubSpot implementation needs work
Your pipeline is a graveyard
Deals sit in the same stage for weeks. Nobody updates them. The CRM is where opportunities go to be forgotten.
Forecasting is guesswork
You pull a report and have no confidence in the number. Different people give different answers to the same question.
Your team isn't using it
Reps log calls after the fact, if at all. The CRM reflects what people thought happened, not what did.
You can't see what's working
No reliable view of conversion rates, sales velocity, or where deals are falling out. You're flying blind on what to fix.
Marketing and sales aren't aligned
Leads come in, disappear, and nobody's sure what happened. Different teams have different views of the same contacts.
You've added complexity without value
Workflows nobody understands, properties nobody uses, and a system that's technically full of data but practically useless.
You inherited someone else's setup
Previous admin, previous agency, previous theory. You're working around it rather than fixing it because nobody wants to break anything.
You're about to scale and the cracks are showing
One or two reps worked fine. More people means the process gaps become impossible to ignore.
Solutions Partner
HubSpot implementation with commercial context, not just technical execution.
As a HubSpot Solutions Partner, I work with the platform at a technical level — but the implementation is always led by the revenue question, not the configuration question. What matters is whether the system produces better commercial outcomes. The technical setup is the mechanism, not the goal.
How it starts
HubSpot work usually starts with Discovery Week.
Before touching any configuration, I need to understand your revenue function — how you sell, where it breaks down, and what the CRM needs to support. That's Discovery Week. Everything that follows is built on that diagnosis.
HubSpot implementation might be a standalone project, part of a Fractional engagement, or an Advisory retainer depending on what you need. The model follows the diagnosis.
A CRM your team trusts changes what's possible.
Book Discovery Week. A structured diagnostic of your revenue function — and a clear view of what your HubSpot should actually look like.
Book Discovery Week