Software we can build for multi-location businesses
Every location runs a little differently, reports a little differently and keeps its own spreadsheet. Leadership sees the business a week late, assembled by hand. We build systems that give every location one way of working — and give you one view of all of them.
Where the work gets stuck in multi-location businesses.
- A spreadsheet per location
Each site tracks its numbers in its own file, with its own columns, and nobody is quite sure which version is current.
- Weekly reports built by hand
Someone at head office collects figures from every manager, chases the late ones and combines them before leadership can look.
- Procedures that drift
Opening, closing, safety and audit checklists are done differently at each site, and there is no record they were done at all.
- Requests lost between sites and head office
Purchasing, maintenance and staffing requests go by email, and approvals depend on who happens to see them.
- Stock and transfers by phone
One location runs short while another has plenty, and moving it means a call and a note on paper.
- Every new location starts from scratch
Opening a site means rebuilding the files, forms and contacts the others already have.
From one location’s day to leadership’s view
The work happens at the locations; the decisions happen centrally. The gap between the two is where the spreadsheets live.
- Opening checklist Done the same way everywhere
- Daily operations Logged as it happens
- Issues & requests Raised from a phone
- Approvals Routed by type and amount
- Inventory & orders Counts, orders, transfers
- Closing & daily numbers Captured, not emailed
- Regional roll-up Grouped automatically
- Leadership dashboard Live, every location
How a connected system would tie these together
- Every location works from the same checklists and forms, and completion is recorded rather than assumed.
- Requests route themselves by type and amount to the person who can approve them, with a record of the decision.
- Stock levels are visible across sites, so a transfer is a request in the system rather than a phone call.
- Daily figures arrive from the point-of-sale and the locations themselves, not from a manager’s email.
- Leadership sees every location, region and the whole business in one dashboard — the same day.
Systems we could build.
Starting points, not a product list. Most projects begin with one of these and grow from what the first phase teaches.
- Centralized operations platform
One system every location works in, configured centrally, with each site seeing what it needs.
- Checklist and audit app
Opening, closing, safety and quality checks on a phone or tablet, with photos and time stamps.
- Request and approval system
Purchasing, maintenance and staffing requests with routing rules, limits and an audit trail.
- Cross-location dashboard
Sales, labour, stock and completion figures by location and region, without anyone assembling them.
- Location template
A new site configured from your standard set-up in an afternoon, not rebuilt over weeks.
What it would connect to.
The figures you need usually already exist in other systems:
- Point-of-saleSuch as Square, Toast, Clover or Lightspeed, for daily sales by location.
- AccountingQuickBooks Online, Xero or your general ledger, for costs and spend by site.
- Scheduling and payrollLabour hours and cost per location, where the provider’s API allows.
- Google Workspace or Microsoft 365Staff accounts, calendars and shared files.
- SuppliersOrdering by API or file where a supplier supports it.
Vendor names are examples of systems you may already use, not partnerships. What can be connected depends on each vendor’s API and terms, which we confirm before anything is quoted.
What custom software should not replace.
A central platform should pull from your operational systems, not stand in for them. It should not replace:
- Your point-of-sale.
- Accounting and payroll.
- Industry platforms each location already depends on day to day.
- Franchise-mandated systems you are contractually required to use.
A workflow consultation, then a specification.
The first conversation is about 30 minutes and costs nothing: you show us how the work runs today, and we tell you whether custom software is worth exploring. Only a strong fit goes on to a paid specification.
- 01 Workflow consultation Free · about 30 minutes
Show us the workflow or the problem. We ask questions and tell you whether custom software is worth exploring — or whether something simpler would do.
- 02 Discovery & specification Paid engagement
Where there is a strong fit, we map the workflow properly and write it up as a specification: what the system does, for whom, how it connects, what it costs and when. You keep it whether or not we build it.
- 03 Fixed-scope build Quoted against the spec
The build is quoted and scheduled against the specification, so the figure you approve is the figure you pay. Anything new is quoted separately rather than absorbed quietly into the timeline.
- 04 Launch & care Optional monthly plan
Launch, then hosting, updates, security patches, store submissions and changes as your business moves. Whoever built it maintains it, and you can stop the plan whenever it stops being worth paying for.
Common questions.
Can each location see only its own data?
Yes. Access is set by role and by location, so a manager sees their site, a regional lead sees their region and leadership sees everything.
Our locations use different software. Can they still report into one place?
Usually. Each source is connected where its API allows, and the figures are normalised into one model so locations can be compared fairly. Where a system cannot be connected, a short daily form can stand in for it.
Can we start with one location?
Often that is the best way to start: build and refine with one site, then roll the same template out to the rest.
Show us how one location reports to head office today.
The spreadsheet, the weekly email, the checklist on the back wall. We’ll tell you whether one connected system is worth exploring.
You’ll hear directly from PiTech, typically the same business day.