Intern
What you actually do
Day one: separate sources on paper (inbound form, purchased list, partner, LinkedIn). Draw two sequences max. Write who approves outbound before anything leaves. Do not connect a scraper.
Outbound is a tool. The pipeline is a vibe.
Read it once, then stop negotiating with it. Prospecting CRM for operators in San Diego is a wiring job: source → temperature → approve → 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.
Operators in San Diego do not have a Prospecting CRM problem because they lack GoHighLevel. They have it because outbound is a tool. The pipeline is a vibe.
Wire these objects first: Lead source field, GHL contact, pipeline by temperature, sequence (workflow) per temperature, human-approve step, calendar as conversion, DNC/opt-out tag.
Then these edges, in order: List import → source custom field + tag source:*; never dumped on 'everyone' · Temperature cold → slow sequence; human approve before first send · Temperature warm/inbound → faster path; still not the same as a booked buyer · Meeting booked → conversion; opens are not a stage
Done looks like a test you can repeat: Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won.
Start here: Lead sources are separated
Operators in San Diego already have GoHighLevel. The leak is not a missing feature. Outbound is a tool. The pipeline is a vibe. 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: Lead source field, GHL contact, pipeline by temperature, sequence (workflow) per temperature, human-approve step, calendar as conversion, DNC/opt-out tag. Then connect these edges, in order: List import → source custom field + tag source:*; never dumped on 'everyone' · Temperature cold → slow sequence; human approve before first send · Temperature warm/inbound → faster path; still not the same as a booked buyer · Meeting booked → conversion; opens 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. Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won. How you know it worked on the board: Meetings is the metric (held, not booked ghosts). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Lead sources are separated An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: separate sources on paper (inbound form, purchased list, partner, LinkedIn). Draw two sequences max. Write who approves outbound before anything leaves. Do not connect a scraper.
Operator
You already feel outbound is a tool. the pipeline is a vibe. Outbound is a tool. The pipeline is a vibe. Protect one sequence for 90 days. The four moves are source → temperature → approve → conversion. The edges are List import → source custom field + tag source:*; never dumped on 'everyone' then Temperature cold → slow sequence; human approve before first send. Lead sources are separated. Sequences match temperature. A human approves before volume. Meetings — not opens — are the conversion.
CEO
This is a money leak, not a preference about tools. Outbound is a tool. Until meetings is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: List import → source custom field + tag source:*; never dumped on 'everyone'.
Before
Tuesday. Someone among operators in San Diego. Outbound is a tool. The pipeline is a vibe. 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. Lead sources are separated. Sequences match temperature. A human approves before volume. Meetings — not opens — are the conversion. List import → source custom field + tag source:*; never dumped on 'everyone' The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in operators in San Diego already paid for GoHighLevel. Outbound is a tool. The pipeline is a vibe. 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. Lead sources are separated. Prove write-in: Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won. This week is one move: Lead sources are separated If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Outbound is a tool. Sequences fire. The pipeline is a vibe. Meetings are hoped for. Opens are celebrated. Human approve before send does not exist, so the domain pays.
The system
Lead sources are separated. Sequences match temperature. A human approves before volume. Meetings — not opens — are the conversion.
Cold, warm, and inbound must not share a cadence. Treating a past buyer like a scraped list is how you get replies you cannot defend. Source tags are how you stop that.
If nobody approves the first fifty sends, you do not have prospecting. You have a spam engine with a dashboard. Meetings booked is the number. Everything else is a vanity layer.
Lead sources are separated. Sequences match temperature. A human approves before volume. Meetings — not opens — are the conversion.
Outbound is a tool. The pipeline is a vibe when sources are mixed and sequences ignore temperature. Lead sources must be a field and a tag, not a memory of 'I think these were from the event'. Cold gets a slower proof path and a human approve before the first send — otherwise you will spam and call it prospecting. Warm inbound is a different pipeline or at least a different stage, because speed-to-lead and tone are different jobs. Meetings are the conversion. Opens, clicks, and 'interested' are not stages.
Wire the sequence to the source and temperature, then to the calendar. A reply in Conversations pauses the sequence and belongs on the contact. Opt-out and DNC are operational, not a footer you hope they see. Data quality is a weekly check: bounce, bad phone, duplicate email. If the list is dirty, the sequence is a megaphone into a landfill. Do not add a third sequence until the first two have stop rules.
Two databases: the sequencer (Instantly, LinkedIn tool, a spreadsheet) and GHL. If meetings book on Calendly and never create an opportunity, you are reporting theatre. Pick GHL as record of the person. The sending tool can fire, but replies and books write back. The intern's job is source hygiene and the approve queue, not 'more volume'. Volume into a mixed pipeline is how you train the market to ignore you.
Lead source field, GHL contact, pipeline by temperature, sequence (workflow) per temperature, human-approve step, calendar as conversion, DNC/opt-out tag.
List import → source custom field + tag source:*; never dumped on 'everyone'
Temperature cold → slow sequence; human approve before first send
Temperature warm/inbound → faster path; still not the same as a booked buyer
Meeting booked → conversion; opens are not a stage
Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won.
Day one: separate sources on paper (inbound form, purchased list, partner, LinkedIn). Draw two sequences max. Write who approves outbound before anything leaves. Do not connect a scraper.
Inbound, warm, cold — separate lists and sequences.
Cadence matches how they know you. No 'same 12-step' for everyone.
Human eyes on copy and list before volume.
Meetings held. Opens are not a business.
On one line, for operators in San Diego: Outbound is a tool. The pipeline is a vibe. 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.
Lead source field, GHL contact, pipeline by temperature, sequence (workflow) per temperature, human-approve step, calendar as conversion, DNC/opt-out tag.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Inbound, warm, cold — separate lists and sequences. Then wire: List import → source custom field + tag source:*; never dumped on 'everyone'
Why: Operators in San Diego cannot skip this edge. Outbound is a tool. If it is not true, GoHighLevel is already a second database.
Done when: List import → source custom field + tag source:*; never dumped on 'everyone' is true on a test.
Cadence matches how they know you. No 'same 12-step' for everyone. Then wire: Temperature cold → slow sequence; human approve before first send
Why: Operators in San Diego skip this and the leak returns as a private language. Wire the sequence to the source and temperature, then to the calendar. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Temperature cold → slow sequence; human approve before first send is true on a test.
Human eyes on copy and list before volume. Then wire: Temperature warm/inbound → faster path; still not the same as a booked buyer
Why: Operators in San Diego feel this as Outbound is a tool. The pipeline is a vibe. Two databases: the sequencer (Instantly, LinkedIn tool, a spreadsheet) and GHL.
Done when: Temperature warm/inbound → faster path; still not the same as a booked buyer is true on a test.
Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Meetings (Held, not booked ghosts), then approve (Protect the domain). 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.
Lead sources are separated
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.
Lead source field, GHL contact, pipeline by temperature, sequence (workflow) per temperature, human-approve step, calendar as conversion, DNC/opt-out tag.
If objects aren't named, software invents a second database.
Outbound is a tool. The pipeline is a vibe.
Inbound, warm, cold — separate lists and sequences. Then wire: List import → source custom field + tag source:*; never dumped on 'everyone'
Operators in San Diego cannot skip this edge. Outbound is a tool. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how operators in San Diego actually work — not the snapshot demo. Edge: Temperature cold → slow sequence; human approve before first send
Cadence matches how they know you. No 'same 12-step' for everyone. Then wire: Temperature cold → slow sequence; human approve before first send
Operators in San Diego skip this and the leak returns as a private language. Wire the sequence to the source and temperature, then to the calendar. Spec tags, fields, and states have to be the same objects the next workflow will read.
Lead sources are separated. Sequences match temperature. A human approves before volume. Meetings — not opens — are the conversion.
Human eyes on copy and list before volume. Then wire: Temperature warm/inbound → faster path; still not the same as a booked buyer
Operators in San Diego feel this as Outbound is a tool. The pipeline is a vibe. Two databases: the sequencer (Instantly, LinkedIn tool, a spreadsheet) and GHL.
Lead sources are separated
Because the login already exists. Outbound is a tool. Sequences fire. A new feature on a missing spec is a second database. Finish this edge first: List import → source custom field + tag source:*; never dumped on 'everyone'.
Day one: separate sources on paper (inbound form, purchased list, partner, LinkedIn). Draw two sequences max. Write who approves outbound before anything leaves. Do not connect a scraper. 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. Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won. 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. Sources (Or you will spam your buyers) 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. Lead sources are separated. Sequences match temperature. A human approves before volume. Meetings — not opens — are the conversion. Watch meetings 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. Lead sources are separated 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
Lead source field, GHL contact, pipeline by temperature, sequence (workflow) per temperature, human-approve step, calendar as conversion, DNC/opt-out tag.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
List import → source custom field + tag source:*; never dumped on 'everyone'
Skip this
Calling it done because a screenshot looks busy.
Do this
Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won.
Skip this
Leaving “Conversion” to chance.
Do this
Meetings held. Opens are not a business.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Inbound, warm, cold — separate lists and sequences. Then prove write-in: Import five test rows with a clear source.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect List import → source custom field + tag source:*; never dumped on 'everyone' 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
Meetings: The metric. Held, not booked ghosts. 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.
Meetings
The metric
Held, not booked ghosts
Approve
Before volume
Protect the domain
Sources
Split
Or you will spam your buyers
This week
Lead sources are separated
San Diego · West. Remote-first. The examples follow the city; the spine does not.
Lead sources are separated
Sequences match temperature
Human approve exists before spam
Meetings are the conversion, not opens
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.
Operators in San Diego do not have a Prospecting CRM problem because they lack GoHighLevel. They have it because outbound is a tool. The pipeline is a vibe. Wire these objects first: Lead source field, GHL contact, pipeline by temperature, sequence (workflow) per temperature, human-approve step, calendar as conversion, DNC/opt-out tag. Then these edges, in order: List import → source custom field + tag source:*; never dumped on 'everyone' · Temperature cold → slow sequence; human approve before first send · Temperature warm/inbound → faster path; still not the same as a booked buyer · Meeting booked → conversion; opens are not a stage Done looks like a test you can repeat: Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won. Start here: Lead sources are separated
Yes. Remote-first, US-friendly hours. San Diego is how people search — not a storefront.
Examples, timing, and scheduling. The spine does not get rewritten for every skyline: source → temperature → approve → conversion.
Before: Tuesday. Someone among operators in San Diego. Outbound is a tool. The pipeline is a vibe. 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. Lead sources are separated. Sequences match temperature. A human approves before volume. Meetings — not opens — are the conversion. List import → source custom field + tag source:*; never dumped on 'everyone' The next move is written. That is the difference between a login and a system.
Lead sources are separated
Because the login already exists. Outbound is a tool. Sequences fire. A new feature on a missing spec is a second database. Finish this edge first: List import → source custom field + tag source:*; never dumped on 'everyone'.
Day one: separate sources on paper (inbound form, purchased list, partner, LinkedIn). Draw two sequences max. Write who approves outbound before anything leaves. Do not connect a scraper. 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. Import five test rows with a clear source. Confirm they land in the cold pipeline, not the inbound one. Attempt a send: human approve must exist. Book one meeting from the sequence. Opens without a meeting do not move Won. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
The CRM is open. The operating system is not.
Read ↗Booked calls leak because the CRM never saw them.
Read ↗Traffic hits a page. The journey after that is improvised.
Read ↗Broadcasts exist. A sequence that earns the next conversation does not.
Read ↗Everyone is busy. Nobody owns the next 90 days.
Read ↗Email and WhatsApp stay open. A call is for installing the system.