Direct answer
Score ten questions about what happens when you're away: would enquiries get booked, invoices go out and get chased, the team's questions get answered, records get produced, and decisions get made without you? Two points for yes, one for partly, none for no. Under 9 means the business runs through you, and your lowest-scoring loop is where to start.
A week away can be covered by goodwill and a phone you keep checking. Four weeks means invoices cycle, customers chase and someone has to make the calls you'd normally make. Below is the test as a printable table, then what to fix for each "no".
The test: ten questions, scored
Answer for the business as it runs today, not as it would run if you briefed everyone first. Score Yes 2, Partly 1, No 0. Write the score in the last column, then add each pair to get a loop score out of 4. Rather click than print? Take the four-week test: the same ten questions, plus the goal question, run in your browser, with your loop scores worked out and no email needed.
Swipe or scroll to compare the columns.
| # | Loop | Question | What it really asks | Score (2 / 1 / 0) |
|---|---|---|---|---|
| 1 | Enquiries | If you were away for four weeks, would every enquiry still get a reply and a booking? | Phone, website, email and WhatsApp, without anyone ringing you to ask. | |
| 2 | Enquiries | Could someone else price a typical job without asking you? | From written prices and rules, not from memory. | |
| 3 | Quotes to cash | Would invoices still go out on time without you? | Including deposits and stage payments. | |
| 4 | Quotes to cash | Would overdue invoices still get chased without you starting it? | And could someone see who owes what today without exporting a report? | |
| 5 | The numbers | Could someone else answer "how did we do last week?" from the systems? | Sales, cash and jobs completed, not your memory. | |
| 6 | The numbers | Would you hear about a problem without being the one who spots it? | A big job slipping, cash running short, a customer about to leave. | |
| 7 | Records | If an inspector, insurer or buyer asked for your records tomorrow, could someone else produce them? | Staff holiday and absence, safety, waste or tenancy records, whichever apply to you. | |
| 8 | Records | Do customer, job and invoice records live in systems the business owns? | Not in your inbox, your phone or your head. | |
| 9 | People | Would your biggest customers keep dealing with the business if you stopped taking their calls? | Who do they ring when something goes wrong? | |
| 10 | People | Does someone other than you make day-to-day decisions, and know they're allowed to? | Who decides when you're on holiday? |
Add the ten scores for a total out of 20, then read your band.
Swipe or scroll to compare the columns.
| Score | Band | What it means |
|---|---|---|
| 16–20 | It would cope | Most of the business runs without you. Look at your lowest-scoring loop: that's what a stand-in, or a buyer, would hit first. |
| 9–15 | A week, not four | The business would get through a week. After that, your lowest loop would start waiting for you. That's the loop to take out first. |
| 0–8 | It runs through you | Right now most things wait for you. It's fixable one loop at a time, starting with your lowest loop, where a system can take the routine and a person keeps the decisions. |
Your first loop to take out is the lowest of the four system loops: enquiries, quotes to cash, the numbers and records. Leave People out of that choice; it gets its own section below. If two loops tie, take them in that order. Enquiries come first because a slow reply costs money the same week, while a records gap usually costs it later.
Answer one more question for yourself, unscored: what would you do with the time? Grow the business, get it ready to sell in the next one to three years, step back and keep it, or settle in after buying it. The answer changes what you do with your score, as the last section shows.
What to fix for each "no", loop by loop
Enquiries (questions 1 and 2). Enquiries that wait for you are money waiting too, and this is often the quickest loop to take out. The fix has two parts. First, write down how you price: the rates, the minimums, the extras and the jobs you turn away. Until that exists on paper, no person or system can quote for you. Second, put a first reply and a booking step in front of every channel. That can be an online booking link, a shared inbox with an owner, or an AI agent on WhatsApp or web chat that collects the details and books into the real calendar, with a person taking the cases it shouldn't handle. Our WhatsApp order processing case shows that pattern: the agent handles routine exchanges and the team takes over complex conversations with the context intact.
Quotes to cash (questions 3 and 4). Invoices that wait for you delay cash by as long as you're away. If an accepted quote has to pass through your hands before it becomes an invoice, that hand-off is the thing to remove. Rules can turn an accepted quote into a deposit invoice and schedule the reminders; your accounts software may already do part of it, and where its own reminders are enough, use them. Chasing that depends on you happens when you have time. Reminders by rule, with a person on the awkward calls, cover the routine. In the PaxBespoke build, bookings, proposals, e-signatures and deposit invoices are connected with reminders at each stage, and no generative AI is used to set prices or decide timing.
The numbers (questions 5 and 6). If the answer to "how did we do last week?" lives in your head, nobody can steer while you're away. Agree which five or six figures matter (sales, cash in, cash owed, jobs completed, jobs at risk), where each one comes from and how it is defined. Then have them arrive on a schedule, as a short brief from your own systems, so the team reads the same numbers you do. Problems you spot yourself stay hidden while you're away. Alerts with a named person behind them do the spotting: cash below a floor, a large job past its date, a good customer gone quiet.
Records (questions 7 and 8). Records only you can find are a risk in an inspection and a red flag in a sale. Records kept in your inbox or your head leave when you do; they belong in systems the business owns. Start with the records you're required to keep, because they come with a date and someone outside the business who may ask. Then make customer, job and invoice records agree with each other, so the same customer has the same name, the same jobs and the same balance everywhere. A good test is to ask someone else to produce a full year of one set of records without your help, and time it.
The two people questions, and what software can't do
Questions 9 and 10 are about people, and they're the hardest gap to close. Software can't make customers loyal to the company rather than to you, and it can't appoint a deputy. That's your call.
What software can do is make handing over cheaper. If your biggest customers ring you because only you know their history, put that history where someone else can see it: past jobs, prices agreed, the last three conversations, the thing they complained about in March. If nobody else decides because nobody else has the information, give your deputy the same brief and alerts you get, then tell them in writing which decisions are theirs.
If you scored 2 or less out of 4 on People, deal with it alongside whichever loop you fix first. Systems give a deputy the facts; permission to decide has to come from you.
Loop by loop: system of record, what to automate, what a person still signs
Use this table to plan the first fix. "System of record" is the one place that holds the true version of the data; everything else reads from it.
Swipe or scroll to compare the columns.
| Loop | System of record | What to automate | What a person still signs off |
|---|---|---|---|
| Enquiries | CRM, or the booking calendar if there's no CRM | First reply on every channel, collecting details, booking into the real calendar, logging the enquiry | Unusual jobs, prices outside the written rules, complaints |
| Quotes to cash | Accounts software, such as Xero or QuickBooks | Deposit invoices from accepted quotes, scheduled reminders, matching payments to invoices | Credit notes, payment plans, disputes, write-offs |
| The numbers | Accounts and job systems, read by a reporting layer | A daily or weekly brief, threshold alerts, answers that cross systems | What the numbers mean and what to do about them |
| Records | Whichever system the duty applies to, or a records app where nothing fits | Capturing records as work happens, dated and complete, with an audit trail | What the law requires of you (your solicitor, accountant or trade body confirms it) |
| People | Not a system | Shared customer history and the same brief for a deputy | Who is allowed to decide, and who looks after which customer |
Rules handle what must be exact, AI handles what needs judgement, such as reading a free-text enquiry, and a person signs off where mistakes are expensive. That split is the difference between a loop you can leave and one that needs watching.
Count before you change anything. Note how many enquiries waited more than a working day this week, how many invoices you typed or chased yourself this month, and how many questions the team brought you. Count again two to four weeks after the fix. That before-and-after is yours to check, and it tells you more than any score.
Using your score if you plan to sell
Buyers look at how much of the business depends on you, and these ten questions are a fair rehearsal. Value Builder's analytics team puts owner-dependent businesses at about 2.9 times earnings against about 3.9 times for those that run without the founder, across more than 80,000 companies (Advisor News, a Value Builder-sponsored newsletter, 11 February 2026). That is vendor data, not independently checked, so treat it as a direction rather than a promise.
If your answer to "what would you do with the time?" was selling, fix the loops in the order a buyer will test them, which usually means records and the numbers first. And keep the before-and-after counts: "the business ran for four weeks while I was away, and here are the invoices it sent" is evidence a buyer can check. We cover the full checklist in Selling in two or three years: the operations checklist buyers test.
If you've just bought the business, the same test tells you which loops still run through the previous owner. The first 100 days after buying a business puts those into a week-by-week plan.
This test is a self-assessment to help you decide where to start, not a valuation. Buyers and advisers use their own tests. We don't value businesses or broker sales; we build the systems and records, and we're happy to work alongside your accountant or broker. If you're selling in the next few years, book a sale-readiness call.
