Resources · Checklist · Free, no email · Updated

CRM HYGIENE SPOT-CHECK

Wrong titles, zombie lists and duplicate contacts do not wait for an operations project. Run a guided check in HubSpot, Salesforce or both, mark what fails, and leave with a fix list sized for this week and a cadence for the months after.

How it works

  1. Choose the platform you are checking today.
  2. Say why you are running it, so the order suits the reason.
  3. Work through the checks in your own CRM and mark each one.
  4. Fix the failures that block this week, put the not-sure items on an ask list, and keep the monthly cadence.

Run your CRM hygiene spot-check

What are you checking today?
Why are you running this?

It changes the order and the note at the top. Every check stays available.

Nothing you enter here leaves your browser. Close the page and it is gone.

Your spot-check list will appear here.

Fix the failures that block this week first. Put the not-sure items in one message to whoever owns the CRM rather than sending them one at a time. If the real problem turns out to be which tools hold what, the MarTech stack audit is the wider job.

A hygiene aid, not CRM, legal or privacy advice. Field names and navigation differ between organisations, so confirm in your own instance. Nothing you enter is sent anywhere or stored.

Goes well with

Worksheet
The MarTech stack audit worksheet

You are probably paying for software nobody logs into.

Get the worksheet

If you would rather have this done with you than to you, this is the work I do. See services

Run it before the send, not after

Most of these checks take minutes and every one of them is cheaper before a campaign than after it. A bounce rate found on Thursday morning is a suppression list. The same bounce rate found on Friday afternoon is a deliverability problem that follows you into next quarter. The checks are written so a marketer can run them from their own seat, with the ones that need administrator rights marked as asks rather than left out.

Dirty data is rarely a data problem

Duplicates usually come from a form, an import or a sync that nobody owns. Empty fields usually come from a capture path that was never revisited. Fixing the records without fixing the source buys about a month. That is why each failure comes with an owner and a next step rather than a count, and why the monthly cadence matters more than the first run. If the underlying question is which tools hold what and who owns them, the stack audit is the wider inventory.

COMMON QUESTIONS

Is this a RevOps data audit?

No. It is a marketer-facing spot-check. It does not inventory objects, automations or integrations, and it does not need administrator access for most of the checks.

Does it connect to HubSpot or Salesforce?

No. You run the checks in your own interface and mark the result. Nothing connects and nothing is stored.

Do I need admin rights?

Not for most of it. Where a check needs rights you do not have, mark it not sure and it appears on an ask list worded for a ticket.

How often should I run it?

Before any significant send, and once a month otherwise. The monthly version is short and it is the one that stops the crisis version being needed.