regional.fit
Local demand management for distributed organisations
2026 - current · MVP live - Self-Built Product / SaaS
regional.fit is our own product - a demand management system for distributed organisations. Multi-role briefing flow: local managers submit structured requests, regional managers validate against strategy, admins govern the rules, production executes. One dataset, role-tuned views, every level sees the same truth. Live MVP demo running, fitness chains as pilot vertical, productisation roadmap underway.
Tension
Distributed organisations - fitness chains, retail networks, multi-venue F&B, hospitality groups - leak operational margin through local demand chaos. Unit managers ask for marketing assets, training materials, local campaigns, brand exceptions, ops fixes - via email, Slack, WhatsApp, calls. Regional managers can't see what's important versus noise. Production gets requests stripped of context. Nobody knows where anything stands. The cost shows up everywhere: in middle management time, in slipped openings, in inconsistent local brand, in burned trust. The actual bottleneck isn't talent or tools - it's the absence of a structured demand layer between the field and the centre.
Decisions
We treated the local-demand problem as productisable - not consultable. The methodology that worked one-off for individual launches at Zdrofit pointed to a deeper truth: every distributed organisation has the same problem, structurally. So we built a SaaS, not a deck. Designed four roles around the actual decision boundaries: local manager (origin of demand), regional manager (strategic gate-keeper), administrator (rule-setter), production team (execution). Each role owns one move in the workflow - no overlap, no ambiguity. One shared data layer underneath. Live MVP first, customers second, scope third.
Approach
Role-first product architecture. Each persona sees only what they need to decide. Local managers fill structured forms grounded in context (location, goal, operational reality) - not blank email fields. Regional managers see a queue ranked by strategic priority + available resources - not a flood of DMs. Admin defines structure (locations, hierarchies, asset types, approval rules). Production tier is mapped in the roadmap but out of MVP scope - we ship the decision layer first, execution layer second. AI-native foundation: structured intake becomes structured signal that future automation can act on. Built to plug into any distributed-org topology - not just fitness.
"We stopped consulting around the demand problem and started productising it. regional.fit is r3loop applied to the most expensive recurring chaos in every distributed organisation - the gap between local need and central execution.
Outcome
MVP live, pilot customers being onboarded. The pilot instruments four decision roles on one screen; deployment count, requests processed and hours redirected from coordination to decisions are being measured now and will be published as the pilots mature.
Reflection
Consulting around the same problem repeatedly is a tell. When five clients describe the same chaos with the same words, you're not delivering a service - you're documenting a market. regional.fit exists because the local-demand problem in distributed organisations is universal, structural, and expensive - and nobody is selling the operating layer that solves it.
Before we rolled out the system, most of my week went into answering 'where are we on the opening' emails. Now there's one screen every level sees - from my team to the director. We swapped five-person status meetings for a screen link. The time I got back goes into real decisions, not writing reports.
Joanna LachSenior Specialist, Marketing of New Openings · Zdrofit (pilot deployment)
work.visuals
