The audit we run before recommending any new tool

When a prospect asks us whether they should buy a new tool, the honest answer most of the time is “not yet, and possibly not at all.” That answer is not going to land unless we can show our work, so before we recommend anything we run the same short audit on what the team already owns. The audit takes about a week of calendar time and somewhere between six and twelve hours of our time. It pays for itself before the next renewal in roughly four engagements out of five.

I am writing it down here because the audit is not proprietary. Any senior marketing operator can run it on their own stack, and most of them will be better off doing that than reading another category report.

What the audit covers

We look at four things, in order, and we do not move on from one until we are satisfied with the read on it.

The first is utilization. What percentage of the licensed seats on the existing platforms are being used in a given month, and which features inside the platform are being touched at all. In most stacks we audit, somewhere between forty and seventy percent of paid capability is dormant. A team that is paying for a marketing automation platform with workflow, lead scoring, deliverability tooling, and a reporting layer, but is using only the workflow engine, does not need a new tool. They need to turn on the rest of the one they have.

The second is data quality. We pull a sample of the contact records, the company records, the activity logs, and the segment definitions, and we look at how many of them are coherent with each other. Field naming, field population rates, duplicate rates, definitional drift on what a “lead” is between the CRM and the marketing platform. The point is not to produce a report card. The point is to find out whether the data underneath the next purchase is going to make the next purchase work.

The third is process. Who, on the current team, is responsible for which decisions. Who reviews a workflow before it goes live. Who owns the segmentation logic. Who owns the unsubscribe list. Who answers a deliverability complaint at 4pm on a Friday. If the answer to two or more of these is “nobody specifically,” the new tool is going to be operated the same way, which is to say poorly.

The fourth is the actual problem. We ask the team to describe, in their own words, the failure they are trying to fix with the purchase. We ask twice. The first answer is usually a category name (“we need a CDP”). The second answer, after a follow‑up, is usually a specific operational pain (“our event registrations are not getting into the CRM in time for the SDR follow‑up”). The second answer is the one we actually work with.

What the audit usually finds

Three patterns recur often enough that I want to flag them here.

The first pattern is that the team has the capability already and does not know it. The platform shipped a feature in a release nobody read carefully, the feature is included in the current tier, and turning it on is a configuration change. We see this most often with native lead scoring, native attribution, and the deliverability tooling inside the major MAPs.

The second pattern is that the team has the capability and the data underneath it is too inconsistent for the capability to work. Buying a second tool will not help. The new tool will read the same inconsistent data and produce the same inconsistent output, plus an additional integration to maintain. The right move is to spend the budget on cleanup, not on capacity.

The third pattern is that the capability is genuinely missing and the purchase is justified, but the purchase the team was about to make was the wrong size. They were looking at the platform their largest competitor uses, when their actual volume is a tenth of that competitor’s and the right tool is two tiers down at a third of the price.

What the audit does not do

It does not generate a tool recommendation report with vendor logos and a scoring matrix. There are firms that produce that document, and the document has a place, but it is downstream of the work above. Producing the matrix before the audit gets the order wrong, and the matrix becomes the artifact the team defends rather than the one they use.

It also does not produce a multi‑year roadmap. We have learned the hard way that roadmaps written before the cleanup is done get rewritten three months in. The audit produces a sequenced list of what to do in the next ninety days. Anything beyond ninety days is a guess, and we mark it as such.

Why we do this for free on the first call

We run a stripped‑down version of this audit on the first call with a prospect at no charge, because the alternative is selling work that does not need to be done. We would rather lose the engagement on call one than lose the renewal on month thirteen. (Discipline is the product, and that includes the discipline of telling a prospect they do not need us yet.)

If you want a quick read on whether your current stack is being run at the capability you are paying for, we are reachable. The first conversation is short and almost always saves money before it costs any.