Quick checklist
- Can one location see another's customers, and should it?
- When head office asks for group numbers, who assembles them and how long does it take?
- When an enquiry comes in, what decides which location it belongs to?
- If a site manager leaves, what do they still have access to?
- Is every location doing it the same way, or the way that site invented?
Opening a second location rarely breaks the work. Plumbing is plumbing, a haircut is a haircut. What breaks is everything around the work: who can see which customers, whose revenue is whose, and which site a new enquiry belongs to.
Most businesses meet this the same way — a second copy of the spreadsheet, a second inbox, and a monthly evening spent adding two sets of numbers together.
The four things that actually break
Data separation. Site B should not be browsing Site A’s customer list. That sounds obvious until you try to enforce it in a system that was designed for one location, where the honest answer is usually “we just trust everyone”. Trust is not a permission model, and it stops being sufficient the day a manager leaves for a competitor.
Reporting rollup. Head office needs group numbers, each site needs only its own, and both need to agree. Assembling that by exporting two spreadsheets and pasting them together works for exactly as long as nobody is busy. It is also the point where the numbers quietly stop matching.
Territory routing. A new enquiry arrives. Which location owns it? If the answer is “whoever picks up the phone”, you get two people calling the same customer, or nobody calling. Routing by postcode is the usual fix and it is not hard — but it has to live somewhere, and a rule in someone’s head is not a system.
Consistency. Every location eventually invents its own way of quoting. Six months later nobody can compare anything, because Site B’s “job” means something different from Site A’s.
Franchising makes all of it contractual
If the second site is a franchise rather than a branch, these stop being convenience problems and become obligations. Royalties have to be calculated from numbers the franchisee can see and trust. Compliance has to be evidenced, not asserted. And a franchisee’s data is genuinely theirs — head office seeing everything by default is a problem, not a feature.
That is the point where a spreadsheet stops being merely awkward and starts being a liability.
We built one, which is why we are blunt about the cost
Our own platform runs this: postcode-routed territories, royalty calculation, per-site data separation, head-office rollup, and roles that decide who sees what. It is what we use to run this business, and you can look at it.
Building it took far longer than the operations software underneath it. That is the honest shape of this work — the multi-site layer is usually more effort than the thing it is wrapped around, because it is all edge cases about visibility. Multi-site platforms start from $35,000 for that reason, and the pricing page has the rest.
When you should not build this
If you have two locations and one owner who sees everything, you do not have a permissions problem. You have a spreadsheet problem, and a shared system with a “location” column solves it for a fraction of the price.
Build the multi-site layer when one of these is true: someone outside your household needs restricted access, money is split between parties who each need to trust the figures, or you intend to add sites faster than you can personally supervise them.
Before that point, this is expensive insurance against a risk you do not have yet.
Bottom line
One location is a business. Two is a reporting problem wearing a business costume. The work is almost never the operations — it is deciding who can see what, and making the software enforce it.
Want a hand with this?
Tell us what you're trying to sort out and we'll give you practical, plain-English advice before you spend money.
