HubSpot's 2026 layoffs and restructuring: what website teams should know

HubSpot is cutting about 7% of its workforce, nearly 660 roles, and reorganising its product teams around customer outcomes instead of its Hubs. Chief executive Yamini Rangan announced the plan to employees on 6 October 2026, and HubSpot published her memo the same day.

For a business that runs its website on HubSpot, the question is what this changes about the platform. The memo does not mention Content Hub, HubSpot’s website product, or set out changes to its packaging, prices or support. It describes a new structure for the teams that build HubSpot’s software.

What HubSpot announced

The cut is roughly one in fourteen HubSpot employees, the same proportion as the reduction HubSpot made in January 2023. The board authorised the plan on 1 October, according to the Form 8-K HubSpot filed with the US Securities and Exchange Commission, and the company expects the role eliminations to be substantially complete by the end of March 2027, subject to local law and consultation requirements.

Product teams will be organised around four outcomes, which the memo names as generating demand, winning deals, delighting customers and scaling growth, “with each team owning the full customer journey and clear accountability for the outcome.” HubSpot will also reduce management layers and, in the memo’s words, “reduce fragmented ownership.”

Rangan ties the change to a strategy shift over the past year, from building software that helps customers grow to “delivering outcomes for them with AI.” She writes that the decision is “not driven by AI-related efficiencies” and is “not simply a cost-cutting exercise.” In the same 8-K, HubSpot reaffirmed its financial guidance for the third quarter and for the full year 2026.

What website owners know, and what to ask

The teams that build HubSpot’s products are being reorganised, so the owner of a feature your site relies on may change. HubSpot says its AI strategy “is transforming product, pricing and how we serve our customers,” which leaves the packaging of Content Hub as a question for your account team. HubSpot has not said which functions or regions carry most of the cuts, CMSWire reported on 6 October.

A reorganisation inside HubSpot does not amend your subscription. HubSpot’s published customer terms say that changes to the service during your current term will not materially degrade its overall functionality, with exceptions that include free and beta services and changes outside HubSpot’s control. Fees do not rise during the current term except for overages, upgrades, add-ons and anything your order form provides. At renewal, HubSpot can raise them up to its then-current list price with at least 30 days’ notice.

The same terms state that HubSpot’s obligations do not depend on future features or on anything it says about them, so a roadmap answer is planning information, and a commitment you need belongs in your order form. Where an order form and the published terms conflict, the order form controls for that order.

Ask your HubSpot account team, ahead of renewal:

• Which team will own the features your site depends on, such as pages, blogs, forms, memberships and HubDB (HubSpot’s database tables for structured content), and who your contact will be.
• Whether any of those features is in beta, since beta services sit outside the protection above.
• What support your seats carry, and whether it changes at renewal. HubSpot’s product terms give users with paid seats on Professional and Enterprise tiers phone and in-app support; paid Starter seats can select in-app options.
• What your renewal will include: price, packaging, and the seat or credit model.
• Whether any API your integrations call is due to change. HubSpot records these in its developer changelog.

Three ways to arrange a website and a CRM

A website and a CRM are separate decisions, even when one vendor supplies both, so a team can review its website without reopening its CRM and marketing automation.

Arrangement	Best fit	What stays connected	What you take responsibility for
Website and CRM both in HubSpot	Content Hub, at your plan level, meets your editing, governance and integration needs	Pages, forms, contact records, page analytics and smart content work together with no integration code	Plan limits and upgrades, templates in HubL (HubSpot’s template language), and renewal terms set from HubSpot’s list price
HubSpot for CRM and marketing, a separate CMS for the website	The website needs its own content model, release process or engineering control, and marketing wants to keep HubSpot	Contacts, email, automation and reporting stay in HubSpot; the site feeds them through HubSpot forms or the Forms API and the tracking code	The integration: form submissions and their failures, the workflows they are meant to trigger, consent, attribution, data that has to sync both ways, and the features that run only on HubSpot pages
Replace a wider part of the stack	Documented functional, contractual or cost requirements reach beyond the website	Only the systems you keep, and each link to them is rebuilt	Moving customer data, workflows, emails and reports, training staff, and running both systems through cutover

Keeping both in HubSpot means no integration between the website and the CRM to build or maintain. If a constraint is pushing you to look elsewhere, check whether it belongs to the platform or to your plan. HubSpot’s product catalog lists content approvals, multisites, activity logging and custom permission sets as Content Hub Enterprise features, so an upgrade belongs in the comparison.

