Salesforce and HubSpot Health Check: What Should Be Reviewed Before You Invest More?

When Salesforce and HubSpot start creating friction, the instinct is often to add something.

More licenses. Another managed package. A new integration. More automation. More development.

That can make the problem worse.

Before investing more money into Salesforce or HubSpot, I prefer to step back and understand what is already happening inside the org.

A proper Salesforce and HubSpot health check should answer three questions:

What is working?
What is creating unnecessary cost or complexity?
What should be fixed first?

Here are the areas I normally review.

1. User Adoption and License Usage

I start with the users.

Who is logging in regularly? Who is barely using Salesforce? Which teams rely on it every day, and which users only need occasional or limited access?

This helps identify whether licenses are aligned with actual usage.

I also look at whether people are avoiding Salesforce and using spreadsheets, email, or other tools instead.

Low adoption is often a symptom of poor system design, not just poor training.

2. Data Quality

If the data cannot be trusted, reporting and automation cannot be trusted either.

I review duplicates, incomplete records, stale opportunities, inconsistent field values, ownership issues, and fields that are no longer useful.

I also look at where the bad data is coming from.

Cleaning the data is only half the job. The underlying process needs to stop creating the same problems again.

3. Automation and Flow

Automation tends to accumulate over time.

I review active Flows, legacy automation, validation rules, Apex, assignment logic, and other processes that update records.

The objective is to identify overlapping logic, unnecessary complexity, failure points, and automations that no longer match the current business process.

If nobody understands why a Flow or Automation exists, that is usually a warning sign.

4. Integrations and Managed Packages

Integrations and managed packages can add significant value, but they also add dependency and cost.

I review which applications are connected, what data they exchange, and whether those tools are still required.

I also look at feature utilization.

If a company is paying for a package but only using a small part of it, there may be a simpler or cheaper way to handle the same requirement.

5. Reporting and Forecast Accuracy

One of the clearest signs of a weak Salesforce and HubSpot setup is when leadership does not trust the reports.

I review whether the dashboards reflect how the business actually operates.

That includes pipeline stages, forecast logic, conversion metrics, source attribution, activity reporting, and opportunity management.

If management still needs spreadsheets to understand performance, something is missing in the CRM.

6. Security and Permissions

Permissions often become messy over time.

Users change roles. New profiles or permission sets are created. Access is added temporarily and never removed.

I review who can see and edit critical data, how permissions are structured, and whether access still reflects current responsibilities.

This is both a governance and operational issue.

7. Technical Debt and Documentation

Technical debt is one of the biggest hidden costs in Salesforce and HubSpot.

Duplicate fields, old objects, redundant automation, inconsistent naming, undocumented integrations, and obsolete configurations all make future changes slower and more expensive.

I also review documentation.

If the org depends entirely on what one administrator or consultant remembers, the company has unnecessary operational risk.

8. Cost and Total Ownership

Finally, I look at the commercial side.

That includes licenses, add-ons, managed packages, integrations, storage, sandboxes, and external software connected to Salesforce and HubSpot.

The goal is not simply to reduce the CRM invoice.

It is to understand the total cost of ownership and identify where money is being spent without enough business value.

Fix the Right Problems First

A CRM health check should not produce a long list of technical observations with no priorities.

The outcome should be clear:

• What needs immediate attention

• What can be simplified

• What can be removed

• What should be rebuilt

• What can wait

• Where there are opportunities to reduce cost

Before adding more technology to Salesforce or HubSpot, it makes sense to understand the condition of the environment you already have.

In many cases, the fastest improvement is not adding something new.

It is fixing what is already there.