Engagement snapshot
- Mandate
- Replace the spreadsheet operating model with software the client could own and scale.
- Timeline
- 18 weeks from discovery through multi-region launch.
- Team shape
- COO, 1 product manager, 3 engineers, and 6 franchise operator advisors.
The problem
HQ and franchisees managed onboarding, compliance, and local performance tracking across spreadsheets, forms, and email threads that could not keep up with network growth.
What we built
Rebuilt the operating model as a multi-tenant web platform with role-based dashboards, workflow rules, and a controlled data model for HQ and local operators.
Operating context
The client had validated its operating model but not its software. Rapid franchise growth exposed how brittle the no-code and spreadsheet stack had become, especially around compliance, onboarding, and shared reporting.
Key constraints
- HQ and franchisees needed different permissions and data views without separate systems.
- The rollout had to avoid breaking daily store operations during migration.
- The client wanted full code ownership and clear handoff documentation after delivery.
What we built
Multi-tenant core
Designed franchise, region, and HQ boundaries into the data model so the platform could scale without access confusion.
Workflow-driven compliance
Mapped onboarding and compliance events into explicit workflows instead of hidden spreadsheet logic.
Operational observability
Added dashboards, alerts, and audit trails so HQ could see where stores were blocked without manual reporting.
Delivery path
Process reconstruction
Mapped the real HQ-to-franchise operating flow first so the software matched the business rather than the old tooling quirks.
Dual-run migration
Moved franchise groups in waves and ran old and new processes together until operational accuracy was proven.
Ownership handoff
Delivered environment setup, documentation, and release procedures so the internal team could extend the platform post-launch.
Why it mattered
The client moved from a fragile operating model to a true product system. Reliability improved because critical franchise processes stopped depending on individual memory, spreadsheet discipline, and inbox follow-up.
Implementation notes
- Rebuilding the operating model mattered as much as rebuilding the software.
- Multi-tenant permission design needs to happen early or the rest of the platform gets warped around it.
- Migration trust came from dual-run validation, not from promising a perfect cutover.