One pipeline from first enquiry to work in progress
Enquiry → qualify, estimate, propose, chase → won work handed straight to delivery
This firm had GoHighLevel but was only using it as a contact list. Deals lived in someone's head between the enquiry and the invoice: estimates in spreadsheets, proposals in a docs folder, follow-ups only when someone remembered. We built the whole thing as one pipeline in GHL, eight stages from lead to operations, with the estimate feeding the proposal, the proposal feeding the follow-up, and a won deal opening itself as a project. Nothing gets to sit still with no next step.
Results at a glance
- One pipeline covers the whole journey: lead, qualification, estimation, proposal, follow-up, win/loss, project intake, operations
- Estimates feed the proposal, so numbers are typed once
- Follow-up runs on a schedule and stops the moment someone replies
- Every deal closes with a reason, so lost work is countable instead of anecdotal
- A won deal opens itself as a project: folder, kickoff, onboarding, owner
- No deal can sit in a stage with no next action against it
The problem
The firm was paying for GoHighLevel and using it as an address book. Everything between the first enquiry and the first invoice lived somewhere else: estimates in spreadsheets, proposals in a shared docs folder, follow-up entirely on memory. Nobody could say how many live deals there were or which ones had gone quiet. Won work was worse. The person who sold it knew what had been promised, and the person delivering it found out in a meeting. Deals were not lost on price so much as lost in the gap between two stages nobody owned.
What was built
Lead
Every source lands in one pipeline: web forms, calls, referrals, inbound email. One place to look, so nothing arrives somewhere nobody checks.
Qualification
A short set of qualifying questions against fixed criteria: scope, budget range, timeline, decision maker. Poor-fit enquiries get a courteous no early rather than three weeks of drift.
Estimation
Scope and pricing built from a standard rate card in GHL's custom fields, rather than a fresh spreadsheet each time. The estimate is data, not a file.
Proposal
The proposal is generated from the estimate and sent for signature. The numbers are typed once, so the document cannot quietly disagree with the pipeline.
Follow-Up
A scheduled cadence after the proposal goes out, in business hours, stopping the moment the client replies or signs. Chasing is the stage that used to depend entirely on someone remembering.
Win/Loss
Every deal closes explicitly, with a reason. Price, timing, scope, went quiet, lost to someone else. Loss reasons are how you find out what is actually costing you work.
Project Intake
A won deal opens itself as a project. Drive folder, kickoff booked, onboarding sent, delivery owner assigned. What was sold travels with it, so delivery is not learning the scope secondhand.
Operations
Delivery tasks, status, and client comms stay attached to the same record. The account owner sees where the work is without asking.
What keeps it from breaking
A stage cannot be skipped empty
Each stage has required fields before a deal can advance. A proposal with no estimate behind it is how a pipeline turns back into a guess.
Follow-ups know when to stop
The cadence halts on any reply, booking, or signature, and sends only in business hours. Chasing without a stop condition turns a helpful system into a complaint.
Nothing closes without a reason
Win and loss both require a reason code. Without it you get a tidy pipeline that still cannot tell you why work is being lost.
How the approach worked
The firm did not need another tool. It needed the one it already paid for to cover the whole journey instead of the front of it. The gaps were never inside a stage, they were between stages: estimate to proposal, proposal to follow-up, won deal to delivery. Close those handoffs and the pipeline stops being a place work is recorded and starts being the thing that moves it along.
The results
Enquiry through to delivery now runs in a single GoHighLevel pipeline. The estimate feeds the proposal, the proposal starts its own follow-up, a closed deal records why, and a won one opens as a project with the scope attached. Live work is visible at a glance rather than reconstructed from memory. The firm did not track cycle times or close rates before the build, so there is no honest before-and-after to publish here, and nothing is claimed.
GHL as a contact list. Estimates in spreadsheets, proposals in a folder, follow-up from memory, delivery briefed in a meeting.
One pipeline, eight stages, first enquiry to work in progress. Every deal has a next step and every won deal arrives at delivery with its scope.
Tools & technologies
Have a process like this slowing your business down? Tell me your stack and goals and I'll send back a build plan.
Take the stack assessment →