Case study · Automation
CRM Automation Build
A pipeline, an intake form, and a branching lead-routing workflow — built solo, end to end, in a trial GoHighLevel account for an invented custom home builder.
Cornerstone Custom Homes is invented. This was a solo practice build in a trial GoHighLevel account, done to actually know the platform hands-on rather than just claim it — not a client engagement.
A pipeline, an intake form, and a lead-routing workflow, built end to end in a trial GoHighLevel account for an invented custom home builder — the full loop from a form submission to a routed, valued opportunity and two notifications landing.
Budget routes into a real forecast value, tags trace every lead back to its channel, and a second workflow carries a finished project through to a review ask.
01 — The pipeline
Probability is set to track how much real uncertainty resolves at each stage, not how far along it visually looks. "Won" and "Completed" are different stages that both correctly sit at 100% — the pipeline is a forecasting tool, not a status tracker.
02 — The intake form
"Request a Consultation" — eight fields plus two consent checkboxes. Budget is the field the rest of this build turns on.
03 — One lead, start to finish
The builder itself — the trigger chain, the branch condition, and all four paths it fans out into.
app.gohighlevel.com/v2/location/••••••••••••••••/automation/workflow/lead-intake
If / else
Fork the contact journey based on conditions
Action name
Branches
And the same run narrated step by step, following one lead through the $6-9M branch. Nothing runs on a timer — step through it at your own pace.
- 01 Form submitted
- 02 Tag applied
- 03 Opportunity created
- 04 Budget routed
- 05 Value set
- 06 Confirmation email
- 07 Internal notification
The whole run, start to finish. Seven steps from a form submission to both the lead and the internal notification landing.
Website — Request a Consultation
Trigger — Form Submitted, filtered to this form
Action — Add contact tag
Action — Create or update opportunity
Action — Route by Estimated Budget
If / Else, four branches
Action — Update opportunity (inside the $6-9M branch)
Action — Send Email
SubjectWe received your request!
Hi Jordan, thanks for reaching out to Cornerstone Custom Homes — we'll be in touch within 1 business day to schedule your consultation.
Action — Internal Notification (Email)
SubjectNew consultation request from Jordan Reyes
New lead: Jordan Reyes, +1 (415) 555-0148, [email protected]. Estimated budget $6-9M. Check the Consultation Pipeline — New Inquiry.
04 — Review routing
A second workflow, two triggers deep, since a survey response comes back on its own schedule rather than right after the stage change that requests it. Reaching "Completed — Review Requested" sends a short rating survey. When that survey comes back, the response forks on the answer.
A bad review never goes live before someone on the team has had the chance to follow up — the public ask only fires on the branch that earned it.
05 — What the build taught
Route the data, not just the lead
A budget answer sitting on a form isn't worth much until it's wired into the number the pipeline actually forecasts on. The routing logic in step 03 is what turns a dropdown answer into a real dollar value the whole pipeline can report against.
The tool builds the thing and reads it back
Claude Code wasn't just used to talk about this build — it read real pipeline data through the platform's own API to check the work. That's the same habit worth bringing to a live account: verify against the data, not just the workflow diagram.
A pipeline is a forecasting tool
Every stage's win-probability and every opportunity's routed value feed the same Forecast math — probability times value. Building both deliberately, not just one or the other, is what makes that number mean something.