HubSpot's New Theme Creates a New RevOps Documentation Problem

 HubSpot changing its interface might seem like a cosmetic update. 

It isn't.

For RevOps teams, one of the most overlooked consequences of a major HubSpot UI change is what happens to all of the documentation you've already created.

Your internal SOPs.

Your onboarding guides.

Your Loom videos.

Your training documents.

Your implementation documentation.

Your partner documentation.

Your "How to do this in HubSpot" articles.

And eventually, your institutional knowledge.

HubSpot's new theme changes the overall appearance and navigation experience of the platform. HubSpot's own documentation has already been updated to reflect the new experience, including instructions that reference the new navigation and account interface.

That creates a problem for businesses that have spent years documenting how their teams use HubSpot.

The Problem Isn't That Your Documentation Is Wrong

This distinction matters.

Your process might still be completely correct.

The problem is that the instructions used to execute that process may no longer match what users see.

Imagine your internal SOP says:

"Go to Settings, select X, then click Y."

Your process is still correct.

But the employee opens HubSpot and doesn't see X or Y where your documentation says they should be.

Now you have a training problem.

Then a support problem.

Then an adoption problem.

And eventually someone opens a ticket with RevOps because "HubSpot isn't working."

Except HubSpot is working.

Your documentation is outdated.

This Is Bigger Than the New Theme

This is something I think RevOps teams need to start treating as a normal part of CRM governance.

HubSpot is changing quickly.

New features are being released constantly. Navigation changes. Existing tools get redesigned. Features move. New AI capabilities are added. Old functionality gets replaced.

That means documentation has a shelf life.

And the shelf life is getting shorter.

HubSpot's own Knowledge Base illustrates this pretty well. There are currently separate articles for newer knowledge base functionality and legacy knowledge base functionality, while HubSpot has also introduced migration processes between the experiences.

That's not necessarily a bad thing.

It's what happens when software evolves.

But businesses need to account for it.

Your Internal Documentation Is Now a RevOps Asset

I don't think documentation should be treated as something you create during implementation and forget about.

It should be treated like your workflows, properties, integrations, and reporting architecture.

It needs an owner.

It needs version control.

It needs periodic review.

And it needs to be connected to the actual processes your business uses.

If your RevOps team has a 40-page HubSpot SOP that hasn't been touched since 2024, there's a pretty good chance at least some of it is no longer accurate.

The new theme is simply making the problem much more obvious.

Don't Just Update Screenshots

This is where I think teams can make another mistake.

You don't want to simply replace screenshots.

You want to validate the process.

If an SOP says:

"Navigate to X > Y > Z."

Don't just confirm that the buttons look different.

Ask whether X > Y > Z is still the best way to accomplish the business objective.

HubSpot may have changed the navigation because the underlying product has changed.

There may now be a better way to accomplish the same task.

This is particularly important with processes involving workflows, automation, reporting, data management, permissions, and integrations.

Updating the screenshot without reviewing the process is just putting a fresh coat of paint on potentially outdated documentation.

This Is Where Breeze Could Become Extremely Useful

One of the more interesting opportunities here is using HubSpot's AI capabilities to help identify documentation that needs to be reviewed.

HubSpot already allows Breeze to generate and refine knowledge base content, including improving existing articles for clarity, tone, and readability.

The next logical step for RevOps is using AI to help identify where documentation conflicts with the current portal experience.

Imagine being able to ask:

"Find our documentation that references the old navigation."

"Which SOPs mention workflows being located under this menu?"

"Find documentation that references legacy knowledge base functionality."

"Which internal articles mention properties that no longer exist?"

"Find every SOP that references this workflow."

That's where AI becomes genuinely useful for RevOps.

Not writing another generic article.

Finding the 47 existing articles you forgot about.

Your Knowledge Base Isn't the Only Thing That Needs Reviewing

I'd create a documentation inventory before making any major HubSpot changes.

I'd look at:

Internal SOPs

Employee onboarding documentation

Sales playbooks

Customer service procedures

Marketing process documentation

RevOps runbooks

Partner documentation

Training videos

Loom recordings

Internal wiki pages

External help articles

Knowledge base articles

Implementation documentation

Anything that tells someone where to click in HubSpot should be considered a candidate for review.

Especially if the documentation contains screenshots.

Screenshots are often the first thing that tells you a document is outdated.

But they're not necessarily the only thing.

The Bigger RevOps Lesson

This is actually a good reminder of something that gets overlooked in CRM implementations.

Your HubSpot portal isn't the only system you have to maintain.

You also have the system of knowledge surrounding the portal.

If your CRM changes but your documentation doesn't, you've created a disconnect between the system and the people operating it.

That's technical debt.

And it behaves a lot like technical debt in your CRM.

It compounds.

A small outdated instruction isn't a big deal.

Twenty outdated instructions create confusion.

A hundred create operational friction.

Eventually, nobody knows which documentation is correct, so everyone starts asking RevOps.

Now your RevOps team has become the documentation search engine.

That's not scalable.

What I'd Do Right Now

If you're moving to HubSpot's new experience, don't try to update every document at once.

Start with your highest-impact processes.

Review the documentation associated with lead routing, lifecycle management, deal creation, pipeline management, reporting, customer onboarding, support processes, and anything your sales or service teams use every day.

Then identify the documents that are purely instructional versus the documents that contain actual business logic.

Prioritize the latter.

A screenshot being wrong is annoying.

A documented routing rule being wrong can create a revenue problem.

That's the distinction I'd make.

HubSpot Is Going to Keep Changing

And that's a good thing.

A CRM that never changes would probably be a much bigger problem.

But as HubSpot continues to evolve, RevOps teams need to stop thinking about documentation as a one-time implementation deliverable.

It needs to become part of ongoing CRM governance.

Because the question isn't:

"Is our documentation accurate today?"

It's:

"What happens to our documentation the next time HubSpot changes?"

If you don't have an answer for that, the new theme isn't really the problem.

It's just the thing that exposed it.