| Franchise IT support is the arrangement covering technology across sites a group does not own: which systems are mandated, who pays for them and who fixes them. The work is harder than ordinary multi-site IT because each site is a separate business with its own bank account, so the group can specify a system but cannot buy it. |
A franchise group in Christchurch runs fourteen sites. Eleven belong to franchisees and three belong to the group.
Head office rolls out a new till system. Nine sites take it, two ask for a delay, and three keep what they already had because nobody can tell them they must change.
The franchise agreement runs to sixty pages and says almost nothing about technology. It names the brand, the territory, the fees and the fit-out, then leaves the systems to a clause about following the operations manual.
That clause was drafted before the operations manual mentioned software. So the group has one standard on paper and eleven readings of it in practice.
Franchise IT support is the work of turning eleven readings into one. It starts with a line most agreements never draw, between what the group decides, what the group suggests and what the site chooses for itself.
Most groups file this under governance and leave it for a calmer quarter. The cost is already running, and it comes out of the monthly numbers.
The figures below are illustrative. Take the same fourteen-site group and price a year of it.
Six sites buy their own till support locally at about $180 a month, where the group has negotiated $95. That is $6,120 a year off the profit of six franchisees, and the franchisor feels it at renewal.
The group help desk also fields about forty calls a month for faults a local provider has already billed a site for. Double-handling at that rate costs around $1,900 a year in wages.
So the standing cost is about $8,020 a year. Then a franchisee sells up, and the 2,100 customer records for that site turn out to sit in a booking system head office has never had a login to. Replacing that trade over the following year is worth about $9,000.
One boundary before we start. Buying a site back and folding it into head office is a different job with a day-one sequence of its own, and this article stays with the sites that stay separate.
What Is Franchise IT Support?
Franchise IT support covers standards, help desk routes, data ownership and procurement, with one difference from ordinary IT. Multi-site IT management inside one company has a single owner, a single budget and a single decision. A franchise group has one brand and as many balance sheets as it has franchisees.
Four things follow. Identity, data, support and procurement each break in ways they never break inside a single company, and each needs an answer written down before it is needed.
What makes a franchise group different from a business with several branches?
A branch has no separate legal owner and a franchised site does. A branch manager operates on a delegation from head office. A franchisee has signed a contract, put their own capital in and answers to a bank.
Every technology question in this article comes back to that difference. A group can install software in a branch on a Tuesday afternoon and cannot install anything at a franchised site until the owner agrees to pay for it.
Who is in charge of technology in a franchise group?
Nobody, in a good many groups, and the gap is seldom deliberate. The franchisor owns the brand and the systems carrying it, the franchisee owns the site and its equipment, and nobody has written down who owns the decisions in between.
Someone has to hold the standard, and in a group under thirty sites that person already has another job. Bringing in an outside advisor in a virtual CIO role is one way groups close it, because the work runs to a few days a quarter and does not justify a hire.
Which Systems Should a Franchise Group Mandate?
A group should mandate only the systems that carry the brand promise or hold group data, and leave the rest alone. In practice that is a short list: point of sale, the customer database, the booking or ordering channel, and staff identity.
Point of sale, usually shortened to POS, is the till system from the opening and the software behind it. It sets the prices a customer sees and the sales figures the group reports on, so a group with no visibility of it cannot manage the brand.
Three tiers do the sorting. Mandated systems are chosen and paid for by the group, and recommended systems are specified by the group and bought by the site.
Optional systems belong to the site alone. A group with an opinion about a site’s accounting package is interfering in a business it does not own.
Franchisor IT standards get easier to enforce once every system on the list carries a tier. The argument stops being about the group’s right to decide and becomes a shorter question about which tier a system sits in.
What belongs on the recommended tier?
The recommended tier holds systems where the group has a view and the site has a real choice. Rostering is the clearest example: a group can require that a site publishes rosters and logs swap requests without naming the product that does it.
In practice the rostering software a multi-site franchisee settles on is driven by the payroll they already run. A group that mandates a product here inherits a support obligation it never wanted.
Phones sit on the same tier. Mobile numbers deserve a separate look, because whose name the mobile account sits in decides whether the site keeps the number a customer has saved.
Who Pays for Franchise IT, the Group or the Site?
Whoever decides should normally pay, and most disputes start where those two come apart. A group that mandates a system and expects the site to fund it has created a cost the franchisee never agreed to.
The reverse happens just as often. Head office funds a tool, cannot make anyone use it, and carries a licence bill for eleven sites where four people log in.
Plot every system against those two questions and most land in an obvious corner. Two or three sit on the diagonal, where the group decides and the site pays, and those are worth arguing over in a room before anyone signs.
| System | Who should decide | Where the argument starts |
|---|---|---|
| Point of sale | The group | A site holding a paid-up licence for something else |
| Customer database | The group | Enquiries the franchisee generated with their own local advertising |
| Staff identity and email | The group | Franchisees who want their own domain on outgoing mail |
| Rostering and payroll | The site | A group wanting labour percentages it can compare across sites |
| Local internet and WiFi | The site | An outage the group help desk gets called about first |
| Help desk and support | The group | A site paying twice because the local provider answers faster |
Why does a group procurement deal fall over?
A group deal fails when the franchisor cannot commit the volume it quoted. Vendors price on committed sites, and a franchisor who signs for fourteen and delivers nine loses the discount at the first review.
Software licensing is the sharper version, because a licence bought by head office and used by a separate legal entity often breaches the terms it was sold under. Check the entity named on every agreement before the group counts a saving.
Should Franchisee Staff Sit in the Group’s Microsoft 365 Tenant?
Yes, but only if the group is prepared to administer them, which is a larger commitment than it looks. A tenant is the group’s own instance of Microsoft 365, and every account inside it is created, licensed and eventually disabled by whoever holds the administrator role.
The directory underneath is Microsoft Entra ID, which most administrators still call Azure Active Directory. Whoever holds it holds the off switch for every account inside it, and the schedule should say so in writing.
Putting franchisee staff in the group tenant gives head office one directory to search and one list to disable. It also makes head office the password reset desk for eleven businesses that pay it nothing.
Leaving each site on its own tenant puts both jobs back on the site. Head office stops resetting passwords, and also loses any way to confirm a departed manager lost their access.
How does trusted access work when a site keeps its own tenant?
Trusted access lets a franchisee’s staff reach group systems with the accounts they already have, so the group never issues them a second one. Microsoft calls this business-to-business collaboration, and Microsoft’s own documentation describes the partner signing in with their own credentials while the host keeps control of the shared resources.
Cross-tenant access settings then decide which users from which site can authenticate against which applications. Franchisees keep their own directory, and the group keeps a switch it can turn off on the day a site exits.
Who Owns the Customer Data in a Franchise Group?
The brand usually owns the customer relationship and the site usually holds the records, and only the franchise agreement settles which is which. Group and site are separate agencies under the Privacy Act 2020, which replaced the Privacy Act 1993, so passing a customer list between them counts as a disclosure between organisations.
Information privacy principle 11 sets out when an agency holding personal information may disclose it to another agency. The usual ground is that the disclosure was one of the purposes the information was collected for.
Tell the customer at the point of collection. A booking form saying their details are held by both the group and the site settles the question long before anybody asks.
Principle 11 also permits disclosure where it is necessary to facilitate the sale of a business as a going concern. Groups lean on that ground when a franchisee sells their site to an incoming operator.
Whatever the agreement says, write down which system holds each site’s customer records and who has a login. Most groups cannot answer the second half.
What happens to employment records when a franchisee exits?
They stay with the franchisee, because the franchisee is the employer. Employment New Zealand requires an employer to keep wage and time records and holiday and leave records for six years, even after the employee has gone, under the Employment Relations Act 2000 and the Holidays Act 2003.
So an exiting franchisee cannot hand the whole system across and walk away. Write the split into the exit runbook while both parties are still on speaking terms.
How Should Franchise IT Support Work Across Sites?
Franchise IT support works when the group covers the mandated tier, the site covers everything else, and both routes are published. A franchisee left to guess will ring whoever answers, and the group pays for the same fault twice.
It stops working the week the group desk starts fixing printers at a site that also pays a local provider, because two organisations are then half-responsible and neither holds the whole picture.
Write the escalation path into the schedule with a named contact and a response target. That target is the service level agreement, or SLA, and it gives a franchisee something to measure the group against.
What should a franchisee do when a fault is theirs to fix?
Ring their own provider first and tell the group afterwards. A site’s internet connection, its local network and the gear behind the counter belong to the site, and the group help desk has neither access nor a contract to touch them.
The exception is a fault on a group system that stops the site trading. Those go to head office first, because head office holds the vendor relationship.
Put both numbers on a card by the till. The person who opens up and finds the fault has usually never read the schedule.
What Belongs in a Franchise Technology Schedule?
A franchise technology schedule lists every system a site touches, the tier it sits in, who pays and who supports it. It attaches to the franchise agreement so it can be updated without reopening the contract, and a new franchisee reads it before signing.
Six things belong in it: the system list with tiers, the identity arrangement, the data ownership statement, the support routes, the procurement terms and the change process. Anything a franchisee could reasonably argue about later deserves a line.
The franchisee onboarding runbook and the exit runbook then make the schedule real. Onboarding covers accounts created, systems provisioned and training booked before opening day. Exit covers accounts disabled, group data returned, licences reassigned and the site’s employment records left with the outgoing franchisee.
What should a franchisee ask before they sign?
Ask which systems are mandated, what each costs per month, and who pays when the group changes its mind. A franchisor who cannot answer that in writing has not done this work yet.
Then ask the two exit questions: what happens to this site’s customer records, and what happens to the staff accounts, when the agreement ends. Both answers belong in the schedule, in writing, before anybody signs.
How is the schedule kept current as systems change?
Review it once a year and version it, the same way the operations manual is versioned. A schedule naming a product the group dropped two years ago gives a franchisee fair reason to ignore all of it.
Give one person the pen. Changes agreed in a franchisee council meeting and never written down are the main reason groups end up back where they started.
How Much Does Franchise IT Support Cost?
Around $4,800 once and about $180 a month afterwards, for a group under twenty sites. Take the fourteen-site group from the opening.
The one-off buys the system audit, the schedule and the two runbooks. The monthly figure covers keeping the standard current, at $2,160 a year. Franchise IT support for the mandated systems is priced separately and per site, outside both of those figures.
Against the $8,020 a year the gap was costing, that leaves about $5,860 a year, and the $4,800 is paid once. The $9,000 exit exposure sits outside that arithmetic. The exit runbook removes it separately.
What makes one franchise group cost more than another?
Variation matters more than site count. A group of thirty sites all running the same three systems costs less to standardise than a group of twelve where every owner chose their own.
Age is the other factor. A group fifteen years into franchising holds agreements from four eras, and the oldest say the least about technology. Read those before quoting the work, because they set the floor for what the group can require.
How Do You Get a Franchise IT Standard in Place?
Start with an audit of what every site is running today, because most groups are wrong about this. Then work through the following.
- List every system in use across every site, including the ones nobody at head office approved. Ask the franchisees, because the finance system will never show a $40 a month subscription paid on a personal card.
- Sort each system into mandated, recommended or optional, and write who decides and who pays beside it.
- Settle the identity question before anything else. Group tenant or site tenant with trusted access, chosen once and applied the same way at every site.
- Write the data ownership statement, covering customer records, employment records and anything a departing site would want to take with it.
- Publish the support routes with a named contact for each, and tell every franchisee which number to ring for which kind of fault.
- Attach the schedule to the agreement, then run the next onboarding and the next exit against the runbooks to find what is missing.
Book a Franchise IT Review
Exodesk has supported South Island businesses since 1989 and works with clients across Canterbury, Otago and Southland from offices in Christchurch and Dunedin. Our IT consulting work with franchise groups starts with the system audit and ends with a schedule your lawyer can attach to the agreement.
Contact us today to discuss how we can help your business or connect with us on LinkedIn to stay updated with more insights.
Frequently Asked Questions
What does a franchisor need to put in writing about technology?
A franchisor should record the system list, the tier each system sits in, who pays for it and who supports it. Data ownership and the identity arrangement belong in the same document. Without those written down, every question falls back on a clause about following the operations manual.
Can a franchisor make a franchisee buy a particular system?
Yes, where the franchise agreement or the operations manual it refers to says so, and no where both are silent. Older agreements say almost nothing about software, and a group in that position can only ask.
What happens to a franchisee’s customer list when they exit the group?
The franchise agreement decides it, and many older agreements do not address the question at all. Where the group owns the customer relationship, the exit runbook should name the format and the deadline for the handover. Agree that wording while the relationship is working, because an exiting franchisee has little reason to cooperate later.
How much should a franchise group budget for a technology schedule?
A schedule, two runbooks and the system audit behind them sit in the region of $4,000 to $6,000 for a group under twenty sites, with ongoing coordination at a few hundred dollars a month. Older groups cost more because of the number of legacy agreements somebody has to read.
Is a group help desk cheaper than every site using a local provider?
Yes for the mandated systems, and usually no for everything else. Franchise IT support bought centrally pays for itself on the till system and the customer database, where one team learns the product once. Local providers still win on cabling, printers and anything somebody has to walk in and look at.
What happens to a franchisee’s Microsoft 365 accounts when they leave the group?
Accounts living in the group tenant are disabled on the exit date, and the mailboxes and files inside them go at the same time. A site running its own tenant keeps all of it, and the group withdraws trusted access. Decide which of the two applies before a site is signed, because migrating afterwards is a project in itself.
Who is responsible when a franchised site has a security incident?
The franchisee is responsible for their own business and the group is responsible for the systems it mandates. Both are separate agencies under the Privacy Act 2020, so both can carry their own notification duty. The schedule should name who the site calls first and who tells whom. Groups that leave it to the day of the incident usually find their agreement covers none of it.
Does every site in a franchise group need the same point-of-sale system?
Yes in almost every group, because the point of sale sets the prices a customer sees and produces the sales data head office reports on. Back-office tools such as accounting can be left to the site.
How long does it take to agree a franchise IT standard?
Six to ten weeks for a group under twenty sites, most of it spent waiting for franchisees to answer the audit questions. The writing takes a fortnight. Getting it signed depends on whether the change goes in as a schedule or needs the agreement itself reopened. Groups that consult a franchisee council first usually land it faster.
Does Exodesk work with franchise groups outside Christchurch and Dunedin?
Yes. Exodesk supports clients across Canterbury, Otago and Southland, and franchise work is mostly remote once the site audit is done.
What is the first thing a new franchise group should do about IT?
Draw the line between mandated, recommended and optional systems before the second site opens. Setting a standard is far easier when there is one franchisee to agree it with. The schedule can be short at that stage. Groups that leave it until site eight are renegotiating with seven owners who have already bought something.
