Intern
What you actually do
Day one: write the definition of warm in days and events (bought, held discovery, referred). List who is excluded from broadcast. Do not build a 'win-back' that nags customers as if they were strangers.
Library / academies / Warm journey
Sales academies that cannot run their own pipeline teach the wrong lesson.
Read it once, then stop negotiating with it. Warm journey for sales academies is a wiring job: see it → spec it → install it → review it. 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.
Sales academies do not have a Warm journey problem because they lack GoHighLevel. They have it because past buyers and warm leads get the same broadcast as strangers.
Wire these objects first: Contact state 'warm' (definition + date), relationship-age field, offer-match rule, re-engagement workflow with stop, sales context fields, exclusion from cold blasts.
Then these edges, in order: Past buyer or held-call → tag status:warm + date; excluded from cold spine · Offer match → only offers that fit relationship age (no $47 blast to a $8k client) · Re-engagement sequence → finite; stop rule written; not infinite 'checking in' · Sales view → context fields visible (last offer, last held call), not a raw list export
Done looks like a test you can repeat: Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends.
Start here: Those three numbers. No-show recovery. Application or booking as the only conversion.
Sales academies already have GoHighLevel. The leak is not a missing feature. Past buyers and warm leads get the same broadcast as strangers. 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: Contact state 'warm' (definition + date), relationship-age field, offer-match rule, re-engagement workflow with stop, sales context fields, exclusion from cold blasts. Then connect these edges, in order: Past buyer or held-call → tag status:warm + date; excluded from cold spine · Offer match → only offers that fit relationship age (no $47 blast to a $8k client) · Re-engagement sequence → finite; stop rule written; not infinite 'checking in' · Sales view → context fields visible (last offer, last held call), not a raw list export. 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. Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends. How you know it worked on the board: Owner is named (or it will not run). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Those three numbers. No-show recovery. Application or booking as the only conversion. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: write the definition of warm in days and events (bought, held discovery, referred). List who is excluded from broadcast. Do not build a 'win-back' that nags customers as if they were strangers.
Operator
You already feel past buyers and warm leads get the same broadcast as strangers. Sales academies that cannot run their own pipeline teach the wrong lesson. Protect one sequence for 90 days. The four moves are see it → spec it → install it → review it. The edges are Past buyer or held-call → tag status:warm + date; excluded from cold spine then Offer match → only offers that fit relationship age (no $47 blast to a $8k client). Show rate, close, and time-to-cash should be on a Monday dashboard, not in a founder's memory.
CEO
This is a money leak, not a preference about tools. Broadcasts feel like work. Until owner is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Past buyer or held-call → tag status:warm + date; excluded from cold spine.
Before
Tuesday. Someone among sales academies. Sales academies that cannot run their own pipeline teach the wrong lesson. 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. Show rate, close, and time-to-cash should be on a Monday dashboard, not in a founder's memory. Past buyer or held-call → tag status:warm + date; excluded from cold spine The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in sales academies already paid for GoHighLevel. Sales academies that cannot run their own pipeline teach the wrong lesson. 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. Nurture is a spine with manners: a short sequence, a human on replies, a stop rule, and segments that match relationship — not 'everyone who ever opted in'. Prove write-in: Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends. This week is one move: Those three numbers. No-show recovery. Application or booking as the only conversion. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Broadcasts feel like work. Sequences feel like a project. So the list gets another campaign while nobody has a 5-email spine with one job per letter. Replies go nowhere. Unengaged contacts never sunset. Deliverability pays the bill.
The system
Nurture is a spine with manners: a short sequence, a human on replies, a stop rule, and segments that match relationship — not 'everyone who ever opted in'.
Write the sequence as if you will still be proud of it in six months. Each email does one job. If you need a discount to make it work, the offer is unclear. If you cannot sunset, you do not respect the inbox — including your own domain.
Warm is a defined state. Offers match relationship age.
Show rate, close, and time-to-cash should be on a Monday dashboard, not in a founder's memory.
Warm is a defined state, not a compliment. A past buyer, a held discovery, a referral — pick the events and a freshness window. Put that state on the contact as a tag plus a date field so it can expire. Offers must match relationship age. Sending the cold lead magnet to a client is how you train them that you do not know who they are. Sales should see context on the record: last offer, last event held, last reply. A raw list called 'warm' is a second database.
Re-engagement has a stop rule. Three touches, then a clean last look, then silence or a sunset tag. Infinite 'just checking in' is a broadcast. Wire exclusions: warm contacts do not enter cold sequences, do not get first-time discount logic, do not get 'nice to meet you'. If a workflow cannot see status:warm, it will contaminate. Conversations from warm people pause the sequence and stay on the contact.
The split: email tool thinks they are new, CRM thinks they are customers, calendar thinks they are a no-show from 2022. Reconcile on one contact. The intern builds the exclusion list before any new campaign. If HQ wants a blast, the question is 'does this list exclude warm?' If the answer is slow, the state is not installed. Past buyers are a journey. Treat them like one.
Contact state 'warm' (definition + date), relationship-age field, offer-match rule, re-engagement workflow with stop, sales context fields, exclusion from cold blasts.
Past buyer or held-call → tag status:warm + date; excluded from cold spine
Offer match → only offers that fit relationship age (no $47 blast to a $8k client)
Re-engagement sequence → finite; stop rule written; not infinite 'checking in'
Sales view → context fields visible (last offer, last held call), not a raw list export
Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends.
Day one: write the definition of warm in days and events (bought, held discovery, referred). List who is excluded from broadcast. Do not build a 'win-back' that nags customers as if they were strangers.
Warm is a defined state
Offers match relationship age
Re-engagement has a stop rule
Sales sees context, not a raw list
On one line, for sales academies: Past buyers and warm leads get the same broadcast as strangers. 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.
Contact state 'warm' (definition + date), relationship-age field, offer-match rule, re-engagement workflow with stop, sales context fields, exclusion from cold blasts.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Warm is a defined state Then wire: Past buyer or held-call → tag status:warm + date; excluded from cold spine
Why: Sales academies cannot skip this edge. Warm is a defined state, not a compliment. If it is not true, GoHighLevel is already a second database.
Done when: Past buyer or held-call → tag status:warm + date; excluded from cold spine is true on a test.
Offers match relationship age Then wire: Offer match → only offers that fit relationship age (no $47 blast to a $8k client)
Why: Sales academies skip this and the leak returns as a private language. Re-engagement has a stop rule. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Offer match → only offers that fit relationship age (no $47 blast to a $8k client) is true on a test.
Re-engagement has a stop rule Then wire: Re-engagement sequence → finite; stop rule written; not infinite 'checking in'
Why: Sales academies feel this as Past buyers and warm leads get the same broadcast as strangers. The split: email tool thinks they are new, CRM thinks they are customers, calendar thinks they are a no-show from 2022.
Done when: Re-engagement sequence → finite; stop rule written; not infinite 'checking in' is true on a test.
Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Owner (Or it will not run), then weekly number (Or reporting is theatre). 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.
Those three numbers. No-show recovery. Application or booking as the only conversion.
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.
Contact state 'warm' (definition + date), relationship-age field, offer-match rule, re-engagement workflow with stop, sales context fields, exclusion from cold blasts.
If objects aren't named, software invents a second database.
Sales academies that cannot run their own pipeline teach the wrong lesson.
Warm is a defined state Then wire: Past buyer or held-call → tag status:warm + date; excluded from cold spine
Sales academies cannot skip this edge. Warm is a defined state, not a compliment. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how sales academies actually work — not the snapshot demo. Edge: Offer match → only offers that fit relationship age (no $47 blast to a $8k client)
Offers match relationship age Then wire: Offer match → only offers that fit relationship age (no $47 blast to a $8k client)
Sales academies skip this and the leak returns as a private language. Re-engagement has a stop rule. Spec tags, fields, and states have to be the same objects the next workflow will read.
Show rate, close, and time-to-cash should be on a Monday dashboard, not in a founder's memory.
Re-engagement has a stop rule Then wire: Re-engagement sequence → finite; stop rule written; not infinite 'checking in'
Sales academies feel this as Past buyers and warm leads get the same broadcast as strangers. The split: email tool thinks they are new, CRM thinks they are customers, calendar thinks they are a no-show from 2022.
those three numbers. No-show recovery. Application or booking as the only conversion.
Because the login already exists. Broadcasts feel like work. Sequences feel like a project. A new feature on a missing spec is a second database. Finish this edge first: Past buyer or held-call → tag status:warm + date; excluded from cold spine.
Day one: write the definition of warm in days and events (bought, held discovery, referred). List who is excluded from broadcast. Do not build a 'win-back' that nags customers as if they were strangers. 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. Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends. 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. Stop rule (Or you will scale the leak) is how you stop the leak returning dressed as a new feature. Write the sequence as if you will still be proud of it in six months. Each email does one job. If you need a discount to make it work, the offer is unclear. If you cannot sunset, you do not respect the inbox — including your own domain.
More leads into a leak is a more expensive leak. Show rate, close, and time-to-cash should be on a Monday dashboard, not in a founder's memory. Watch owner 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. Those three numbers. No-show recovery. Application or booking as the only conversion. 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
Contact state 'warm' (definition + date), relationship-age field, offer-match rule, re-engagement workflow with stop, sales context fields, exclusion from cold blasts.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Past buyer or held-call → tag status:warm + date; excluded from cold spine
Skip this
Calling it done because a screenshot looks busy.
Do this
Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends.
Skip this
Leaving “Review it” to chance.
Do this
Sales sees context, not a raw list
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Warm is a defined state Then prove write-in: Take a real past buyer.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Past buyer or held-call → tag status:warm + date; excluded from cold spine 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
Owner: Named. Or it will not run. 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.
Owner
Named
Or it will not run
Weekly number
Believed
Or reporting is theatre
Stop rule
Written
Or you will scale the leak
This week
those three numbers. No-show recovery. Application or booking as the only conversion.
UK operators · UK hours. The CRM is often inherited from an agency; the spec still has to be written here.
Warm is a defined state
Offers match relationship age
Re-engagement has a stop rule
Sales sees context, not a raw list
Want the longer lesson, not the page for this niche? A CRM login is not a system ↗
Working notes
A journey that respects the price: apply, show up, close, onboard. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Sales academies do not have a Warm journey problem because they lack GoHighLevel. They have it because past buyers and warm leads get the same broadcast as strangers. Wire these objects first: Contact state 'warm' (definition + date), relationship-age field, offer-match rule, re-engagement workflow with stop, sales context fields, exclusion from cold blasts. Then these edges, in order: Past buyer or held-call → tag status:warm + date; excluded from cold spine · Offer match → only offers that fit relationship age (no $47 blast to a $8k client) · Re-engagement sequence → finite; stop rule written; not infinite 'checking in' · Sales view → context fields visible (last offer, last held call), not a raw list export Done looks like a test you can repeat: Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends. Start here: Those three numbers. No-show recovery. Application or booking as the only conversion.
Broadcasts feel like work. Sequences feel like a project. So the list gets another campaign while nobody has a 5-email spine with one job per letter. Replies go nowhere. Unengaged contacts never sunset. Deliverability pays the bill. Show rate, close, and time-to-cash should be on a Monday dashboard, not in a founder's memory.
Before: Tuesday. Someone among sales academies. Sales academies that cannot run their own pipeline teach the wrong lesson. 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. Show rate, close, and time-to-cash should be on a Monday dashboard, not in a founder's memory. Past buyer or held-call → tag status:warm + date; excluded from cold spine 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: see it → spec it → install it → review it.
Owner: Named — Or it will not run. Then weekly number (Or reporting is theatre). If those are folklore, do not add another GoHighLevel workflow.
those three numbers. No-show recovery. Application or booking as the only conversion.
Because the login already exists. Broadcasts feel like work. Sequences feel like a project. A new feature on a missing spec is a second database. Finish this edge first: Past buyer or held-call → tag status:warm + date; excluded from cold spine.
Day one: write the definition of warm in days and events (bought, held discovery, referred). List who is excluded from broadcast. Do not build a 'win-back' that nags customers as if they were strangers. 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. Take a real past buyer. Confirm they are not in this week's cold campaign. Enroll a warm test. Confirm the offer in email 1 matches their last purchase or last held call. Confirm the sequence ends. 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 ↗Tags multiply. Insight does not.
Read ↗Booked calls leak because the CRM never saw them.
Read ↗Broadcasts exist. A sequence that earns the next conversation does not.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.