A franchise group replaced its Monday spreadsheet ritual with a workflow that never forgets

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

Nine fitness studios operate under one franchise banner, each with its own manager, its own booking system, and its own relationship with paperwork. The group's week is anchored by a Monday 9am franchise meeting where every studio's performance is read aloud and argued over. The operations manager sits at the centre of it — half analyst, half diplomat — and the studios' managers are fitness professionals first, reporting reluctantly and at their own pace.

What it was costing

Every Monday, the operations manager pulled nine studios' numbers from three systems into a group spreadsheet, chased two studios that always reported late, and rebuilt the same charts for the franchise meeting. The ritual consumed a day and was wrong twice a quarter.

What they could see

• Monday mornings vanished into chasing two studios that always reported late, every week, without exception.
• KPI numbers were rebuilt three ways and disagreed with each other in the meeting, repeatedly and publicly.
• The same charts were recreated from scratch for every franchise meeting because nobody trusted the last set.
• Studio managers resented reporting they suspected was surveillance, so numbers arrived late or defensively rounded.

The constraints we worked inside

• Studio managers reported manually and resented surveillance — the automation had to reduce their work, not add monitoring.
• Three source systems, one without an API — export-file handling had to be robust.
• The franchise meeting moved to Mondays 9am — the data deadline was immovable.

What had been tried before

A shared spreadsheet template with locked formulas was issued to all nine studios.

Locks got broken, cells got pasted over, and the template's trust died the first time a meeting number had to be retracted.

The franchise software's built-in dashboard was adopted as the group view.

It covered the systems with APIs and ignored the two that didn't have them, so the group view was permanently two studios short and mis-defined.

What we proposed

We proposed reading the data where it lives: systems with APIs are polled directly, the two without are fed scheduled export files with format checks, so studio managers stop being the integration layer. KPI definitions get encoded once, in writing, with the ops manager's sign-off — ending the whose-number-is-right debates that opened every meeting. The report generates itself with per-studio drill-downs and lands at 8:45 Monday, before the 9am meeting, with late sources flagging themselves instead of being chased. Nothing about the studios' tools had to change; the deadline did the forcing.

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

• A business-intelligence platform rollout — One source system has no API at all, so any BI tool still depends on export files — the tool would dress up the same fragility.
• Mandating one booking system group-wide — Studios chose their systems before the group existed and franchisees guard that autonomy; the fight would outlast the engagement.
• A group-wide CRM with native reporting — Out of scope twice over: the Monday deadline needed reporting in five weeks, and the studios' workflow would have to change first.

How the work ran

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

The stack, and the reasoning

n8n (cloud)

The group has no infrastructure staff; the cloud tier means the ops manager's laptop being closed doesn't matter to Monday morning.

API + file ingestion

Scheduled exports from the API-less systems get format-checked on arrival — a missing column fails the file before it can poison a metric.

Scheduled workflows

The Monday 9am deadline is immovable, so collection runs on schedule through the weekend with slack built in for late files.

Report generation

The report generates itself with per-studio drill-downs, so the meeting reads results instead of watching someone rebuild charts live.

Error workflows

A missing source file now flags itself before the meeting instead of being discovered as a gap mid-sentence on Monday morning.

What went wrong

How we worked together

Cadence

A mid-week build review with the operations manager, and a full rehearsal run against the real Monday deadline in week three.

Client side

The ops manager owned the KPI definitions and the report layout; two cooperative studio managers tested the export handoffs.

Decisions

Metric definitions were signed off in writing by the ops manager before any code consumed them — the retention argument settled that rule early.

They provided

Export access for the two API-less systems, a historic quarter of numbers to validate against, and the ops manager's honest Monday-morning availability.

What changed

The headline: weekly reporting effort for the operations manager, measured across the first quarter — 6 hrs → 20 min, read from Time estimate vs workflow logs. A second check: late-studio data incidents since go-live at 0.

Monday belongs to the meeting again. The ops manager reads a report that landed at 8:45 instead of constructing one at 8:50, and the argument that used to open every meeting has been replaced by arguments about what to do, which is what the meeting was for. Studio managers stopped resenting Mondays because their reporting work dropped to nothing; the numbers arrive from their systems, not from them. The Monday-morning chase stopped existing — the ops manager's half-hour hunt for late studios vanished from her calendar in week six and nothing replaced it.

The result was read from Time estimate vs workflow logs against the pre-engagement baseline over the stated window, with a guardrail check on late-studio data incidents since go-live. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The n8n cloud workspace polling the studios' booking systems and export inboxes, with a versioned export of all workflows.
• The written KPI definitions the meeting now cites as its standard.
• A runbook for the two export-file sources, including format-check behavior.
• The late-file flagging rules and who gets notified, documented and tested, with the workspace credentials held by the ops manager.
• A walkthrough for adding a tenth studio without touching the group logic.