Library / Tool / Sale map: stages as jobs with exit rules

ToolHow to wire it

Sale map: stages as jobs with exit rulesIf a new hire needs a story to explain a card, the column is a mood.

A sale map is one page: the real steps from first touch to paid, each with an exit rule, an owner, and what object proves it (form, calendar, payment). This worksheet is what an intern fills before anyone opens Workflows. Moods (hot, warm, nurture) are not rows.

00

The short version

Intern through CEO

A sale map is one page: the real steps from first touch to paid, each with an exit rule, an owner, and what object proves it (form, calendar, payment). This worksheet is what an intern fills before anyone opens Workflows. Moods (hot, warm, nurture) are not rows.

  1. 01

    Write how you actually sell, not how the snapshot was demoed. Discovery booked, held, proposal out, paid can be audited. Interested cannot.

  2. 02

    Each row needs an exit: what must be true to leave. 'They feel ready' is not an exit.

  3. 03

    Lost is a row with reasons, not a delete. Optional lost is how you buy the same traffic twice.

  4. 04

    If two offers have different jobs, they can be two maps. Two personalities on one offer is still one map.

  5. 05

    Done: a stranger can audit a live card against this page without Slack.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

You own the page and the one-card test. You do not build automations until the page is shared.

Operator

What you protect

Jobs with exits. Proof objects. One map per offer motion. Monday uses these names only.

CEO

What you refuse to fund

If Won cannot be said in one sentence with a proof object, you do not have a pipeline. You have a shared hallucination.

Wire

How to connect it

Objects, then edges

Stage name, exit rule, owner role, proof object, lost path, Won definition.

  1. 01

    First touch → first stage with a writer (form/call/ads)

  2. 02

    Booked → calendar event exists

  3. 03

    Held → event marked held or notes same day

  4. 04

    Paid → Stripe/invoice; Won is not a drag without proof

Steps

Do this in order

Why, then done when
  1. 01

    List the work, not temperature

    Draft 4–8 jobs. Cut any you cannot explain in five words.

    Why: Moods cannot be reported.

    Done when: Every leftover row is a job.

  2. 02

    Write exit rules

    One sentence under each stage. Object that proves it.

    Why: Without proof, Won is a feeling.

    Done when: Each row has a proof object.

  3. 03

    Name owners

    Role per stage. Not 'the team'.

    Why: Two owners stall.

    Done when: Each row has a role.

  4. 04

    Add lost reasons

    Five is enough. Required to enter Lost.

    Why: No reasons, no learning.

    Done when: Lost row exists.

  5. 05

    Test one live card

    Pick a contact. Does the stage match the proof?

    Why: The page is a lie until a card matches.

    Done when: One pass or a rewrite.

What an intern fills first

Rows below. No Workflows. Sit with whoever sells. If two people write different first stages, stop and agree.

What a CEO refuses

A second funnel or snapshot until this page exists and one live card matches. Tools on a missing map make reporting worse.

The usual failure

Snapshot defaults. Hot/warm. Won is a drag. Lost optional. That is a login.

The test

Stranger explains a card using only this page. If they need a story, rewrite the row.

Why

Questions people actually ask

Pushback is normal

Why not keep 'nurture' as a stage?

Nurture is a journey. A contact still needs a next date. Parking in nurture is how cards rot.

Can we copy a template pipeline?

As a prompt, yes. As truth, no. Your jobs differ. Templates become moods in week two.

How many stages?

As few as you can audit. More than eight usually means moods snuck back in.

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. First-touch stage name + exit rule

    What writer creates this? Form, call, ads, DM log. Not 'new' unless you define it.

  2. Qualified or booked stage + proof object

    Calendar event type or complete application. Mood words banned.

  3. Held / completed conversation + same-day rule

    Who marks held? What if they no-show?

  4. Proposal / plan / estimate out + dated artifact

    Field: sent_on + link. Aging >7 days is backlog.

  5. Verbal yes vs Won

    Verbal is not paid. What object makes Won true?

  6. Won proof (payment, signed, booked package)

    User cannot drag to Won without this — policy if not technical.

  7. Lost reasons (list five)

    Required. Include no-show, not a fit, hired elsewhere, price, silence.

  8. Owner role per stage

    ISA, closer, front desk, founder. Not 'team'.

  9. Second pipeline needed? (yes/no + why)

    Only if the job is a different motion (delivery vs prospect), not a personality.

  10. Live card test (contact URL + pass/fail)

    Paste a GHL link. Stage matches proof or rewrite.

This week

This week: fill the rows, test one card, ban temperature words, make lost required. No new pipeline.

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.