Why revenue leaks are hard to see from the inside

When revenue is below where it should be, the usual first assumption is a traffic problem, and the usual first response is to buy more attention. Sometimes that is right. More often the attention already exists and is being lost somewhere between arriving and becoming work.

The difficulty is that each handoff looks fine when examined alone. Search rankings look healthy. The website looks professional. Someone does reply to inquiries. There is a CRM. Every part passes inspection, and revenue still leaks, because the loss happens in the joints rather than the parts.

A diagnostic is useful here for the same reason a checklist is useful in any domain where the failure is a gap rather than a fault: it forces each junction to be examined separately, and it makes the weakest one visible instead of letting a strong average hide it.

The six systems

Five statements per system, thirty in total. Each is scored from zero to four, or Not sure.

SystemThe question it asksWhat it examines
01 VisibilityCan buyers find you?Search, AI discovery, local presence, category authority.
02 ConversionDoes attention become action?Offer clarity, proof, calls to action, the path to inquiry.
03 Speed-to-leadHow fast do you respond?Acknowledgment, routing, ownership, response standards.
04 Follow-upWhat happens after day one?Nurture, pipeline discipline, reactivation, human handoffs.
05 MeasurementDo you know what creates revenue?Attribution, reporting, and the decisions they support.
06 CapacityCan your system handle growth?Whether delivery holds when demand increases.

How the scoring works

The scale is deliberately unkind to intentions.

  1. Not at all

    The practice does not happen. Planning it does not count.

  2. Rarely

    It happens occasionally, usually when someone remembers.

  3. Sometimes

    It happens, but not reliably.

  4. Consistently

    It happens reliably, and it does not depend on one person.

  5. Consistently, and we keep improving it

    It happens reliably, and someone reviews it and makes it better.

  6. Not sure

    Scores zero and is listed in your results as a blind spot to check.

Principle

Score what happens today, not what is planned. A system that exists in a document and not in anyone’s week is a zero, and recording it as anything else makes the diagnostic useless to the person taking it.

Reading the total

Section scores are worth more than the total. The total is a rough position; the lowest section is the instruction. Each system is read against the same four bands.

ScorePositionWhat it usually means
0 to 39Major leaksCritical gaps are letting leads and revenue slip away.
40 to 59Leaking revenueWorking pieces are held back by weak handoffs.
60 to 79Solid, with gapsMost of the system holds. Targeted fixes are the next step.
80 to 100StrongKeep measuring, and check your lowest system against real numbers.

What this diagnostic does not do

It is directional. It tells you which system to examine first, and it does not predict revenue, forecast a return, or guarantee an outcome. The scorecard says so on its own pages, and the same standard applies here: a score is a starting point for a conversation, not a measurement of anything that has happened yet.

It also cannot see your numbers. It records your assessment of your own systems, which is useful precisely because it is fast, and limited for exactly the same reason. Where a score surprises you, the next step is to check it against evidence rather than to trust the score.

Whose tool this is

The scorecard is a product of AI Marketing Box, the commercial practice, and it opens on their site under their branding. This page explains it; the practice delivers it. That separation is deliberate and it runs through everything here: this domain publishes the thinking, and commercial engagement happens at AI Marketing Box.

Taking the scorecard does not commit you to anything. Your results appear on screen without an email address. If you ask for the emailed report, Martin may follow up personally once, and you only receive occasional insights if you tick the box for them.

Frequently asked questions

How long does it really take?

About ten minutes if you answer from what you already know, which is how it is designed to be used.

It takes considerably longer if you stop to verify each answer, and that is worth doing afterwards rather than during. The first pass is meant to surface where to look.

Do I need technical knowledge?

No. Every statement describes an observable business practice: whether inquiries get acknowledged, whether follow-up has an owner, whether anyone measures which channel produces revenue.

If you do not know whether something happens, answer Not sure. It scores zero and is listed in your results as a blind spot to check.

What happens with my answers?

The scorecard runs on aimarketingbox.org. Your answers are scored in your browser and saved on your device so you can pick up where you left off, and they are not sent anywhere unless you ask for the emailed report. Then AI Marketing Box receives your first name, email, company if you add it, and your scores. How it handles those details is set out in their privacy policy, not this site’s.

Nothing about the scorecard requires confidential detail. It asks about the shape of your processes, not about your customers or your numbers.

Is a low score bad news?

It is usually the most useful result. A low score in one system with high scores elsewhere is the clearest kind of finding, because it means the surrounding machinery already works and one junction is losing what the rest produces.

A uniformly high score is harder to act on, and worth a second look at whether the scoring was generous.

Author:
Martin Zialcita
Published:
Last reviewed:
Corrections:
Editorial policy