Intern
What you actually do
List, records, stops. You do not scrape 5,000. You prove the person exists in GHL.
Library / System / Outbound writes a pipeline or it is a mood with a sequence tool
Prospecting as an operating layer is a named list, a reason, a finite sequence, write-in to GHL on first touch, a next date, lost reasons, and a stop when the role or the offer closes. The leak is dumping connections, Slack as assignment, and 'outbound' that never becomes an opportunity until someone is already on a call. This hub is how to install outbound so it does not poison inbound or the domain.
Prospecting as an operating layer is a named list, a reason, a finite sequence, write-in to GHL on first touch, a next date, lost reasons, and a stop when the role or the offer closes. The leak is dumping connections, Slack as assignment, and 'outbound' that never becomes an opportunity until someone is already on a call. This hub is how to install outbound so it does not poison inbound or the domain.
Connection ≠ consent to a 12-step. Named lists with a reason. Raw dumps are how you look careless and how email dies.
If the sequence lives only in Instantly/HeyReach/LinkedIn and GHL is empty until they book, you cannot manage next dates or owners. Write-in early.
Outbound copy that sounds like a webinar funnel is how serious buyers leave. The CRM still needs stages. Manners still apply.
When the offer or the role closes, the sequence stops. Continuing is how you become a joke in that account.
Speed-to-lead on inbound and cadence on outbound are different clocks. Mixing them in one workflow is how you SMS a cold list like they filled a form today.
Intern
List, records, stops. You do not scrape 5,000. You prove the person exists in GHL.
Operator
Outbound is a pipeline motion. Write-in early. Different clock from inbound. Stops at list and person. Manners.
CEO
Row count is not pipeline. Meetings from a named list with write-in are. Until that exists, more outbound tools buy reputation risk.
Named list, reason for outreach, GHL contact, source:outbound, sequence (email/LinkedIn/phone) with stop, owner, next date, opportunity only when qualified, suppression vs inbound.
List + reason → contacts created with source:outbound before the first touch, or on first touch the same day
Sequence steps → logged; reply pauses; booked writes Discovery
Disqualify → lost_reason; do not leave in 'nurture' forever
Inbound and outbound → same pipeline jobs, different source; do not mix sequences
Who, why this week, what offer. Size capped so follow-up is human. No 5,000-row hope.
Why: Unnamed lists are dumps. Dumps become domain and reputation incidents.
Done when: A list title, reason, cap, owner.
GHL records with source:outbound, list name, next date. Sequence tool may send; GHL owns the person.
Why: Tool-only outbound is a second CRM. Booking then becomes a stranger.
Done when: A first-touch test exists in GHL the same day.
Step count capped. Reply or book stops. Channel mix written (LI vs email vs phone) so you do not triple-tap.
Why: Endless cadences are inbound-quality spam.
Done when: A reply test pauses. A no-reply test ends.
Opportunity when they are a real job (meeting booked or explicit interest). Not one opportunity per unopened email.
Why: Boards full of unopened outbound destroy close rate and trust.
Done when: Pipeline count matches qualified, not touches.
Offer closed, role filled, they said no. Suppress. Do not recycle into inbound spines.
Why: Recycling no’s into 'nurture' is how you train the market to ignore the brand.
Done when: A no is lost with reason and excluded from the inbound acquire spine.
One named list, cap, reason. Create those contacts in GHL. Run a five-step max cadence with pause. Confirm a no is lost, not recycled. Confirm inbound form-fillers are not in the outbound sequence. You are not buying another sequencer.
More sequencer seats, more scraped rows, or a 'growth' SDR pod until write-in and stop rules exist. Headcount on a dump is a reputation risk.
CSV of connections. Instantly blasting. GHL empty until Calendly. Inbound and outbound in one SMS workflow. No’s recycled. Domain hurt. That is a mood with a tool.
Named list. Same-day GHL. Finite cadence. Reply pauses. Qualified-only opportunities. No’s excluded from inbound. Monday: touches vs meetings, not row count.
Same jobs if the sale is the same. Source differs. A separate pipeline is OK if the motion is truly different — then definitions still match where they can.
Because booking, invoicing, and inbound already live in GHL — or they should. Two records of the same human is the original leak.
Methodology without write-in is a workshop. This layer is objects and stops. The talk track can live elsewhere.
This week
This week: one named list, GHL write-in, finite cadence, qualify rule, no-recycle. No new sequencer.
Until stages, fields, and write-in have owners, the sub-account is a filing cabinet.
Read ↗If every automation can fire, none of them is an operating system.
Read ↗If the thank-you does not change the contact, you paid for a brochure.
Read ↗Broadcasts feel like work. A spine with manners is the product.
Read ↗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 — not for a tour of tools.