Intern
What you actually do
Count goes down. Tests: junk, booked, reply. You do not add a 'just in case' automation.
Library / System / A workflow is a job with a stop rule, not a pile of on-switches
GHL workflows feel like progress because they are visible. The leak is enrollment on junk tags, no stop when a human replies, and twelve workflows that all send 'just checking in'. The operating layer is a short list of named jobs — spine, reminder, no-show, onboarding, sunset — each with a trigger on the spec, a stop, and an owner. Everything else is off.
GHL workflows feel like progress because they are visible. The leak is enrollment on junk tags, no stop when a human replies, and twelve workflows that all send 'just checking in'. The operating layer is a short list of named jobs — spine, reminder, no-show, onboarding, sunset — each with a trigger on the spec, a stop, and an owner. Everything else is off.
Inventory live workflows. If you cannot name the job of each in five words, turn it off until you can. Volume of workflows is not sophistication.
Triggers listen only to spec tags and stages. Leftover snapshot tags are landmines. A test junk tag must do nothing.
Stops are the product. Booked contacts still getting email four is how you look unsupervised. Paid contacts still in acquire is how you look greedy.
Replies are the point of nurture. If the workflow cannot pause for a human, you built a broadcast with extra steps.
New workflow requests go through the job list. 'We just need one more' is how the pile returns in week three.
Intern
Count goes down. Tests: junk, booked, reply. You do not add a 'just in case' automation.
Operator
Jobs with stops. Spec-only triggers. Change control. Conversations beats the tree.
CEO
Workflow count is not an asset. Unexpected sends are a tax. Finite jobs with stops are the operating layer.
Workflow, trigger (tag/stage/event), enrollment rules, wait, goal/stop, Conversations pause, owner, finite step count, junk-tag exclusion.
Spec tag or stage → enroll exactly one job workflow
Human reply in Conversations → wait/pause; no stacked pitch
Booked, paid, or sunset → exit; no leftover 'checking in'
Junk or demo tags → cannot trigger anything live
Export workflows. Five-word job or off. Allowed starters: first spine, reminders, no-show, onboarding, sunset, dunning if you own it.
Why: Unnamed workflows are how two sequences hit the same person.
Done when: A finite list posted. The rest are draft or deleted.
Each live workflow: trigger field/tag/stage from the spec page. Remove snapshot leftovers.
Why: Correct copy on a junk trigger still mails the wrong world.
Done when: Junk-tag test does nothing. Spec-tag test enrolls once.
Goal: booked, paid, unsubscribed, sunset days, human reply. Then add waits. Not the reverse.
Why: Waits without stops are a novel you cannot end.
Done when: A booked test contact leaves the spine the same day.
If Conversations gets a reply, marketing waits. Owner visible. After-hours auto-reply is honest, not a pitch.
Why: Bot-on-human is how you lose the lead and the brand.
Done when: Reply test: no third automated message in the next hour.
New workflow = new job or a documented change to an existing job. No stealth duplicates 'for the new funnel'.
Why: Funnels that bring their own workflows recreate the pile.
Done when: A request log. Duplicates rejected.
List every published workflow. Kill or draft anything without a five-word job. Test junk tag. Test booked-stop. Test reply-pause. You are reducing count, not adding AI steps.
An automation contractor whose deliverable is 'more workflows' until the job list is finite and stops work. More on-switches on junk tags is a more expensive pile.
Snapshot workflows all on. Demo tags trigger. Booked people still in nurture. Two 'welcome' automations. Nobody owns errors. That is a pile of on-switches.
Finite job list. Junk cannot trigger. Booked exits. Reply pauses. New request rejected unless it is a named job. Monday: unexpected sends investigated.
Paused is how they get turned on in a panic. Delete or archive with a note. Drafts are not production.
Then you cannot stop one job. Split by job. Shared waits across jobs are how paid people get reminders for a call they already had.
Giant trees are untestable. Prefer small workflows on clear states. If you need a novel, the data model is unfinished.
This week
This week: inventory, kill unnamed, spec triggers, stops, reply pause. No new workflow unless it replaces one.
Until stages, fields, and write-in have owners, the sub-account is a filing cabinet.
Read ↗If the thank-you does not change the contact, you paid for a brochure.
Read ↗Broadcasts feel like work. A spine with manners is the product.
Read ↗If campaigns do the work of flows, the list is large and the list is not alive.
Read ↗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.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.