What is HubSpot? The complete guide, written by engineers

HubSpot is a cloud customer platform that combines a shared CRM database with connected software for marketing, sales, customer service, content management, data operations and commerce. Founded in 2006 and listed on the New York Stock Exchange, HubSpot serves just under 300,000 businesses worldwide, from a genuinely free CRM to Enterprise plans.

SpotDev is a HubSpot Diamond partner. This guide is written by the engineers who build on the platform, including what it does not do out of the box.

Most explanations of HubSpot are written by marketers, for marketers, and they stop at the feature list. This guide is written from the other side of the platform: by the people who work with its objects, APIs and workflow engine every day, and who get called in when a business hits the edges of what it does natively.

That vantage point matters because the question "what is HubSpot?" is really three questions. What does the software actually do? Where does it stop? And is it the right foundation for your business? This guide answers all three, in that order, with the limits stated as plainly as the strengths.

What is HubSpot? The short answer

HubSpot is a single platform for running the customer-facing side of a business. At its centre sits the Smart CRM, a shared database of contacts, companies, deals and tickets. Around that database sit six Hubs (Marketing, Sales, Service, Content, Data and Revenue) plus Breeze, an AI layer, all reading from and writing to the same records.

The one-database design is the whole point. In a typical stack, marketing software, sales software and support software each hold their own copy of the customer, and keeping those copies aligned becomes a permanent integration project. HubSpot removes that problem for the functions it covers, because every team works on the same record.

You have almost certainly used HubSpot without knowing it. If you have booked a meeting through a scheduling link, filled in a form on a B2B website, received a tracked sales email or read a company blog with a "download the guide" offer, there is a fair chance HubSpot was serving it. The platform's fingerprints are on a large share of the B2B web.

HubSpot the company is as established as software vendors get. The headline facts, all publicly reported, are below.

Definitions are sharper when they include the negative space, so here is what HubSpot is not:

• Not just an email marketing tool. Email is one feature of one Hub. Treating HubSpot as a glorified mailing list is the most common way to waste the licence fee.
• Not an ERP or accounting system. HubSpot manages the customer relationship, not the general ledger, stock or manufacturing. Finance systems remain separate and need connecting.
• Not a data warehouse. HubSpot holds operational customer data. Heavy analytical workloads belong in a warehouse that HubSpot feeds.
• Not a ready-made customer portal. The built-in customer portal covers support tickets and knowledge base access. Richer self-service experiences are a build, not a toggle.
• Not entirely free. The free CRM is real and genuinely useful, but the platform most buyers are picturing starts at the Professional tier.
• Not self-implementing. HubSpot is easy to switch on and easy to under-adopt. The software succeeds or fails on the implementation around it.

Where HubSpot came from, and why it matters

HubSpot was founded in 2006 by Brian Halligan and Dharmesh Shah around a single thesis: buyers had stopped responding to interruption, so businesses should earn attention with useful content instead. The company popularised the term "inbound marketing" to describe that approach and built its first product to serve it.

HubSpot's history explains its character. The platform grew from small-business marketing software upwards, adding a free CRM, then sales tools, then service, content, data and commerce products, and moving steadily upmarket into the mid-market and enterprise. Growth came from making sophisticated capability operable by generalists, not from feature-count wars.

That heritage is the key to reading the rest of this guide. HubSpot's greatest strength (software non-specialists genuinely adopt) and its most consistent boundary (deep customisation eventually needs engineering) are two sides of the same design philosophy. Neither is an accident, and neither is going away.

What is HubSpot used for?

HubSpot is used to run the jobs that sit between "someone has heard of us" and "someone is a happy repeat customer". In practice that means generating and capturing leads, working them through a sales pipeline, serving them after the sale, running the website they visit, and reporting on the whole journey from one database.

The concrete jobs businesses buy HubSpot to do include:

