Free tool
What should you automate first?
Nine questions about how your week actually runs. Out comes the three jobs worth doing first, in order, with the hours each one gives back and a plain description of what the fixed version looks like. Nothing you answer leaves your browser.
Your week
-
1
What kind of business is it?
-
2
How many enquiries reach you in a typical week?
Calls, messages, forms and walk-ins together. A rough count is fine.
-
3
How many of those wait more than an hour for a real reply?
-
4
Where do they arrive?
Tick everything that gets used.
-
5
What normally has to happen after the first reply?
-
6
Who chases the ones that go quiet?
-
7
How do appointments get booked and reminded?
-
8
How much of the week goes on typing the same information into more than one place?
-
9
How often do past customers hear from you?
Answer all nine and the result appears here. Nothing is sent anywhere.
Automate these three first, in this order
The rest, ranked
How these hours were worked out
The volumes are the ones you entered. The per-unit factors above are ours, and they are deliberately modest. This estimates the size of the job, not a promise, and it is written so you can argue with the arithmetic instead of trusting the headline.
How the ranking works
There are seven categories of work in a small business, and almost every automation project is one of them. The scanner estimates how many hours a month each one is currently costing you, then orders them.
- Answering and capturing every enquiry. The calls, messages and forms that get picked up late or not at all.
- Chasing the ones that go quiet. Quotes, trials and conversations that stop, and the follow-up that depends on somebody remembering.
- Booking, reminders and no-shows. Getting people into the diary and keeping them there.
- Intake, quoting and documents. Collecting what a real answer needs, and reading the documents that arrive instead of retyping them.
- Records, invoicing and re-typing. The same information entered into more than one place.
- Repeat business and reviews. The customers you already have, contacted on a cycle rather than on a whim.
- Knowing your numbers without asking. Reporting that arrives rather than being assembled.
The two things it does are honest and separate. It measures hours from the volumes you enter, using factors it prints on screen. Then it weights those hours by industry, because the same number of hours is not worth the same everywhere: a dead chair in a salon and a slow quote in manufacturing are different kinds of problem.
The honest framing, same as every other tool we publish: this estimates the size of a job, not a promise. It is built so you can argue with the arithmetic rather than trust a headline.
What to do with the answer
Build the first one only. Every automation project that fails does so by trying to do all seven at once, and the first one is what proves whether any of this is worth continuing.
The staged version of that argument, three phases over three months, is in the ninety day roadmap. If you would rather see what the whole operating system looks like before choosing a piece of it, that is the back office blueprint.
Not sure your industry page exists yet? The industries hub lists the ones written so far, and the four problems underneath them are the same everywhere.