What a real revenue systems diagnostic actually looks like

Why diagnosis has to come before everything else

There is a reason the most sophisticated buyers in the world insist on a diagnostic before any engagement begins: pure efficiency.

Every dollar spent on execution before you understand the system is a bet. Sometimes it pays off. Usually it doesn't. And when it doesn't, you've lost not just the money but the time — months of activity running against broken infrastructure, producing data that can't be trusted, generating leads that fall into gaps nobody knew existed.

The diagnostic eliminates the bet. It replaces assumption with evidence. It tells you, specifically, where money is going and where it's leaking, before you spend another dollar.

The businesses that skip this step — the ones that hire agencies and say "just start running" — are the ones I hear from two years later. They've spent $150,000. They can't explain what it produced. Leads came in and nobody can tell you where they went or why they didn't close.

That's a revenue operations failure. No amount of new creative or additional spend fixes an operations problem.

The businesses that start with a proper diagnostic spend less, produce more, and can actually explain their results. Because they understood the system before they started spending on it.

What "rigorous" actually means

Rigorous means knowing what matters. An eager intern reads every document, builds the comprehensive spreadsheet, checks every box. That kind of thoroughness produces noise.

When you have run dozens of these engagements, you stop looking at everything. You know which signals are symptoms and which signals are root causes. You know that a low email open rate is almost never the real problem. You know that a high click-through rate on paid ads combined with poor lead quality means the problem is in the audience build. You know that a CRM with low utilization almost always means the handoff from demand generation to sales is broken.

That experience is what you're paying for when you hire a senior diagnostician. It is what makes the difference between a 40-page audit that tells you nothing actionable and a 10-page report that changes how you run the business.

The Diagnostic I run is built on 20 years of that experience, across journalism, technology, development, and growth strategy, inside businesses ranging from early-stage to nine figures. The timeline — one to three weeks, depending on complexity — is set by the rigor required to see the system clearly, not by a standard process applied uniformly to every business.

Can you actually see what's happening?

What I'm assessing: Whether your data infrastructure can connect investment to outcome — and whether any decision-maker in your business can trust the numbers they're looking at.

This is the foundation. Everything else in the Diagnostic depends on it. If the data layer is broken — if you can't trust the numbers — then every decision about where to invest, what to cut, and what to build is a guess wearing a spreadsheet.

What I look at:

• GA4 configuration. Most businesses have GA4 installed. Very few have it configured correctly. I check whether conversion events are firing accurately, the data stream is clean, and cross-domain tracking is in place. A misconfigured GA4 doesn't tell you things aren't working — it tells you nothing at all, which is worse.
• Attribution model. Last-click attribution systematically undercredits awareness and nurture activity. If budget decisions are being made on last-click data, you're almost certainly underspending on what works and overspending on what doesn't.
• Conversion definition. What counts as a conversion? A page view, a form submission, a qualified lead, a booked call, a closed sale? The definition is the most important variable in your analytics and it's frequently wrong.
• UTM architecture. UTMs are the connective tissue between campaign activity and downstream outcomes. An inconsistent or missing UTM structure means campaign data and analytics data can't talk to each other.
• Pixel and tracking health. A broken or misconfigured pixel means retargeting campaigns run against audiences that don't exist, conversion signals aren't firing, and the platforms can't learn.
• Reporting infrastructure. What does the business actually look at to make decisions? The quality of reporting infrastructure tells you immediately how decisions are made — and whether they're based on real signal.

Where is new revenue coming from?

What I'm assessing: Whether the systems generating new demand are structured to produce repeatable, measurable, connected results — or running in isolation from everything else.

Demand generation is where most founders increase investment when growth stalls. More spend. New creative. Different platform. It rarely produces a different outcome — demand generation can only perform as well as the system it feeds into. If the intelligence layer is broken, the targeting is wrong, or the pipeline can't process what comes in, more spend makes the problem more expensive.

What I look at:

• Account architecture. Is there a logical campaign structure, or has the account grown over time into overlapping campaigns, duplicated audiences, and inconsistent naming? Account structure determines how much signal a platform's algorithm can extract from spend.
• Audience infrastructure. Are first-party audiences in play — customer lists, website visitors, CRM exports — or is the business relying entirely on platform-defined interest categories? First-party audiences consistently outperform interest audiences. Most businesses underutilize them because nobody set up the infrastructure.
• Creative system. Is there a systematic testing process, one variable at a time, with enough budget and time to reach significance — or is creative being produced by feel? Most businesses have no creative system. They have creative.
• Spend allocation against funnel shape. Where is the budget going, and does the allocation reflect how buyers actually move toward a decision? A business spending 90% on conversion objectives will run out of retargeting pool.
• True ROAS. Not reported ROAS — actual ROAS, accounting for attribution methodology and the validity of the data feeding it. I look at historical performance by campaign type, platform, audience, and creative.
• Platform mix. Is the business on the right platforms for its audience and offer? Businesses frequently end up on platforms because an agency had expertise there, not because the audience justified it.

