Tools · picker
Five waits on the path a dollar takes through your business, from the reply to the invoice. The picker circles the one to automate first, and says whether it is a Zap, a system, a habit, or a switch in the software you already pay for.
First it sets stops aside. A stop you skipped is not yours to automate. A stop you still do differently every week is not ready: automation copies your process, and if the process is not settled you are paying to copy the wrong one. A stop that carries a complaint, a refund or a promise stays with a person, because a wrong automatic answer costs more than a slow human one. Each set-aside stop is listed on the tile with its reason.
Then it finds the leaks. A stop leaks when the customer waits there past its line. The reply’s line is minutes, because the study behind it found the odds of qualifying a lead fell 21-fold between a five-minute reply and a thirty-minute one. The other four lines are mine, from the systems I have built and run: the quote goes out the day of the visit, a quiet quote is chased by day three, the customer has a date within a day of saying yes, the invoice goes out the day the job is done. They are not industry numbers and the page does not dress them as such.
The first leak from the left wins. Everyone who becomes a customer passes the reply; only the quoted reach the chase; only the booked reach the invoice. The earlier the wait sits on the path, the more people leave at it, so a shorter wait near the start outranks a longer one near the end, and the tile says so when that happens. The next leaks to the right are then, and then.
Last, the verdict. The invoice is a switch: the accounting subscription you already pay for sends the reminder and drafts the invoice when a job closes, so it is bought, not built. The reply is a system when who takes it depends on area, skill or load, because a trigger and an action cannot score people on three things or reroute after 15 minutes. A stop that runs fewer than 15 times a month, other than the reply, is a habit: at a dozen a month a rule you keep beats a build. Everything else is a Zap, one trigger and one action, and the cost line prices it from your count: on a two-step Zap the trigger is free and the one action is a task, so runs a month is tasks a month, held against Zapier’s free plan at 100 tasks, Professional at 750 and Team at 2,000. A system you own runs on Cloudflare’s free plan at 100,000 requests a day, or for 5 dollars a month on the paid plan.
What the picker does not do. It puts no dollar figure on the wait; the lead response time calculator does that for the reply, from your job value and close rate. It does not rank by how annoying a task is. And it does not know your business better than you do: if the step it circles is wrong, the reason is in one of the boxes above, and changing the box changes the answer.
Zapier’s own 2021 report, built on a survey of 2,000 US knowledge workers at small and mid-sized businesses, lists what people automate most: manual data entry at 38 percent, document creation and filing at 32, and only then lead management, at 30. Data entry is the annoyance. The lead is the money, and the Lead Response Management study, six companies and more than 15,000 leads, is why: the odds of qualifying a lead fell 21-fold when the reply stretched from five minutes to thirty. No invoice reminder has a number like that behind it.
The scoring frameworks that rank for this question multiply frequency by time by consistency, and their own worked examples land on the invoice chase and the weekly report, because that arithmetic is built to find chores. This page asks where a customer is waiting and how many of them wait there, which is why it lands on the reply so often, and why it does not when your reply is already in minutes.
| Stop | Trigger | Action | The number to watch | What it grows into |
|---|---|---|---|---|
| Reply | A form posts, a call is missed, a message arrives | The customer gets a text in seconds with a name and a time | The median minutes from an enquiry landing to a person’s answer. | Assignment by a rule, a claim window, a reroute after 15 minutes |
| Quote | A lead is marked visited, or the form already holds what you need | The quote drafts itself from your template into your drafts, for one look before it goes | Days from the visit, or the ask, to the quote sent. | The quote that prices itself |
| Follow-up | A quote goes out | A dated task lands on day three with the customer’s name (a delay is a third step, so on the free plan the chase is dated, not sent) | The share of quiet quotes chased by day three. | The follow-up date that sets itself, and the message that goes with it |
| Job | A quote is accepted | The customer gets a text with the booking link | Days from the yes to a date on the calendar. | The reminder the day before, and the crew’s name and distance in the text |
| Invoice | The job is marked done | The invoice drafts itself from the job, and the subscription’s own reminder chases it | Days from the job done to the invoice sent, and days to paid. | Nothing: this one is bought, not built |
Each one is an afternoon on the free plan of whatever you already use, and each should hold for a month before the next step is added. The order they arrived in on the lead desk on my homepage is the order I would give any business that sells a job: intake, acknowledge, assign, the deadline, the after-hours answer, then the money steps.
The rule has weights. A trigger and an action can send a text. They cannot score twelve crews on distance, plan tier and this week’s load, widen a radius when nobody covers the point, and reroute after 15 minutes. When the rule has weights it is a system, and the hub on my homepage is what that looks like: a lead assigned in 2.4 seconds median, rerouted in 15 minutes when ignored.
The chain fails in silence. Rented chains fail quietly when an app changes its login or its fields, and the failure shows up as a customer who never heard back. A system you own logs every step and tells you when one fails; the routing hub writes the maths of every assignment to a log for exactly that reason.
The bill scales with your success. A busy small business runs about 140 leads, 60 quotes and 900 messages in a month, by the ledger on my homepage. The reply alone is past Zapier’s free plan at that volume, and every step you add multiplies the tasks. A system you own runs the same month for about 5 dollars on Cloudflare’s paid plan. The full argument is the guide on when a small business should build custom software.
What a system costs is the next question. The custom software cost estimator takes the shape of the build and gives the hours behind the number, from published breakdowns. Read what it prints as what an agency would quote. Mine is one fixed price agreed at the map stage, and it is a smaller number than the one that page shows.
If the step you circled is a system, send me the path with the waits on it and book the call: thirty minutes, free, and I will tell you which of the four it really is. The other calculators are on the tools page.
The step closest to the money where a customer is waiting, which for most businesses that sell a job is the reply to a new enquiry. A form posts or a call is missed and the customer gets a text within seconds with a name and a time. One trigger, one action, an afternoon, and the free plan of whatever you already use. The picker checks whether that is true for you or whether a stop further along leaks first.
Because everyone who becomes a customer passes the reply, and only the quoted reach the chase. The study behind the reply’s line found the odds of qualifying a lead fell 21-fold between a five-minute reply and a thirty-minute one; nothing about follow-up has a number like that behind it. The chase is still on your page, as the next step, and the tile names it as the longest wait.
For the first automation, yes. The free plan runs two-step Zaps, one trigger and one action, at 100 tasks a month, and the trigger is free, so one run of the reply is one task. At 100 enquiries a month you are at the edge; Professional is 19.99 a month paid yearly for 750 tasks. Those figures were read on Zapier’s pricing page on the date under the sources, and the page will be wrong the day Zapier changes them, which is why the row names the date.
The same shape at a different price. Make’s free plan carries 1,000 credits a month and two active scenarios, and its Core plan is 9 a month for 10,000, as read on the date under the sources. The picker prices Zapier because the guide does and because its task counting is published and simple. The step it circles does not change with the tool.
Anything with a complaint, a refund or a promise in it, because a wrong automatic answer costs more than a slow human one. Anything you still do differently every week, because automation copies your process and an unsettled process gets copied wrong. And the books: accounting is the job every business has the same way, so the subscription already automates it better than a chain you build. The two boxes under each stop set those aside.
Measure the one number it was meant to move, before and after. For the reply that is the median minutes from an enquiry landing to a person answering, and the lead response time calculator’s measure mode works it out from last month’s rows. If the number did not move in thirty days, the automation was the wrong first step, and you learned that cheaply.
No, and that is the difference from the scoring frameworks. They multiply frequency by time by consistency, which finds the chores: data entry, the weekly report, the invoice chase. This page starts from where a customer is waiting and how many of them wait there, from your own three numbers. The chores can come second; the waits cost jobs.
No, while the page’s script is running. The rule runs in your browser. The only thing that carries your answers is the link you copy, which holds the fields of the form and nothing else, so that whoever opens it sees the same result. With JavaScript turned off the page still works, and then the fields do travel to my server in the address, the same way a link you copy does.
Why the step closest to the money comes first, why one trigger and one action is the right first shape, the order I automate a lead in, and the three lines where Zapier stops being enough.
What to automate first in a small businessThe step closest to the money, with one trigger and one action. Not the chore that annoys you most, and not the whole business at once.Read the guide →Next step · Norvahl, one designer-engineer, both tradesTaking on projects
Send me the path with the waits on it. I read it myself and reply within a working day with which of the three it is.
reply within a working day · me, not an assistant · a 30 minute call, free · no newsletter · hello@norvahl.com