SAMPLE — fictional company and numbers, not a customer result

Sample Revenue Leak Snapshot

A sample Revenue Leak Snapshot and recovery queue

This is the kind of work the 30-Day Revenue Recovery Pilot starts with, shown for a fictional roofing company. Every name and number on this page is made up. It is not a customer result and it is not a promise of one.

What this is

An illustration of the Revenue Leak Snapshot that begins the pilot: where calls, forms, estimates, and old leads are slipping, and a ranked list of who to look at first.

What it is not

Not a customer result, a case study, or a forecast. The company, the homeowners, and every count and dollar amount are fictional.

Where it fits

You start with the free Lead Leak Check. If the pilot looks like a fit, it begins with a Snapshot like this one, built from your own records.

SAMPLE — fictional company and numbers, not a customer result

Revenue Leak Snapshot

Example Ridge Roofing

A fictional residential roofing company with one location. Sample window: the last 60 days of activity.

  • 19 of 54estimates sent with no follow-up logged for 14 or more days
  • 22 of 148inbound calls unanswered with no callback in the call log
  • 9 of 37web form requests with no first reply logged within 1 business day
  • 126CRM leads with no activity for 90 or more days

Findings, tagged by how well they are supported

  • VERIFIED

    19 of the 54 estimates sent in the window have no follow-up logged for 14 or more days.

    Estimate export (sample)

  • VERIFIED

    The amounts written on those 19 estimates add up to $187,400. That is the listed value on the quotes, not expected revenue and not a forecast.

    Estimate export (sample)

  • VERIFIED

    22 of 148 inbound calls went unanswered and have no callback in the call log.

    Call log export (sample)

  • VERIFIED

    9 of 37 web form requests have no first reply logged within 1 business day.

    Form inbox export (sample)

  • VERIFIED

    126 leads in the CRM show no activity for 90 or more days.

    CRM export (sample)

  • POSSIBLE RISK

    Unanswered calls cluster on weekday evenings. Worth confirming with the owner, because the call log alone cannot say why.

    Call log timestamps (sample)

  • UNKNOWN

    Close rate on estimates. It is not in the export, so no revenue estimate is made.

    Not in the records provided

  • UNKNOWN

    Whether unanswered callers were reached some other way, such as a text, a different number, or in person.

    Not in the records provided

  • UNKNOWN

    Who currently owns follow-up on estimates that go quiet.

    Not in the records provided

Recommended first workflow

Stale Estimates · confidence High

It is the largest pile of listed value with no logged follow-up, and every one of those records has a phone number on file.

Confidence is about the records, not the outcome. Nothing here says how many of these customers will buy.

Questions I would bring to the discovery call

  • How are estimates followed up?
  • Who reviews open estimates that have gone quiet?
  • Who owns follow-up after a new inquiry?
  • Who approves customer communication?

SAMPLE — fictional company and numbers, not a customer result

Sample recovery queue

Who to look at first, and who to leave alone

Example Ridge Roofing (fictional). Names are placeholders and every number is made up.

  • 145records flagged: 19 stale estimates and 126 untouched leads
  • 87held out by the safety checks below
  • 58in the queue, ranked. The first 6 are shown.
  1. Homeowner A · Unsold estimate

    Full re-roof estimate · 48 days since last activity · $18,400 listed · phone and email on file

    66priority, 0 to 100

    Why it ranks here: 48 days stale (+6); estimate amount $18,400 (+30); both phone and email on file (+15); unsold estimate (+10); prior outbound contact on record (+5).

    Next step: a founder call, once you approve the queue and the message library.

  2. Homeowner B · Unsold estimate

    Roof replacement with gutters · 63 days since last activity · $9,200 listed · phone and email on file

    57priority, 0 to 100

    Why it ranks here: 63 days stale (+9); estimate amount $9,200 (+18); both phone and email on file (+15); unsold estimate (+10); prior outbound contact on record (+5).

    Next step: a founder call, once you approve the queue and the message library.

  3. Homeowner C · Unsold estimate

    Storm-damage repair estimate · 36 days since last activity · $24,900 listed · phone only on file

    53priority, 0 to 100

    Why it ranks here: 36 days stale (+5); estimate amount $24,900 (+30); one contact method on file (+8); unsold estimate (+10).

    Next step: a founder call, once you approve the queue and the message library.

  4. Homeowner D · Unsold estimate

    Small repair estimate · 29 days since last activity · $6,300 listed · phone and email on file

    41priority, 0 to 100

    Why it ranks here: 29 days stale (+4); estimate amount $6,300 (+12); both phone and email on file (+15); unsold estimate (+10).

    Next step: a founder call, once you approve the queue and the message library.

  5. Homeowner E · Older CRM lead

    Older inquiry from the CRM · 142 days since last activity · phone and email on file

    40priority, 0 to 100

    Why it ranks here: 142 days stale (+20); both phone and email on file (+15); prior outbound contact on record (+5).

    Next step: a founder call, once you approve the queue and the message library.

  6. Homeowner F · Older CRM lead

    Older inquiry from the CRM · 205 days since last activity · email only on file

    37priority, 0 to 100

    Why it ranks here: 205 days stale (+29); one contact method on file (+8).

    Next step: a founder call, once you approve the queue and the message library.

Priority is a small, explainable ranking from days stale, listed amount, contact details on file, and record type. It decides who gets looked at first. It is not a likelihood of sale and it is not expected revenue.

Held out of the queue, and why (87 sample records)

  • 24

    Already sold or won

    Never chased.

  • 14

    Do-not-contact flag on file

    Blocks the call, not just the email.

  • 21

    Duplicate of another record

    Same phone number or email as a record already in the queue.

  • 18

    No valid phone or email

    Nothing to act on.

  • 10

    Customer activity in the last 14 days

    Recently touched, so it is left alone.

What a real Snapshot depends on

The sample shows the shape of the work. A real one is only as good as the records behind it, and it says so.

Built from records you share

An estimate export, a lead list from your CRM or a spreadsheet, and call and form logs if you have them. Anything you cannot share shows as unknown, never as a guess.

Every number traces to a record

The Snapshot counts what is in your records. It does not estimate recovered revenue, close rates, or return on investment.

Nothing is contacted until you approve

Nothing contacts your customers outside the approval rules you set. In the pilot, I work the queue by phone myself after you approve the message library.

Start with the Lead Leak Check.

It is free, takes a few minutes, and tells you whether the 30-day pilot looks like a fit before anything is scoped or billed. Nothing is sent to your customers.

See the 30-Day Pilot · See pricing

Run Free Lead Leak Check