Notes · CRM and ESP audits

What a CRM and ESP audit actually covers

An audit is a close look at how your email platform, your customer data, and your lifecycle journeys work together. Mostly it's about finding where things are stuck.

This is what I look at, in the order I usually go.

The platform

How it's set up, what's connected to it, and what's been bolted on over time. Most platforms collect leftovers. Old lists, old templates, fields nobody uses anymore.

None of that is a crisis on its own. It does slow a team down, and it makes every new build harder than it should be.

The data

What customer data reaches the platform, how fast it gets there, and whether it's right. A trigger is only as good as the event behind it.

If purchase data shows up a day late, a post-purchase message shows up a day late too. If a field means two different things in two different places, segments drift. I trace the important events from source to send.

The journeys

I map every live flow. What starts it, who's in it, what it says, and when it stops.

That map usually turns up overlap, gaps, and a few flows nobody remembers building. It also shows where one customer could get three messages in a day from three different programs.

Deliverability

Sending reputation, authentication, list hygiene, and inbox placement. If mail isn't landing, nothing else in the audit matters much, so I check this early.

Flows that aren't performing

Some flows run fine and still don't do much. I look at what each one is supposed to do and whether it's doing it. Then I look at why, whether it's timing, targeting, the message, or the data underneath.

What you get

A plain list of bottlenecks and gaps, ranked by effort and payoff, with what I'd fix first. Some fixes are quick. Some need engineering time. I'll say which is which.

If you want help with AI marketing, CRM, or lifecycle, text (508) 322-1436 or email drew@drewpion.com.