Won. Then Google Drive, a Notion page, and a kickoff that starts from zero because none of the sales notes made it over. Renewal is a cold email in month eleven.
Read it once, then stop negotiating with it. Delivery CRM for coaches is a wiring job: split → kickoff → notes → renewal. 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.
Coaches do not have a Delivery CRM problem because they lack GoHighLevel. They have it because won is the finish line. Delivery then lives in Google Drive.
Wire these objects first: Customer vs prospect split, kickoff stage+date, delivery notes, renewal next date, GHL opportunity (delivery pipeline), files linked, owner.
Then these edges, in order: Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date · Kickoff held → notes write back; delivery milestones as stages or dated fields · Delivery notes → on the contact/opportunity, not only Google Drive · Renewal next date → field + workflow; Won is not the finish line
Done looks like a test you can repeat: Mark a test Won. Confirm they leave prospect blasts and a kickoff exists. Write a delivery note. Set a renewal date; confirm it is visible. If delivery lives in Drive with no dates in GHL, fail.
Start here: Customer vs prospect is a hard split
Coaches already have GoHighLevel. The leak is not a missing feature. Won is the finish line. Delivery then lives in Google Drive. 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: Customer vs prospect split, kickoff stage+date, delivery notes, renewal next date, GHL opportunity (delivery pipeline), files linked, owner. Then connect these edges, in order: Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date · Kickoff held → notes write back; delivery milestones as stages or dated fields · Delivery notes → on the contact/opportunity, not only Google Drive · Renewal next date → field + workflow; Won is not the finish line. 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. Mark a test Won. Confirm they leave prospect blasts and a kickoff exists. Write a delivery note. Set a renewal date; confirm it is visible. If delivery lives in Drive with no dates in GHL, fail. How you know it worked on the board: Kickoff dated is won + 7d (or delivery starts from folklore). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Customer vs prospect is a hard split An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: Won is the finish line, delivery lives in Google Drive — that is the leak. Customer vs prospect hard split. Kickoff as a stage with a date. Notes write back. Renewal next date. Do not add a PM tool until GHL has the dates.
Operator
You already feel won is the finish line. delivery then lives in google drive. Won is the finish line. Delivery then lives in Google Drive. Protect one sequence for 90 days. The four moves are split → kickoff → notes → renewal. The edges are Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date then Kickoff held → notes write back; delivery milestones as stages or dated fields. Prospect and customer are different pipelines. Kickoff is a stage with a date. Delivery notes write on the same contact. Renewal has a next date from day one of delivery.
CEO
This is a money leak, not a preference about tools. Won. Until kickoff dated is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date.
Before
Tuesday. Someone among coaches. Won is the finish line. Delivery then lives in Google Drive. 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. Prospect and customer are different pipelines. Kickoff is a stage with a date. Delivery notes write on the same contact. Renewal has a next date from day one of delivery. Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in coaches already paid for GoHighLevel. Won is the finish line. Delivery then lives in Google Drive. 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. Prospect and customer are different pipelines. Prove write-in: Mark a test Won. Confirm they leave prospect blasts and a kickoff exists. Write a delivery note. Set a renewal date; confirm it is visible. If delivery lives in Drive with no dates in GHL, fail. This week is one move: Customer vs prospect is a hard split If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Won. Then Google Drive, a Notion page, and a kickoff that starts from zero because none of the sales notes made it over. Renewal is a cold email in month eleven.
The system
Prospect and customer are different pipelines. Kickoff is a stage with a date. Delivery notes write on the same contact. Renewal has a next date from day one of delivery.
Do not keep delivery in a second database. When a card is won, it moves — or a linked customer pipeline opens — with the notes, the offer, and the kickoff date already on it.
Put the next renewal or review date on the account the week they pay. If that field is empty, you will scramble in month eleven and call it 'relationship work.'
Prospect and customer are different pipelines. Kickoff is a stage with a date. Delivery notes write on the same contact. Renewal has a next date from day one of delivery.
Won is the finish line in a leaky shop; delivery then lives in Google Drive. Customer vs prospect is a hard split. Kickoff is a stage with a date, delivery notes write back, and renewal has a next date. Drive can hold files; it cannot be the only place status lives. If the only owner of delivery is a freelancer's Notion, the company cannot renew.
Wire a delivery pipeline or delivery stages on the same opportunity — pick one and write it. Customers do not get 'book a discovery' mail. Kickoff uses intake if you have it. Milestones that matter (assets in, launched, first review) are stages with exit rules, not vibes. Time-in-stage still applies. A delivery that sits is work, not 'they're on pause'.
Two databases: Drive/Notion and GHL. Put dates and status in GHL; put files in Drive with links on the record. The intern creates a Won test and walks kickoff. They do not reorganize folders first. Folders without a kickoff date are still a leak, just tidier. Renewal is a field you will thank later.
Customer vs prospect split, kickoff stage+date, delivery notes, renewal next date, GHL opportunity (delivery pipeline), files linked, owner.
Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date
Kickoff held → notes write back; delivery milestones as stages or dated fields
Delivery notes → on the contact/opportunity, not only Google Drive
Renewal next date → field + workflow; Won is not the finish line
Mark a test Won. Confirm they leave prospect blasts and a kickoff exists. Write a delivery note. Set a renewal date; confirm it is visible. If delivery lives in Drive with no dates in GHL, fail.
Day one: Won is the finish line, delivery lives in Google Drive — that is the leak. Customer vs prospect hard split. Kickoff as a stage with a date. Notes write back. Renewal next date. Do not add a PM tool until GHL has the dates.
Prospect vs customer. Hard. Not a tag that means both.
A stage with a date. Automatic access if there is a product.
Sales notes visible to delivery. Same contact.
Next date on day one. Not in month eleven.
On one line, for coaches: Won is the finish line. Delivery then lives in Google Drive. 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.
Customer vs prospect split, kickoff stage+date, delivery notes, renewal next date, GHL opportunity (delivery pipeline), files linked, owner.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Prospect vs customer. Hard. Not a tag that means both. Then wire: Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date
Why: Coaches cannot skip this edge. Won is the finish line in a leaky shop; delivery then lives in Google Drive. If it is not true, GoHighLevel is already a second database.
Done when: Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date is true on a test.
A stage with a date. Automatic access if there is a product. Then wire: Kickoff held → notes write back; delivery milestones as stages or dated fields
Why: Coaches skip this and the leak returns as a private language. Wire a delivery pipeline or delivery stages on the same opportunity — pick one and write it. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Kickoff held → notes write back; delivery milestones as stages or dated fields is true on a test.
Sales notes visible to delivery. Same contact. Then wire: Delivery notes → on the contact/opportunity, not only Google Drive
Why: Coaches feel this as Won is the finish line. Delivery then lives in Google Drive. Two databases: Drive/Notion and GHL.
Done when: Delivery notes → on the contact/opportunity, not only Google Drive is true on a test.
Mark a test Won. Confirm they leave prospect blasts and a kickoff exists. Write a delivery note. Set a renewal date; confirm it is visible. If delivery lives in Drive with no dates in GHL, fail.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Kickoff dated (Or delivery starts from folklore), then renewal field (The week they pay). 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.
Customer vs prospect is a hard split
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.
Customer vs prospect split, kickoff stage+date, delivery notes, renewal next date, GHL opportunity (delivery pipeline), files linked, owner.
If objects aren't named, software invents a second database.
Won is the finish line. Delivery then lives in Google Drive.
Prospect vs customer. Hard. Not a tag that means both. Then wire: Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date
Coaches cannot skip this edge. Won is the finish line in a leaky shop; delivery then lives in Google Drive. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how coaches actually work — not the snapshot demo. Edge: Kickoff held → notes write back; delivery milestones as stages or dated fields
A stage with a date. Automatic access if there is a product. Then wire: Kickoff held → notes write back; delivery milestones as stages or dated fields
Coaches skip this and the leak returns as a private language. Wire a delivery pipeline or delivery stages on the same opportunity — pick one and write it. Spec tags, fields, and states have to be the same objects the next workflow will read.
Prospect and customer are different pipelines. Kickoff is a stage with a date. Delivery notes write on the same contact. Renewal has a next date from day one of delivery.
Sales notes visible to delivery. Same contact. Then wire: Delivery notes → on the contact/opportunity, not only Google Drive
Coaches feel this as Won is the finish line. Delivery then lives in Google Drive. Two databases: Drive/Notion and GHL.
Customer vs prospect is a hard split
Because the login already exists. Won. Then Google Drive, a Notion page, and a kickoff that starts from zero because none of the sales notes made it over. A new feature on a missing spec is a second database. Finish this edge first: Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date.
Day one: Won is the finish line, delivery lives in Google Drive — that is the leak. Customer vs prospect hard split. Kickoff as a stage with a date. Notes write back. Renewal next date. Do not add a PM tool until GHL has the dates. 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. Mark a test Won. Confirm they leave prospect blasts and a kickoff exists. Write a delivery note. Set a renewal date; confirm it is visible. If delivery lives in Drive with no dates in GHL, fail. 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. Second database (Drive is not a CRM) 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. Prospect and customer are different pipelines. Kickoff is a stage with a date. Delivery notes write on the same contact. Renewal has a next date from day one of delivery. Watch kickoff dated 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. Customer vs prospect is a hard split 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
Customer vs prospect split, kickoff stage+date, delivery notes, renewal next date, GHL opportunity (delivery pipeline), files linked, owner.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date
Skip this
Calling it done because a screenshot looks busy.
Do this
Mark a test Won. Confirm they leave prospect blasts and a kickoff exists. Write a delivery note. Set a renewal date; confirm it is visible. If delivery lives in Drive with no dates in GHL, fail.
Skip this
Leaving “Renewal” to chance.
Do this
Next date on day one. Not in month eleven.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Prospect vs customer. Hard. Not a tag that means both. Then prove write-in: Mark a test Won.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Won → customer status; prospect nurture excludes them; delivery pipeline opens with kickoff date 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
Kickoff dated: Won + 7d. Or delivery starts from folklore. 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.
Kickoff dated
Won + 7d
Or delivery starts from folklore
Renewal field
Filled
The week they pay
Second database
None
Drive is not a CRM
This week
Customer vs prospect is a hard split
Customer vs prospect is a hard split
Kickoff is a stage with a date
Delivery notes write back
Renewal has a next date
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.
Delivery CRM does not split by niche and city. The wiring is the same: objects, edges, one test conversion. Read a connect map if two tools are already in the stack, or a vertical essay if the language needs to change.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗Senior operators will not wait on a messy CRM while the calendar fills with the wrong calls.
Read ↗Day 0–7 after payment predicts completion more than the curriculum does.
Read ↗Busy and unbooked at the same time is a missing next-date object, not a marketing problem.
Read ↗Email and WhatsApp stay open. A call is for installing the system.