Intern
What you actually do
Day one: screenshot the page. Circle every button. There should be one conversion. Write what the thank-you must do to GHL. Do not design a second page until a test submit writes a contact.
Library / coaches / Coaching funnel
Business coaches preach systems and run their own on memory.
Read it once, then stop negotiating with it. Coaching funnel for business coaches is a wiring job: one cta → thank-you → same-day spine → only conversion. 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.
Business coaches do not have a Coaching funnel problem because they lack GoHighLevel. They have it because traffic hits a page. The journey after that is improvised.
Wire these objects first: Landing page, one CTA (apply or book), thank-you page, GHL form, contact, opportunity, workflow nurture, UTM hidden fields.
Then these edges, in order: Landing CTA → GHL form write-in: contact + opportunity New inquiry · Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks · UTM hidden fields → source:* tags + custom fields on the contact · Only conversion → calendar book or complete application; clicks are not a stage
Done looks like a test you can repeat: Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other.
Start here: Write the tag spec on one page. Archive junk. Automations only fire on spec tags.
Business coaches already have GoHighLevel. The leak is not a missing feature. Traffic hits a page. The journey after that is improvised. 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: Landing page, one CTA (apply or book), thank-you page, GHL form, contact, opportunity, workflow nurture, UTM hidden fields. Then connect these edges, in order: Landing CTA → GHL form write-in: contact + opportunity New inquiry · Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks · UTM hidden fields → source:* tags + custom fields on the contact · Only conversion → calendar book or complete application; clicks are not a stage. 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. Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other. How you know it worked on the board: CTA is one (competing buttons are a leak). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Write the tag spec on one page. Archive junk. Automations only fire on spec tags. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: screenshot the page. Circle every button. There should be one conversion. Write what the thank-you must do to GHL. Do not design a second page until a test submit writes a contact.
Operator
You already feel traffic hits a page. the journey after that is improvised. Business coaches preach systems and run their own on memory. Protect one sequence for 90 days. The four moves are one cta → thank-you → same-day spine → only conversion. The edges are Landing CTA → GHL form write-in: contact + opportunity New inquiry then Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks. If a new VA cannot explain a contact in thirty seconds, you are teaching systems you do not run.
CEO
This is a money leak, not a preference about tools. A page goes live. Until cta is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Landing CTA → GHL form write-in: contact + opportunity New inquiry.
Before
Tuesday. Someone among business coaches. Business coaches preach systems and run their own on memory. 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. If a new VA cannot explain a contact in thirty seconds, you are teaching systems you do not run. Landing CTA → GHL form write-in: contact + opportunity New inquiry The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in business coaches already paid for GoHighLevel. Business coaches preach systems and run their own on memory. 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 funnel is a handoff: offer, proof, one next step. Prove write-in: Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other. This week is one move: Write the tag spec on one page. Archive junk. Automations only fire on spec tags. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
A page goes live. Traffic arrives. The thank-you is a dead end. The calendar is disconnected. Nurture is a broadcast written in a panic. That is a leak with a headline.
The system
A funnel is a handoff: offer, proof, one next step. The CRM sees the conversion the same day. Nurture starts without a human remembering. Booking or application is the only conversion that counts.
Two CTAs is not abundance. It is indecision. If 'book a call' and 'watch the VSL' compete, neither is a system. Pick the conversion that matches the price. High-ticket wants a filter. Low-ticket can take a checkout. Mixing them on one page trains the wrong buyer.
The thank-you page is not a courtesy. It is where the contact state changes and the first email is allowed to exist. If that page does not write to GHL, you paid for traffic your ops cannot see.
If a new VA cannot explain a contact in thirty seconds, you are teaching systems you do not run.
A funnel is a handoff, not a stack of pages: offer, proof, one next step. Two CTAs is indecision — book a call and watch a VSL on the same screen trains the wrong buyer. High-ticket wants a filter (application); a call is a filter too if intake exists; low-ticket can take checkout. Mixing them is how you fill a calendar with people who wanted a PDF. The landing page does not need to 'do CRM'; it needs to submit a form whose fields are the CRM.
The thank-you page is where the contact state changes. If that page does not write to GHL, you paid for traffic your ops cannot see. Wire: submit → contact + opportunity, source and offer tagged separately, workflow starts the hour they convert — not when someone remembers to import a CSV. Opens and clicks are not the business. Meetings or complete applications are. If you need a second conversion 'just to capture the tire-kickers', you are building a second database of people you will feel guilty about.
The split: page analytics say conversions, GHL is empty; or GHL is full of contacts with no opportunity; or UTMs died on the thank-you redirect. Hidden fields must survive — test with a real UTM in the URL, and if the contact has no source, the form is a vanity. Do not add a popup until the primary form writes, and do not add a webinar on the thank-you until the spine exists. One page, one write-in, one sequence: that is a coaching funnel. The rest is a brochure.
Landing page, one CTA (apply or book), thank-you page, GHL form, contact, opportunity, workflow nurture, UTM hidden fields.
Landing CTA → GHL form write-in: contact + opportunity New inquiry
Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks
UTM hidden fields → source:* tags + custom fields on the contact
Only conversion → calendar book or complete application; clicks are not a stage
Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other.
Day one: screenshot the page. Circle every button. There should be one conversion. Write what the thank-you must do to GHL. Do not design a second page until a test submit writes a contact.
Offer, proof, one next step. Application or booking — not both.
Contact created or updated. State changed. Not a dead 'thanks'.
Nurture starts the hour they convert, not when you remember.
Meetings or complete apps. Opens and clicks are not the business.
On one line, for business coaches: Traffic hits a page. The journey after that is improvised. 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.
Landing page, one CTA (apply or book), thank-you page, GHL form, contact, opportunity, workflow nurture, UTM hidden fields.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Offer, proof, one next step. Application or booking — not both. Then wire: Landing CTA → GHL form write-in: contact + opportunity New inquiry
Why: Business coaches cannot skip this edge. A funnel is a handoff, not a stack of pages: offer, proof, one next step. If it is not true, GoHighLevel is already a second database.
Done when: Landing CTA → GHL form write-in: contact + opportunity New inquiry is true on a test.
Contact created or updated. State changed. Not a dead 'thanks'. Then wire: Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks
Why: Business coaches skip this and the leak returns as a private language. The thank-you page is where the contact state changes. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks is true on a test.
Nurture starts the hour they convert, not when you remember. Then wire: UTM hidden fields → source:* tags + custom fields on the contact
Why: Business coaches feel this as Traffic hits a page. The journey after that is improvised. The split: page analytics say conversions, GHL is empty; or GHL is full of contacts with no opportunity; or UTMs died on the thank-you redirect.
Done when: UTM hidden fields → source:* tags + custom fields on the contact is true on a test.
Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at CTA (Competing buttons are a leak), then crm saw it (Thank-you writes the contact). 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.
Write the tag spec on one page. Archive junk. Automations only fire on spec tags.
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.
Landing page, one CTA (apply or book), thank-you page, GHL form, contact, opportunity, workflow nurture, UTM hidden fields.
If objects aren't named, software invents a second database.
Business coaches preach systems and run their own on memory.
Offer, proof, one next step. Application or booking — not both. Then wire: Landing CTA → GHL form write-in: contact + opportunity New inquiry
Business coaches cannot skip this edge. A funnel is a handoff, not a stack of pages: offer, proof, one next step. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how business coaches actually work — not the snapshot demo. Edge: Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks
Contact created or updated. State changed. Not a dead 'thanks'. Then wire: Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks
Business coaches skip this and the leak returns as a private language. The thank-you page is where the contact state changes. Spec tags, fields, and states have to be the same objects the next workflow will read.
If a new VA cannot explain a contact in thirty seconds, you are teaching systems you do not run.
Nurture starts the hour they convert, not when you remember. Then wire: UTM hidden fields → source:* tags + custom fields on the contact
Business coaches feel this as Traffic hits a page. The journey after that is improvised. The split: page analytics say conversions, GHL is empty; or GHL is full of contacts with no opportunity; or UTMs died on the thank-you redirect.
write the tag spec on one page. Archive junk. Automations only fire on spec tags.
Because the login already exists. A page goes live. Traffic arrives. A new feature on a missing spec is a second database. Finish this edge first: Landing CTA → GHL form write-in: contact + opportunity New inquiry.
Day one: screenshot the page. Circle every button. There should be one conversion. Write what the thank-you must do to GHL. Do not design a second page until a test submit writes a contact. 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. Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other. 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. Book / apply (Traffic without this is a hobby) is how you stop the leak returning dressed as a new feature. If two CTAs compete, neither is a system. If the thank-you page does not change the contact, you paid for traffic that your ops cannot see. Build the spine first: capture, route, remind, recover no-shows. Then argue about copy.
More leads into a leak is a more expensive leak. If a new VA cannot explain a contact in thirty seconds, you are teaching systems you do not run. Watch cta 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. Write the tag spec on one page. Archive junk. Automations only fire on spec tags. 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
Landing page, one CTA (apply or book), thank-you page, GHL form, contact, opportunity, workflow nurture, UTM hidden fields.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Landing CTA → GHL form write-in: contact + opportunity New inquiry
Skip this
Calling it done because a screenshot looks busy.
Do this
Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other.
Skip this
Leaving “Only conversion” to chance.
Do this
Meetings or complete apps. Opens and clicks are not the business.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Offer, proof, one next step. Application or booking — not both. Then prove write-in: Open the live page.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Landing CTA → GHL form write-in: contact + opportunity New inquiry 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
CTA: One. Competing buttons are a leak. 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.
CTA
One
Competing buttons are a leak
CRM saw it
Same day
Thank-you writes the contact
Book / apply
The metric
Traffic without this is a hobby
This week
write the tag spec on one page. Archive junk. Automations only fire on spec tags.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
Offer, proof, and next step sit on one page
The thank-you path is designed
Nurture starts the same day
Application or booking is the only conversion
Want the longer lesson, not the page for this niche? A CRM login is not a system ↗
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.
Business coaches do not have a Coaching funnel problem because they lack GoHighLevel. They have it because traffic hits a page. The journey after that is improvised. Wire these objects first: Landing page, one CTA (apply or book), thank-you page, GHL form, contact, opportunity, workflow nurture, UTM hidden fields. Then these edges, in order: Landing CTA → GHL form write-in: contact + opportunity New inquiry · Thank-you page → workflow Same-day spine enroll; state changed, not a dead thanks · UTM hidden fields → source:* tags + custom fields on the contact · Only conversion → calendar book or complete application; clicks are not a stage Done looks like a test you can repeat: Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other. Start here: Write the tag spec on one page. Archive junk. Automations only fire on spec tags.
A page goes live. Traffic arrives. The thank-you is a dead end. The calendar is disconnected. Nurture is a broadcast written in a panic. That is a leak with a headline. If a new VA cannot explain a contact in thirty seconds, you are teaching systems you do not run.
Before: Tuesday. Someone among business coaches. Business coaches preach systems and run their own on memory. 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. If a new VA cannot explain a contact in thirty seconds, you are teaching systems you do not run. Landing CTA → GHL form write-in: contact + opportunity New inquiry 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 cta → thank-you → same-day spine → only conversion.
CTA: One — Competing buttons are a leak. Then crm saw it (Thank-you writes the contact). If those are folklore, do not add another GoHighLevel workflow.
write the tag spec on one page. Archive junk. Automations only fire on spec tags.
Because the login already exists. A page goes live. Traffic arrives. A new feature on a missing spec is a second database. Finish this edge first: Landing CTA → GHL form write-in: contact + opportunity New inquiry.
Day one: screenshot the page. Circle every button. There should be one conversion. Write what the thank-you must do to GHL. Do not design a second page until a test submit writes a contact. 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. Open the live page. Submit as a stranger. Land on thank-you. Confirm one contact, one opportunity, UTMs present, and the first nurture email or SMS in under an hour. Competing CTAs on the page fail the test — pick one and delete the other. 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 ↗The quiz converts. The follow-up is a spreadsheet.
Read ↗Booked calls leak because the CRM never saw them.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.