Franchising
Franchise software built around what the business actually does
Most franchise software is built for the franchisor's oversight needs, not for the operational work franchisees do every day. This module starts from best-of-breed booking, billing, and membership, then adds the franchise layer on top. Franchisees get software they want to use. Franchisors get numbers they can trust, because they come from the operational record itself.
Developed using AI-augmented engineering, delivering production-quality franchise management logic 80-90% faster than traditional development.
Upload franchise agreements and the AI extracts fee structures, compliance requirements, and permission rules into reviewable, publishable configuration.
Change MSF structures, compliance policies, and permission configurations without code changes. Self-service for franchisors, zero bespoke logic per franchise agreement.
Franchise network data exposed via MCP (Model Context Protocol). Your AI tools query network performance, franchisee data, and compliance status directly.
Why franchise operators compromise on software
Franchise businesses face a choice no one should have to make: software that serves the franchisor's oversight needs, or software that serves the franchisee's operational needs. The result is usually a compromise that serves neither well.
Franchise management systems prioritise oversight
Built for the franchisor's view: royalties, compliance, benchmarking. But the operational workflows franchisees use every day are an afterthought. Booking is basic, billing is bolted on, and the customer-facing experience suffers.
Operational systems do not understand franchising
Best-of-breed booking and billing platforms have no concept of franchisors, franchisees, MSF, or multi-level permissions. Franchise operators end up running two systems, with manual reconciliation in between.
Franchisees work around the software
When the system does not fit how the business works, the Excel layer grows: manual fee calculations, emailed compliance documents, spreadsheet reconciliation. The data the franchisor sees is only as good as what franchisees bother to enter.
Franchisor, franchisee, site: one ownership chain
The data model is built around how franchise networks actually work. Every site belongs to a franchisee, every franchisee belongs to a franchisor. Aggregation, fees, and permissions all flow from this structure.
Franchisor, franchisee, site
A clean ownership chain from network to individual location. Every site belongs to a franchisee, every franchisee belongs to a franchisor. Data aggregation, fee calculation, and permissions all flow from this structure.
Directly operated sites
Franchisors that run their own locations alongside franchisees do not need workarounds. Directly operated sites are modelled as a special franchisee record, so the network view includes them naturally and fee calculations can apply differently.
Logical multi-tenancy
Shared database with tenant isolation through the ownership chain. No physical DB separation needed, no performance penalty at scale. Add a new franchisee and their sites are structurally isolated from day one.
See exactly what you should. Nothing more.
Permissions are scoped at every level of the hierarchy and enforced at the API layer. A franchisee cannot see another franchisee's data. A site user cannot see franchisee financials. These are architectural constraints, not configuration options.
Scoped claims with hierarchical resolution
Permissions are scoped at Site, Franchisee, or Franchisor level. A franchisee-scoped claim automatically resolves to all their sites. A franchisor-scoped claim covers the whole network. No manual enumeration when locations change.
Cross-site without over-promotion
A staff member covering two locations gets explicit site-level grants, not a franchisee-level promotion. They see exactly the sites they work at, with no bleed into financial or management views they should not have.
Franchisor-only capabilities
Three distinct capabilities the franchisor has that franchisees cannot see: system configuration (fee structures, network settings), aggregated cross-franchisee visibility, and the ability to intervene inside a franchisee's site. Each is separately controlled.
Revenue figures both sides trust
Management service fees are calculated from the billing engine's actual payment records. The franchisor sees the same numbers the franchisee's customers paid against. No reconciliation, no disputes.
Configurable fee structures
Percentage of revenue, flat fee, tiered, or custom. Each franchise agreement can have its own MSF calculation rules. Configure once, and the platform calculates automatically at every billing cycle.
Operational source of truth
MSF is calculated from the billing engine's actual payment records, not self-reported figures. The franchisor trusts the numbers because they are the same numbers the franchisee's customers paid against. No reconciliation, no disputes over revenue figures.
Statement generation with audit trail
Automated MSF statements generated per franchisee per period. Both sides see the same breakdown: gross revenue, applicable fees, net amount. Every calculation is auditable with the underlying transaction records.
The whole network at a glance
Rolled-up KPIs across all franchisees, drillable to individual site level. The same billing analytics engine that powers per-site reporting gives franchisors a network-wide view.
Network-wide dashboards
Revenue, bookings, utilisation, and customer growth across the entire franchise network. Drill from network to franchisee to individual site. Month-over-month comparisons and batch drill-downs inherited from the billing analytics engine.
Franchisee benchmarking
Anonymous or named performance comparison across the network so the franchisor can spot outliers. Identify underperforming locations, recognise top performers, and share insights that improve the whole network.
Certificates, qualifications, insurance: tracked centrally
Simple to use, operationally critical. Franchisors need to demonstrate network-wide compliance for due diligence, audits, and legal protection.
Document store with expiry alerts
Franchisees upload certificates, qualifications, and insurance documents. Configurable expiry windows trigger alerts before documents lapse. No more emailed PDFs or spreadsheets tracking renewal dates.
Network compliance view
Franchisors see compliance status across the entire network at a glance. Traffic-light indicators flag which franchisees are current, approaching expiry, or lapsed. Drill into any franchisee to see individual document status.
Full transparency when head office acts
Franchisors sometimes need to operate inside a franchisee's space. The platform makes this explicit, auditable, and transparent to both sides.
Explicit mode switch
When a franchisor user operates inside a franchisee's site, the system requires an explicit mode switch. The action is never accidental, and the UI makes the context clear. This protects both parties and prevents disputes about who changed what.
Intervention audit trail
Every action is recorded with the actor's identity, the scope they were operating in, and whether it was a franchisor intervention. Franchisees can filter their own audit log to see when and what head office touched. Transparency builds trust.
What sets it apart
Operational source of truth
MSF and royalty numbers come from actual bookings and payments, not self-reported figures. The franchisor trusts the numbers because they are the same numbers the franchisee's customers see.
One platform, not two
Replaces both the franchise management system and the operational system. No integration layer, no reconciliation, no data falling between systems.
Permissions are architectural
Multi-level access control is enforced at the API layer, not configured in an admin panel. A franchisee cannot see another franchisee's data even if someone misconfigures a setting.
Built for franchisees too
The operational layer (booking, billing, membership) is best-of-breed, not a compromise. Franchisees get software they actually want to use, which means better data for the franchisor.
Best-practice UX, WCAG AA
Every screen is designed to meet WCAG AA accessibility standards with a modern, intuitive interface. Staff, franchisees, and their customers get a product that is easy to use from day one.
Your brand, delivered fast
The UI is built to be re-themed quickly. We use AI-assisted tooling to apply your brand colours, typography, and identity so the product looks and feels like yours within days, not weeks.
Capabilities in depth
Feature-by-feature detail for evaluators: what each capability does, how it is modelled, and why it matters.
Franchise hierarchy: network, franchisees, territories, one model
How the Franchising module models the network: franchisor, franchisee, and territory entities, master franchises, directly-operated sites, ownership history, and transaction-level attribution.
Scoped permissions: a matrix, not a muddle
How the Franchising module controls access: a module-and-action permission matrix, roles scoped to network, franchise, territory, or site, field-level masking, and a tested catalogue.
Secure, scalable, observable
Built on Microsoft Azure with Clean Architecture and domain-driven design. Every permission check, fee calculation, and intervention is logged, traced, and auditable.
.NET and C#
Clean Architecture with CQRS. Domain-driven design, immutable models, and full test coverage.
Microsoft Azure
AKS, Azure SQL, Redis, Azure OpenAI. Production-ready infrastructure orchestrated with Azure Aspire.
API-layer enforcement
Permission boundaries are enforced at the API layer, not in UI code. Every request is validated against the user's scoped claims.
Full audit trail
Every event recorded with actor, scope, timestamp, and field-level diffs. Franchisor interventions are explicitly flagged.
Part of a connected system
The Franchising module adds the franchise layer on top of the core Booking, Billing, and Membership modules. Each module works independently, but together they share a common data layer and the same platform foundations.
Booking Engine
Real-time scheduling, capacity management, waitlists, and credit-based bookings. API-first policy enforcement across all channels.
Billing Engine
Recurring Direct Debit, refunds, analytics, and full auditability. The billing data that MSF calculations are drawn from.
Membership
Flexible packages, multi-site pricing bands, scheduled price changes, and atomic lifecycle operations across the franchise network.
All modules share the platform's domain-modelled data layer, API-enforced business rules, and reporting foundations.
Frequently asked questions
Who needs the Franchising module?
Any franchisor operating a network where franchisees take bookings, bill customers, or manage memberships. Whether your franchisees run appointment-based services, classes, or subscriptions across multiple sites, this module adds the franchise layer (hierarchy, permissions, MSF, compliance) on top of the operational platform.
Can I use the core modules without the Franchising module?
Yes. The Booking Engine, Billing Engine, and Membership modules work independently for non-franchise operators. The Franchising module adds the hierarchy, multi-level permissions, and MSF calculation layer on top. It is not required for single-operator or directly-managed multi-site businesses.
How is MSF calculated?
MSF (Management Service Fee) calculation is configurable per franchise agreement. You can set percentage of revenue, flat fee, tiered, or custom structures. The key difference is that the calculation uses the billing engine's actual operational payment data, not self-reported revenue figures from franchisees. Both sides see the same numbers.
What about directly operated sites?
Franchisors that operate their own sites alongside franchisees are fully supported. Directly operated sites are modelled as a special franchisee record owned by the franchisor. Fee calculations can skip or apply differently to these locations. The network dashboard includes them naturally without architectural workarounds.
Can permissions be customised per franchise agreement?
Yes. Claims are scoped and assignable per franchisee. Different franchise agreements can result in different permission configurations. A franchisee running a single site might see a simpler view than one managing ten locations. The permissions model supports Site, Franchisee, and Franchisor scope levels with hierarchical resolution.
What happens when a franchisor acts inside a franchisee's site?
An explicit mode switch captures the context. The system records the action as a franchisor intervention in the audit trail, including the actor identity, the scope they were operating in, and what changed. Franchisees can filter their own audit log to see when and what head office touched. This transparency builds trust rather than eroding it.
Does this replace our existing franchise management system?
Yes. It replaces both the franchise management layer and the operational system. Instead of a franchise management platform with weak operational capabilities, or a generic operational system that does not understand franchising, you get best-of-breed booking, billing, and membership with the franchise layer built in. MSF calculation, compliance tracking, network dashboards, and multi-level permissions are native to the platform.
How does the data model handle multi-tenancy?
Shared database with logical tenant isolation through the Franchisor/Franchisee/Site ownership chain. Every entity is scoped to its position in this chain, and the permissions layer enforces visibility boundaries at the API level. No physical database separation is needed, and there is no performance penalty at scale. Adding a new franchisee or site is a configuration action, not an infrastructure change.
What licence do we get?
You receive a perpetual source code licence, the same as all other modules. You own all project-specific code outright, and you hold a perpetual licence to the underlying accelerator components. You can choose to have Talk Think Do provide ongoing support, or you can self-support with your own team. There is no lock-in.
Guides for franchise operators
Evergreen, vendor-neutral guides on choosing franchise software and the economics behind owning your platform. No product pitch, just the decision frameworks.
Franchise management vs operations software
Why networks end up running two systems, the operations gap that results, and how a unified platform closes it.
How to choose franchise software
The criteria that matter, an RFP checklist you can lift into a tender, and a structured evaluation process.
Own vs rent: licence vs per-member SaaS
How per-member subscription fees compare to an owned platform over a three-to-five-year total cost of ownership.
Ready to go further than the module? See how we deliver bespoke franchise platforms built around your operating model and owned by you.
Ready to see the franchise module in action?
Book a consultation and we will walk you through the platform, discuss your franchise requirements, and show you how quickly we can have you live.
Book a demoor call 01202 006729