• Capturing and tracking leads. Forms, live chat, meeting booking links and ad integrations feed enquiries into the CRM with their full interaction history attached.
• Email marketing and automation. Segmented lists, marketing emails and multi-step automated journeys triggered by behaviour or data changes.
• Running a sales pipeline. Deals move through defined stages with tasks, sequences, call logging and forecasting layered on top.
• Customer service and ticketing. A shared inbox, help desk, knowledge base and surveys, with every ticket attached to the customer record the sales team already uses.
• Publishing the website and landing pages. Content Hub is a full CMS, so the site that generates the leads lives on the same platform that tracks them.
• Quoting and taking payment. Quotes, payment links, invoices and subscriptions through Revenue Hub.
• Keeping data clean and synchronised. Data Hub adds two-way sync with other tools, data quality tooling and programmable automation.
• Reporting across the funnel. Dashboards that join marketing, sales and service activity because all three live on the same records.
• Putting AI to work on customer data. Breeze agents answer support conversations, enrich records and draft content using the context the CRM already holds.

The pattern across all of these jobs is consolidation. Companies rarely adopt HubSpot to do something no software could do before; they adopt it to do eight things on one platform that previously needed eight tools and seven fragile connections between them.

HubSpot's centre of gravity is B2B companies with a dedicated sales team, where marketing generates enquiries that humans then work through a pipeline. B2C businesses use it too, particularly for considered purchases, but pure transactional e-commerce is better served elsewhere. Within a company, the daily users are marketers, salespeople, service agents and the RevOps or operations people who administer the platform.

A concrete example makes the consolidation point better than any list. A prospect reads a blog post on your HubSpot-hosted site, downloads a guide through a HubSpot form, and gets scored and routed by a workflow. A salesperson works the deal through a pipeline with every email and call logged, a quote goes out through Revenue Hub, and after the win the service team inherits the complete history on the same record. Nothing was exported, imported or re-keyed at any step.

What are the HubSpot Hubs?

HubSpot Hubs are the product lines the platform is sold in. There are six: Marketing, Sales, Service, Content, Data (formerly Operations Hub) and Revenue (formerly Commerce Hub). Each Hub is bought separately or in bundles, comes in Starter, Professional and Enterprise tiers, and runs on the same Smart CRM database rather than as separate applications.

The renames matter when you are researching, because most articles online still say Operations Hub, Commerce Hub or CMS Hub. The products are the same; the names changed as HubSpot repositioned the platform around data and revenue rather than departmental silos.

Hubs are bought in combinations, and the combinations follow company shape. A marketing-led business typically starts with Marketing Hub Professional plus free sales tools; a sales-led business starts with Sales Hub and adds marketing later; a support-heavy business leads with Service Hub. The Customer Platform bundles price all the Hubs together at a discount for companies consolidating in one move.

Tiers run consistently across every Hub. Starter removes HubSpot branding and unlocks the basics, Professional unlocks the automation, customisation and reporting that make the platform genuinely powerful, and Enterprise adds governance and scale: custom objects, sandboxes, partitioning and advanced permissions. The practical consequence is that "we use HubSpot" tells you almost nothing; the tier tells you what the business can actually do with it.

Breeze is HubSpot's AI layer rather than a seventh Hub: it spans Copilot (an assistant inside the CRM), packaged agents such as the Customer Agent for support conversations, and enrichment under Breeze Intelligence, all metered in HubSpot Credits (each tier includes an allowance, the Customer Agent consumes 50 credits per resolved conversation, and extra credits cost £9 per 1,000, checked in July 2026). Breeze is genuinely useful and improving quickly, but it is a consumption-billed layer on top of the platform, so it belongs in your cost model from day one. We cover the whole AI layer separately in our guide to AI for HubSpot.

Is HubSpot free? The free CRM versus the paid platform

HubSpot is free at its core and paid everywhere else. The free CRM offers contact, company and deal management for up to 2 users at no cost, indefinitely, with basic versions of many tools attached. The platform that HubSpot is famous for (automation, custom reporting, the full CMS, AI agents) starts at the paid tiers and mostly at Professional.

The free CRM is not a crippled trial. Small teams run real sales processes on it, and HubSpot openly uses it as the top of its own funnel: start free, feel the value, upgrade when you hit a wall. The walls are real, though, and it pays to know where they are before you commit.

HubSpot's commercial design is a graduated ladder: free to Starter (£18/mo per Hub, with a new-customer promotion from £7/mo/seat on annual billing, checked in July 2026), Starter to Professional, Professional to Enterprise. Each rung roughly changes the game rather than just raising limits, which is why budgeting for "HubSpot" without naming the tier is meaningless. We unpack exactly what the free tier does and does not include in Is HubSpot free?.

