A signed network and forty separate onboardings
Head office of a franchise network has signed. The plan is to make your product the standard for all offices. What actually happens is forty small onboardings, each with a franchise owner who has their own view about whether they need it. Some offices are live in a week. Some never finish setup because the owner is busy. A few use it in ways head office specifically asked them not to.
Head office asks you for a list of which offices are live. Your team builds it by hand from the database and it is out of date by the time it is sent.
Head office signs, the offices decide
Franchise networks sit in between a single company and a set of independent businesses. Head office sets brand standards, some processes and preferred suppliers. Each franchisee still owns its office, its staff and often its own local setup.
- Your product was designed with one agency as one account, so there is no way to express a group.
- Head office wants consistency, but every setting has to be configured office by office.
- Franchisees may be separate legal entities with their own data, and head office should not see everything.
- Rollout progress lives in your customer success person's spreadsheet.
- Training is repeated for each office, from scratch.
Why a slow rollout hurts more than a slow sale
A network deal is often priced on the whole network, and the offices that never get going become the reason for a difficult renewal conversation. Head office loses confidence when it cannot see progress. Your team spends more time on onboarding calls per office than the contract assumed, and offices that set things up inconsistently create support tickets that are really configuration problems.
There is a reputational edge to it too. Franchise owners talk to each other at network conferences and in private groups. An office that had a messy start tells the others, and offices that have not begun yet arrive at their first call already doubtful. A rollout that looks organised from the first office onwards gives the later ones a reason to get on with it.
How we build group rollouts into your product
What we build adds a group level above the office, and makes rollout a thing the product tracks.
- A group account with offices under it, each office keeping its own users, data and billing entity where needed.
- Group templates set by head office: listing text standards, email templates, workflow settings and branding, which offices inherit and can override only where head office allows.
- Data boundaries set out clearly: which information head office can see across offices (usage, rollout status, agreed metrics) and which stays private to the franchisee.
- A rollout tracker per office, with steps such as setup started, CRM connected, users invited, first live use, and trained, updated automatically from what happens in the product.
- Group reporting for head office, and alerts to your team when an office stalls at a step.
- Reusable training material and in-product guides, so each office starts from the same place.
| Setting | Set by | Office can change? |
|---|---|---|
| Branding on customer-facing pages | Head office | No |
| Email templates | Head office | Within allowed fields |
| Local contact details | Office | Yes |
| CRM connection | Office | Yes, with support |
| Usage visible to head office | Agreed in the contract | No |
A rollout head office can follow
Head office opens the group view and sees each office's stage. Thirty are live, six are connected but have not invited users, four have not started. Your customer success person has already had an alert about the six, and has a call booked with two of them. Offices that come on later inherit the group templates automatically, so their setup is shorter and looks the same as everyone else's. Franchise owners still control their own office, and head office sees what it agreed to see.
Checklist for networks and groups
- Your product has no concept of a group above an agency account.
- Head office settings have to be copied into each office by hand.
- Rollout status is tracked in a spreadsheet outside the product.
- It is unclear which data head office should see across franchisees.
- Each office's training starts from zero.