Sale map: stages as jobs with exit rules
If a new hire needs a story to explain a card, the column is a mood.
Open ↗Scoreboards and spec pages an intern can fill. They live in the browser until you copy them into the CRM description, a pinned note, or Monday's agenda. They are not calculators for fun.
Sale map and tag spec first. Those two pages are the product of week one.
Write-in test before a second form. If the test fails, stop building.
Monday review is fifteen minutes with three numbers, not a dashboard ritual.
Speed-to-lead and show rate are clocks. If they are folklore, ads are a vanity spend.
Klaviyo flow score: if campaigns are doing flow jobs, do not write another brand story.
If a new hire needs a story to explain a card, the column is a mood.
Open ↗If you cannot explain a tag in five words, it is a note.
Open ↗A dashboard with no action is theatre. This is the script.
Open ↗If you merge contacts after the test, the identity key is wrong — do not add a dedupe workflow.
Open ↗If GHL sees the lead at 9:12 and they submitted at 9:03, you already lost a share.
Open ↗If the next visit is not on the contact, you are hoping they remember you.
Open ↗A blended vanity across all event types hides the leaky calendar.
Open ↗If campaigns are doing a flow’s job, you do not have lifecycle. You have a calendar.
Open ↗Optional lost is how you keep buying the same traffic and calling it a funnel problem.
Open ↗If source is always direct, you are arguing with ads in the dark.
Open ↗Working notes
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.