Custom Software for Franchisors and Multi-Unit Operators
Royalties calculated from self-reported sales, a new-unit opening pipeline that lives in one spreadsheet per location, and brand audits on a paper clipboard. Here is what a franchise system is worth building — and what to leave alone.
Your product is the system, and you are running it on email
A franchisor does not sell sandwiches, or haircuts, or gutter cleaning. It sells a repeatable operating system and the right to run it, and it gets paid a percentage of whatever that system produces. Everything that matters commercially comes down to three questions: are the units performing, are they operating the way the brand requires, and are you collecting what the agreement says you are owed.
Most franchise systems under a few hundred units answer all three the same way — a monthly email from each operator, a workbook one person maintains, and a field visit whose findings live on a clipboard. That works at ten units. Somewhere between twenty and fifty it quietly stops working, and the failure is not dramatic. Royalty disputes take a week to resolve. Nobody can say which units are trending down until the quarter closes. The same standards problem shows up at four locations and nobody notices it is a pattern.
The interesting part is that franchisors usually have more leverage from software than almost any other kind of small business, because whatever you build gets applied across every unit at once. A day saved per location per month is not a day. It is the number of units times twelve.
Where off-the-shelf breaks for a franchise system
There is real franchise management software on the market and you should look at it seriously before building anything. The trouble is that these products encode one opinion about how a franchise works, and franchise agreements are famously specific. Yours has a gross sales definition, a royalty structure, an ad fund arrangement, a transfer process, and a set of standards that are not quite anyone else's.
- Royalties are calculated from numbers you cannot verify. Units self-report sales, someone re-keys them into a workbook, and the royalty is whatever the formula in that workbook produces. Exclusions, adjustments, minimums, and late fees get applied by memory. When a franchisee disputes a figure, the reconciliation is an archaeology project.
- Sales data is stranded in four different point-of-sale systems. Locations opened in different years on different hardware, a few acquired units kept their own, and one operator switched last spring without telling anybody. There is no single sales number for the system that was not assembled by hand.
- Opening a new unit lives in a spreadsheet per location. Site approval, lease, permits, build-out, equipment, training, pre-opening inventory, grand opening — a hundred-plus milestones with dependencies and dates, tracked in a copy of a template that drifts from the original the day it is copied. Nobody can see which of the six units in the pipeline is actually behind.
- Brand standards audits produce paper, not change. The field consultant visits, scores the location, notes the same three issues, emails a PDF. There is no reliable record of whether the corrective action happened, no trend by location, and no way to see that a supplier problem is showing up in nine stores rather than one.
- Franchisees get nothing back. The operator sends numbers up every month and receives a bill. They have no benchmark, no current document library, no visibility into their own history. So they treat reporting as a tax, and the data quality reflects that.
- Ad fund accounting is opaque to everyone. Contributions come in, spending goes out, and the reporting franchisees receive is a summary they have no way to check. This is a common source of friction and occasionally of litigation, and it is almost entirely a bookkeeping-visibility problem.
The diagnostic works the same way it does everywhere: find the spreadsheets. In a franchise office they are almost always a royalty workbook, an opening checklist per location, a contact and agreement-terms list, and an audit log. Those four documents are a precise specification of what your software does not do — the signal is covered in when to replace your spreadsheets with custom software.
The royalty engine is the product
If you build one thing, build this. It is the only system that touches every franchisee every single period, it is where trust is won or lost, and it is usually the least reliable thing in the business.
A working royalty engine holds each unit's actual agreement terms — rate, gross sales definition, exclusions, ad fund percentage, any minimum, the effective dates when terms change. It receives the sales figure, applies the formula, and produces a statement the franchisee can look at line by line. It tracks what was invoiced against what was collected, flags underpayments before they become a quarter old, and keeps the history so that a dispute in March about a figure from November takes ten minutes instead of a day.
The second-order benefit is the one franchisors do not expect. Once the sales history is clean and continuous, you can finally see the system rather than the anecdotes: which units are trending, which cohort of openings underperformed, whether the operators who came from inside the brand outperform the ones who came from outside. That reporting is a different discipline from dumping columns, and it is covered in custom reporting software. Pushing the resulting invoices and receipts into your books without re-keying is covered in custom software with QuickBooks integration.
Read the registers. Do not replace them
The instinct when sales data is scattered across four point-of-sale systems is to standardize everyone onto one. Sometimes that is right as an operational decision. It is almost never right as a software decision, and it is a bad reason to start a build. Point-of-sale carries payment processing, tax handling, and certified hardware, and rebuilding it buys you nothing your competitors do not already have.
Build the layer above instead. Your system reads sales out of whatever each unit runs, normalizes the numbers into your definition of gross sales, and becomes the single source for royalty, benchmarking, and reporting. Units that cannot be connected submit a figure manually through the same pipeline, so the process is identical whether the data arrived by API or by hand. The patterns for pulling from systems you do not control, without destabilizing them, are in connecting two business systems. The general version of this problem across locations is in custom software for a multi-location business.
The opening pipeline is a project, so treat it like one
Every new unit is the same project run again with different dates, and the spreadsheet template is an admission that you already know the sequence. The problem is that a copy of a template cannot tell you anything across locations.
Encode the sequence once — site approval, lease execution, permits, contractor, equipment order, training dates, inventory, opening — with real dependencies, owners, and expected durations. Then every unit in development is a live instance of it, and the question “which openings are at risk” is a screen rather than six phone calls. The value compounds over time, because you accumulate honest data about how long each stage actually takes, which is what makes the next development schedule credible instead of optimistic.
Franchisee onboarding belongs in the same flow: application, qualification, discovery day, the disclosure and signing steps, initial training, and transfer into the operating system. The documents that pile up at every stage need a filing system rather than an inbox, which is the subject of custom document management software.
Field audits that produce corrective action, not PDFs
The field visit is your only direct observation of whether the brand is being operated as promised, and in most systems its output evaporates. A scored checklist on a tablet with photos attached is a small build. What makes it worth doing is everything downstream: each finding becomes an item with an owner and a due date, the operator sees it in their own portal, and the next visit opens with what was outstanding from the last one.
Once a season of audits exists as data rather than documents, patterns surface that no individual visit could show. The same failure appearing across a region usually means a supplier, a training gap, or a procedure that does not survive contact with a real kitchen — and any of those is a brand-level fix rather than nine separate conversations.
Give the franchisee a reason to log in
This is where most franchisor systems fail, and it is a design failure rather than a technical one. If the portal exists to collect reports, enforce standards, and chase payments, operators will use it exactly as much as the agreement requires. Data quality follows engagement, so a portal nobody wants to open produces worse numbers than the email it replaced.
The thing that reliably earns adoption is benchmarking. An operator who can see how their unit compares to the system on the numbers they already lose sleep over — sales trend, labor percentage, ticket average, the metrics your brand actually manages to — will open the portal without being asked. Add the practical items around it: current versions of every operations document, their own statements and history, a place to submit a request and see where it stands. What belongs in a portal and what does not is covered in what a client portal is and whether your business needs one.
Two constraints are worth stating plainly. Comparative performance data has to be presented so that no operator can identify another operator's numbers, and how you aggregate that is a decision to make deliberately rather than by accident. And any financial performance information you publish to prospective franchisees sits inside disclosure rules — your franchise counsel governs what can be represented and how it must be substantiated. Build the reporting so it can produce a defensible number with its source data attached, and let your attorney decide what leaves the building.
What to build, in what order
The failure mode here is scope. Royalties, POS integration, openings, audits, training, supply chain, marketing funds, and a franchisee portal in one build is a long project with a real chance of collapsing under its own weight, and none of it is necessary.
Start with the unit record and the royalty engine, because every other feature is a property of a location that has sales, terms, and a history. Add sales-data ingestion next, since it removes the largest source of manual work and makes the royalty numbers defensible. The franchisee portal comes third, launched with benchmarking included so it is worth opening on day one. Field audits after that, because the checklist is small but the corrective-action loop needs an audience that is already logging in. Openings and onboarding last, since they involve the fewest people and benefit from a team already fluent in the system. Sequencing work like this is in how to scope a software project.
When you should not build anything
Three situations argue against a custom build, and each deserves to be ruled out first.
If you run a handful of units and one person handles royalties in an afternoon, the workbook is genuinely working. The economics turn when more than one person needs to know the answer without asking the person who owns the file.
If you already license franchise management software and use a third of it, look there before building. Plenty of brands are paying for an audit module or a portal inside a product they own and abandoned during a busy quarter when the setup stalled.
And if two people in your office would describe the gross sales definition differently, software will encode the disagreement rather than resolve it. Settle the contract interpretation first — with counsel if it is genuinely ambiguous — because a royalty engine built on an unsettled definition will be wrong faster and more consistently than a spreadsheet ever was. How to tell which situation you are in is in seven signs your business has outgrown its software.
How we approach it
Brad Walker has spent more than twenty years building operational systems for service businesses, distributors, and manufacturers from Wake Forest, NC. A franchise engagement starts by following one period end to end: what each unit reported, how it got into the workbook, what the formula did to it, what was invoiced, what was collected, and what had to be corrected afterward. That trace usually explains most of the friction in the system and defines a build small enough to finish.
Engagements are fixed price, with the scope agreed before development starts. You know what you are getting, what it costs, and when it lands.
Frequently asked questions
What should a franchisor build first?
The royalty engine, because it is the one system that touches every franchisee every period and it is almost always the least trustworthy thing in the business. That means a single place that holds each unit's agreement terms, receives or pulls the sales figure, applies your actual definition of gross sales including the exclusions in the contract, calculates royalty and ad fund contributions and any minimum, produces a statement the franchisee can see, and tracks what was collected against what was owed. Most franchisors run some version of this in a workbook that one person maintains, which means reconciliation happens by memory and disputes get settled by whoever has the better email thread. Fixing that first also creates the sales history everything else depends on: benchmarking, field-audit context, and honest reporting about how units actually perform.
Should a franchise system replace its point-of-sale software?
No. Point-of-sale is a mature product category with payment processing, tax handling, and certified hardware behind it, and rebuilding it produces no competitive advantage. The problem in most franchise systems is not the POS itself — it is that different locations run different ones, or different versions, and nothing pulls the numbers into one place. The right build reads sales data out of whichever systems your units run, normalizes it into one definition, and leaves the registers alone. That is an integration project rather than a replacement project, and it is substantially smaller, cheaper, and safer than it sounds.
Will franchisees actually use a franchisor-built system?
Only if it gives them something. A portal that exists to collect reports, enforce standards, and chase payments will be used exactly as much as the agreement requires and no more. The systems that get adopted give the operator something they cannot get anywhere else — most often, how their unit compares to the rest of the system on the numbers they already care about, plus a single place to find the current version of any document, submit a request, and see where it stands. Build the franchisee-facing value at the same time as the franchisor-facing reporting, not after it. Adoption is the whole ballgame, because a compliance tool nobody opens produces worse data than the email it replaced.
If closing a royalty period takes a week and the answer to “how is unit fourteen trending” is a phone call, that is a fixable problem — and a smaller build than it feels. Start the conversation. The first step is a discovery call to trace one royalty period from the register to the deposit.
Ready to talk about your project?
Tell us what you're building. Brad reviews every submission personally.
Start Your Project