Reducing the Technology Load on Franchise Head Office
In most growing franchise networks, head office never decided to become the technology function. It happened because someone at a site needed help and someone at head office knew the answer.
That person helped. The next time there was a problem, the same person was called. Over time, a support role was created without anyone designing one, and it landed on people whose actual jobs are operations, finance or growth.
The cost is rarely visible as a line item. It shows up as interrupted work, slow decisions, and senior people spending their day on things a defined support path should have handled without them.
The short answer
Head office ends up as the network's IT helpdesk because there is no defined support path, so every problem escalates to whoever helped last time; the fix is to give technology support a clear, owned path that does not route through operations or finance staff, and to automate the work that is purely rule-based so the remaining load is genuine judgement that belongs with a person. The LOOKUP Business Modernisation Framework provides the method for sequencing that work.
How head office ends up carrying it
Store staff call whoever helped last time. That is not a failure of the store — it is the only path they know. If the network has not published a support number or a helpdesk, the person who answered before becomes the default.
There is usually no defined support path because the network grew without one. At the first few sites, asking head office was fine. By the time there are enough sites that it is no longer fine, the habit is entrenched and the people carrying it are too busy to step back and design a replacement.
The people absorbing the load are almost never IT staff. They are operations managers, finance officers or franchise coordinators who happen to be good with technology, or who were the first person someone rang. They have other jobs, and every interruption costs them more than the time the call takes.
What it actually costs
Senior people interrupted
The largest cost is not the time spent on the call. It is the work that was in progress when the call came in, and the time it takes to return to it after the call ends. Senior people interrupted mid-task lose more than the duration of the interruption — they lose the thread.
Slow resolution because nobody owns it
When a problem lands with someone whose job is not IT, it sits behind their real work. A password reset that a helpdesk would handle in minutes can wait days, because the person who received the request has a report to finish first.
Inconsistent answers
Different sites get different advice depending on who they called and what that person knew at the time. The same problem gets solved differently at every location, which makes the network harder to support as it grows.
No record of what went wrong or how often
Calls taken on a mobile phone and fixed by word of mouth leave no record. Head office cannot see what is breaking, how often, or whether a recurring problem needs a permanent fix rather than another workaround.
How this maps to the LOOKUP Business Modernisation Framework™
Reducing the technology load on head office follows the same eight-stage sequence, because a defined support path only holds once identity, access and information are under control.
Understand the current environment
Protect identities, devices and information
Remove legacy technology constraints
Create consistent systems and processes
Improve workflows and productivity
Establish governance and AI readiness
Introduce technology deliberately
Measure, review and continuously improve
Understand the current environment
Protect identities, devices and information
Remove legacy technology constraints
Create consistent systems and processes
Improve workflows and productivity
Establish governance and AI readiness
Introduce technology deliberately
Measure, review and continuously improve
Discover
Map where technology support currently lands across the network, who is absorbing it, and which problems recur most often at the site level.
Secure
Put identity, access and device security under a managed baseline so the most common support calls — password resets and access changes — have a defined path rather than a phone call to head office.
Modernise
Standardise the Microsoft 365 environment across sites so staff at every location use the same tools and the same configuration, reducing the variation that generates support calls.
Standardise
Define a single support path with a published helpdesk, so every site knows where to go and head office stops being the default escalation point for routine technology problems.
Optimise
Identify the support requests that are purely rule-based — password resets, account unlocks, device enrolment — and route them to automation or a managed service rather than head office staff.
Prepare
Review which remaining requests genuinely require human judgement and confirm those stay with a named owner, so automation does not remove the decisions that need a person.
Implement
Deploy the managed support path site by site, starting with one location, proving the model, then replicating it so head office is removed from the loop gradually rather than through a single cutover.
Improve
Review what the support path is handling, what is still reaching head office, and whether the remaining calls indicate a deeper problem that needs a permanent fix rather than ongoing support.
The visibility problem underneath it
Head office is asked to be responsible for the network's technology without being able to see it. Decisions about security, compliance and support are made blind, because the information needed to make them sits at individual sites or with local suppliers who do not report back.
Device health across every location
A central view of whether devices are patched, online and compliant should not require emailing each site manager. Head office needs to see the state of the network without asking for it, or it cannot act until something has already gone wrong.
Security posture in one place
Multi-factor authentication coverage, endpoint protection status and access reviews should be visible from a single dashboard, not assembled from spreadsheets and phone calls. Without that view, head office cannot answer a simple question: are we exposed right now?
Compliance without asking each site
When a compliance question arrives, head office should be able to answer it from central systems rather than chasing each location for evidence. If producing a compliance report means ringing every site, the network is too large for the process that produced it.
The recurring reporting problem
Compliance reminders, recurring reports and network-wide summaries are usually produced manually, by hand, on a cycle. Someone at head office collects the information, formats it, checks it and sends it — every week, every month, every quarter.
This is the most automatable work in the whole network and usually the last thing anyone looks at. It is repetitive, rule-based and entirely predictable in its timing and shape, which is exactly the profile of work that should never touch a senior person's calendar.
It survives because it was built before the tools existed to replace it, and because the person doing it has never had the authority to stop. Meanwhile, the franchise groups that address it first recover the attention of the people who should be working on growth, not on formatting.
The three kinds of work
Work that should be eliminated
Some of the load on head office exists only because of a gap in process. A password reset that reaches a finance manager, a compliance report assembled by hand, a support call routed through operations — none of these should be happening at all once a defined path and basic automation are in place.
Work that should be automated
Recurring reporting, compliance reminders, account provisioning and device enrolment are entirely rule-based. They follow the same steps every time, produce the same output, and depend on no judgement. This is the work that automation handles cleanly and that should never sit with a senior person.
Work that must stay with a person
Decisions about a franchisee relationship, a commercial dispute, a strategic technology change or a response to a serious incident require judgement about the business. That work stays with a named owner. The point of removing the other two categories is to protect the time for this one, not to eliminate it.
A defined support path
The answer is not head office trying harder. The people absorbing the load are already capable; the problem is that there is no path, so every problem finds its own way to the same person.
A defined support path means site staff know exactly who to contact, how to contact them, and what happens next. It means head office is no longer the default escalation point for a password reset or a printer fault. And it means the calls that do reach head office are the ones that genuinely belong there.
Once the path exists, the load does not need to be managed — it needs to be routed. That is the difference between a network that grows and a network that just gets louder.
A published example
Soul Origin, a national food retail network, worked with LOOKUP to address exactly this problem. As published, centralised helpdesk support for both head office and store managers reduced the time head-office staff spent acting as a makeshift IT helpdesk.
The centralised support path gave store staff a defined contact for technology problems, so head office was no longer the default. That is the part of the story relevant here. The broader technology standardisation behind those store openings is covered separately in the repeatable blueprint behind new store openings.