Automation still sounds like something for companies with an IT department. It isn't. Most of the automation work I do is for one-person and small-team businesses: a coach with a booking system, a shop owner drowning in order emails, a consultant who's tired of copying the same data between five tools by hand.
The tools got a lot more accessible. n8n specifically is built so that automations aren't locked behind custom code, and the effort to set one up doesn't scale with the size of your company. A five-person business and a fifty-person business can run the exact same workflow.
The part that actually trips people up isn't the technology. It's picking the right first thing to automate.
Where small businesses get the most out of automation first
Getting leads into one place. If someone fills out a form, DMs you on Instagram, and books a call, and those three things live in three different places you have to check manually, that's usually the first thing worth fixing. A workflow that pulls everything into one spreadsheet or CRM automatically saves you from the thing that actually loses business: forgetting to follow up.
Invoicing and payment reminders. Chasing unpaid invoices by hand is slow and easy to put off. An automation that checks what's overdue and sends a reminder, or nudges you to, removes the task that keeps sliding to the bottom of your list.
Client onboarding. The emails, the welcome sequence, the "here's what happens next" message, the internal notification so you actually know a new client signed up. This is repetitive by definition, which makes it a good automation candidate and a genuinely bad use of your time to do manually every time.
Reporting you currently do by hand. If you're copying numbers from three tools into a spreadsheet every week to see how the business is doing, that's a workflow, not a task. It should run itself and land in your inbox.
The pattern across all four: repetitive, rule-based, and annoying enough that you'd notice if it stopped happening. That's the actual test for whether something is worth automating, not how impressive it would sound.
What to avoid automating first
The most ambitious idea in your head is usually the wrong place to start. Complex, judgment-heavy processes (anything where you'd say "well, it depends") are harder to automate reliably and painful to debug when something goes wrong. Start with the boring, obvious, repetitive thing. Build confidence and a working system first. The ambitious stuff comes easier once you've got one automation actually running in production.
What it costs to get started
This varies a lot by scope, but as a reference point, a single focused automation, scoped to one specific problem, typically starts around €497 with a fixed price agreed upfront. That's not a subscription. You pay once, you own what gets built, and it keeps running without paying anyone monthly.
Should you build it yourself or hire someone
If you're already comfortable with tools like n8n and have a few hours to spend learning it, building a simple workflow yourself is genuinely realistic. n8n's learning curve is far gentler than writing custom integration code.
Where it stops making sense to DIY: when the time you'd spend learning and debugging costs more than just paying someone who already knows the tool, or when the automation touches something where a mistake is expensive (payments, client data, anything client-facing). At that point the hourly math flips in favor of hiring it out.
If you want a second opinion on what's actually worth automating in your business before you spend money on it, book a free discovery call. I'll tell you honestly if it's a DIY job.