Intern
What you actually do
Run steps 01 and 02 this week. Do not add a feature. Write the real steps a person takes. Discovery booked, held, proposal out, paid — not moods.
Library / Guides / A CRM login is not a system
If a new hire needs a story to explain a contact, you do not have a CRM. You have a filing cabinet with anxiety on top. This is the first lesson — for interns who just got admin access and for CEOs who just paid the annual invoice.
A system is four boring things: stages that mean work, fields that mean one thing, forms that write to those fields, and a weekly number someone will defend. Until those exist, more pages are decoration.
A system is four boring things: stages that mean work, fields that mean one thing, forms that write to those fields, and a weekly number someone will defend. Until those exist, more pages are decoration.
Start on paper. List how a person actually goes from first touch to paid. Those steps are stages. 'Hot' is not a stage. Then connect calendars and forms so they create the same contact. Then one short sequence. Then stop.
The CEO question is not 'do we have GoHighLevel?' It is 'can we name show rate, time-to-first-message, and what won requires?' If the answer is a story, the invoice is a login fee.
Intern
Run steps 01 and 02 this week. Do not add a feature. Write the real steps a person takes. Discovery booked, held, proposal out, paid — not moods.
Operator
Protect the sequence. Start on paper. List how a person actually goes from first touch to paid. Those steps are stages. 'Hot' is not a stage. Then connect calendars and forms so they create the same contact. Then one short sequence. Then stop.
CEO
Do not fund more traffic or more seats until the scoreboard in this lesson is a number you will defend. The CEO question is not 'do we have GoHighLevel?' It is 'can we name show rate, time-to-first-message, and what won requires?' If the answer is a story, the invoice is a login fee.
Write the real steps a person takes. Discovery booked, held, proposal out, paid — not moods.
Why: Software cannot invent how you sell. If you skip this, every automation is a guess.
Done when: A stranger can audit a card without asking Slack.
Three axes. Never one tag that tries to be all three.
Why: Reporting lies when one string means three jobs.
Done when: You can filter 'Google + high-ticket + customer' without folklore.
Submit a test form and book a test call. Watch the contact.
Why: If the calendar is full and the pipeline is empty, you built a second database.
Done when: One real conversion lands on the right stage.
Five emails or SMS. One job each. A human on replies.
Why: A second funnel before a first sequence is how teams stay busy and unbooked.
Done when: Nurture starts without a hero remembering.
Write-in %, show rate, time to first sequence.
Why: What is not reviewed returns as a new tool request.
Done when: Fifteen minutes. One action or 'hold'.
Do not build a workflow. Sit with whoever sells. Write the steps. Circle where the CRM currently lies. That document is the product of week one.
Another landing page, another seat, another AI add-on, until write-in is 100% on test conversions. Tools on a missing spec make reporting worse, not better.
A sub-account opens. Pipelines are snapshot defaults. Calendly may or may not write a contact. Tags exist from a demo. Nobody can say what 'won' requires. That is a login.
The snapshot is someone else's sale map. Your stages will not match. You will spend months renaming moods.
A list without exit rules is a pile. Importing multiplies junk tags. Archive first, then spec, then automate.
Revenue hides leaks until a hire leaves, a location drifts, or ads get more expensive. The spec is cheap now.
The CRM is open. The operating system is not.
Open the playbook ↗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.