Library / franchise systems / Tagging nomenclature
Community plus CRM is a product. Most groups only shipped the community.
Read it once, then stop negotiating with it. Tagging nomenclature for mastermind franchises is a wiring job: one page → three axes → archive → fire on spec. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
Mastermind franchises do not have a Tagging nomenclature problem because they lack GoHighLevel. They have it because tags multiply. Insight does not.
Wire these objects first: Tag (spec only), tag prefix axes (source / offer / status), contact, workflow trigger, smart list, archived junk tags.
Then these edges, in order: Form hidden field utm_source → tag source:google (never source+offer mashed) · Opportunity Won → tag status:customer; source and offer tags stay put · Workflow trigger → only spec tags on the one-page list, never leftover demo tags · Junk tag (snapshot leftover) → archived; smart lists rebuilt on spec tags only
Done looks like a test you can repeat: Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob.
Start here: Three tags that mean those states. Automations that respect them.
Mastermind franchises already have GoHighLevel. The leak is not a missing feature. Tags multiply. Insight does not. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: Tag (spec only), tag prefix axes (source / offer / status), contact, workflow trigger, smart list, archived junk tags. Then connect these edges, in order: Form hidden field utm_source → tag source:google (never source+offer mashed) · Opportunity Won → tag status:customer; source and offer tags stay put · Workflow trigger → only spec tags on the one-page list, never leftover demo tags · Junk tag (snapshot leftover) → archived; smart lists rebuilt on spec tags only. If you skip an edge, the next one is decoration. If you add a GoHighLevel feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob. How you know it worked on the board: Spec tags is finite (a list you can print). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Three tags that mean those states. Automations that respect them. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: export every tag. On paper, three columns — source, offer, status. Anything that tries to be two columns is a synonym to kill. Do not build a workflow until the page exists and junk is archived, not 'kept for old automations'.
Operator
You already feel tags multiply. insight does not. Community plus CRM is a product. Most groups only shipped the community. Protect one sequence for 90 days. The four moves are one page → three axes → archive → fire on spec. The edges are Form hidden field utm_source → tag source:google (never source+offer mashed) then Opportunity Won → tag status:customer; source and offer tags stay put. Member vs prospect vs alumni are three journeys. One list is how you burn the room.
CEO
This is a money leak, not a preference about tools. Tags multiply because every automation needed a switch. Until spec tags is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Form hidden field utm_source → tag source:google (never source+offer mashed).
Before
Tuesday. Someone among mastermind franchises. Community plus CRM is a product. Most groups only shipped the community. GoHighLevel is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. Member vs prospect vs alumni are three journeys. One list is how you burn the room. Form hidden field utm_source → tag source:google (never source+offer mashed) The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in mastermind franchises already paid for GoHighLevel. Community plus CRM is a product. Most groups only shipped the community. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. A taxonomy is a naming spec on one page: source, offer, and status stay separate. Prove write-in: Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob. This week is one move: Three tags that mean those states. Automations that respect them. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Tags multiply because every automation needed a switch. Source, offer, and status share one messy string. Insight does not appear. Automations fire on junk. The contact looks busy and means nothing.
The system
A taxonomy is a naming spec on one page: source, offer, and status stay separate. Automations only fire on spec tags. Everything else is archived, not 'just in case'.
If you cannot explain a tag in five words, it is not a tag. It is a note someone was afraid to delete. Notes belong in a field. Tags are for filters and automations.
Separate the three axes or reporting will always lie. A person can be Google + high-ticket + customer. One tag that tries to be all three will break the next workflow you add.
Member vs prospect vs alumni are three journeys. One list is how you burn the room.
Tags are switches for filters and automations. They are not notes, not biography, not a place to hide a sentence you were afraid to delete. If you cannot explain a tag in five words, it belongs in a custom field. The spec is one page: prefixes if you need them, no synonyms, three axes that never combine. A person can be source:linkedin + offer:high-ticket + status:customer at the same time. One tag named 'linkedin-high-ticket-customer' will break the next workflow you add because you cannot filter on one axis.
Wire tags at write-in, not in a nightly cleanup. The form, the calendar, the Stripe event, the lead ad — each should apply the spec tag as it writes the contact. Workflows listen only to that list: if a workflow still triggers on a demo tag from a snapshot, you do not have a nomenclature; you have archaeology. Archive junk — do not hide it in a folder of four hundred. Smart lists are rebuilt from spec tags; reporting that groups by tag is otherwise a word cloud.
Two databases show up as: ads report one source, GHL tags another; status:customer exists and the opportunity is still open; automations fire twice because source:google and Google Ads both exist. The intern test is simple — print the spec, pick a contact at random, and read their tags aloud. If you need a translator, the spec is not installed. Automations that 'just need one more tag' are how the list dies. Add a field or add a stage. Do not add a fourth axis in the tag soup.
Tag (spec only), tag prefix axes (source / offer / status), contact, workflow trigger, smart list, archived junk tags.
Form hidden field utm_source → tag source:google (never source+offer mashed)
Opportunity Won → tag status:customer; source and offer tags stay put
Workflow trigger → only spec tags on the one-page list, never leftover demo tags
Junk tag (snapshot leftover) → archived; smart lists rebuilt on spec tags only
Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob.
Day one: export every tag. On paper, three columns — source, offer, status. Anything that tries to be two columns is a synonym to kill. Do not build a workflow until the page exists and junk is archived, not 'kept for old automations'.
Write the convention. Prefixes if you need them. No synonyms.
Source ≠ offer ≠ status. Never combine them in one tag.
Junk is archived, not left 'for old automations'.
Workflows only listen to tags on the page. The rest cannot trigger.
On one line, for mastermind franchises: Tags multiply. Insight does not. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
Tag (spec only), tag prefix axes (source / offer / status), contact, workflow trigger, smart list, archived junk tags.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Write the convention. Prefixes if you need them. No synonyms. Then wire: Form hidden field utm_source → tag source:google (never source+offer mashed)
Why: Mastermind franchises cannot skip this edge. Tags are switches for filters and automations. If it is not true, GoHighLevel is already a second database.
Done when: Form hidden field utm_source → tag source:google (never source+offer mashed) is true on a test.
Source ≠ offer ≠ status. Never combine them in one tag. Then wire: Opportunity Won → tag status:customer; source and offer tags stay put
Why: Mastermind franchises skip this and the leak returns as a private language. Wire tags at write-in, not in a nightly cleanup. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Opportunity Won → tag status:customer; source and offer tags stay put is true on a test.
Junk is archived, not left 'for old automations'. Then wire: Workflow trigger → only spec tags on the one-page list, never leftover demo tags
Why: Mastermind franchises feel this as Tags multiply. Insight does not. Two databases show up as: ads report one source, GHL tags another; status:customer exists and the opportunity is still open; automations fire twice because source:google and Google Ads both exist.
Done when: Workflow trigger → only spec tags on the one-page list, never leftover demo tags is true on a test.
Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Spec tags (A list you can print), then junk (Not hidden in a folder of 400). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
Three tags that mean those states. Automations that respect them.
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
Tag (spec only), tag prefix axes (source / offer / status), contact, workflow trigger, smart list, archived junk tags.
If objects aren't named, software invents a second database.
Community plus CRM is a product. Most groups only shipped the community.
Write the convention. Prefixes if you need them. No synonyms. Then wire: Form hidden field utm_source → tag source:google (never source+offer mashed)
Mastermind franchises cannot skip this edge. Tags are switches for filters and automations. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how mastermind franchises actually work — not the snapshot demo. Edge: Opportunity Won → tag status:customer; source and offer tags stay put
Source ≠ offer ≠ status. Never combine them in one tag. Then wire: Opportunity Won → tag status:customer; source and offer tags stay put
Mastermind franchises skip this and the leak returns as a private language. Wire tags at write-in, not in a nightly cleanup. Spec tags, fields, and states have to be the same objects the next workflow will read.
Member vs prospect vs alumni are three journeys. One list is how you burn the room.
Junk is archived, not left 'for old automations'. Then wire: Workflow trigger → only spec tags on the one-page list, never leftover demo tags
Mastermind franchises feel this as Tags multiply. Insight does not. Two databases show up as: ads report one source, GHL tags another; status:customer exists and the opportunity is still open; automations fire twice because source:google and Google Ads both exist.
three tags that mean those states. Automations that respect them.
Because the login already exists. Tags multiply because every automation needed a switch. Source, offer, and status share one messy string. A new feature on a missing spec is a second database. Finish this edge first: Form hidden field utm_source → tag source:google (never source+offer mashed).
Day one: export every tag. On paper, three columns — source, offer, status. Anything that tries to be two columns is a synonym to kill. Do not build a workflow until the page exists and junk is archived, not 'kept for old automations'. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. Automations (No trigger on leftover demo tags) is how you stop the leak returning dressed as a new feature. Start with how you actually sell, not with how the snapshot was demoed. Name stages as jobs, not moods. Separate source, offer, and status. If a new hire cannot explain a contact in thirty seconds, you do not have an operating system — you have a database with anxiety on top.
More leads into a leak is a more expensive leak. Member vs prospect vs alumni are three journeys. One list is how you burn the room. Watch spec tags before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. Three tags that mean those states. Automations that respect them. That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because GoHighLevel is “set up”.
Do this
Tag (spec only), tag prefix axes (source / offer / status), contact, workflow trigger, smart list, archived junk tags.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Form hidden field utm_source → tag source:google (never source+offer mashed)
Skip this
Calling it done because a screenshot looks busy.
Do this
Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob.
Skip this
Leaving “Fire on spec” to chance.
Do this
Workflows only listen to tags on the page. The rest cannot trigger.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Write the convention. Prefixes if you need them. No synonyms. Then prove write-in: Create a test contact.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Form hidden field utm_source → tag source:google (never source+offer mashed) first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Spec tags: Finite. A list you can print. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Spec tags
Finite
A list you can print
Junk
Archived
Not hidden in a folder of 400
Automations
On spec
No trigger on leftover demo tags
This week
three tags that mean those states. Automations that respect them.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
A naming convention exists on one page
Source, offer, and status are separate
Junk tags are archived
Automations only fire on spec tags
Want the longer lesson, not the page for this niche? Write the tag spec on one page ↗
Working notes
What HQ should lock, what locations can change, and how rollout actually works. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Mastermind franchises do not have a Tagging nomenclature problem because they lack GoHighLevel. They have it because tags multiply. Insight does not. Wire these objects first: Tag (spec only), tag prefix axes (source / offer / status), contact, workflow trigger, smart list, archived junk tags. Then these edges, in order: Form hidden field utm_source → tag source:google (never source+offer mashed) · Opportunity Won → tag status:customer; source and offer tags stay put · Workflow trigger → only spec tags on the one-page list, never leftover demo tags · Junk tag (snapshot leftover) → archived; smart lists rebuilt on spec tags only Done looks like a test you can repeat: Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob. Start here: Three tags that mean those states. Automations that respect them.
Tags multiply because every automation needed a switch. Source, offer, and status share one messy string. Insight does not appear. Automations fire on junk. The contact looks busy and means nothing. Member vs prospect vs alumni are three journeys. One list is how you burn the room.
Before: Tuesday. Someone among mastermind franchises. Community plus CRM is a product. Most groups only shipped the community. GoHighLevel is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases. After: Same Tuesday, after write-in exists. Member vs prospect vs alumni are three journeys. One list is how you burn the room. Form hidden field utm_source → tag source:google (never source+offer mashed) The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because GoHighLevel is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: one page → three axes → archive → fire on spec.
Spec tags: Finite — A list you can print. Then junk (Not hidden in a folder of 400). If those are folklore, do not add another GoHighLevel workflow.
three tags that mean those states. Automations that respect them.
Because the login already exists. Tags multiply because every automation needed a switch. Source, offer, and status share one messy string. A new feature on a missing spec is a second database. Finish this edge first: Form hidden field utm_source → tag source:google (never source+offer mashed).
Day one: export every tag. On paper, three columns — source, offer, status. Anything that tries to be two columns is a synonym to kill. Do not build a workflow until the page exists and junk is archived, not 'kept for old automations'. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Create a test contact. Apply source:test, offer:discovery, status:lead. Confirm a workflow that should fire on offer:discovery enrolls, and a leftover snapshot tag does nothing. Then search smart lists: the contact appears on the spec list and not on a 'everyone' blob. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
The CRM is open. The operating system is not.
Read ↗Stages are labels. Nobody knows what 'won' requires.
Read ↗The quiz converts. The follow-up is a spreadsheet.
Read ↗Traffic hits a page. The journey after that is improvised.
Read ↗Conversations die in DMs.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.