Library / franchise systems / Pipeline design
Advisor networks need routing and snapshots, not a shared spreadsheet.
Read it once, then stop negotiating with it. Pipeline design for advisor networks is a wiring job: jobs → lost → owner → review. 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.
Advisor networks do not have a Pipeline design problem because they lack GoHighLevel. They have it because stages are labels. Nobody knows what 'won' requires.
Wire these objects first: Pipeline, stage (job + exit rule), opportunity, lost reason custom field, owner (user), contact, reporting view.
Then these edges, in order: Stage Discovery booked → exit rule: event held or no-show tagged the same day · Stage Proposal out → custom field proposal_sent_on + document link on the contact · Stage Lost → lost_reason required; opportunity cannot sit in Lost with a blank reason · Won → contact status customer; owner remains the closer, not 'unassigned'
Done looks like a test you can repeat: Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at.
Start here: Routing rules in writing. Overflow defined. Speed-to-lead measured.
Advisor networks already have GoHighLevel. The leak is not a missing feature. Stages are labels. Nobody knows what 'won' requires. 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: Pipeline, stage (job + exit rule), opportunity, lost reason custom field, owner (user), contact, reporting view. Then connect these edges, in order: Stage Discovery booked → exit rule: event held or no-show tagged the same day · Stage Proposal out → custom field proposal_sent_on + document link on the contact · Stage Lost → lost_reason required; opportunity cannot sit in Lost with a blank reason · Won → contact status customer; owner remains the closer, not 'unassigned'. 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. Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at. How you know it worked on the board: Exit rules is all stages (if it cannot be audited, it is a mood). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Routing rules in writing. Overflow defined. Speed-to-lead measured. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: do not add a workflow. Write stages as jobs with one exit rule each. Ban temperature words (hot, warm, nurture) as stages. Name the owner role per stage. List lost reasons (five is enough). Put that page in the sub-account description or a pinned note.
Operator
You already feel stages are labels. nobody knows what 'won' requires. Advisor networks need routing and snapshots, not a shared spreadsheet. Protect one sequence for 90 days. The four moves are jobs → lost → owner → review. The edges are Stage Discovery booked → exit rule: event held or no-show tagged the same day then Stage Proposal out → custom field proposal_sent_on + document link on the contact. Stolen leads are a culture story until they are a visible event in the CRM.
CEO
This is a money leak, not a preference about tools. Stages were copied from a template. Until exit rules is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Stage Discovery booked → exit rule: event held or no-show tagged the same day.
Before
Tuesday. Someone among advisor networks. Advisor networks need routing and snapshots, not a shared spreadsheet. 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. Stolen leads are a culture story until they are a visible event in the CRM. Stage Discovery booked → exit rule: event held or no-show tagged the same day The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in advisor networks already paid for GoHighLevel. Advisor networks need routing and snapshots, not a shared spreadsheet. 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 pipeline is a set of jobs. Prove write-in: Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at. This week is one move: Routing rules in writing. Overflow defined. Speed-to-lead measured. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Stages were copied from a template. 'Won' is a feeling. Lost is optional. Two people can move the same contact for opposite reasons. The dashboard is a screenshot nobody will defend in a meeting.
The system
A pipeline is a set of jobs. Each stage has an exit rule, an owner, and a next action. Lost has reasons. Reporting can be trusted because the definitions are shared — not because the chart is pretty.
Name stages as work, not temperature. Discovery booked, discovery held, proposal out, verbal yes, paid — those can be audited. 'Warm' cannot. If a new hire needs a story to explain a card, the stage is a mood.
Capture lost on purpose. Without lost reasons you will keep buying the same traffic and calling it a funnel problem. Review the board weekly against the rules, not against hope.
Stolen leads are a culture story until they are a visible event in the CRM.
A pipeline is not a set of labels — it is a set of jobs. Discovery booked means an event exists; discovery held means the call happened; proposal out means a dated artifact left the building; verbal yes is not paid; paid is Won. If a new hire needs a story to explain why a card sits in a stage, the stage is a mood and reporting will be theatre. Write the exit rule under the stage name as if you will audit it on Monday. 'Moved when they feel ready' is not an exit rule; 'moved when the Calendly event with type Discovery is marked held, or when no-show is tagged' is.
Lost is a first-class stage, not a delete: without lost reasons you will buy the same traffic twice and call it a funnel problem. The opportunity should not be allowed to enter Lost with an empty lost_reason. Owners must be unambiguous — one user (or one role) moves the card, because two owners is how cards rot. Time-in-stage is the real backlog — a proposal sitting fourteen days is work, not a vibe. Wire the stage names to the objects that prove them: calendar events, custom fields, payments. If Won can be clicked without a payment or signed agreement field, Won is a feeling.
The split into two databases is almost always this: the calendar or inbox is the real pipeline, and GHL is a screenshot — or two pipelines exist for the same offer because someone duplicated 'just in case'. Pick one pipeline per offer motion. If you sell a workshop and a retained sprint, those can be two pipelines because they are different jobs; if you sell one coaching offer with two personalities on the team, that is still one pipeline. Review Monday: counts, time-in-stage, lost reasons. If the numbers need a story, the stages are still moods — fix the names before you add a dashboard.
Pipeline, stage (job + exit rule), opportunity, lost reason custom field, owner (user), contact, reporting view.
Stage Discovery booked → exit rule: event held or no-show tagged the same day
Stage Proposal out → custom field proposal_sent_on + document link on the contact
Stage Lost → lost_reason required; opportunity cannot sit in Lost with a blank reason
Won → contact status customer; owner remains the closer, not 'unassigned'
Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at.
Day one: do not add a workflow. Write stages as jobs with one exit rule each. Ban temperature words (hot, warm, nurture) as stages. Name the owner role per stage. List lost reasons (five is enough). Put that page in the sub-account description or a pinned note.
Stages named as work. Exit rule written under each.
Lost is a stage with reasons. Optional lost is fiction.
One human (or one role) moves the card. Ambiguous owners stall.
Monday: counts by stage, time-in-stage, lost reasons. Actions attach.
On one line, for advisor networks: Stages are labels. Nobody knows what 'won' requires. 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.
Pipeline, stage (job + exit rule), opportunity, lost reason custom field, owner (user), contact, reporting view.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Stages named as work. Exit rule written under each. Then wire: Stage Discovery booked → exit rule: event held or no-show tagged the same day
Why: Advisor networks cannot skip this edge. A pipeline is not a set of labels — it is a set of jobs. If it is not true, GoHighLevel is already a second database.
Done when: Stage Discovery booked → exit rule: event held or no-show tagged the same day is true on a test.
Lost is a stage with reasons. Optional lost is fiction. Then wire: Stage Proposal out → custom field proposal_sent_on + document link on the contact
Why: Advisor networks skip this and the leak returns as a private language. Lost is a first-class stage, not a delete: without lost reasons you will buy the same traffic twice and call it a funnel problem. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Stage Proposal out → custom field proposal_sent_on + document link on the contact is true on a test.
One human (or one role) moves the card. Ambiguous owners stall. Then wire: Stage Lost → lost_reason required; opportunity cannot sit in Lost with a blank reason
Why: Advisor networks feel this as Stages are labels. Nobody knows what 'won' requires. The split into two databases is almost always this: the calendar or inbox is the real pipeline, and GHL is a screenshot — or two pipelines exist for the same offer because someone duplicated 'just in case'.
Done when: Stage Lost → lost_reason required; opportunity cannot sit in Lost with a blank reason is true on a test.
Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Exit rules (If it cannot be audited, it is a mood), then lost captured (Otherwise you repeat the same leak). 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.
Routing rules in writing. Overflow defined. Speed-to-lead measured.
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.
Pipeline, stage (job + exit rule), opportunity, lost reason custom field, owner (user), contact, reporting view.
If objects aren't named, software invents a second database.
Advisor networks need routing and snapshots, not a shared spreadsheet.
Stages named as work. Exit rule written under each. Then wire: Stage Discovery booked → exit rule: event held or no-show tagged the same day
Advisor networks cannot skip this edge. A pipeline is not a set of labels — it is a set of jobs. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how advisor networks actually work — not the snapshot demo. Edge: Stage Proposal out → custom field proposal_sent_on + document link on the contact
Lost is a stage with reasons. Optional lost is fiction. Then wire: Stage Proposal out → custom field proposal_sent_on + document link on the contact
Advisor networks skip this and the leak returns as a private language. Lost is a first-class stage, not a delete: without lost reasons you will buy the same traffic twice and call it a funnel problem. Spec tags, fields, and states have to be the same objects the next workflow will read.
Stolen leads are a culture story until they are a visible event in the CRM.
One human (or one role) moves the card. Ambiguous owners stall. Then wire: Stage Lost → lost_reason required; opportunity cannot sit in Lost with a blank reason
Advisor networks feel this as Stages are labels. Nobody knows what 'won' requires. The split into two databases is almost always this: the calendar or inbox is the real pipeline, and GHL is a screenshot — or two pipelines exist for the same offer because someone duplicated 'just in case'.
routing rules in writing. Overflow defined. Speed-to-lead measured.
Because the login already exists. Stages were copied from a template. 'Won' is a feeling. A new feature on a missing spec is a second database. Finish this edge first: Stage Discovery booked → exit rule: event held or no-show tagged the same day.
Day one: do not add a workflow. Write stages as jobs with one exit rule each. Ban temperature words (hot, warm, nurture) as stages. Name the owner role per stage. List lost reasons (five is enough). Put that page in the sub-account description or a pinned note. 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. Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at. 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. Time in stage (Cards that rot are the real backlog) is how you stop the leak returning dressed as a new feature. Start with how you actually sell, not with how the snapshot was demoed. Name stages as jobs, not moods. Separate source, offer, and status. If a new hire cannot explain a contact in thirty seconds, you do not have an operating system — you have a database with anxiety on top.
More leads into a leak is a more expensive leak. Stolen leads are a culture story until they are a visible event in the CRM. Watch exit rules 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. Routing rules in writing. Overflow defined. Speed-to-lead measured. 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
Pipeline, stage (job + exit rule), opportunity, lost reason custom field, owner (user), contact, reporting view.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Stage Discovery booked → exit rule: event held or no-show tagged the same day
Skip this
Calling it done because a screenshot looks busy.
Do this
Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at.
Skip this
Leaving “Review” to chance.
Do this
Monday: counts by stage, time-in-stage, lost reasons. Actions attach.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Stages named as work. Exit rule written under each. Then prove write-in: Create a test opportunity.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Stage Discovery booked → exit rule: event held or no-show tagged the same day 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
Exit rules: All stages. If it cannot be audited, it is a mood. 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.
Exit rules
All stages
If it cannot be audited, it is a mood
Lost captured
Required
Otherwise you repeat the same leak
Time in stage
Watched
Cards that rot are the real backlog
This week
routing rules in writing. Overflow defined. Speed-to-lead measured.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
Every stage has an exit rule
Lost reasons are captured
Owners are unambiguous
Reporting can be trusted weekly
Want the longer lesson, not the page for this niche? Pipeline stages are jobs ↗
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.
Advisor networks do not have a Pipeline design problem because they lack GoHighLevel. They have it because stages are labels. Nobody knows what 'won' requires. Wire these objects first: Pipeline, stage (job + exit rule), opportunity, lost reason custom field, owner (user), contact, reporting view. Then these edges, in order: Stage Discovery booked → exit rule: event held or no-show tagged the same day · Stage Proposal out → custom field proposal_sent_on + document link on the contact · Stage Lost → lost_reason required; opportunity cannot sit in Lost with a blank reason · Won → contact status customer; owner remains the closer, not 'unassigned' Done looks like a test you can repeat: Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at. Start here: Routing rules in writing. Overflow defined. Speed-to-lead measured.
Stages were copied from a template. 'Won' is a feeling. Lost is optional. Two people can move the same contact for opposite reasons. The dashboard is a screenshot nobody will defend in a meeting. Stolen leads are a culture story until they are a visible event in the CRM.
Before: Tuesday. Someone among advisor networks. Advisor networks need routing and snapshots, not a shared spreadsheet. 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. Stolen leads are a culture story until they are a visible event in the CRM. Stage Discovery booked → exit rule: event held or no-show tagged the same day 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: jobs → lost → owner → review.
Exit rules: All stages — If it cannot be audited, it is a mood. Then lost captured (Otherwise you repeat the same leak). If those are folklore, do not add another GoHighLevel workflow.
routing rules in writing. Overflow defined. Speed-to-lead measured.
Because the login already exists. Stages were copied from a template. 'Won' is a feeling. A new feature on a missing spec is a second database. Finish this edge first: Stage Discovery booked → exit rule: event held or no-show tagged the same day.
Day one: do not add a workflow. Write stages as jobs with one exit rule each. Ban temperature words (hot, warm, nurture) as stages. Name the owner role per stage. List lost reasons (five is enough). Put that page in the sub-account description or a pinned note. 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. Create a test opportunity. Move it through every stage. At Lost, the UI must demand a reason. At Won, open the contact and confirm status flipped. Then open the pipeline report: counts by stage must match the board you are staring at. 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 ↗The quiz converts. The follow-up is a spreadsheet.
Read ↗Traffic hits a page. The journey after that is improvised.
Read ↗Conversations die in DMs.
Read ↗Outbound is a tool. The pipeline is a vibe.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.