Running Location Two Without Cloning Yourself

It's a Tuesday, the new spot has been open nine days, and your phone has buzzed six times before lunch. None of it is an emergency. One crew member wants to know which supplier you use for the blue stock, one forgot the gate code, and one is asking whether you comp a customer who showed up late or hold firm. Small questions, all of them. Every single one lands on you.

That's the part nobody warns you about when you open location two. The work isn't the hard bit, you already know how to do the work. The hard bit is that everything you used to just know, the prices and the passwords and the little rules you invented over the years, now has to live somewhere other than inside your own head.

One location runs fine on memory and instinct, because you're always there. Two locations run on whatever you've managed to write down, because you physically cannot stand in both places at once. This isn't really about buying software. It's about getting what's in your head into a shared place before the gaps start costing you customers.

The stuff that lived in your head now needs an address

For years you've been the manual. A customer asks a weird question, you know the answer. A new hire wonders where the spare blades are, they ask you, you tell them. The business ran on your recall, and that worked because you were the one constant in the room.

Open a second location and that breaks in a single move. You can't be the manual for a room you're not standing in. So the first job isn't automation at all, it's a brain dump: getting the knowledge out of your head and into a spot your crew can reach without calling you mid-job.

Keep it plain to start. One shared document, or a small handful, that answer the questions you field most:

Prices and rules. What you charge, what you'll bend on, what you won't.
Vendors and accounts. Who you buy from, the account numbers, who to call when an order shows up wrong.
Codes and keys. Gate codes, alarm steps, where the spare is hidden.
The little rules. The comp policy, the no-show policy, how you handle the regular who always angles for a discount.

You don't need every line of it on day one. Each time the phone rings with a question someone else should've been able to answer, jot that answer down after you hang up. In a month you'll have most of it captured.

One inbox, one calendar, one version of the truth

Here's where two locations quietly turn into a mess: a booking lands in your personal texts while the crew at the other spot books the same slot on a paper pad. Nobody did anything wrong. You just had two brains keeping two calendars, and the two drifted apart.

Pull the schedule into one shared calendar that both locations can see and both can update. Same goes for messages. A shared inbox, meaning one place where calls, texts, and form submissions all land instead of scattering across three personal phones, is the difference between "we've got it covered" and "wait, I thought you called them back."

A few things worth setting up early:

One calendar per location, visible to everyone and color coded, so a glance tells you who's where.
A single number customers call or text, routed to whoever's on shift, so your personal cell stops being the business line.
A missed-call text-back, so nobody slips through while both crews have their heads down.
A clear rule for who owns a message once it arrives, because a shared inbox with no owner is just a group chat everyone ignores.

Machines are genuinely good at this part. Routing a call, firing off a "we got your message, we'll be in touch by noon" text, dropping a fresh booking onto the right calendar: that's pure relay, and relay is exactly the kind of thing that should sit with the robots instead of your people.

Standardize the boring parts, not the craft

There's a real fear that writing everything down turns your business into a fast-food script, and that the thing which made customers pick you in the first place gets sanded off. Fair worry. So be precise about what you actually standardize.

Standardize the repeatable parts, the stuff that should happen the same way every time no matter whose hands are on it. How a job gets booked. What the confirmation says. When the invoice goes out. The order you close up in. None of that is your craft, it's the rails your craft rides on, and it should look identical at both locations.

Leave the craft itself alone. How you talk down a nervous customer, how you solve the odd problem on site, the judgement that comes from twenty years of doing this: that doesn't belong in a template, and it never will.

Use a quick test for whether something should be written down:

If doing it differently at each location would confuse customers or cost money, standardize it.
If the right answer changes with the situation, leave it to the person on site.
If you'd be irritated to find it done two different ways, it's a candidate for a checklist.

Write these as short checklists, not essays. A new hire at location two should be able to open the "how we close out a job" list and follow it without texting you a single question.

The calls that stay yours

Automation and a written playbook can carry the relay. They can't carry judgement, and you shouldn't ask them to. The whole reason to get the routine off your plate is to free you up for the calls that genuinely need you in them.

Some decisions stay with you, at least for now:

Pricing the odd job. A template handles the standard quote. The strange one, with the access problem or the rush, is a human call.
The unhappy customer. A robot can say "we're sorry and we're on it." Making it right is yours.
Who you hire. Location two lives or dies on the people in it. No shortcut there.
When to bend a rule. You wrote the policy. You also know the regular who's earned an exception this once.

Be honest with yourself about this split, because the failure mode cuts both ways. Hand a judgement call to a template and you get a tone-deaf answer that costs you a customer. Keep a pure relay task for yourself (the booking confirmation, the reminder) and you're right back to being the manual, standing in location one answering questions shouted from location two.

Worth doing this week

Don't try to fix all of this at once. Pick the few that stop the bleeding first.

Start the brain dump. One shared doc, and every time someone calls with a question you've answered before, write the answer down the moment you hang up.
Put both locations on one shared calendar everyone can see and update. Kill the second calendar living in your text messages.
Set up a missed-call text-back on your main number so nobody waits while both crews are slammed.
Pick one repeatable process, how a job gets booked, say, and turn it into a short checklist both locations follow the same way.
Write down three judgement calls that stay with you, and tell your crew those three come to you every time.

Do those five and location two stops running on your phone battery. If you want a hand wiring up the relay part, the shared inbox, the call routing, the reminders that fire on their own, that's the sort of thing we build at TellRobots. But even if you never automate a thing, getting what's in your head into a shared place is the move that makes two locations possible in the first place. Tell the robots the repeatable bits. Keep the judgement for yourself.