When someone asks me for a HubSpot review, the answer isn't a straight recommendation or a straight warning. I've used HubSpot since 2016 and delivered dozens of client projects on it — but I've been building WordPress sites the whole time too, and both platforms have always had their strengths and their problems. This is an honest assessment of where HubSpot actually fits, what works, what frustrates and when it's worth paying for.
This post is the verdict. If you want something else, these will get you there faster:
- What is HubSpot, and what do the Hubs do? The plain-English guide.
- How does the CRM hold up on its own? The HubSpot CRM review.
- What does it cost? Seats, credits and tiers explained.
- HubSpot or WordPress? The full comparison.
Where it started
I started using HubSpot in 2016 through my employer at the time, Harva Marketing (now WaveCrest). We were looking for a CRM, and HubSpot's newly released free CRM got our attention. We became a HubSpot partner soon after.
At first we ran only the CRM and Marketing Hub, with websites still on WordPress. As soon as the CMS Hub proper launched we moved sites onto HubSpot, and we've built a great many HubSpot websites for clients since.
Over the years I've used every Hub: CMS, Marketing, Sales and Service. Large Service Hub rollouts have shown me the platform's limits, and Enterprise-tier custom objects have become familiar through several demanding custom builds. That background colours how I assess it: not as a fan, but as someone who has built on it and seen its edges.
Who HubSpot actually suits
The typical client project is a larger organisation adopting marketing automation or a sales system — though I've had plenty of smaller clients too.
HubSpot starts genuinely paying off once you have, say, several salespeople and centralising information into one CRM becomes the sensible move. Because of contact-based pricing it usually suits B2B companies with a long pipeline and high deal values best. That's when the pricing model is justified and tracking a contact's activity in detail is worth doing.
It also works on the consumer side if the relationship is long-lived or the purchase is large. For genuinely commodity products sold at volume, contact-based pricing doesn't necessarily make sense — more on that below.
What HubSpot is best at
Two things stand out.
Usability. HubSpot stood out on interface quality from the beginning. Systems get compared on feature lists far too often, and IT decision-makers in particular don't always account for how much time and friction disappears when usability is right and one system covers several jobs. HubSpot also integrates easily, so it works best when it's allowed to be the primary home for data and the interface people work in.
Pace of development. New capability lands constantly, and HubSpot invests enormously in the platform. Set against many long-established enterprise systems, it's a completely different scale of ongoing improvement.
The best part of the single-platform model is seeing the entire funnel at once. With a carefully built setup you can genuinely say how much revenue a given ad produced and what a lead is worth — and all of that is transparent to the whole team.
What frustrates
In fairness, the downsides.
It can't be best at everything. The flip side of one platform is that it won't lead every category. There are systems dedicated purely to customer service and ticketing that do that part better than Service Hub.
The licensing thicket. HubSpot began as a marketing tool with a heavy price tag. Now there's Free, Starter, Professional and Enterprise across several Hubs, so working out pricing and licensing can be hard at the start. I spend a lot of time explaining this to clients: where the price comes from, what contacts cost. Agents and data enrichment have since joined, running on credits — part of the price is outcome-based, part depends on data volume. That adds another dimension to understanding the whole.
AI integration lags. HubSpot's own AI integration into the platform is a little slow compared with what you can now do with, say, Claude and a HubSpot connector. The built-in AI doesn't yet reach what external tools manage.
Pros and cons at a glance
| Pros | Cons |
|---|---|
| Excellent usability — teams actually use it | Can't be best at everything (better dedicated ticketing tools exist) |
| Fast development, constant new capability | Licensing and pricing are hard to work out |
| One platform → the whole funnel visible and measurable | Contact-based cost can balloon in mass marketing |
| Integrates easily with other systems | Its own AI integration lags external tooling |
| Custom objects handle demanding builds (Enterprise) | Professional is a big jump up from Starter |
Is HubSpot worth the money?
If the platform is used for the right things — producing results and saving time — then yes.
If the goal is brand marketing and there isn't much digital interaction with the audience, think hard. If you're only collecting an email list and sending newsletters while the product sells through retail with no trackable path to purchase, you won't get enough out of HubSpot. A standard WordPress site and a separate email platform is the better and cheaper choice — I've compared the two platforms point by point elsewhere.
What HubSpot can be pushed to do
The best builds have been the ones where HubSpot became the single primary platform, holding all the data and running the operation. Enterprise-tier custom objects are what make that possible.
- For Avara we integrated their rental system into HubSpot. After that, a support agent could immediately reach contracts, rental history and previous service requests — and the team's work became measurable.
- For Isku we've done comparable B2B marketing and systems work on HubSpot.
- For a construction-sector client we built an entire training management system on custom objects.
These show HubSpot's real strength: it bends to a great deal, particularly at Enterprise tier with custom objects in play.
Should you adopt HubSpot?
The honest answer is: it depends. And it depends on exactly the things covered above — what your team looks like, what you sell, what the sales process is and whether there are systems you're obliged to integrate.
If you sell larger B2B deals over a longer pipeline, have several salespeople and want the whole funnel visible from one place, HubSpot is a strong candidate. If it's brand visibility with no trackable path to purchase, spend the money elsewhere.
If a platform decision is on your table and you'd like to think it through with someone, get in touch — I'm happy to work through these same questions against your situation.
Frequently asked questions
Is HubSpot worth it?
It depends on what you sell and how. HubSpot is strong if you sell larger B2B deals with a longer pipeline, have several salespeople and want the whole funnel visible in one place. For pure brand marketing with no trackable path to purchase it's oversized, and the cost is hard to justify.
What is HubSpot best at?
Usability and pace of development. It's easy enough to use that teams actually adopt it, which is rarer in this category than it sounds, and the platform improves constantly. The single-platform model gives you visibility across the whole customer journey — you can see what a given ad eventually produced in revenue.
What are HubSpot's weaknesses?
A single platform can't be best in every category — there are better dedicated ticketing tools than Service Hub, for instance. Licensing and pricing are genuinely hard to work out. And HubSpot's own AI integration lags a little behind what you can build with external tools against its API.
Who should use HubSpot?
It fits B2B companies with several salespeople, a long pipeline and high deal values. That's where contact-based pricing is justified and tracking every lead pays for itself. If you sell commodity products to a mass market, a lighter combination is usually more sensible.
Is HubSpot better than WordPress?
They solve different problems. HubSpot is a customer platform with a CRM at its core; WordPress is a website platform. For websites specifically both have real strengths and weaknesses, which I cover in a separate comparison.