The seven layers every business runs, and which of them can run themselves

Why layers, and not a flowchart

Process diagrams get drawn, admired and never opened again, because they describe an ideal that does not survive a Tuesday.

Layers are more useful because each one has its own failure mode, its own owner and its own answer to a single question: does this need judgement, or does it just need doing? That question is the entire basis for what to automate, and it can be answered layer by layer without redesigning anything.

Layer 1, enquiry in

Everything that arrives from outside: calls, texts, forms, DMs, emails, walk-ins, referrals. This is the layer with the most doors and the least ownership, which is why it leaks most.

The failure mode. Not slowness, invisibility. A missed call leaves no record, so the loss is genuinely unknown rather than merely unmeasured. Most owners underestimate this layer badly, and they underestimate it in a specific direction.

What judgement it needs. Almost none for the first response. Working out what someone is asking, answering the routine part and capturing the rest is exactly the work that stopped needing a person recently.

• Runs itself: answering, capturing, classifying, recording, routing, out-of-hours cover, both languages.
• Stays yours: anything angry, anything ambiguous, anything where the answer commits you to something.
• The tell that it is broken: you cannot produce a list of every enquiry from last week.

Layer 2, follow-up

What happens to the ones who did not answer, did not book, or said they would think about it. In most businesses this layer does not exist as a layer at all. It exists as one conscientious person and their memory.

The failure mode. It works brilliantly on quiet weeks and vanishes on busy ones, which is exactly backwards, because busy weeks are when the most enquiries are arriving.

What judgement it needs. The content needs judgement once, when you write it. The sending needs none at all. That split is why this layer automates better than any other in the business.

• Runs itself: the schedule, the sending, stopping on reply, opt-outs, handing over to a person at the right moment.
• Stays yours: what the messages say, and the decision to keep pursuing something unusual.
• The tell that it is broken: your conversion is noticeably different depending on who was on shift.

Layer 3, booking

Getting a time into a diary and keeping it there. Deceptively deep, because it touches availability, staff, rooms, equipment, travel time and your own rules about what can be booked next to what.

The failure mode. Double the trouble at both ends: friction stops people booking, and no-shows waste the slots of the people who did. Both are fixable and they are fixed by different things.

What judgement it needs. The rules need judgement. Applying them does not, and applying them consistently is something software does better than a tired person at a desk.

• Runs itself: self-service booking against real availability, deposits, confirmations, reminders, reschedules, waitlist promotion when something frees up.
• Stays yours: the rules themselves, and the exceptions you choose to make for people who deserve them.
• The tell that it is broken: empty slots on the same day someone was turned away, or told to call back.

Layer 4, the job or the order

The actual work. This is the layer you are in business to do, and the one where automation has the least to offer and the most to get wrong.

The failure mode. Not the work itself, the information around it. The crew arrives without the gate code. The order ships without the note. The stylist does not know it is a correction. Almost every problem in this layer is a handover problem.

What judgement it needs. All of it. What automation contributes here is getting the right information to the right person at the right moment, and getting out of the way.

• Runs itself: job packs assembled, status updates to the customer, on-the-way notifications, photo and document capture, handover notes.
• Stays yours: the work, obviously, and every decision inside it.
• The tell that it is broken: someone phones the office mid-job to ask something the office already knew.

Layer 5, the invoice

Getting paid. The most reliably automatable layer in any business and the one owners are most reluctant to hand over, usually because chasing feels like a relationship matter.

The failure mode. Late invoicing rather than late payment. Work finishes, the paperwork waits for a free evening, and the payment clock only starts when the evening arrives. Most businesses that think they have a collections problem have a paperwork scheduling problem.

What judgement it needs. Almost none until it gets serious. Everything up to the third reminder is timing, and timing is not a relationship skill.

• Runs itself: invoice raised on job completion, sent, receipted, reminded on schedule, escalated on a rule.
• Stays yours: disputes, payment plans, and deciding when a good customer gets slack.
• The tell that it is broken: the gap between finishing work and sending the invoice is measured in days.

Layer 6, the review

Asking, at the right moment, in one tap. A tiny layer that punches far above its weight for any business competing in map results.

The failure mode. It depends on remembering, and the moment it depends on is the moment everyone is busiest, which is right as a job finishes.

What judgement it needs. None for the ask. Plenty for the answer, especially when the review is bad.

• Runs itself: the request, its timing, the follow-up if nobody responded, routing a poor rating to a person before it becomes public.
• Stays yours: every reply to a negative review. Nothing on this list is a worse candidate for automation.
• The tell that it is broken: review volume that arrives in clumps whenever someone remembers to run a campaign.

Layer 7, the repeat customer

The people who already bought. Structurally the cheapest revenue in the business and the layer most often left completely unbuilt.

The failure mode. Nothing happens. There is no alert when a regular stops being regular, because nobody is watching one person's pattern, so churn is discovered by accident weeks later.

What judgement it needs. The cycle needs judgement once. Noticing who has fallen off it needs none, and is exactly the kind of watching people are bad at and systems are good at.

• Runs itself: contact timed to the product's own cycle, lapsed-customer detection, win-backs, seasonal campaigns, loyalty that does not need a card.
• Stays yours: the call you make to a good customer who has drifted. That one should always be a person.
• The tell that it is broken: you have a customer list you have never once used.

The whole thing on one page

Read down this table and mark each layer honestly. Whichever line you cannot answer is usually the one to build first.

How to use this without building all seven

You are not meant to build seven systems. Almost nobody needs to, and the businesses that try are the ones that end up with seven half-finished ones.

1. Mark each layer green, amber or red. Green means it works without you thinking about it. Red means it depends on somebody remembering. Be honest about amber, because amber is usually red on a busy week.
2. Find your first red going down the list. The order matters: a red layer poisons every layer below it. There is no point automating invoicing if half the jobs never got recorded.
3. Build that one, finish it, and leave the rest alone. Finished means boring. A week where nobody mentions it because nothing went wrong.
4. Re-mark the table a month later. Fixing one layer usually changes the colour of another, sometimes for the worse, because volume that used to be lost now arrives somewhere that cannot cope with it.