Use case
Opening a second location without doubling the admin
One site runs on people knowing each other. Two sites run on written processes, and the businesses that struggle are the ones that discover this after opening.
The situation
A business with a single location decides to open a second. The commercial case is sound and the operational plan is mostly about premises, staffing and stock. Systems rarely feature, because the current systems work.
They work because a single site is coordinated by proximity. People overhear things, ask across the room, and correct each other's mistakes without a process existing. None of that survives a second site, and what replaces it is either written process or a large volume of phone calls.
The symptom arrives about three months in: the founder or manager is spending most of their week travelling between sites, holding the business together personally, and cannot open a third.
How it shows up
- The same question is asked and answered differently at each site.
- Stock, pricing or promotions differ between locations without anyone deciding they should.
- Reporting is produced separately per site and combined by hand.
- The manager is the only communication channel between the two teams.
- New staff at the second site were trained by someone describing how it works rather than from anything written.
- Nobody can compare the two sites on a like-for-like basis, so problems are noticed late.
Symptom, cause and change
The most expensive mistake in this situation is treating a symptom as a diagnosis. These are the three columns kept apart.
Why it happens
- Process lived in people, not documents
- A single site does not need written procedure, so none was written and the gap only appears at two.
- Systems were configured for one location
- Single-site assumptions are baked into stock, pricing, rotas and reporting more deeply than expected.
- No definition of what is standard
- Without deciding what must be identical, both sites drift toward local preference immediately.
- Reporting was never comparable
- Metrics that made sense for one site do not automatically make sense per site, so comparison is impossible.
- The founder absorbed the gap
- Personal presence substitutes for process, which works at two sites and fails at three.
How we approach it
Decide what must be identical
The first decision is not technical. What must be the same at every site — pricing, product, brand, safety, the customer experience — and what is legitimately local, such as staffing patterns and supplier choices. Written down, this is the specification for everything that follows and it prevents the argument recurring at every site.
Document the process while you still have one site
The best time to write down how the business runs is before the second location exists, because at that point there is a single correct answer. Afterwards there are two versions and a negotiation. This is the highest-return work available and it is almost always skipped.
Make the systems multi-site before opening
Stock, pricing, rotas, bookings and reporting each carry single-site assumptions that surface at the worst moment. Configuring for location as a dimension, in advance, is considerably cheaper than retrofitting it while a new site is trying to trade.
Build per-site reporting from day one
Every operational number should carry a location, and comparison between sites should be available without assembly. This is what turns a problem at the second site into something noticed in week two rather than in the quarterly accounts.
Replace proximity with a communication structure
A defined channel for operational questions, a place where decisions are recorded and visible to both sites, and a short regular contact between the teams. Without it every question routes through the manager, which is the constraint that prevents a third site.
Automate the coordination, not the work
Rota generation, stock replenishment, consolidated ordering, and reporting distribution are the tasks that scale linearly with sites and are the right first automation targets. The work at each site is largely unchanged; the coordination around it is what multiplies.
What changes
- The second site opens on a defined process
- Rather than on a description of how the first one works.
- Comparable numbers from week one
- So a problem at either site is visible early rather than at quarter end.
- The manager is not the only channel
- Which is the specific constraint that decides whether a third site is possible.
- Standards hold without policing
- Because what must be identical was defined before either team had a preference.
- Coordination effort stays flat
- Rotas, ordering and reporting scale with configuration rather than with hours.
- A repeatable opening
- The second site becomes a template, which is the point at which expansion stops being bespoke each time.
Where it goes wrong
Opening first and documenting afterwards is the most common and most expensive sequence. Once two sites exist, there are two versions of every process and agreeing them becomes a negotiation rather than a decision.
Assuming the current systems will cope. Single-site assumptions are usually deeper than they appear, particularly in stock, pricing and rota tools, and they surface during the opening when there is no capacity to deal with them.
Centralising everything. Removing all local discretion produces a second site that cannot respond to its own market and a team that stops trying, which is a different failure from drift but not a better one.
Reporting that is not per site. Combined figures hide a struggling location for months, and by the time it shows in the total the problem is expensive.
Underestimating the communication gap. Two teams who never meet develop different practices quickly, and the divergence is not visible to either of them.
Copying the first site exactly, including its accidents. An opening is a good moment to discard the things the original site does only because it always has.
What else you could do instead
Not every expansion needs the same amount of systems work, and it is worth being honest about which situation you are in.
- Open lean and fix afterwards
- Viable if the second site is small, genuinely temporary, or a test. The cost is that documentation happens under pressure with two competing versions to reconcile.
- Document and configure first
- The usual recommendation. It delays the opening slightly and removes most of the failure modes, and the documentation is reusable for every subsequent site.
- Franchise or licence instead
- A different model with different economics, and one that forces the documentation to exist because someone else has to follow it. Worth considering if the plan is many sites rather than two.
- Stay at one site and grow it
- Sometimes the right answer. A second location adds fixed cost and coordination overhead, and expanding the existing site or its hours occasionally produces more margin with less complexity.
How we would know it worked
Before opening, record how many operational questions currently route through one person per week, and whether any of your core numbers can already be reported by location.
During the opening, the useful measure is how much of the process the new site can run from documentation without asking — which is a direct test of whether the documentation is real.
Afterwards, watch coordination hours per site and the divergence between sites on the metrics you defined as standard. If coordination hours are rising in proportion to sites, a third one is not yet feasible.
How long it takes and what it costs
Process documentation and defining what must be standard is typically three to six weeks, and it should happen before the opening rather than alongside it.
Making systems multi-site varies enormously with what is installed — sometimes configuration in days, sometimes a genuine change of platform. This is the item worth assessing early because it has the widest range.
Coordination automation — rotas, replenishment, reporting distribution — is usually better done a month or two after opening, when the real coordination burden is visible rather than assumed.
Estimates are labelled as estimates. Timelines here are planning ranges from comparable work, not commitments, and not measured client outcomes. We quote against a defined scope after a discovery call.
Services involved
Business Process Automation
Removing the manual steps between systems — the copying, re-typing, chasing and exporting that consumes hours nobody counts.
Read more →Systems Integration
Making the systems you already pay for talk to each other, reliably, without a person in the middle re-typing things.
Read more →Data Engineering & BI
Getting numbers out of the systems that hold them, into one place, in a state somebody can actually make a decision from.
Read more →Digital Transformation Consulting
Working out what to do, in what order, before anyone spends money building it.
Read more →CRM & Sales Systems
The system of record for revenue: where leads land, how they are routed, what happens next, and whether anyone can see the truth of the pipeline.
Read more →AI Knowledge Bases & RAG
Making the documents a business already owns answerable — with citations, access controls, and an honest "I do not know".
Read more →Questions
When should we start the systems work?
Before opening. Once two sites exist there are two versions of every process, and agreeing them becomes a negotiation between teams rather than a decision. The documentation is also considerably easier to write when there is only one correct answer.
Will our current systems handle a second location?
Assess it early, because the range is wide. Some tools handle location as a dimension out of the box; others have single-site assumptions embedded in stock, pricing and rotas that only surface during the opening, which is the worst time to find them.
How much should be centralised?
Whatever must be identical for the brand, the customer experience, safety and compliance. Beyond that, local discretion is usually valuable — a second site that cannot respond to its own market is a different failure, not a better one.
Why is per-site reporting so important?
Because combined figures hide a struggling location for months. By the time a problem shows in the total it has usually been running for a quarter, and the cost of finding it late is far larger than the cost of reporting by location from the start.
The manager is spending all their time travelling. Is that normal?
It is common and it is the signal that proximity has not been replaced with structure. It also works at two sites and fails at three, which makes it the specific constraint on further expansion rather than a temporary inconvenience.
Should we copy the first site exactly?
Copy what works and use the opening to discard what the original site does only because it always has. A second location is one of the few moments when questioning an established practice is organisationally easy.
What if we are planning ten sites, not two?
Then the documentation and multi-site configuration are not overhead, they are the product, and it is worth investing considerably more in them at site two. A franchise or licence model may also be worth examining, since it forces the same discipline for commercial reasons.
Can AI help with any of this?
Modestly and usefully: a retrievable knowledge base of procedures answers the questions that would otherwise route through the manager, which is exactly the constraint that limits expansion. It is a better fit here than customer-facing automation.
What does it cost?
Quoted per phase. The documentation and standards work is small, separable and worth doing regardless of what happens to the systems, so we would generally propose it first and on its own.
Other situations
- Replacing spreadsheets with a real system
- Cutting cost per qualified lead
- Launching in a new European market
- Making company knowledge searchable
- Automating quote to invoice
- Recovering from a failed migration
- Inheriting undocumented software
- Passing a customer security review
- Merging systems after an acquisition
Recognise this?
Tell us what it looks like in your business. We will tell you what we would do about it, and whether it is worth doing.
Get in touch