
Most small businesses I talk to don't have an automation problem. They have a prioritization problem.
When I started Aistralis, I spent the first few months doing what everyone does: testing every tool, building workflows that looked impressive in demos, and convincing myself I was being productive. I was automating things left and right. And yet, nothing was actually moving faster. Nothing was growing. I had layers of clever little systems doing things that, honestly, didn't matter that much.
That was my lesson, and I see it play out with almost every SMB I work with today: the issue isn't that you're not automating. It's that you're automating the wrong things first.
I see this constantly in projects that look good on the surface but don't actually move the business (I broke this down in more detail in why automation projects fail).
Author: Peter
Published: May 1, 2026
Here's how it usually goes. Someone watches a YouTube video about an n8n workflow that looks cool. Or they sign up for an AI tool because the landing page promised it would "10x their productivity." They set it up, it kind of works, and they move on to the next shiny thing.
A few months later, they've got five tools running in the background, a couple of half-finished automations, and no real idea whether any of it is actually helping the business.
The problem is that most of these automations end up attached to low-impact tasks. Reformatting internal reports nobody reads. Generating social captions for an account with 200 followers. Organizing files in a folder structure that only one person uses. It feels like progress because something is happening automatically. But none of it is driving revenue, fixing bottlenecks, or making customers happier.
Automation should not start with what's convenient to set up. It should start with what actually matters to your business.
Before building any workflow, I run every task through three questions. A good automation candidate needs to tick at least two of these boxes, and the best ones tick all three.
Does it happen often? Frequency is where automation compounds. If a task happens fifty times a day, shaving ten seconds off it adds up fast. If it happens twice a month, even a perfect automation barely registers. Daily, repetitive tasks are where you want to start.
Does it affect revenue? This one cuts through a lot of noise. Tasks tied to how leads come in, how quickly you respond, how well you follow up, how customers get onboarded. These are the ones that directly affect whether money comes into your business. Prioritize them above everything else. Lead response and follow-up are especially critical here, because small delays have a disproportionate impact on conversion(I explain where this typically breaks in why your leads stop responding).
Is it slowing things down? Bottlenecks are gold. They're the places where work piles up, leads go cold, or your team spends energy on manual stuff that a workflow could handle in seconds. Fix a bottleneck and you often unblock the entire system around it.
Run your task list through this filter and the fog clears quickly. If you want a more structured way toevaluate this, I wrote a full framework for deciding what's actually worth automating.
Across all the businesses I've worked with, from local service companies to e-commerce stores to B2B consultancies, the same three areas keep coming up as the highest-ROI places to start. These are also thefirst systems I recommend in most cases (I listed all 7 high-impact automations here).
Speed matters more than people realise. There's a reason the conversion rate on a lead drops dramatically after the first hour. People are exploring options. They filled out your form and three other forms. Whoever responds first, thoughtfully and quickly, wins a disproportionate amount of the time.
Most small businesses are still handling this manually. Someone checks the email, writes a reply, maybe gets back to the lead that afternoon or the next morning. That delay is expensive, even if it doesn't feel like it.
Automating lead response means the moment someone fills out your contact form or sends a message, they get a real, relevant reply within seconds. Not a generic "thanks for reaching out" autoresponder, but something that acknowledges what they asked, asks a qualifying question or two, and gives them a next step, a booking link, a resource, something useful. By the time you personally get involved, the lead is already warm and engaged.
This is one of the first things I set up for almost every client, and it consistently delivers results faster than anything else.
This is where the majority of revenue quietly walks out the door.
Most leads don't convert on the first interaction. They need time, reminders, and a few touchpoints before they make a decision. But manual follow-up is inconsistent. Things get busy, notes get missed, and a lead that was genuinely interested three weeks ago has now gone with someone else because you simply forgot to follow up.
A structured follow-up sequence fixes this completely. It doesn't need to be aggressive or spammy. A few well-timed messages over the course of a week or two (a reminder, something useful, maybe a case study or an offer) keeps your business in front of people without requiring you to remember to do it manually.
I've seen this single automation double conversion rates for businesses without any change to their traffic or their offer. The leads were always there. They just weren't being followed up on consistently.
The problem wasn't lead generation.
It was what happened after the lead came in.
As a business grows, the communication channels multiply and things get chaotic fast. Emails, form submissions, DMs, support messages, … everything lands in different places and everything looks equally urgent until you actually read it.
Without a system, important leads get buried under general inquiries. Response times slow down. Good opportunities disappear because nobody noticed them in time.
Inbox triage automation solves this by treating different types of messages differently. A pricing inquiry gets flagged as high priority and routed straight to the right person. A general question gets handled by an automated response. A support issue triggers a specific workflow. Everything gets categorized and directed before a human even looks at it.
Your team stops wading through noise and starts focusing on what actually needs their attention. Response quality goes up, not because you hired more people, but because the system is smarter about what reaches who.
Just as important as knowing where to start is knowing what to skip.
If a task only happens occasionally, automating it won't return much. You'll spend more time building the workflow than you'll ever save running it. These can come later.
Internal admin work is another trap. It's one of the most common hidden time drains in small teams. Automating how reports are formatted, how files are organized, or how internal notifications are sent can feel productive, but none of it directly touches revenue. Until the front end of your business, how leads come in and how they convert, is running smoothly, internal admin automation is a distraction.
Build the revenue-facing systems first. Everything else can wait. This is part of a bigger shift in how businesses approach AI and automation. Most teams jump into tools without a clear system behind it, which iswhy results stay inconsistent (I break this down in the AI CEO roadmap).
If you want, send me:
I'll show you exactly what I would automate first and where you're likely losing time or revenue.
Book a Free AuditAutomation is not about doing more things faster. It's about doing the right things faster, in the right order, starting with the parts of your business that actually drive growth.
Get those foundations right and everything else becomes a lot more straightforward.