Your marketing team picked HubSpot. Here's what that decides about the website.

A contact database first, with everything else built on it

A CRM, customer relationship management, is one shared list of the people and companies you deal with, with the history attached. What they downloaded, who called them, what they bought, whether they agreed to be emailed. Before a business has one, that history sits in four inboxes and a spreadsheet somebody keeps privately. The value isn't the software, it's that there's a single answer to who this person is.

HubSpot is that list, with tools sold around it. Marketing, sales, service and content are packaged and priced separately, and all of them read and write the same records underneath. The contact database itself has a free tier, which is how most companies end up here. The website builder is one of those packages, which is the sentence that explains most of what follows.

It was built to answer one question about a visitor

HubSpot started in 2006 around an argument about how buying had changed. People research on their own long before they talk to anyone in sales, so marketing's job is to be found rather than to interrupt.

Marketing ran an email tool, a landing page tool, a forms tool and an analytics tool, while sales ran a CRM none of them touched. Nobody could connect the page somebody read in October to the deal that closed in March.

So everything here resolves to a person. A form submission creates or updates a contact, and a tracking script attaches that person's browsing to their record, including the visits from before you knew their name. The CMS exists for that reason rather than because HubSpot set out to be a web platform.

The argument for keeping the site and the records together

The argument is mostly about plumbing that then doesn't have to exist. A form on a HubSpot page lands on a contact record with nothing in between. No integration, no queue, nothing to fail quietly at two in the morning.

The second is that a page can read the record. A known customer sees something a stranger doesn't, and a form skips the fields it already has, with nobody building anything to make that happen.

The third is pace for people who aren't developers. A marketing lead builds a landing page, puts a form on it, and has the follow-up running that afternoon. If the site changes twice a year instead, most of the reason to host it here goes with it.

Where the website half stops

Judged as a content system rather than as part of a CRM, HubSpot's CMS is capable and less flexible than a tool built only for that job.

Templates are written in HubSpot's own templating language, HubL, so the people who can work on your site are people who have worked on HubSpot before. That pool is smaller than WordPress or Webflow's, and outside a large city smaller again. It's the practical ceiling more often than a missing feature is.

Structured content is the other one. Pages, posts and landing pages are comfortable. A catalogue with its own fields, entries that relate to each other and four ways of listing them works against the grain of a tool organised around one record type that happens to be a person. HubDB, the table feature, is thinner than a dedicated content system's.

Then there's anything that behaves like an application: customer accounts, records belonging to one person and not another, a calculation the site runs and keeps. Content can be put behind a login, and gating content is not an account model.

That doesn't make it the wrong answer. It makes the website half the part worth testing against your requirements, because the CRM half rarely fails that test.

The bill tracks a number your own marketing increases

Most software is priced per seat, so the bill moves when you hire. The marketing side of HubSpot is priced by how many contacts you market to, so it moves when marketing does its job. That's the price following the value rather than a trick.

Run a good campaign, import a list, come back from a conference with badge scans, and the number the invoice is worked out from goes up. It moves in blocks, so it arrives as a step nobody planned.

There's a control, and it's the most useful thing to know here. A contact can be marked as one you don't market to, which keeps them available to sales while taking them out of that part of the bill. List housekeeping is real work with a number on it.

Seats are priced on top, and the tiers gate features rather than volume, so the upgrade that eventually gets triggered is a capability nobody costed. Published pricing changes, so check it the day you decide.

Who has to own the contact database

Week to week, almost nothing here needs a developer. Pages, emails, forms, workflows and reports get built by marketing people in an editor, which is the point of the product. A developer appears for template work at the start and rarely after.

What it needs instead is one person who owns the contact database as an asset. Someone who decides what a lifecycle stage means and holds that definition, stops the property list growing three fields that mean the same thing, and does the housekeeping the bill depends on.

They don't have to be full time or technical. They do have to exist and be named. Without them the workflows pile up, two reports disagree, and you pay for contacts nobody has emailed in years.

Settle that before you settle the website question. A business with nobody in that role ends up running a CRM as an expensive mailing list.