What happens when the right person finds you?

What I'm assessing: Whether the surfaces where prospects land are actually built to convert them, or leaking demand the business paid to generate.

Most business websites are built as brochures. They describe what the business does. They look professional. They have a contact form somewhere. And they convert a trickle of the traffic they receive — wildly disproportionate to the investment that drove that traffic there.

What I look at:

• Conversion readiness by page. For each page receiving significant traffic: what is this page supposed to make the visitor do, and is it designed to do that? Most high-traffic pages describe but don't direct.
• Lead capture architecture. Where and how is the site capturing contact information? Are there intermediate capture mechanisms for visitors not ready for the primary CTA? Is every form connected to the CRM, or are submissions landing in an inbox and being manually processed?
• Landing page efficiency. I look at load time, message match between ad and landing page, offer clarity, trust signal placement, and CTA design. A weak landing page can cut the effective ROAS of a well-structured paid campaign in half.
• User path from discovery to action. How many clicks, how much scrolling, how much trust has to be established before the ask? Mapped from the perspective of a first-time visitor with no prior knowledge of the business.
• Trust architecture. Case studies with specific outcomes, testimonials that speak to the buyer's situation, credentials, methodology — these build trust and their placement matters as much as their presence.
• Technical conversion factors. Page speed, mobile performance, Core Web Vitals — these are conversion metrics, not just SEO metrics. A slow-loading page loses a measurable percentage of visitors before they ever see the offer.

What catches people who aren't ready yet?

What I'm assessing: Whether the infrastructure between first contact and closed revenue is actually built, or whether interested prospects are falling into a gap nobody knows exists.

Most sales cycles have a gap in the middle. The prospect shows interest. They're not ready to buy. And then nothing happens — because there's no system designed to stay in contact, build trust, and move them toward a decision over time. That gap is where a significant percentage of the leads your business generates are quietly dying.

What I look at:

• List health and deliverability. Deliverability, open, click, and unsubscribe rates are vital signs. A deliverability problem can silently destroy the economics of your entire nurture operation. I look at list hygiene, suppression processes, and technical infrastructure (SPF, DKIM, DMARC).
• Segmentation architecture. Is the list segmented by anything that reflects buyer behavior — lead source, engagement level, stated interest, stage in consideration? Or is everyone getting the same message regardless of where they are? The default for most businesses is one undifferentiated list.
• Automation infrastructure. What happens when someone raises their hand? I look at every automation flow: welcome sequence, lead magnet delivery, post-inquiry nurture, behavior-triggered sequences, re-engagement flows, post-purchase onboarding. Most businesses have one or two flows partially built.
• Connection between nurture activity and sales outcomes. Is the nurture system producing pipeline? Not opens and clicks — actual booked calls, submitted applications, completed purchases. Are there clear conversion paths inside sequences?
• CRM and automation integration. When a prospect clicks a pricing page link, does anything happen in the pipeline? When engagement hits a threshold, does it trigger a sales action? These integrations are the connective tissue between marketing activity and sales outcomes. Most businesses don't have them.

Where do qualified opportunities go to die?

What I'm assessing: Whether the infrastructure from qualified interest to closed revenue is built and functioning — or whether the business is generating demand it can't convert.

This is where most revenue disappears. The pipeline architecture that's supposed to catch, process, and close qualified opportunities either doesn't exist, or exists in a form that doesn't function. A lead that enters a broken sales system is a lead you paid to generate and lost.

What I look at:

• Pipeline architecture. Is the pipeline organized in stages that reflect how buyers in this specific business actually move toward a decision? Are stages defined clearly enough that anyone using the system agrees on what each stage means?
• CRM utilization. Does a CRM exist, and is it being used accurately? The most common CRM reality in a founder-led business: a CRM set up years ago and maintained inconsistently, a CRM set up by the last agency that nobody has touched since, or no CRM at all.
• Lead routing and response protocol. When a lead comes in, what happens? Lead response time is one of the highest-leverage variables in sales conversion. A lead contacted within five minutes is dramatically more likely to convert than one contacted within an hour. Most businesses have no protocol.
• Marketing-to-sales handoff. Is there a defined point at which a prospect moves from nurture to direct sales engagement? The absence of a clear handoff is one of the most common revenue leaks in businesses with both a marketing function and a sales function.
• Follow-up architecture. What happens when a prospect doesn't convert immediately? Is there a structured sequence for leads who showed interest but didn't book? Most businesses have none of this formalized. Follow-up happens when someone remembers.
• Pipeline reporting. Can the business answer: How many qualified leads came in last month? How many converted to sales conversations? How many of those converted to clients? If the answer to any of these is 'I'd have to pull that manually,' the pipeline architecture is not doing its job.

