A fitness franchise scaled its lead follow-up to 9 studios from one working setup

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Boutique fitness studios under one franchise brand: small-group training, local owners, and a corporate team of three who set the brand and live off studio performance. The group has grown from the founding studio to a handful of sites, with more openings planned, and every studio's growth engine is the same — a low-cost trial that should convert to membership inside a fortnight or not at all. Trial leads arrive from local ads and walk-ins, and each studio manager has built follow-up habits that suit their own temperament.

What it was costing

Every studio followed up on trial leads differently — some texted, some called, one did neither reliably. Corporate had no visibility, trials expired quietly, and the newest studios copied the oldest studio's accidental habits.

What they could see

• Corporate cannot see which studios contacted this week's trial leads and which let them sit.
• A trial finishes their fortnight and quietly lapses; nobody at the studio noticed the window close.
• The newest studio copied the founding studio's follow-up habits — including steps that exist for reasons nobody remembers.
• One studio texts every lead within the hour; another waits for the member to call back, and both believe they are the normal one.
• Opening a new studio means reinventing lead follow-up from scratch with whoever is free to help.

The constraints we worked inside

• Studio culture is local — corporate sets the minimum, studios keep personality.
• Trials convert inside 14 days or rarely at all — the follow-up window was the whole game.
• The group planned three more studios; the setup had to be deployable per studio in a day.

What had been tried before

Corporate issued a follow-up standard — every trial contacted within a day — and asked studios to report weekly.

Reporting depended on the same managers who were failing to follow up; the studios that needed the standard reported the least.

A shared messaging channel was created for lead alerts so studios could coordinate quickly.

It became noise within weeks — alerts without ownership — and the quiet studios stayed quiet where it mattered.

An all-in-one fitness platform was trialled at two studios with member apps and booking built in.

Per-location cost and a rollout measured in months killed it before trial follow-up, the actual problem, was ever addressed.

What we proposed

A floor, not a script: one corporate-standard trial sequence — contact on day zero, then days one, three, seven, and ten — that every studio runs as the minimum, with each manager free to append their own personality on top. Built once, packaged as a snapshot, and deployed per studio in a day, so the ninth studio opens with the system already working and the next opening needs nobody's help. Reporting splits by audience: corporate sees trial-to-member conversion per studio; each studio sees its own funnel. Culture stays local; the follow-up window stops being optional.

Just as important is what we ruled out, and why:

• An enterprise multi-location CRM — Per-studio licensing and a rollout measured in months, for a group whose actual need was one repeatable pipeline and honest reporting.
• Corporate-locked, one-size messaging — Studio culture is local by design; managers would quietly revert to their own habits within a quarter and the floor would rot.
• Per-studio custom builds — Nine bespoke setups contradicted the deploy-in-a-day requirement, and every new opening would have needed an integrator instead of a button.

How the work ran

Delivered by the systems pod — automation specialist over 7 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

GoHighLevel snapshot

The whole setup — pipeline, calendars, sequences — packages into one deployable unit, which is the only way studio nine opens ready and studio twelve never calls us.

Opportunities & Pipelines

The trial window maps to stages day by day, so an expiring trial is visible on a screen rather than discoverable in hindsight.

Trial sequences

The day-zero-to-day-ten cadence is the floor every studio runs; studios append personality after it rather than choosing whether to bother.

Multi-location reporting

Corporate needs comparison between studios and studios need privacy from each other; one reporting layer with two audiences delivers both honestly.

What went wrong

How we worked together

Cadence

A pilot at two studios with weekly rollout calls, then a fortnightly manager call once the snapshot existed; corporate got the same reporting cadence as the studios.

Client side

The corporate operations head owned the floor and the snapshot; studio managers owned everything appended after it.

Decisions

Disputes about sequence steps were settled by conversion data after the first full month — the floor stayed, the extras that converted stayed, the rest were cut.

They provided

Each studio's lead sources and trial definitions, studio-manager time for onboarding sessions, and the corporate reporting requirements that shaped the dashboards.

What changed

The headline: trial-to-member conversion, averaged across the 9 studios over one quarter — 22% → 34%, read from Pipeline stage reports. A second check: setup time for a new studio (was: 'depends who's free') at 1 day.

Studio managers compare funnels instead of excuses, and the conversation between corporate and studios shifted from asking whether follow-up happened to asking why a stage converts differently. New openings lost their chaos: a studio now opens with follow-up working on day one, and the managers who once argued for their own habits stopped arguing for the plainest reason — the old weekly report was retired, and the snapshot is simply where the work happens now. Trials stop expiring silently because an expiring trial is a stage, not a memory.

The result was read from Pipeline stage reports against the pre-engagement baseline over the stated window, with a guardrail check on setup time for a new studio (was: 'depends who's free'). Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The snapshot package itself, with version notes so corporate controls what changes between studios.
• A rollout playbook — deploy, onboard a manager, verify the first week — written for the next opening.
• Per-studio dashboard logins and the corporate cross-studio view, configured per audience.
• A manager training video covering the floor sequence and the add-on branches.