One buying note from experience: businesses that already know they need automation should not spend months on the free tier proving what the free tier cannot show them. The free CRM demonstrates the database and the interface; the return on investment lives in Professional features. Trial the level you intend to run, or the evaluation answers the wrong question.

Verdict: the free CRM is the best free customer database on the market, but it is a starting point and a sales funnel, not a long-term platform for a growing business.

How does HubSpot work? An engineer's view of the architecture

HubSpot works as a relational customer database with an automation engine and an API surface wrapped around it. Everything you see in the interface (contacts, pipelines, emails, tickets) is data structured as objects, properties and associations. Understanding those three concepts, plus workflows and the API, tells you more about what HubSpot can and cannot do than any feature tour.

Objects, properties and associations

HubSpot stores every entity as an object record. The standard objects are contacts (people), companies (organisations), deals (revenue opportunities) and tickets (service issues), joined by supporting objects such as products, quotes, calls and meetings. Enterprise tiers add custom objects, so you can model things HubSpot did not anticipate: properties under management, policies, vehicles, course enrolments.

Every object carries properties, which are its fields. HubSpot ships hundreds of default properties (lifecycle stage, deal amount, last activity date) and lets administrators add custom ones of various types, including calculated fields at higher tiers. Property design is where good and bad HubSpot implementations diverge: clean, well-governed properties make automation and reporting trivial, while improvised ones quietly rot the database.

Associations are the relationships between records: this contact works at that company, this deal involves these three contacts, this ticket belongs to that deal. Association labels let you name the relationship (decision maker, billing contact), which sounds cosmetic but is what makes serious B2B data models possible on the platform.

A worked example ties the three concepts together. A manufacturer selling through distributors might model each distributor as a company, each buying contact as a contact associated to it with a "purchasing" label, each order opportunity as a deal, and each warranty claim as a ticket associated to both the company and the original deal. Every question the business asks later ("which distributors raised claims against orders over £50k?") is answerable exactly because those relationships were modelled deliberately at the start.

Pipelines and workflows

Pipelines give process shape to deals and tickets: a defined sequence of stages, each with probabilities, required fields and automation hooks. Multiple pipelines let one business run, say, new business, renewals and support escalations as separate processes over the same database.

Workflows are HubSpot's automation engine and the feature that turns a database into an operating system for the customer journey. A workflow watches for a trigger (form submitted, stage changed, date reached), then executes actions: send an email, update a property, create a task, rotate a lead, call an external system. From Professional tier upwards, workflows can branch on any data in the CRM, and Data Hub adds custom-coded actions so engineers can run bespoke logic mid-flow.

The everyday workflows are unglamorous and valuable. Route new enquiries to the right salesperson by territory within seconds. Chase the salesperson when a deal sits in one stage too long. Reopen a nurture sequence when a closed-lost contact revisits the pricing page. Alert an account manager when a customer's ticket volume spikes. Individually each is small; collectively they are the operational discipline most businesses never manage to enforce by memo.

The API surface

HubSpot exposes nearly everything through documented REST APIs: objects, properties, associations, pipelines, files, CMS content and more. Webhooks push change notifications outward, the marketplace hosts hundreds of pre-built app integrations, and the developer platform supports private apps, serverless functions and UI extensions that render custom cards inside the CRM itself.

Access is governed sensibly. Private apps carry scoped tokens so an integration can touch only the data it needs, granular user permissions control what humans see, and audit tooling improves as the tiers rise. For most mid-market security reviews, HubSpot's cloud posture and documentation stand up well; the questions to press on are data residency and your own integration hygiene, not the platform itself.

Tiers are architecture, not just price

HubSpot's tiers gate capability, so the tier decision is an architectural decision. Workflows, custom reporting and most serious automation arrive at Professional. Custom objects, sandboxes, data partitioning and the strongest governance features arrive at Enterprise. A team that designs its data model assuming custom objects, then buys Professional, has designed a system it cannot build.

The same logic applies to change management. Enterprise sandboxes let engineering teams test structural changes before they reach production data; below Enterprise, changes happen in the live portal, so discipline substitutes for tooling. None of this is unusual for SaaS platforms, but buyers moving from custom-built systems are often surprised that version control and staging environments are tier privileges rather than defaults.

