Library / Tool / Monday CRM review: fifteen minutes, one action or hold

ToolHow to wire it

Monday CRM review: fifteen minutes, one action or holdA dashboard with no action is theatre. This is the script.

Monday review is an operating habit: write-in, show rate, time-in-stage, lost reasons, one action or the word hold. This checklist is what an intern runs and a CEO sits through. If the meeting needs Slack archaeology, the CRM failed — fix the record, do not praise the thread.

00

The short version

Intern through CEO

Monday review is an operating habit: write-in, show rate, time-in-stage, lost reasons, one action or the word hold. This checklist is what an intern runs and a CEO sits through. If the meeting needs Slack archaeology, the CRM failed — fix the record, do not praise the thread.

  1. 01

    Fifteen minutes. If it runs an hour, you are debating definitions. Stop and write the definition.

  2. 02

    Three numbers beat twelve. Write-in, the leak number of the 90, and aging.

  3. 03

    Hold is a valid outcome. A forced action every week is how you create junk work.

  4. 04

    The intern prepares screenshots before the meeting. The meeting does not 'pull the data live' as a personality.

  5. 05

    What you reward (clever Slack memory) is what you get instead of a CRM.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

Prepare the one-pager. Tick the boxes. Capture the action line. You are the clerk of the review.

Operator

What you protect

Three numbers. Definitions. Action or hold. No Slack archaeology.

CEO

What you refuse to fund

If Monday requires Slack, you do not have a CRM. The action line is the product of the meeting.

Wire

How to connect it

Objects, then edges

Write-in %, show rate, aging cards, lost reasons, unmatched payments, one action, hold.

  1. 01

    Numbers from GHL (or Klaviyo if that is the layer), not from Slack search

  2. 02

    Each number has a definition on a spec page

  3. 03

    Action attaches to an owner and a date

  4. 04

    If a number is a vibe, the action is instrument, not more traffic

Steps

Do this in order

Why, then done when
  1. 01

    Prepare before the meeting

    Screenshots of the three numbers. Exceptions listed.

    Why: Live clicking is theatre.

    Done when: A one-pager exists at 9:00.

  2. 02

    Read write-in

    Test or production: forms/books that missed.

    Why: Traffic on a miss is expensive.

    Done when: Pass/fail + tickets.

  3. 03

    Read the 90’s number

    Show, speed, RPR, recare — whichever you chose.

    Why: Unowned 90 is a deck.

    Done when: Number said aloud.

  4. 04

    Aging and lost

    Cards past exit. Reasons this week.

    Why: Rot is the backlog.

    Done when: One aging action or hold.

  5. 05

    Write action or hold

    Owner, date. Or hold.

    Why: Meetings without this line did not happen.

    Done when: Logged.

Intern

One-pager before the meeting. You do not wait to 'just pull it up'.

CEO

Protect the slot. Refuse a second workstream that is not the action. If the number is a vibe, fund instrument, not media.

Failure

Hour of stories. Slack search. No action line. Dashboard pretty. Leak unchanged.

Test

A stranger can see last Monday’s action and whether it shipped. If not, the review is journaling.

Why

Questions people actually ask

Pushback is normal

Can we do this Friday?

You can. Monday is so the week can still change. Friday is a recap. Prefer Monday.

What if the numbers are embarrassing?

Then the meeting is working. Hiding them is how you buy more ads.

Do we need a BI tool?

Not to start. GHL views + this checklist. BI later if volume demands, same definitions.

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. One-pager prepared before the meeting

    Screenshots, not live clicking as the culture.

  2. Write-in: forms/books/payments that missed (count)

    Zero is the goal on tests; production misses are tickets.

  3. 90-day leak number said aloud

    Show, speed, RPR, recare — the one you chose.

  4. Definition still matches last week

    If it took a story, rewrite the definition, do not debate.

  5. Aging cards past exit rule (count)

    Proposal >7d, booked-not-held, etc.

  6. Lost reasons this week (top two)

    If lost is empty, that is the finding.

  7. Unmatched payments or dual-send incidents

    Stripe vs Won, two ESPs, two writers.

  8. Action or HOLD written

    Owner + date, or the word hold.

  9. Last week’s action shipped? (yes/no)

    If no, do not add a second action.

  10. Meeting stayed ≤15 minutes

    Over = definition fight. Stop and write.

This week

This week: run the checklist once, log action or hold, write definitions for any number that took more than a minute to explain.

Working notes

90-Day Growth Diagnostic

Pick the one sequence that deserves the next 90 days. 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.