Three questions I ask every business owner before automating anything
The answers decide whether a build pays for itself. The third one usually changes the scope.
Automation projects rarely fail in the build. They fail weeks earlier, in the framing, when everyone agreed to automate the wrong thing. I’m about a year into building these systems for business owners, and these three questions are how I catch that before writing a single workflow.
1. Where does the process break when you get busy?
Every owner can describe their process on a calm day. The truthful version only shows up under load.
Climbers grade a boulder by its crux. Nobody cares how clean the four easy moves at the start are; the grade lives at the single hardest move, because that move decides whether you top out. A business process earns its grade the same way, at the move where it falls apart.
So I ask what falls apart during the busiest week of the quarter, and the answer is almost always specific and almost always different from what they came in wanting to automate. “We stop following up with leads.” “Invoices go out late.” “Onboarding emails get skipped.” That sentence is the automation target. Whatever survives the busy weeks doesn’t need software yet. The thing that collapses under volume is bleeding money exactly when the most money is on the table.
2. What happens to a lead after they say yes?
Owners can talk about the front of their funnel all day, then go vague at the exact moment the funnel starts producing money. I ask them to narrate the journey from “yes” onward: who sends the contract, who collects payment, who schedules kickoff, how long each handoff takes, and what the customer sees during the silence.
Handoffs are where revenue leaks. I’ve watched businesses spend real money acquiring a lead and then lose the signed deal to a kickoff email that took nine days. Automating the post-yes sequence usually costs less than the lead generation it protects, and it pays for itself on the first deal it saves.
3. What will you do with the hours this frees up?
This is the one that changes scope. Some owners answer instantly: more sales calls, more client delivery, a service line they’ve been putting off for a year. For them the automation has a revenue number attached before the build starts, and it usually justifies going bigger.
Other owners go quiet, because the honest answer is that the reclaimed time has no destination yet. Totally fine answer, and it changes my recommendation. Without a plan for the freed hours, the value comes down to error reduction and consistency. Still worth buying, at a smaller scope and price.
Asking it out loud also sets the real success metric. If the goal is ten more sales calls a week, we measure sales calls, and the project has a definition of done that lives in the P&L.
The part I had to learn
The automation is the easy part. n8n, Claude, and a few integrations can automate nearly any process a mid-size business runs. The scarce skill, and the one I’m still sharpening, is picking the process where software converts directly into recovered revenue or redeployed time. Twenty minutes on these questions has killed some projects, shrunk others, and doubled a few. Every one of those outcomes beat building the wrong thing beautifully.