People come in four ways
A 14-page funnel: the Revenue Leak Estimator, a free guide that leads to the $97 Playbook, the toolkit on its own, or booking an audit.
Every contact gets a full record
51 custom fields and 21 lifecycle tags track where each lead came from, what they did and what they agreed to hear about.
Each lead lands in the right pipeline
Owners ready to talk and cold traffic move differently, so each gets its own path.
Sales path, 7 stagesNew › Audit booked › Audit done › Install call › Proposal › Won or lost
Cold path, 5 stagesNew › Estimator done › Toolkit buyer › Hot lead, or lost
18 workflows keep it moving
Capture, nurture, checkout and sales handoff, plus checks that flag any lead gone quiet. A $97 purchase marks a hot lead and gets a person on the call.
Pillar Studio Systems · Fractional Marketing Lead, Growth Systems (contract), Dec 2025 to now
Built a complete lead-to-revenue system in GoHighLevel: 18 workflows, 2 pipelines, a live lead calculator and one data model.
A company that sells revenue systems to boutique fitness studios retained me on contract to design its own. I built it for one Pilates studio first, then scaled it, over about 8 months including testing. I scoped the funnel, the CRM data model and the automation, and hired and directed 3 freelancers, including a CRM developer and a designer, against one quarterly plan, run in two-week sprints.
See the build
The problem
Pillar sells revenue infrastructure to studio owners. To sell it, the business needed its own: capture interest, separate buyers from browsers, follow up automatically and route hot leads to a call. None of it existed.
Constraints
- A lean team: me and 3 freelancers, including a CRM developer and a designer.
- GoHighLevel has no page or workflow API. Everything is built by hand, so specs had to be exact enough to build without coming back to me.
- Canadian and US contact law (CASL, TCPA, A2P 10DLC) designed in from day one.
Decisions and tradeoffs
- Two pipelines. Ready-to-talk owners and cold traffic behave differently, so each got its own stages. More to maintain, but reporting shows exactly where each kind of lead stalls.
- A $97 product as a filter. A buyer is far more likely to take a call, so two hot-lead workflows fire on that signal.
- No lead goes quiet unnoticed. A weekly stale-lead alert flags anyone 21+ days in without booking or buying. It notifies a person and never contacts the lead.
- A human answers replies. Reply handlers alert a person instead of letting a bot respond in phase 1.
- A reactivation module for dead leads. Dead-lead import, 3-touch SMS, 5-branch intent classification on replies, gated by consent rules.
Inside it: the Revenue Leak Estimator
A 5-question calculator that shows a studio owner what slow follow-up costs them, before asking for an email. The email unlocks the full breakdown and creates a scored contact in the CRM in real time.
- Number before the gate. Some people leave with the number and no email. The ones who stay have already seen the value.
- The webhook cannot lose a lead silently. A retry after 2 seconds, then a backup send; the result still shows if both fail.
- Consent built in. Separate, unchecked email and SMS boxes, stored on the contact.
Try it live ↗ Live since Aug 19 2026. Too early for conversion data.
What QA caught before launch
Tagging, routing and access-timing defects, and a missing workflow that would have broken the lifecycle on day one. During the estimator install: a stale webhook field picker, an unreadable CTA button, an auto-padded logo and three wrong links.
Outcome
The system is live, documented and QA'd, and built to handle 20 studio clients in its first year. This case shows the build and the decisions.
What I learned
Build for one real customer first. Designing around one Pilates studio made every stage concrete before the system had to scale.
How these numbers were measured
| Result | How it was measured |
|---|---|
| 18 workflows, 2 pipelines (7 and 5 stages) | Live GoHighLevel read, Oct 27 2026 |
| 51 custom fields, 21 tags | GoHighLevel API, Oct 27 2026 (test items excluded) |
| 14-page funnel | The live funnel, page by page |
| Built to handle 20 studio clients in year one | System design capacity, not a result |
Proves: owns the martech stack, builds lifecycle automation and routing and writes requirements developers can build from












