Intern
What you actually do
Day one: list program states. List which spines exist. Write how launch and evergreen coexist (exclusions). Do not write launch copy. Open replies ownership. Glance at bounces.
Library / academies / Academy email system
Bootcamps have urgency. Their CRM usually does not.
Read it once, then stop negotiating with it. Academy email system for bootcamp brands is a wiring job: evergreen → launch pulse → state segments → replies. 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.
Bootcamp brands do not have a Academy email system problem because they lack GHL email. They have it because you paid for a CRM. You still write one-off launches.
Wire these objects first: Evergreen workflow spines, launch campaigns, deliverability metrics, segments by program state, Conversations for replies, GHL email domain.
Then these edges, in order: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter · Evergreen spine → always on; launch campaign excludes in-spine where they collide · Reply → Conversations human; launches do not send from a no-reply hole · Deliverability watch → bounces/complaints weekly; launch does not skip hygiene
Done looks like a test you can repeat: Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned.
Start here: Operationally true dates. Application CTA. Sales sees who started an app.
Bootcamp brands already have GHL email. The leak is not a missing feature. You paid for a CRM. You still write one-off launches. 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: Evergreen workflow spines, launch campaigns, deliverability metrics, segments by program state, Conversations for replies, GHL email domain. Then connect these edges, in order: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter · Evergreen spine → always on; launch campaign excludes in-spine where they collide · Reply → Conversations human; launches do not send from a no-reply hole · Deliverability watch → bounces/complaints weekly; launch does not skip hygiene. If you skip an edge, the next one is decoration. If you add a GHL email feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned. How you know it worked on the board: Two calendars is coexist (evergreen + launch). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Operationally true dates. Application CTA. Sales sees who started an app. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: list program states. List which spines exist. Write how launch and evergreen coexist (exclusions). Do not write launch copy. Open replies ownership. Glance at bounces.
Operator
You already feel you paid for a crm. you still write one-off launches. Bootcamps have urgency. Their CRM usually does not. Protect one sequence for 90 days. The four moves are evergreen → launch pulse → state segments → replies. The edges are Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter then Evergreen spine → always on; launch campaign excludes in-spine where they collide. If scarcity is a copy line and the calendar is always open, serious buyers feel it.
CEO
This is a money leak, not a preference about tools. You paid for a CRM. Until two calendars is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter.
Before
Tuesday. Someone among bootcamp brands. Bootcamps have urgency. Their CRM usually does not. GHL email 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 scarcity is a copy line and the calendar is always open, serious buyers feel it. Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in bootcamp brands already paid for GHL email. Bootcamps have urgency. Their CRM usually does not. 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. Evergreen and launch coexist. Prove write-in: Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned. This week is one move: Operationally true dates. Application CTA. Sales sees who started an app. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
You paid for a CRM. You still write one-off launches. Evergreen and launch smash each other. Deliverability is unwatched. Replies hit a void.
The system
Evergreen and launch coexist. Deliverability is watched. Segments match program state. Replies hit a human.
The spine is evergreen: inquiry, apply, waitlist, onboard, alumni. Launch is a pulse on top with suppressions. If every email is a hero launch, you have no system — only seasons of shouting.
Segments are states: applicant, seated, paused, alumni. Everyone who ever opted in is how you destroy the domain and the offer at once.
If scarcity is a copy line and the calendar is always open, serious buyers feel it.
You paid for a CRM; you still write one-off launches when evergreen and launch cannot coexist as objects. Segments match program state. Deliverability is watched so a launch does not torch the domain, and replies hit a human. Evergreen does the state work (applicant nurture, onboarding, alumni); launch does the calendar work (cohort open). If launch is how you do everything, you do not have an email system — you have a panic muscle.
Wire exclusions both ways: students do not get 'apply now'; waitlist does not get homework login mail. Custom fields for cohort and start date drive the merge. One from-name and domain. If founders still send from Gmail, you have two senders and one reputation problem. UTMs on launch links write back on apply.
Two databases: GHL email and a founder's ConvertKit 'just for this launch'. Kill the side sender or you will never know the list. The intern maintains exclusion lists and the reply inbox shift. They do not 'craft the sequence' on day one. If complaints spike at launch, the list was the wrong object, not the subject line.
Evergreen workflow spines, launch campaigns, deliverability metrics, segments by program state, Conversations for replies, GHL email domain.
Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter
Evergreen spine → always on; launch campaign excludes in-spine where they collide
Reply → Conversations human; launches do not send from a no-reply hole
Deliverability watch → bounces/complaints weekly; launch does not skip hygiene
Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned.
Day one: list program states. List which spines exist. Write how launch and evergreen coexist (exclusions). Do not write launch copy. Open replies ownership. Glance at bounces.
A spine that runs in the quiet months.
On top. Suppressions so it does not smash the spine.
Program state, not one list.
A human. Deliverability watched weekly.
On one line, for bootcamp brands: You paid for a CRM. You still write one-off launches. 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.
Evergreen workflow spines, launch campaigns, deliverability metrics, segments by program state, Conversations for replies, GHL email domain.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
A spine that runs in the quiet months. Then wire: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter
Why: Bootcamp brands cannot skip this edge. You paid for a CRM; you still write one-off launches when evergreen and launch cannot coexist as objects. If it is not true, GHL email is already a second database.
Done when: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter is true on a test.
On top. Suppressions so it does not smash the spine. Then wire: Evergreen spine → always on; launch campaign excludes in-spine where they collide
Why: Bootcamp brands skip this and the leak returns as a private language. Wire exclusions both ways: students do not get 'apply now'; waitlist does not get homework login mail. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Evergreen spine → always on; launch campaign excludes in-spine where they collide is true on a test.
Program state, not one list. Then wire: Reply → Conversations human; launches do not send from a no-reply hole
Why: Bootcamp brands feel this as You paid for a CRM. You still write one-off launches. Two databases: GHL email and a founder's ConvertKit 'just for this launch'.
Done when: Reply → Conversations human; launches do not send from a no-reply hole is true on a test.
Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Two calendars (Evergreen + launch), then domain (Complaints, bounce, sunset). 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.
Operationally true dates. Application CTA. Sales sees who started an app.
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.
Evergreen workflow spines, launch campaigns, deliverability metrics, segments by program state, Conversations for replies, GHL email domain.
If objects aren't named, software invents a second database.
Bootcamps have urgency. Their CRM usually does not.
A spine that runs in the quiet months. Then wire: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter
Bootcamp brands cannot skip this edge. You paid for a CRM; you still write one-off launches when evergreen and launch cannot coexist as objects. If it is not true, GHL email is already a second database.
On GHL email, this means the data model matches how bootcamp brands actually work — not the snapshot demo. Edge: Evergreen spine → always on; launch campaign excludes in-spine where they collide
On top. Suppressions so it does not smash the spine. Then wire: Evergreen spine → always on; launch campaign excludes in-spine where they collide
Bootcamp brands skip this and the leak returns as a private language. Wire exclusions both ways: students do not get 'apply now'; waitlist does not get homework login mail. Spec tags, fields, and states have to be the same objects the next workflow will read.
If scarcity is a copy line and the calendar is always open, serious buyers feel it.
Program state, not one list. Then wire: Reply → Conversations human; launches do not send from a no-reply hole
Bootcamp brands feel this as You paid for a CRM. You still write one-off launches. Two databases: GHL email and a founder's ConvertKit 'just for this launch'.
operationally true dates. Application CTA. Sales sees who started an app.
Because the login already exists. You paid for a CRM. You still write one-off launches. A new feature on a missing spec is a second database. Finish this edge first: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter.
Day one: list program states. List which spines exist. Write how launch and evergreen coexist (exclusions). Do not write launch copy. Open replies ownership. Glance at bounces. 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. Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned. 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. Replies (Or the spine is a monologue) is how you stop the leak returning dressed as a new feature. The room is not the business. The week after is. Same-day notes, a no-show path that is not the attendee path, UTMs that survive, proof packaged for the person who paid. Reuse the calendar. Do not hero-mode every event.
More leads into a leak is a more expensive leak. If scarcity is a copy line and the calendar is always open, serious buyers feel it. Watch two calendars 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. Operationally true dates. Application CTA. Sales sees who started an app. That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because GHL email is “set up”.
Do this
Evergreen workflow spines, launch campaigns, deliverability metrics, segments by program state, Conversations for replies, GHL email domain.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter
Skip this
Calling it done because a screenshot looks busy.
Do this
Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned.
Skip this
Leaving “Replies” to chance.
Do this
A human. Deliverability watched weekly.
The usual miss
Calling GHL email “set up” because someone logged in and imported a snapshot.
Do this instead
A spine that runs in the quiet months. Then prove write-in: Enroll a student-state test contact and a waitlist contact.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter 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
Two calendars: Coexist. Evergreen + launch. 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.
Two calendars
Coexist
Evergreen + launch
Domain
Watched
Complaints, bounce, sunset
Replies
Human
Or the spine is a monologue
This week
operationally true dates. Application CTA. Sales sees who started an app.
UK operators · UK hours. The CRM is often inherited from an agency; the spec still has to be written here.
Evergreen + launch can coexist
Deliverability is watched
Segments match program state
Replies hit a human
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.
Bootcamp brands do not have a Academy email system problem because they lack GHL email. They have it because you paid for a CRM. You still write one-off launches. Wire these objects first: Evergreen workflow spines, launch campaigns, deliverability metrics, segments by program state, Conversations for replies, GHL email domain. Then these edges, in order: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter · Evergreen spine → always on; launch campaign excludes in-spine where they collide · Reply → Conversations human; launches do not send from a no-reply hole · Deliverability watch → bounces/complaints weekly; launch does not skip hygiene Done looks like a test you can repeat: Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned. Start here: Operationally true dates. Application CTA. Sales sees who started an app.
You paid for a CRM. You still write one-off launches. Evergreen and launch smash each other. Deliverability is unwatched. Replies hit a void. If scarcity is a copy line and the calendar is always open, serious buyers feel it.
Before: Tuesday. Someone among bootcamp brands. Bootcamps have urgency. Their CRM usually does not. GHL email 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 scarcity is a copy line and the calendar is always open, serious buyers feel it. Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because GHL email is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: evergreen → launch pulse → state segments → replies.
Two calendars: Coexist — Evergreen + launch. Then domain (Complaints, bounce, sunset). If those are folklore, do not add another GHL email workflow.
operationally true dates. Application CTA. Sales sees who started an app.
Because the login already exists. You paid for a CRM. You still write one-off launches. A new feature on a missing spec is a second database. Finish this edge first: Program state (waitlist, applicant, student, alumni) → segment; campaigns must filter.
Day one: list program states. List which spines exist. Write how launch and evergreen coexist (exclusions). Do not write launch copy. Open replies ownership. Glance at bounces. 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. Enroll a student-state test contact and a waitlist contact. Send a test launch campaign. Student must be excluded if the campaign is acquire. Reply from waitlist; confirm a human sees it. Check domain auth is still aligned. 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 ↗Booked calls leak because the CRM never saw them.
Read ↗Broadcasts exist. A sequence that earns the next conversation does not.
Read ↗Conversations die in DMs.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.