Library / Tool / Lost reasons: required, finite, reviewed

ToolHow to wire it

Lost reasons: required, finite, reviewedOptional lost is how you keep buying the same traffic and calling it a funnel problem.

Lost is a first-class stage. This worksheet is the finite list of reasons, the rule that a card cannot sit in Lost blank, and Monday’s top reasons. Without this, dashboards are screenshots and you will scale the leak. Five reasons is enough. 'Other' should be rare enough to embarrass you.

00

The short version

Intern through CEO

Lost is a first-class stage. This worksheet is the finite list of reasons, the rule that a card cannot sit in Lost blank, and Monday’s top reasons. Without this, dashboards are screenshots and you will scale the leak. Five reasons is enough. 'Other' should be rare enough to embarrass you.

  1. 01

    Reasons are jobs of information: not a fit, no-show, hired elsewhere, price, silence, conflict, timing.

  2. 02

    If 40% is Other, you do not have reasons. You have a junk drawer.

  3. 03

    No-show is a reason and a sequence. Do not only lose them — recover first, then lose with reason.

  4. 04

    Sales will resist because it feels negative. That is why it is the system. Hope is the alternative.

  5. 05

    Do not add a reason per campaign. Campaign belongs in source/UTM.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

List, require, tally. You do not invent campaign-specific reasons.

Operator

What you protect

Finite, required, reviewed. Recover before lost on no-show. Other is a smell.

CEO

What you refuse to fund

Lost is information. Optional lost is fiction. Top reason is the number that should change spend.

Wire

How to connect it

Objects, then edges

lost_reason field, required on Lost, finite list, Monday tally, action on a repeating reason.

  1. 01

    Move to Lost → reason required (policy or required field)

  2. 02

    Reason → reportable; not a note novel

  3. 03

    Monday → top two reasons

  4. 04

    Repeating reason → spec change (offer, filter, speed), not more ads first

Steps

Do this in order

Why, then done when
  1. 01

    Write five reasons

    Finite. Definitions in five words each.

    Why: Open text is a novel.

    Done when: List locked.

  2. 02

    Make it required

    Field required or a workflow that bounces blank Lost.

    Why: Optional is fiction.

    Done when: Blank Lost test fails.

  3. 03

    Tally last 30 days

    Even partial. Top two.

    Why: Baseline.

    Done when: Two names.

  4. 04

    Attach one action

    If no-show wins, recover. If unfit, filter. If silence, speed.

    Why: Tally without action is journaling.

    Done when: Action on the winner.

  5. 05

    Ban Other as a habit

    Review Other weekly until it is small.

    Why: Other is how the list dies.

    Done when: Other % known.

Intern

Five reasons, required test, 30-day tally, Other %. You are not adding a sixth because someone asked once.

CEO

Ask for top lost reason before more media. If they cannot answer, you are buying the leak.

Failure

Lost optional. Other 60%. No-show never recovered. Ads scaled.

Test

A user cannot leave Lost blank. Last month has a tally. One action exists.

Why

Questions people actually ask

Pushback is normal

Won’t this slow sales?

A five-word pick is slower than a rotting card by about four seconds. The rotting card costs the week.

Can we use tags instead of a field?

A single field is easier to require and report. Tags will multiply. Prefer a field.

What about won reasons?

Optional. Lost is the leak teacher. Do not delay lost for a symmetric won taxonomy.

Sheet

Fill this in

0 marked

This lives in the browser until you copy it out. The point is to write the spec before anyone opens Workflows or Flows. Print or screenshot when it is true.

  1. Reason 1 + five-word definition

    e.g. no-show — event not held, recover failed.

  2. Reason 2 + definition

    not a fit — disqualifier true.

  3. Reason 3 + definition

    hired elsewhere / bought elsewhere.

  4. Reason 4 + definition

    price / budget.

  5. Reason 5 + definition

    silence — no reply after N days.

  6. Other allowed? (yes/no + max %)

    If yes, cap. If 40%+, fail.

  7. Required on Lost? (how enforced)

    Field required or bounce workflow.

  8. 30-day tally (counts)

    Even incomplete. Write the integers.

  9. Action on the top reason

    Owner + change (recover, filter, price, speed).

  10. No-show: recover before lost? (yes/no)

    Lost-only no-show is a missing sequence.

This week

This week: five reasons, required, tally, one action on the top reason. No new ad set until the top reason has a response.

Working notes

GHL Engine Checklist

The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.

Request the notes ↗
Next

If the leak is expensive, talk.

Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.