Layer 1: ICP, tested against reality

Most founders already have an ICP written down. The audit's first job is checking whether it's actually usable, specific enough that you could name twenty real companies matching it today, anchored to a real trigger event (a funding round, a hiring signal, a compliance deadline), not a vague category description. If the current ICP fails that test, it gets rebuilt before anything else in the audit proceeds, because every later layer depends on it being right.

Layer 2: CRM and pipeline discipline

A surprising number of early-stage companies run pipeline entirely out of a founder's memory and a Gmail search. The audit checks whether there's a single source of truth for every prospect's stage, next step, and date of last contact, and whether that record actually gets updated or goes stale within days. If there's no CRM yet, this is where one gets set up, matched to the team's actual technical comfort rather than whatever tool is trendiest.

Layer 3: Message and list quality

This is usually where the real problem lives, even when the founder blamed volume. The audit reviews whatever outbound has already gone out: is the list filtered on a real trigger signal, or just a broad "companies that could theoretically buy this" filter? Does the message lead with a specific, believable offer, or does it ask for a meeting with no proof attached? A message that leads with an offer (a checklist, a short audit, a specific finding) consistently outperforms one that pitches directly, sometimes by a wide margin. This layer gets rewritten, tested in small batches, and measured before volume gets increased.

Layer 4: Cadence and follow-through

Most missed opportunities aren't a bad first message; they're a dropped second or third touch. The audit maps out an actual sequence (how many touches, across which channels, over how many days) and a stop rule, so prospects don't get either abandoned after one email or hounded indefinitely. It also checks the weekly operating rhythm: is outbound happening every week on a schedule, or in bursts followed by silence? Outbound that goes quiet for two weeks shows up as a pipeline gap four to six weeks later, which is long enough that founders often don't connect the two.

What comes out of the audit

A written assessment of where each of the four layers currently stands, a prioritized list of what to fix first (usually ICP and message, rarely the CRM tool itself), and a 90-day plan for implementing the fixes with specific, measurable checkpoints rather than a general "do more outbound" directive.

Score yourself honestly on the four layers and find the lowest one. That's where to start, and it's rarely the CRM, however much it feels like the CRM. If you want a second read on which layer is actually binding, we'll run it with you free.