WEBSITES

A HubSpot site that marketing can manage itself.

A CMS project is not about how many pages go live, but about reusable modules that marketing can deploy without a developer ticket. We build on HubSpot CMS Hub with component architecture, CRM integration and a performance budget built in. Platinum Partner, five years of experience on the platform, and since 2026 also focused on agentic use via Breeze.

Discuss your CMS project Take the Maturity Scan

What's included in the build

01
Theme Tokens, typography, grid, global modules
02
Modules 10 to 25 custom HubL modules
03
Templates Pillar, sub-page, landing, blog, case

The observation

Most HubSpot sites use a fraction of what the platform can do.

Templates only a developer can edit. Modules with too many free fields that trigger brand drift. Forms disconnected from lifecycle, so sales complains about lead quality. And pages that take 5 to 7 seconds to load, while Google wants a green LCP below 2.5s. We do it differently: we build components with restrictions, connect forms to a working CRM architecture and start every build with a performance budget. These are the four patterns we see in almost every HubSpot audit.

Developer-only templates

Every copy change becomes a ticket. Marketing waits two days for a copy correction and therefore simply does not publish. Campaign speed leaks away in the queue.

Modules without restrictions

Free rich-text fields, free colour pickers, free fonts. Within two months three campaign pages diverge and brand consistency is gone.

Forms disconnected from CRM

Form submissions land in a general contacts bucket. Lifecycle and scoring are bolted on afterwards. Sales complains about quality, marketing cannot explain why.

No performance budget

LCP of 4 to 6 seconds, Core Web Vitals in the red. Google ranks lower, AI engines avoid the page as a source and visitors bounce on mobile.

Approach

From architecture to live website in fixed sprints.

A structured build with development discipline. Module architecture, code review, performance budget and QA before we push to production. Eight weeks for an average scope, with a demo at the end of every sprint, embedded in our HubSpot Platinum approach.

01 Wk 1

Architecture

Module inventory, theme tokens, mapping from Figma to HubL components. Performance budget and QA checklist locked down before the build starts.

02 Wk 2-4

Theme & modules

Custom HubL modules with the right fields and restrictions. Drag-and-drop where possible, fixed structure where required. No free rein on colour or typography.

03 Wk 5-6

Templates & pages

Page templates assembled from modules. First pages live in a sandbox environment, with test data from your HubSpot portal for smart content validation.

04 Wk 7

CRM & forms

Forms connected to lifecycle, scoring, workflows and sales routing. Progressive profiling and smart fields enabled so a returning contact does not have to fill everything in again.

05 Wk 8

QA & launch

Cross-browser, mobile, performance audit (LCP below 2.5s, CLS below 0.1), 301 redirect plan for SEO and go-live with monitoring enabled.

Who helps you

Three specialists on your build.

Design, content and CMS architecture in one team. The development work goes live with the right hand-off to marketing.

For the design side, see also web design and branding.

Carsten Huiskamp

CMS Architect (lead)

Owns module architecture, theme development and CRM integration. Builds forms, lifecycle connections and the tracking layer between CMS and CRM. Five years of HubSpot experience, knows which quirks need to be planned for in advance.
Sander Adriaanse

Designer

Delivers design tokens, page templates and the Figma library. Works alongside the developer so the design lands 1-to-1 in HubL, without a section having to be redrawn halfway through.
Dante Zwanenburg

Content & development support

Contributes to modules and delivers copy and micro-content per template. Ensures pages go live with real text and CTAs, not Lorem Ipsum that still needs to be replaced later.

Case · B2B mid-market

From developer-only templates to marketing that publishes itself

A B2B organisation with a WordPress site from 2019 was stuck: every page change was a developer ticket, mobile LCP above 5 seconds, and forms landed in a general contacts bucket without lifecycle. Marketing did not publish new campaigns for weeks because the queue was full.

In eight weeks we delivered a new HubSpot CMS build: 14 custom HubL modules with restrictions, lifecycle in HubSpot live, performance audit green, connected to performance and SEO work. Three months after launch, marketing publishes an average of 2 new pages per week without a developer ticket. Organic pipeline contribution increased by 35%.

What clients usually ask.

The questions that come up before a CMS development project starts.

Do you only build in HubSpot CMS?

Primarily yes. We are a HubSpot Platinum Partner and the advantage of CMS plus CRM on one platform is significant for B2B, especially now that Breeze agents run on the same data. For clients with WordPress we do migrations to HubSpot, or we build landing pages in HubSpot while the main site still runs on WordPress.

How long does a CMS development project take?

Eight weeks for an average scope: one ICP, one language, ten to fifteen templates. Multi-language or integrations with additional tools add four to eight weeks. We work in fixed two-week sprints: 1 sprint architecture, 3 sprints build, 1 sprint QA and launch.

What does a HubSpot CMS build cost?

Our services are custom. The price depends on the number of templates, languages, integrations and whether we also deliver design and content. Many clients choose a RevOps-as-a-Service retainer in which the build continues into optimisation and CRO. Schedule a call and we will put together a quote for your scope.

Can marketers build pages themselves afterwards?

Yes, that is the whole point. Our modules have the right fields and restrictions, so marketing can publish new pages and campaigns without a developer ticket. No free rich-text fields that break the design, but enough freedom to iterate on copy and visual variation.

Do you also do migrations from WordPress to HubSpot?

Yes. Content migration via HubSpot import templates, a 301 redirect plan for SEO preservation, and a rebuild of the site on a new HubSpot theme. An average migration takes six to ten weeks including content review and URL mapping. See also our websites offering.

Do I own the code?

Yes. The theme and all custom modules go into your HubSpot portal. No vendor lock-in, no monthly licence fees to us. Optionally a maintenance retainer for ongoing development and support.

How do you account for AI agents and Breeze?

HubSpot has been an agentic customer platform since 2026. Breeze agents run on contacts, content and page structure. We build forms, lifecycle and structured data so that agents can work with them effectively. A well-built CMS directly improves the quality of agent actions.

How do we know whether we need a rebuild or a refactor?

Three checks. Can marketing publish new pages now without a developer ticket. Do your key templates load in under 2.5 seconds on mobile. Does your form data connect cleanly to lifecycle and deals. Two or more no answers usually means there is too much backlog to continue with isolated fixes. The maturity scan gives an initial indication.

Ready to get started?

Ready for a HubSpot build that still works two years from now?

Schedule a call. We look at your current portal, your design foundation and which modules you actually need. No sales pitch, just an honest scope. Sometimes the honest conclusion is that a refactor is enough.

Schedule a CMS call Take the Maturity Scan