Two architectural facts follow from this design, and buyers should hold both. First, HubSpot is genuinely open: an engineering team can connect it to almost anything, extend the interface and treat it as a reliable system of record. Second, the platform sets deliberate guardrails (rate limits on API traffic, execution time caps on custom code, tier gates on features like custom objects), and those guardrails are exactly where "configuration" ends and "engineering" begins. The next two sections map that boundary.

What does HubSpot do well?

HubSpot's defining strength is adoption. Sales, marketing and service teams actually use it, which sounds like faint praise until you have watched a technically superior CRM die of empty fields. Layered on that are a genuinely unified database, an automation engine administrators can run without engineers, a first-class ecosystem and an unusually fast AI release cadence.

HubSpot's usability is not an accident of good design taste; it is the company's strategy. The platform grew from the small-business end of the market upwards, so every feature had to be operable by a generalist before it shipped. The result, in the implementations we deliver, is that adoption problems on HubSpot are usually process problems, rarely software problems.

The single database deserves specific credit. Attribution reporting that joins ad spend to closed revenue, service agents who can see the deal history behind an angry ticket, marketing suppression lists that update themselves when a deal closes: these are cheap on HubSpot and expensive everywhere else, because nothing needs stitching together.

The automation engine earns its place on this list because of who can operate it. On heavier platforms, meaningful process change routes through a development backlog; on HubSpot, a competent administrator ships most of it the same week. That difference compounds: businesses iterate their processes more often when iteration is cheap, and process iteration is where CRM value actually comes from.

The ecosystem compounds the platform. A large app marketplace covers common integrations out of the box, a mature partner network supplies implementation and engineering capacity, and the documentation (both user-facing and developer-facing) is among the best in business software. Breeze has also moved quickly from announcement to genuinely usable: packaged agents with clear per-use pricing rather than vague AI promises.

Speed to value is measurable and material. A HubSpot Professional deployment for a mid-market B2B team typically goes live in weeks, where the enterprise alternatives are measured in months and consultancy day rates. Faster go-live means faster feedback, and faster feedback is what keeps CRM projects alive through their first budget review.

HubSpot's upgrade ladder is a strength too. A two-person startup and a 500-person mid-market firm can run the same platform at wildly different tiers, which means the CRM does not need replacing every time the business doubles. For a fuller, more critical scoring of these strengths against the weaknesses, see HubSpot pros and cons: an engineering assessment.

Verdict: HubSpot is the most usable serious CRM platform on the market, and usability is the metric that decides whether a CRM makes money.

What does HubSpot not do out of the box?

HubSpot does not natively handle deep ERP integration, long-running custom logic, rich customer portals, bespoke AI agents, warehouse-grade reporting or heavily customised front-end builds. Every platform has boundaries; HubSpot's are unusually well documented and, because the API surface is open, almost all of them are solvable with engineering rather than by replacing the platform.