A separate CMS gives the website its own content model and release process while marketing keeps working in HubSpot. HubSpot’s forms work on external sites on all plans and sync submissions to the CRM, and custom-built forms can submit through the Forms API. The tracking code, HubSpot’s analytics script, has to be installed by hand on external pages to capture analytics. The consent banner works on pages that carry it. Smart forms and smart modules, which show different content to different visitors, work only on HubSpot pages, and memberships restrict access to HubSpot-hosted pages.

Payload is one CMS that fits this arrangement. WAYF is an official Payload partner, and its comparison of HubSpot CMS and Payload sets out the differences feature by feature. For a smaller marketing site kept as files in Git, the Decap CMS and HubSpot comparison sets HubSpot’s plan prices against the build and hosting work Decap needs.

Replacing the CRM and marketing automation as well turns a website project into a programme, and it needs a business case that would stand without the website. The three arrangements differ in cost, and each carries ongoing maintenance.

A review checklist

Run these six checks before your next renewal, whichever way you are leaning.

Check	Evidence to collect	Decision it informs
What the website takes from HubSpot	Pages, blogs, forms, landing pages, smart content, memberships, HubDB tables, and the CRM properties and workflows that forms feed	What each arrangement keeps working, and what a separate CMS would have to rebuild
The constraint, if there is one	A written example: the approval that happened by email, the locale you could not add, the release that waited. A feature another CMS offers counts only if you have needed it	Whether it is a plan tier, a configuration gap or a platform limit
Business-critical integrations	Each integration, its owner, and what happens when it fails	Whether integration risk shapes the arrangement, and who owns each fix
Contract and portability	Renewal date, auto-renewal setting, order form terms, and a test export of pages, files, URL redirects and CRM records	When a decision is due, and whether your data leaves complete
Consent, analytics and attribution	Your consent banner settings, the pages that carry the tracking code, and the attribution reports leadership reads	What has to be rebuilt for those reports to stay correct after a change
Move readiness, if you are considering one	A URL inventory and redirect map, a data validation plan, a cutover date and a rollback route	Whether a move is ready to schedule

Stay when your plan meets every constraint the checklist finds, every critical integration has an owner, and the renewal terms work for you.

Investigate when a constraint exists that a plan tier or configuration might solve, when your renewal terms change materially, or when a critical integration has no owner. Price the fix inside HubSpot against a separate CMS. WAYF’s renewal checklist covers the negotiation.

Plan a change when a documented constraint cannot be met in HubSpot at an acceptable cost, and the case reads the same with the restructuring left out. Start with the URL inventory and the export. The pre-migration checklist lists what to prepare, and the guide to CMS migration tools covers checking redirects and content before cutover.

WAYF’s view

A restructuring is a fair reason to run this review. The decision comes from what the review finds: the constraints, the integrations and the contract. WAYF assesses and builds content platforms, including setups that keep HubSpot as the CRM and move only the website. Even a review that ends in staying leaves the team with an inventory of its dependencies and an export it has tested.

Run that export during your current term. HubSpot’s product terms give no access to your data once a Content Hub subscription has ended.

Verified on 8 October 2026 against the documents listed below.

Sources

• HubSpot, A message from our CEO: Important HubSpot team and business changes (6 October 2026)
• HubSpot, Form 8-K filed 6 October 2026 — plan authorised 1 October 2026, role eliminations expected to be substantially complete by the end of the first quarter of 2027, guidance reaffirmed
• HubSpot, Form 8-K filed 31 January 2023 — the January 2023 reduction of approximately 7%
• CMSWire, HubSpot Lays off 7% of Staff, Moves Away From Hub-Based Product Teams (6 October 2026)
• HubSpot, Customer Terms of Service (last modified 16 September 2026) — sections 2.6, 3.1, 3.2 and 12.8, and the order-of-precedence clause
• HubSpot, Product Specific Terms (last modified 16 September 2026) — retrieval of customer data (5.1.1) and customer support (10)
• HubSpot, Product & Services Catalog — Content Hub features by plan
• HubSpot Knowledge Base, Style and embed HubSpot forms on an external site
• HubSpot Knowledge Base, Install the HubSpot tracking code
• HubSpot Knowledge Base, Set up cookie tracking settings and consent banners
• HubSpot Knowledge Base, Smart content frequently asked questions
• HubSpot Knowledge Base, Export your content and data
• HubSpot, Developer changelog