[object Object]

A marketing team weighs CMS Hub against a WordPress refresh and the conversation gets stuck on theme choice. The real question is whether the website team needs to ship pages without filing a developer ticket, and whether personalization based on CRM data is part of the strategy. CMS Hub is built for both, and its tradeoffs are easier to evaluate when you separate the marketing-platform questions from the publishing-platform questions.

Where CMS Hub fits

CMS Hub is HubSpot’s website publishing platform. Separate SKU from Marketing Hub but with native integration on forms, smart content, analytics, and CRM-driven personalization. Tiers:

Free       - basic site builder, limited pages, HubSpot branding
Starter    - custom domain, blog, basic templates
Professional - dynamic pages, smart content, A/B testing,
               serverless functions, HubDB
Enterprise - memberships, multi-language, multi-domain,
             advanced reporting, sandboxes, content partitioning

Themes and modules

Themes define the site-wide structure: typography, color tokens, default layouts, header and footer. Modules are reusable page components — hero, feature grid, CTA, testimonial slider — that marketers drag into pages without developer help.

Theme: Acme 2026
  Tokens:
    primary: #0B5FFF
    headline_font: Inter 600
    body_font: Inter 400
  Modules:
    hero_split, feature_3col, testimonial_card,
    cta_band, faq_accordion, logo_grid
  Templates:
    landing_page, blog_listing, blog_post,
    product_page, system_page

A well-built theme moves 80 percent of marketing page work out of engineering’s queue.

HubDB for dynamic content

Relational-style tables that back CMS pages. Locations, team bios, product catalogs, knowledge base entries. One template renders any row, dynamic pages live under a parent URL:

{% set rows = hubdb_table_rows(performable_data.table_id, "is_active=true&orderBy=sort") %}
<ul>
  {% for r in rows %}
    <li><a href="/locations/{{ r.slug }}">{{ r.city }}</a></li>
  {% endfor %}
</ul>

Beats spinning up a separate database for content of moderate volume.

Serverless functions

JavaScript functions that run on HubSpot’s platform. Handle form submissions, call external APIs, build features that need server-side logic without a separate hosting platform:

// File: serverless-functions/lookup-stock.functions/lookup-stock.js
exports.main = async ({ params }) => {
  const sku = params.sku;
  const resp = await fetch(`https://stock.example.com/${sku}`);
  const data = await resp.json();
  return {
    statusCode: 200,
    body: { in_stock: data.qty > 0, lead_time_days: data.lead_time }
  };
};

Available on Pro and above. Counts against monthly execution quota.

CRM-driven personalization

The single biggest advantage over WordPress and Webflow: smart content gated on contact properties. A returning customer sees pricing for their plan; an MQL sees the demo CTA; an anonymous visitor sees the entry-level content. No tracking-only pixel pretending to know the user — the CMS reads the actual CRM record:

{% if contact.lifecyclestage == "customer" %}
  {% include "../partials/customer-cta.html" %}
{% else %}
  {% include "../partials/prospect-cta.html" %}
{% endif %}

Comparison to WordPress and Webflow

Strengths:
  - CRM personalization without integration plumbing
  - No plugin sprawl, no security patching
  - Hosting and CDN included
  - Forms and tracking native
  - Single login for marketing operations

Tradeoffs:
  - Smaller theme/template marketplace than WP
  - Higher cost than self-hosted WP for small sites
  - Lock-in to HubSpot platform decisions
  - Custom development uses HubL, not familiar templating

For organizations already running Marketing Hub with serious personalization ambitions, the math usually favors CMS Hub. For marketing-light sites with deep developer customization, WordPress or Webflow can be a better fit.

What to do this week

If you are evaluating CMS Hub, list the three pages your marketing team most often updates and the three pieces of CRM data your homepage should personalize on. The answers determine whether the personalization advantage covers the cost gap versus your current platform.

[object Object]
Share