Can the right people find you at all?

What I'm assessing: Whether your business is visible in the information environment where your buyers are actually making decisions — including the AI-powered platforms that are increasingly replacing traditional search.

When someone who is exactly your ideal client asks an AI assistant for a recommendation in your category — right now, today — do you come up? For most businesses, the answer is no. And that gap is a present revenue problem.

What I look at:

• Current AI citation presence. I run a battery of queries across ChatGPT, Perplexity, Gemini, and Google AI Overviews — queries that mirror how your ideal clients are actually researching your category. I document where you appear, where you don't, and what AI models say about you when they do surface you. Hallucinations happen, and those need to be found and corrected.
• Entity clarity and structured data. AI models build understanding of a business from multiple signals: website content, third-party citations, structured data markup, local listings, review profiles, and consistency across all of them. Inconsistencies create noise that makes AI models less confident and less likely to cite you.
• Content citeability. Question-and-answer structures, clear definitions, specific claims with evidence, FAQ sections, comparison frameworks — these are formats AI models favor when generating responses. I assess whether existing content is structured for citeability or only for human reading.
• Third-party citation footprint. AI models learn from external references. PR placements, podcast appearances, guest content, review profiles, directory listings — these create the external footprint that makes AI models confident enough to surface a business. Most businesses have a thin footprint concentrated on their own website.
• Platform-specific visibility gaps. The overlap between what ChatGPT surfaces, what Perplexity surfaces, and what Google AI Overviews surface is small. Each platform draws from different sources with different weights. I map visibility by platform and identify the most significant gaps.
• Traditional search foundation. Underneath the AI visibility question is the SEO foundation it rests on. On-page fundamentals, title structure, internal linking, page speed, mobile performance — a business invisible in traditional search is typically invisible in AI search too.

What the deliverable actually looks like

After one to three weeks inside your actual accounts — the analytics, the ad platforms, the email system, the CRM, the website, the AI search environment — the Diagnostic produces a report that is unlike any document you've probably received from a marketing or consulting engagement.

For each of the six areas, the report contains: a clear-eyed assessment of current state, specific findings with evidence from the actual accounts reviewed, the structural cause of each finding, the revenue impact in concrete terms, and what it would take to address it.

The findings are prioritized by revenue impact. The highest-leverage fixes come first.

The report is delivered as an interactive, password-protected landing page — with an embedded video walkthrough from me, going through every finding and what it means for your specific business. Because the most important part of a diagnostic isn't the document. It's making sure you understand it well enough to act on it.

What comes after The Diagnostic

The Diagnostic is a standalone engagement. You own the report. You can take it anywhere.

But most founders who go through it want to know: what would it actually take to fix this? That's what The Build is. Based on what the Diagnostic finds, I scope a custom build specific to your business — the exact systems needed to close the gaps, in the right order, built in your stack in your name.

Common builds include a full CRM build into GoHighLevel with custom AI intent scoring and automation flows, analytics and tagging architecture rebuilt from scratch, complete email marketing architecture and behavior-triggered flows, demand generation systems across Meta, Google, LinkedIn, Reddit, or StackAdapt, GEO and AI search visibility work, identity resolution integration, and custom AI tools trained on your voice for content and ad creative.

There is no standard scope. What gets built depends entirely on what the Diagnostic finds. Without the Diagnostic, any scope is a guess. With it, every line item is justified by evidence.

After the Build, my team operates what we built on The Run — with my team running the campaigns, monitoring the results, and improving everything continuously. No handoff to a different execution team. And when we part ways, you keep everything. The systems are in your stack, in your name, accessible to you without us.

Why this level of rigor matters at your scale

The firms that charge six figures for this kind of engagement are working with organizations managing hundreds of millions in revenue. The stakes justify the price. And the junior associate doing the actual work justifies the disconnect between what those engagements cost and what they produce.

You have never had access to this.

The rigor applies more to your business than it does to a Fortune 500. The percentage of revenue you're losing to undiagnosed systems problems is higher. You don't have a full revenue operations team catching the gaps. Every marketing dollar wasted is a dollar that came from you.

Until you know — specifically, with evidence, in your actual accounts, organized by revenue impact — you are guessing. Expensively. That ends with the Diagnostic.