Intern
What you actually do
Day one: the deck goes out, the inbox goes quiet — make proposal-out a stage with a date. Write a short spine. Write lost reasons. Do not build a 12-email 'value sequence' to hide that no one follows up.
Library / agencies and services / Proposal follow-up
Long consider, lots of no-shows, a CRM full of 'interested'.
Read it once, then stop negotiating with it. Proposal follow-up for solar companies is a wiring job: stage → spine → lost → context. 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.
Solar companies do not have a Proposal follow-up problem because they lack GoHighLevel. They have it because the deck goes out. The inbox goes quiet.
Wire these objects first: Proposal-out stage + date, artifact link field, follow-up spine (short), lost reasons, GHL contact, Conversations, owner.
Then these edges, in order: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact · Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back' · Reply or book → spine pauses; human on the thread · Lost → reason required; artifact remains so you know what they saw
Done looks like a test you can repeat: Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, fail.
Start here: Two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood.
Solar companies already have GoHighLevel. The leak is not a missing feature. The deck goes out. The inbox goes quiet. 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: Proposal-out stage + date, artifact link field, follow-up spine (short), lost reasons, GHL contact, Conversations, owner. Then connect these edges, in order: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact · Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back' · Reply or book → spine pauses; human on the thread · Lost → reason required; artifact remains so you know what they saw. 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. Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, fail. How you know it worked on the board: Next date is required (the day it is sent). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: the deck goes out, the inbox goes quiet — make proposal-out a stage with a date. Write a short spine. Write lost reasons. Do not build a 12-email 'value sequence' to hide that no one follows up.
Operator
You already feel the deck goes out. the inbox goes quiet. Long consider, lots of no-shows, a CRM full of 'interested'. Protect one sequence for 90 days. The four moves are stage → spine → lost → context. The edges are Proposal sent → stage Proposal out + proposal_sent_on + link on the contact then Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back'. Appointment show rate is the leak. More leads into the same ghost calendar makes it worse.
CEO
This is a money leak, not a preference about tools. The deck goes out in a glow. Until next date is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact.
Before
Tuesday. Someone among solar companies. Long consider, lots of no-shows, a CRM full of 'interested'. 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. Appointment show rate is the leak. More leads into the same ghost calendar makes it worse. Proposal sent → stage Proposal out + proposal_sent_on + link on the contact The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in solar companies already paid for GoHighLevel. Long consider, lots of no-shows, a CRM full of 'interested'. 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. Proposal-out is a stage with a date. Prove write-in: Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, fail. This week is one move: Two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
The deck goes out in a glow. Then silence. No stage, no date, no spine. Lost is optional. Sales cannot see what was sent. The next proposal is invented again.
The system
Proposal-out is a stage with a date. A short follow-up spine exists. Lost reasons are captured. The contact shows what went out and when.
If it is not a stage, it is a hope in an inbox. Put a next date the day it is sent. Three touches, then lost with a reason — not a card that rots as 'maybe'.
The closer should see the file and the dates without hunting email. If follow-up is personality, volume will break it.
Appointment show rate is the leak. More leads into the same ghost calendar makes it worse.
The deck goes out. The inbox goes quiet. Proposal-out is a stage with a date and a link on the contact so anyone can see what was sent. A short follow-up spine exists. Lost reasons are captured. Sales sees what was sent without asking Slack. If the proposal is a Calendly 'I'll send something' with no artifact field, you cannot review the motion.
Wire the send: same day the file leaves, the opportunity moves. Follow-ups live in GHL email/SMS, not only in a personal Gmail. STOP and unsubscribe still apply. After N touches, the card cannot sit in Proposal out forever — it goes Lost or a human re-dates with a reason. Time-in-stage is the review.
Two databases: Google Drive and GHL. Put the link on the contact. The intern starts the spine on a sandbox deal. They do not redesign the slides. If founders still 'just want to send a quick note from the phone', that note must still land in Conversations or it is a second database. Quick is allowed. Invisible is not.
Proposal-out stage + date, artifact link field, follow-up spine (short), lost reasons, GHL contact, Conversations, owner.
Proposal sent → stage Proposal out + proposal_sent_on + link on the contact
Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back'
Reply or book → spine pauses; human on the thread
Lost → reason required; artifact remains so you know what they saw
Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, fail.
Day one: the deck goes out, the inbox goes quiet — make proposal-out a stage with a date. Write a short spine. Write lost reasons. Do not build a 12-email 'value sequence' to hide that no one follows up.
Proposal-out with a date. Exit rule written.
Three touches. Then a decision.
Reasons required. No vanishing cards.
What was sent lives on the contact.
On one line, for solar companies: The deck goes out. The inbox goes quiet. 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.
Proposal-out stage + date, artifact link field, follow-up spine (short), lost reasons, GHL contact, Conversations, owner.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Proposal-out with a date. Exit rule written. Then wire: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact
Why: Solar companies cannot skip this edge. The deck goes out. If it is not true, GoHighLevel is already a second database.
Done when: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact is true on a test.
Three touches. Then a decision. Then wire: Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back'
Why: Solar companies skip this and the leak returns as a private language. Wire the send: same day the file leaves, the opportunity moves. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back' is true on a test.
Reasons required. No vanishing cards. Then wire: Reply or book → spine pauses; human on the thread
Why: Solar companies feel this as the deck goes out. The inbox goes quiet. Two databases: Google Drive and GHL.
Done when: Reply or book → spine pauses; human on the thread is true on a test.
Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, fail.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Next date (The day it is sent), then lost (Or you repeat the 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.
Two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood.
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.
Proposal-out stage + date, artifact link field, follow-up spine (short), lost reasons, GHL contact, Conversations, owner.
If objects aren't named, software invents a second database.
Long consider, lots of no-shows, a CRM full of 'interested'.
Proposal-out with a date. Exit rule written. Then wire: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact
Solar companies cannot skip this edge. The deck goes out. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how solar companies actually work — not the snapshot demo. Edge: Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back'
Three touches. Then a decision. Then wire: Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back'
Solar companies skip this and the leak returns as a private language. Wire the send: same day the file leaves, the opportunity moves. Spec tags, fields, and states have to be the same objects the next workflow will read.
Appointment show rate is the leak. More leads into the same ghost calendar makes it worse.
Reasons required. No vanishing cards. Then wire: Reply or book → spine pauses; human on the thread
Solar companies feel this as the deck goes out. The inbox goes quiet. Two databases: Google Drive and GHL.
two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood.
Because the login already exists. The deck goes out in a glow. Then silence. A new feature on a missing spec is a second database. Finish this edge first: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact.
Day one: the deck goes out, the inbox goes quiet — make proposal-out a stage with a date. Write a short spine. Write lost reasons. Do not build a 12-email 'value sequence' to hide that no one follows up. 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. Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, 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. Aging (Rotting proposals are the 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. Appointment show rate is the leak. More leads into the same ghost calendar makes it worse. Watch next date 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. Two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood. 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
Proposal-out stage + date, artifact link field, follow-up spine (short), lost reasons, GHL contact, Conversations, owner.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Proposal sent → stage Proposal out + proposal_sent_on + link on the contact
Skip this
Calling it done because a screenshot looks busy.
Do this
Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, fail.
Skip this
Leaving “Context” to chance.
Do this
What was sent lives on the contact.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Proposal-out with a date. Exit rule written. Then prove write-in: Send a test proposal (PDF or doc).
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Proposal sent → stage Proposal out + proposal_sent_on + link on the contact 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
Next date: Required. The day it is sent. 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.
Next date
Required
The day it is sent
Lost
Captured
Or you repeat the leak
Aging
Watched
Rotting proposals are the backlog
This week
two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
Proposal-out is a stage with a date
A short follow-up spine exists
Lost reasons are captured
Sales sees what was sent
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.
Solar companies do not have a Proposal follow-up problem because they lack GoHighLevel. They have it because the deck goes out. The inbox goes quiet. Wire these objects first: Proposal-out stage + date, artifact link field, follow-up spine (short), lost reasons, GHL contact, Conversations, owner. Then these edges, in order: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact · Follow-up spine → 3–4 touches, then stop or lost; not infinite 'circling back' · Reply or book → spine pauses; human on the thread · Lost → reason required; artifact remains so you know what they saw Done looks like a test you can repeat: Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, fail. Start here: Two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood.
The deck goes out in a glow. Then silence. No stage, no date, no spine. Lost is optional. Sales cannot see what was sent. The next proposal is invented again. Appointment show rate is the leak. More leads into the same ghost calendar makes it worse.
Before: Tuesday. Someone among solar companies. Long consider, lots of no-shows, a CRM full of 'interested'. 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. Appointment show rate is the leak. More leads into the same ghost calendar makes it worse. Proposal sent → stage Proposal out + proposal_sent_on + link on the contact 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: stage → spine → lost → context.
Next date: Required — The day it is sent. Then lost (Or you repeat the leak). If those are folklore, do not add another GoHighLevel workflow.
two-way reminders. No-show recovery. Stages with exit rules. Kill 'interested' as a mood.
Because the login already exists. The deck goes out in a glow. Then silence. A new feature on a missing spec is a second database. Finish this edge first: Proposal sent → stage Proposal out + proposal_sent_on + link on the contact.
Day one: the deck goes out, the inbox goes quiet — make proposal-out a stage with a date. Write a short spine. Write lost reasons. Do not build a 12-email 'value sequence' to hide that no one follows up. 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. Send a test proposal (PDF or doc). Confirm stage, date, link. Let the spine run one step. Reply; confirm pause. Move to Lost with a reason. If the deck lives only in the closer's sent folder, 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.
The CRM is open. The operating system is not.
Read ↗Stages are labels. Nobody knows what 'won' requires.
Read ↗Tags multiply. Insight does not.
Read ↗Booked calls leak because the CRM never saw them.
Read ↗Broadcasts exist. A sequence that earns the next conversation does not.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.