Franchising multiplies whatever you actually have. If what you have is an operating system — batches, fees, tests and reporting that run to standard — it multiplies a brand. If what you have is a founder’s heroics, it multiplies chaos. This playbook is about making it the former.
A coaching franchise sells one thing to a franchisee: results that repeat. Families in a new town enrol because the brand promises the same test cadence, the same teaching discipline and the same honesty about progress that made the flagship famous. Every part of that promise is an operations artefact — a batch structure, a mock calendar, a fee policy, a parent-update rhythm. Franchising is therefore not a marketing project with an operations annex; it is the export of your operating system with a logo on top. Institutes that write the operating system down before selling territory keep their brand; institutes that sell territory first spend years doing quality-control archaeology.
The workable split is consistent everywhere it touches the family and the audit, flexible everywhere it touches the locality. The spine: course and level structure, test-series cadence, fee components and receipt discipline, admission process, parent communication rhythm, and the monthly numbers every centre reports. The limbs: local fee levels within agreed bands, local hiring, local marketing. Encode the spine as configuration — courses, fee plans and test templates set up once and cloned per centre — and enforcement stops being a phone call and becomes a default. TutorDesk’s multi-branch structure is built for exactly this cloning; see the second-branch playbook for the single-owner version of the same discipline.
Most franchise disputes are arithmetic disputes: what was enrolment, what was collected, what does the royalty apply to. A percentage-of-revenue royalty is only as good as the ledger it reads from, which is why the franchise agreement and the software decision are the same decision. When every centre’s enrolments, fee collections and dues live in one system — franchisee seeing their centre, franchisor seeing the roll-up — the monthly royalty statement is a report, not a negotiation. The fee and finance layer does the recording; the network report does the trust.
You cannot audit teaching quality from a dashboard, but you can see its instruments: mock tests conducted on schedule, marks entered on time, attendance taken daily, parent updates actually sent. A centre where the instruments go quiet is a centre drifting from the system — visible weeks before the complaints arrive. Watching instrument compliance across centres through results and analytics turns quality control from surprise inspections into a weekly glance, and makes the difficult franchisee conversation specific: the mock calendar shows four tests missed, not “we feel standards are slipping”.
A franchise launch is the startup playbook with a head start: territory chosen, brand supplied, operating system cloned. Set up the centre in the system before the paint dries — courses, fee plans, batch calendar copied from the template, staff added, enquiry pipeline live from day one. The franchisor’s job in the first quarter is watching the same ramp numbers a founder would: enquiries, conversions, seats filled against plan. Our startup-cost calculator gives the franchisee the cash-to-launch number; the shared system gives the franchisor the honest view of the ramp.
Both models exist; what decides the argument is auditability. A percentage royalty is only collectable if enrolments and fee collections are recorded in a system both sides can see — which is why the reporting layer is a franchising decision, not an afterthought.
Standardise the things families experience and the numbers you audit: course structure, fee bands, test cadence, receipts and reporting. Leave local pricing latitude and local marketing to the franchisee — over-standardising is how franchisors end up running every centre themselves.
Yes — each franchisee operates their own branches, batches and ledgers, while the franchisor sees the network roll-up. Access boundaries are what make shared software politically workable.
Converged reporting beats converged tooling as a first step: agree the monthly numbers and formats first. But shared software is where audit friction actually disappears, so make it the default for new franchisees even if legacy centres transition slowly.
When its second branch runs to standard without the founder standing in it. If the playbook only works where you are physically present, franchising will multiply the chaos, not the brand — run the second-branch play first.
A 20-minute demo of multi-centre operations — cloned setups, franchisee views and the network roll-up.