This section is the reason this guide exists. Vendors list features; buyers get surprised by the gaps between them. The table below is the canonical list of the boundaries we are asked to engineer across, stated factually (each one is checkable against HubSpot's own documentation) and paired with the standard build pattern that solves it.

Use the table as a procurement instrument, not just as reading. Before signing, walk your own requirements down the left-hand column and mark every row your business will hit in the first two years. The rows you mark are not reasons to reject HubSpot; they are line items for the real budget, and pricing them before purchase is the difference between a platform decision and a platform surprise.

The three boundaries that bite hardest

Finance integration tops the list by frequency. Marketing and sales run on the CRM, finance runs on the ERP, and the revenue process crosses that boundary on every single deal. A marketplace sync that mirrors invoices one way looks connected in the demo and falls over on the first multi-entity customer, credit note or currency edge case, which is why this boundary is engineered properly or suffered indefinitely.

Customer self-service bites hardest by expectation gap. Buyers hear "customer portal" in the Service Hub feature list and picture their customers managing orders, documents, renewals and account data online. The native portal is a tickets-and-knowledge-base experience, and the distance between those two pictures is a genuine build project that belongs in the budget conversation, not in the post-purchase surprise column.

Long-running logic bites hardest by timing, because teams discover it mid-build. The 20-second cap on custom-coded actions is generous for lookups and transformations and fatal for batch recalculations, large external queries or anything that waits on a slow third party. The fix is architectural (run the heavy work outside HubSpot and let workflows orchestrate it), so discovering the cap after the automation is designed means redesigning.

Read the pattern in that table carefully: none of the limitations says "replace HubSpot". The platform's openness means its boundaries are extension points, and the economics usually favour building the missing 10 per cent over migrating the working 90 per cent. When the boundaries genuinely do bite harder than that, we say so plainly in When you outgrow HubSpot.

Verdict: HubSpot's out-of-the-box boundaries are real, documented and engineerable, and knowing them before you buy is worth more than any feature comparison.

How much does HubSpot cost?

HubSpot costs anywhere from nothing to several thousand pounds a month, depending on tier, Hubs and seats. Checked in July 2026 (UK list prices, ex VAT, annual billing): the free CRM is £0 for up to 2 users, Starter tiers are £18/mo per Hub, and Professional is the step change, at £702/mo for Marketing Hub or £85/mo per seat for Sales and Service.

Headline prices are only half the model. Marketing Hub is priced partly on marketing contacts, Professional and Enterprise purchases carry a required onboarding fee, extra Core Seats start at £40/mo, and Breeze usage is metered in Credits beyond the included allowance. The realistic total for a mid-market deployment is the licence plus implementation plus the engineering that closes the gaps in the table above.

Budget honestly and the platform rarely disappoints; budget only the licence line and the disappointment arrives on schedule. The businesses that report the best return treat year-one HubSpot cost as licence plus implementation plus training, then hold a smaller ongoing line for the integrations and automation the platform will inevitably justify once the team is living in it.

Pricing moves often enough that we maintain a dedicated, regularly re-verified guide: How much does HubSpot cost in the UK? covers every Hub and tier, the hidden costs and worked scenarios.

Who is HubSpot for? (And who is it not for?)

HubSpot fits businesses that sell to other businesses through a real sales process, want marketing, sales and service on one database, and have (or will hire) someone accountable for the platform. HubSpot fits badly where the process is undefined, the organisation needs on-premise software, or nobody owns adoption after the contract is signed.

Company size matters less than company shape, but the sweet spot is real. HubSpot's centre of gravity runs from funded startups to mid-market firms in the hundreds of employees, with the platform increasingly winning larger deployments as the Enterprise tier has matured. Below that range the free and Starter tiers carry a business a long way; above it, the evaluation becomes HubSpot versus the enterprise incumbents on governance and customisation depth.

The sales-team requirement is worth stating bluntly because it filters out the wrong buyers early. HubSpot's paid tiers earn their money when humans work a pipeline: routing, sequencing, forecasting, handoffs. A business with no dedicated salespeople can still use the CRM and the marketing tools happily, but it should size its spend accordingly rather than buying the platform the brochure describes.

The most expensive failure mode deserves its own paragraph, because we see it more often than any technical problem: buying HubSpot and never adopting it. The pattern is always the same. The platform is bought on a compelling demo, a basic setup is rushed, the sponsoring executive moves on, the sales team quietly returns to spreadsheets, and two years later the business is paying five figures annually for an empty database.

HubSpot is unusually resistant to this trap compared with heavier platforms, but no software is immune to it. The defence is boring and reliable: define the process before configuring the tool, migrate clean data, train the team properly and give the platform an owner. That is an implementation discipline, not a product feature, and it is covered in the implementation section below.

Verdict: HubSpot is built for B2B companies that will actually work the system; the platform rewards operational discipline and punishes shelfware buyers at full list price.

How does HubSpot compare to Salesforce, Dynamics 365 and the alternatives?

HubSpot competes with Salesforce and Microsoft Dynamics 365 at the top of the market and with lighter CRMs below it. The honest summary: HubSpot wins on usability, speed to value and platform coherence; Salesforce and Dynamics win on limitless configurability and enterprise ecosystems; the lightweight tools win on price until a business outgrows them.

Comparison shopping rewards specificity, so we keep the detailed head-to-heads in their own guides, including the scenarios where the rival is the right answer. A comparison that never concedes a point is marketing, not analysis.

Run the evaluation on your constraints, not on feature matrices. The questions that actually separate these platforms: who will administer the system day to day, and what can they realistically operate? Which systems must it integrate with, and how deeply? What does the five-year cost look like including implementation, administration and change? Feature parity across serious CRM platforms is high; operability and total cost are where the decisions should be made.

Verdict: for mid-market B2B companies choosing one platform for marketing, sales and service, HubSpot is the default answer, and the burden of proof sits with the alternatives.

How do you implement HubSpot properly?

HubSpot is implemented properly by treating it as an operational change with software attached, not a software purchase with training attached. The sequence that works: define the processes first, design the data model, migrate clean data, configure and automate, train the team on their actual jobs, then iterate. Skipping straight to configuration is how shelfware happens.

1. Define the process. Agree what a lead is, what the pipeline stages mean and who owns each handoff before anyone touches settings. HubSpot will faithfully automate whatever you define, including chaos.
2. Design the data model. Decide which objects, properties and associations represent your business, and what gets archived rather than imported.
3. Migrate clean data. Dedup and standardise before import, not after. A CRM that starts dirty stays dirty.
4. Configure and automate. Build pipelines, permissions and workflows against the defined process, and connect the systems that must stay in sync.
5. Train for adoption, not features. Teams adopt tools that make their day easier; teach the daily job, not the menu structure. Structured HubSpot training pays for itself in field completeness alone.
6. Iterate on evidence. Review usage and reporting monthly for the first quarter and fix friction while habits are still forming.

Data migration deserves the most respect of the six steps, because it is the one you cannot quietly redo later. Legacy CRMs accumulate duplicate records, retired fields, half-finished imports and undocumented conventions, and every one of those problems survives a naive export-import. In the migrations we deliver, the mapping and cleansing work routinely takes longer than the technical transfer, and that ratio is healthy rather than worrying.

Ownership is the other make-or-break variable. The businesses that compound value on HubSpot have a named person (a RevOps lead, an operations manager, sometimes a technically minded marketer) with the authority to say no to property sprawl and the time to keep automation aligned with process. Without that person, entropy wins within a year regardless of how good the initial build was.

Timelines are shorter than enterprise CRM folklore suggests but longer than the sign-up flow implies. A focused Professional implementation for a mid-market team typically runs several weeks from kickoff to go-live, with integrations and data cleansing as the variables that stretch it. The first ninety days after go-live matter as much as the build itself, because that is when habits either form around the platform or around the old spreadsheets.

HubSpot requires an onboarding fee on Professional and Enterprise purchases, which buys vendor guidance on setup. Vendor onboarding is generic by design; a partner-led CRM implementation goes further, covering process design, migration engineering and the integrations the vendor will not build. The step-by-step version of this section, with the first-90-days checklist, is in How to set up HubSpot properly, and the criteria for choosing help are in How to choose a HubSpot partner.

The engineer's verdict

HubSpot earns its market position. The platform's database design is coherent, its APIs are genuinely open, its automation is powerful without demanding a development team for every change, and its teams-actually-use-it advantage is worth more than any feature matrix admits. The boundaries in this guide are real, but they are documented, stable and engineerable, which is the best that can be said of any platform's limits.

HubSpot is the right platform for most mid-market B2B companies, provided you buy it knowing exactly where configuration ends and engineering begins. Businesses that fail on HubSpot almost always failed at implementation and adoption, not at software selection. Buy the tier your process justifies, budget for the gaps that matter to you, give the platform an owner, and HubSpot will repay the investment for years.

Frequently asked questions

What is HubSpot in simple terms?

HubSpot is one piece of software for finding, winning and keeping customers. It stores every contact, company, deal and support ticket in a single shared database, then layers marketing, sales, service, website, data and payment tools on top, so every team works from the same customer record.

Is HubSpot a CRM or something more?

HubSpot is a CRM at its core and a full customer platform around it. The Smart CRM database is free; the six Hubs (Marketing, Sales, Service, Content, Data and Revenue) and the Breeze AI layer are paid products built on that database, sold in Starter, Professional and Enterprise tiers.

What is HubSpot used for?

Businesses use HubSpot to capture and track leads, run email marketing and automation, manage sales pipelines and forecasting, handle customer service tickets, publish their website and landing pages, send quotes and invoices, keep data synchronised across systems, and report on the whole customer journey from one database.

Is HubSpot really free?

Yes, genuinely, at the core. The free CRM supports up to 2 users with contact, company and deal management and basic tools, with no time limit. The features most buyers picture (automation, custom reporting, the full CMS, AI agents) sit in paid tiers, mostly from Professional upwards.

How much does HubSpot cost in the UK?

Checked in July 2026: Starter tiers cost £18/mo per Hub, Sales and Service Professional cost £85/mo per seat, Marketing Professional costs £702/mo, and the all-Hub Customer Platform Professional bundle costs £1,270/mo, all ex VAT on annual billing. Enterprise tiers and onboarding fees sit on top.

What are the six HubSpot Hubs?

Marketing Hub (campaigns and automation), Sales Hub (pipeline and forecasting), Service Hub (help desk and tickets), Content Hub (website and CMS, formerly CMS Hub), Data Hub (sync and data quality, formerly Operations Hub) and Revenue Hub (quotes, invoices and payments, formerly Commerce Hub), all running on the shared Smart CRM.

What is HubSpot Breeze?

Breeze is HubSpot's AI layer: Copilot assistance inside the CRM, packaged agents such as the Customer Agent for support conversations, and data enrichment. Usage is metered in HubSpot Credits, with an allowance included per tier and extra credits priced at £9 per 1,000, checked in July 2026.

Does HubSpot integrate with ERP and finance systems?

Yes, with a caveat. Marketplace apps handle standard-object syncs with common finance tools, while complex requirements (multi-entity accounting, bespoke line-item logic, high volumes) need a custom integration built on HubSpot's APIs and webhooks. The APIs are open and well documented, so almost any system can be connected properly.

Is HubSpot better than Salesforce?

For most mid-market B2B companies, yes: HubSpot delivers faster time to value, better adoption and a lower total cost of ownership. Salesforce wins where deep enterprise customisation, complex org structures and a dedicated admin team are requirements rather than burdens. The honest answer depends on which of those describes you.

Is HubSpot a public company?

Yes. HubSpot was founded in 2006 by Brian Halligan and Dharmesh Shah, is headquartered in Cambridge, Massachusetts, and has traded on the New York Stock Exchange under the ticker HUBS since 2014. It reported 299,458 customers and $3.45bn in annual recurring revenue at Q1 2026.

Do you need a partner to implement HubSpot?

Not always. Small teams on Starter tiers can self-serve with HubSpot's guidance. Professional and Enterprise deployments carry a required vendor onboarding fee, and most benefit from a partner for process design, data migration and integrations, because those are the stages where implementations succeed or fail. Complex builds need engineering either way.

Can HubSpot run your website?

Yes. Content Hub is a full hosted CMS with themes, a blog, landing pages, SEO tooling and membership features, and many businesses run their entire site on it. Standard sites work out of the box; heavily bespoke designs and complex interactive front-ends are a development project on the platform.

Explore the HubSpot guide series

This pillar is the front door to a series of focused guides, each written to the same standard: engineer-authored, honest about trade-offs and checked against current facts.

• How much does HubSpot cost in the UK? The full 2026 pricing guide: every Hub and tier, hidden costs and worked scenarios.
• HubSpot pros and cons: an engineering assessment. The strengths and weaknesses scored, with severity and workarounds.
• Is HubSpot free? What the free CRM really includes and where the paid walls sit.
• HubSpot vs Salesforce. The honest head-to-head, including when Salesforce wins.
• HubSpot vs Microsoft Dynamics 365. The comparison for Microsoft-stack organisations.
• HubSpot alternatives compared honestly. The wider field, assessed by a partner with no reason to flatter it.
• How to set up HubSpot properly. An engineer's first-90-days checklist.
• How to choose a HubSpot partner. The evaluation criteria, including onboarding options.
• When you outgrow HubSpot. The seven signs, and what to build when you hit them.

Going deeper on a specific area? See our complete guide to HubSpot integrations and our guide to training your team on HubSpot.

If you are weighing HubSpot up for your own business, or you run it already and keep hitting the boundaries in this guide, talk to the engineers who work on the platform every day. Request a quote and we will give you a straight answer.