Intern
What you actually do
Run steps 01 and 02 this week. Do not add a feature. Prefixes if you need them. No synonyms. One page.
Library / Guides / Write the tag spec on one page
Every automation wants a switch. That is how you get 400 tags and zero insight. A taxonomy is not fancy. It is a naming spec a tired human can follow on a Thursday.
If you cannot explain a tag in five words, it is a note. Notes belong in a field. Tags are for filters and automations.
If you cannot explain a tag in five words, it is a note. Notes belong in a field. Tags are for filters and automations.
Keep source, offer, and status separate. A person can be Google + high-ticket + customer. One tag that tries to be all three will break the next workflow.
Archive junk. Do not leave it 'for old automations'. Workflows only fire on spec tags. Everything else cannot trigger.
Intern
Run steps 01 and 02 this week. Do not add a feature. Prefixes if you need them. No synonyms. One page.
Operator
Protect the sequence. Keep source, offer, and status separate. A person can be Google + high-ticket + customer. One tag that tries to be all three will break the next workflow.
CEO
Do not fund more traffic or more seats until the scoreboard in this lesson is a number you will defend. Archive junk. Do not leave it 'for old automations'. Workflows only fire on spec tags. Everything else cannot trigger.
Prefixes if you need them. No synonyms. One page.
Why: Two names for the same thing is how automations double-fire.
Done when: A finite list you could hand a VA.
Source ≠ offer ≠ status.
Why: Combined tags make reporting lie forever.
Done when: You can answer 'where did paying customers come from?' without a pivot from hell.
Junk is archived, not hidden in a folder of 400.
Why: 'Just in case' is how the next intern uses a demo tag in a live workflow.
Done when: Live tags fit on one page.
Workflows listen only to spec tags.
Why: Leftover demo tags are landmines.
Done when: A test: a junk tag does nothing.
New tag requests go through the page, or they do not ship.
Why: Otherwise the spec dies in week three.
Done when: A change log with a date.
Hand the tag to an intern. If they need a paragraph, it is not a tag. Put the paragraph in a note field.
Folders hide the mess. They do not stop a workflow from firing on junk. The spec is the stop rule.
Tags multiply. Insight does not.
Open the playbook ↗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.