How a tool would usually handle each of these
Plain descriptions, no promises. Every business is a little different, which is why we ask first.
Typing orders into a spreadsheet
Orders already arrive somewhere: an email, a text, a form, your store. A small tool reads each new order and writes the same row you would type, into the same sheet. What can go wrong: an order in a shape it has never seen. So it sets those aside for a person instead of guessing. First thing we'd ask: where do orders come from today, and what does one row in your sheet look like?
Sending invoices and chasing payment
The tool makes the invoice from the order or the job, sends it, and watches the due date. If nothing has come in by then, it sends a polite reminder you wrote once, then another a week later. You see one list: who owes what, and who has been nudged. What can go wrong: a customer who paid by check gets a reminder anyway. So the tool checks your books before it sends one. First thing we'd ask: where do payments land today?
Answering the same customer questions
Most repeat questions have a fixed answer: hours, prices, where an order is, whether you deliver. A tool can answer those by text, email or on your site, using answers you wrote. Anything it is not sure about goes to a person, with the customer's message attached. What can go wrong: a confident wrong answer. So we keep the list short and let it hand off often. First thing we'd ask: what are your ten most common questions, and what do you say now?
Copying data between apps
When two apps do not talk, someone re-types. A connection moves the record the moment it appears: a new customer in your store lands in your email list, a paid invoice lands in your books. What can go wrong: the same record twice, or a field that does not line up. So the tool looks for a match before it writes, and keeps a log of every move. First thing we'd ask: which two apps, and what does one record look like in each?
Booking and rescheduling
A booking page shows only the times you are really free, takes the booking, and sends the reminder. A change moves the slot and tells everyone who needs to know. What can go wrong: double bookings when two calendars disagree. So the tool treats one calendar as the truth. First thing we'd ask: what decides when you are free?
Building quotes
Most quotes are the same lines with different numbers. A tool takes the few things that change (size, count, options), looks up your prices, and makes the quote as a page the customer can accept online. What can go wrong: a price list that goes stale. So your prices live in one place you can edit yourself. First thing we'd ask: what are the five things that change from quote to quote?
Weekly reports
If the numbers already live in your store, your books or a spreadsheet, a tool can pull them every Monday and send the same report you build by hand. What can go wrong: a number that looks right and is not. So every figure links back to where it came from. First thing we'd ask: which numbers, and where do they live today?
Something else
Almost any task that follows the same steps, from information that already exists, can be handled by a small tool. The test is the three questions above. First thing we'd ask: walk us through it once, step by step, the way you did it last time.
How the math works
Each task has three numbers: how many minutes it takes each time, how many times a week you do it, and what an hour of the person doing it costs. Minutes times the number of times a week, times the weeks you work in a year, divided by 60, is the hours a year. Hours times the cost per hour is the dollars a year. Add up every task and you have the total.
Weeks a year starts at 52 because that is how many there are. If you close for two weeks, change it to 50.
The pay box is the cost of the person's time. If that person is you, use what you would pay someone else to do it. Your time is not free; it is just unpaid.
If you tick "Add benefits and payroll tax", the tool divides the pay by 0.70. That is because wages are 70.0% of what a US private employer pays per hour worked, and the other 30% is benefits and payroll taxes (BLS, Employer Costs for Employee Compensation, June 2026, released 2026-09-09). It is a national average. If you know your own share, type it in the override box.
That is the whole calculation. There is no hidden multiplier and no "efficiency rate". The number on the page is what the work costs you today.
What "ready to automate" means
The three questions in step 3 are our rule of thumb for which task to fix first.
Same steps every time. A tool does exactly what it was told, every time. That is a strength when the steps do not change, and a problem when every case is different.
Information already typed somewhere. If the order is already in an email or a form, a tool can read it. If it only exists in someone's head or on a sticky note, someone still has to type it once.
Rules on one page. If you can write down what to do in each case on one page, a tool can follow it. If it takes a meeting to explain, start with a smaller piece of the task.
We rank your tasks by how many of those got a "yes", then by hours. That is an order to start in, not a promise about what a tool will do. Plenty of tasks with two "yes" answers are still worth doing. The one with three is just the easiest first win.
What we do not tell you
You will find other calculators that promise you will save 40% or 60% or 80% of the time. We do not print a number like that, because we do not have a source we can stand behind, and because it is different for every task. What a tool takes over depends on how tidy the information is and how many odd cases there are. The honest thing is to show what the task costs today and talk about the rest.
Tasks small businesses fix first
The tasks in step 1 are the ones we see most: orders into a spreadsheet, invoices and reminders, the same questions over and over, data copied between two apps, bookings, quotes and the Monday report. Each one is a small tool on its own, and small is good. A small tool is cheap to build, easy to check, and easy to switch off if it is wrong. Read how we build automations and custom tools.
A real build
We built the online store for Barista Plus, a coffee roaster: 12 coffees, subscriptions, a wholesale inquiry form, in English and Spanish. The catalog runs on the store's own data, so the owner changes a price in one place and it changes everywhere. See the Barista Plus build.