Intern
What you actually do
The dump and the archive. Five-word test on each keeper.
Library / Tool / Tag spec: source, offer, and status stay separate
Tags multiply because every automation wanted a switch. This worksheet is the one-page nomenclature: prefixes, no synonyms, three axes, junk to archive, workflows that may fire. An intern can print it. A CEO can refuse a fourth axis.
Tags multiply because every automation wanted a switch. This worksheet is the one-page nomenclature: prefixes, no synonyms, three axes, junk to archive, workflows that may fire. An intern can print it. A CEO can refuse a fourth axis.
A person can be Google + high-ticket + customer at once. One mashed tag will break the next filter.
Notes belong in fields. Tags are switches.
Archive junk. Do not keep it 'for old automations'.
Folders hide mess. They do not stop a trigger.
New tag requests go through this page or they do not ship.
Intern
The dump and the archive. Five-word test on each keeper.
Operator
Three axes. Fire on spec. Archive without sentiment. Campaign names in fields.
CEO
400 tags is not sophistication. A printable list is. Until it exists, reporting is a word cloud.
source:*, offer:*, status:*, custom field (for notes), archived junk, workflow allow-list.
Writer applies spec tags at write-in, not in a nightly cleanup
Won → status:customer; source and offer stay
Workflows listen only to this page
Junk tag test → nothing happens
Dump. Sort into three columns or trash.
Why: You cannot spec what you have not seen.
Done when: A pile and a keep list.
Finite source, offer, status lists.
Why: Open vocabulary is how dialects return.
Done when: Printable lists.
Not hide. Archive.
Why: Interns will use demo tags.
Done when: Live tags fit on this page.
Each live workflow cites a spec tag.
Why: Landmines.
Done when: Junk-tag test does nothing.
Date + new tag or rejected.
Why: Spec dies in week three otherwise.
Done when: A row this month.
Export, three columns, archive, junk test. You do not add a tag to make a Zap easier.
Refuse a workflow that needs a tag not on this page. That request is a field or a no.
Snapshot tags, mashed strings, automations on leftovers. Insight never appears.
Random contact: intern reads tags aloud without a translator. Junk tag does nothing.
Folders do not stop triggers. The spec is the stop rule.
Campaigns belong in a field (utm_campaign). Tags that explode per ad set are how you get 400.
History can live on the contact as a field. Live triggers cannot listen to a museum.
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.
google, meta, linkedin, referral, sphere, phone… casing locked.
Named products, not 'coaching-summer-special-v2'.
lead, booked, customer, sunset, member… not 'hot'.
utm_campaign, quiz answers, notes. List them.
Snapshot leftovers, mashed strings, synonyms.
If it is not here, it is off.
Google Ads vs google vs GAds — pick one.
Apply a leftover tag to a test contact. What fired?
Role + request path. Not every contractor.
Monthly. New tags without a date are how the spec dies.
This week
This week: export, three axes written, junk archived, junk-tag test, one change-log row. No new automation tags.
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.