Hiring a HubSpot consultant is usually a sign the portal has outgrown what one busy admin can keep tidy. Pipelines disagree. Reports get questioned. A renewal is coming and nobody wants to pay for licences that sit idle. Below is what a consultant actually does, how they charge, what to watch for, and what you should have after 90 days.
We're a technical HubSpot partner in Cape Town, so read this knowing where we stand. We'll still tell you when you're better off with an in-house hire, a freelancer, or no extra help at all.
What a HubSpot consultant does
A HubSpot consultant designs and builds the parts of HubSpot that make revenue work for your team. That usually covers some mix of:
- Architecture. Objects, properties, pipelines and lifecycle stages that match how you sell, not a default demo portal.
- Build. Workflows, scoring, forms, quotes, reporting and the integrations that keep finance, support or product tools in sync.
- Cleanup. Duplicate contacts, broken automation, unused properties and reports nobody trusts. See our portal rescue work for the cleanup shape.
- Onboarding and go-live. Getting a new portal (or a new hub) live with training your team will actually use. Our HubSpot onboarding page covers the 4 to 8 week version.
- Ongoing RevOps. Keeping the system honest as the process changes, so the numbers stay believable.
If you're still deciding whether HubSpot is the right CRM at all, start with What is HubSpot? and our guide to CRM software in South Africa. No consultant can fix the wrong platform choice.
Consultant, technical partner or in-house: which fits?
The labels on the market blur. What matters is who does the work, who owns the decisions, and who is still around when something breaks.
Independent consultant. One senior person (sometimes a small circle) who scopes, builds and hands over. Good for a clear project with a defined end. Harder if you need several specialists at once, or cover across time zones.
Technical HubSpot partner. A HubSpot Solutions Partner whose delivery is engineering-led: architecture, build, integrations and documentation. You talk to the people who build the portal. That's how Muloo works. See how we work and our partners page.
Marketing-led firm. Strong on campaigns, content and demand generation. Useful when the main gap is marketing execution on a portal that already works. Less of a fit when the CRM data model, integrations or RevOps design are the real problem.
Freelancer. Fast and flexible for a narrow task. Ask about documentation, backup cover and what happens if they're unavailable mid-project.
In-house admin or RevOps hire. Best when HubSpot is core to how you run, and you have enough ongoing change to fill a role. Still common to bring a partner in for the initial architecture, a migration, or a rescue, then hand day-to-day to the hire.
Plenty of teams mix them. A partner builds the foundation, an in-house admin runs it, and a freelancer picks up the odd campaign.
How they charge
You'll see four common shapes. None of them is automatically better. The wrong shape is the one that hides scope.
- 1. Fixed project. A scoped outcome (for example onboarding, a migration, or a portal rescue) for a set fee. Best when the destination is clear. Push for a written scope, assumptions and a change process.
- 2. Retainer. A monthly block of hours or outcomes. Best when the portal needs steady improvement, not a one-shot rebuild.
- 3. Time and materials. Day or hour rates against an estimate. Fine for discovery or unclear messes. Risky without a cap and a weekly burn report.
- 4. Hybrid. A fixed discovery or architecture phase, then a build phase once the scope is real. Often the honest path when the portal is messy.
Two cost lines get mixed up and shouldn't. Your HubSpot subscription is paid to HubSpot. Our HubSpot pricing guide covers how that works. The consultant or partner fee is for the work on your portal. We don't resell or mark up HubSpot licences. When Muloo onboards you, you pay Muloo for onboarding, not a separate HubSpot onboarding fee.
Ask for a clear split on the quote: what is HubSpot's bill, what is the partner's bill, and what happens if your HubSpot usage changes mid-project.
Red flags
Walk away, or at least slow down, if you hear these:
- No access to the builder. You're sold by an account manager and never meet the person who will touch the portal.
- No written scope. "We'll get HubSpot working" is not a scope. Objects, hubs, integrations, data migration and training should be named.
- No documentation. If they won't write down what they built, you're buying lock-in. We document what we build and hand it over. No lock-in.
- Licence markup you can't see. Ask whether the partner marks up HubSpot licences.
- Guaranteed ranking or pipeline numbers. Nobody honest can promise leads or revenue from a CRM rebuild alone.
- Everything is "configuration", nothing is architecture. If nobody asks how you sell before they build workflows, expect rework.
- Your team is cut out. A portal your people don't understand will drift the week the partner leaves.
Questions to ask
Take these into the first call. The answers matter more than the slide deck.
- 1. Who exactly will build in our portal, and will they be on the calls?
- 2. Which hubs, objects and integrations are in scope, and which are out?
- 3. How do you handle data migration, duplicates and historical activity?
- 4. What do you document, and do we own that documentation?
- 5. How do you price change requests once build starts?
- 6. How do you train our team, and what does "done" look like?
- 7. What does the first 90 days after go-live include?
- 8. When are you the wrong fit?
That last one matters most. A straight answer saves both sides a bad project.
What good looks like in the first 90 days
After three months you should be able to point to proof, not vibes:
- A portal map. Which objects, pipelines and key properties exist, and why.
- Working core journeys. Lead to MQL to SQL to close (or your version), with workflows that match the process you agreed.
- Reports your leaders open. Pipeline, conversion and activity numbers that match reality closely enough to run meetings from.
- Integrations that don't surprise finance. The fields that matter stay in sync, with an owner named for each connection.
- A short admin guide. How to add a property, pause a workflow and request a change without breaking the model.
- A backlog, not a blank stare. The next improvements are listed, sized and ordered, whether you keep the partner on a retainer or run them in-house.
If 90 days in you still can't explain how a lead becomes revenue in HubSpot, the engagement hasn't delivered yet.
Getting help from Muloo
Muloo is a technical HubSpot partner and a HubSpot Gold Solutions Partner of about ten years, listed on the HubSpot Solutions Directory. You talk to the engineer. We work from Cape Town with teams in South Africa, the UK, the US and Australia, remote or on site.
If the portal needs a rebuild, start with portal rescue. If you're new to HubSpot, start with onboarding. Not sure where the portal stands? Get a free portal score first, or book a call with the engineer.
