For a company of 3–10 people, the automations that pay off are the ones that take frequent, rule-based, tedious work off the team: capturing enquiries, invoicing, payment reminders, appointment booking and the weekly report. None of these need AI, and most don't need custom code either: the feature is often already in the tools you use, it's just never been switched on.
We've covered AI separately (where it really pays off and where it doesn't). This is the down-to-earth part: five workflows we recommend to small teams first, plus a simple filter to decide which one to start with.
- Automate a task when it is frequent, rule-based, and costly when missed. If one of the three is missing, it probably isn't worth it yet.
- The five best starter workflows: enquiry handling, order-to-invoice, payment reminders, online booking, a scheduled weekly report.
- Most of these are built-in features of your invoicing, calendar or reporting tool, or can be wired up with a no-code connector.
- Every automation needs an owner and an error alert, otherwise it breaks silently.
- Custom development makes sense once the chain gets too long or business logic creeps in.
When is automation worth it at all?
Before you pick a tool, ask three questions about the process:
- Is it frequent? Several times a week, not once a quarter.
- Is it rule-based? The same steps every time, with few exceptions. If every case needs judgement, it stays a human job.
- Does it hurt when it's missed or done wrong? A lost lead, a late invoice, an unpaid bill: these cost money, not just time.
Three yeses make a good candidate. But don't count only the minutes saved. Every automation is a small piece of software: someone has to set it up and keep it running. Rename a form field or let a tool change its behaviour, and the workflow often just stops without an error message. Our rule of thumb: if an automation has no owner, we don't switch it on.
Which 5 workflows should you start with?
1. Enquiries: from form to confirmation
The most common leak in small teams is an enquiry landing in someone's inbox and staying there. The fixed version:
- every website form submission goes into a shared sheet or CRM, with a timestamp and source;
- a notification goes to the team channel, with a named owner;
- the enquirer gets an instant confirmation email with a realistic response time.
You'll need a connector such as Zapier, Make or n8n. n8n can run on your own server: according to its license FAQ, the self-hosted edition falls under the Sustainable Use License, and if only people in your organisation create and edit workflows, you can use it internally. One tip: don't promise a one-hour reply in the confirmation if you realistically get to it the next morning.
2. Turning orders into invoices automatically
If you invoice in Hungary, the tax authority's guidance says that since 4 January 2021 real-time invoice reporting covers every invoice subject to the VAT Act's invoicing rules. So your invoicing software already talks to the tax system machine-to-machine. The weak spot is a person copying order data from the webshop into the invoicing tool by hand: it's slow, and every typo means a corrective invoice.
Most invoicing tools offer webshop integrations. Számlázz.hu's Számla Agent documentation, for example, notes that for webshops the invoice can be issued automatically after the order or payment and emailed to the customer. Decide upfront who handles cancellations, partial refunds and after-the-fact company-name changes manually.
3. Payment reminders that don't depend on you
Chasing payments is awkward, so we put it off. An automatic reminder takes the personal edge off: it's not you nagging the client, it's the system flagging an overdue date. Billingo, for instance, offers payment reminders that can be sent automatically and customised per client.
A sequence that works for us: a friendly reminder after the due date, a second one a week later, and after that a person picks up the phone. Keep key accounts out of the automation; a personal call works better there.
4. Booking meetings without the email ping-pong
If "does Tuesday work? maybe Wednesday?" threads are a regular thing for you, a booking page removes them entirely. Appointment schedules are built into Google Calendar. Per Google's product page, a personal account can create one booking page, while Workspace subscribers get premium features.
Google's comparison lists automated email reminders, email verification against spam bookings and checking across multiple calendars for conflicts among the advanced features. We'd also add two or three questions to the booking form (topic, website URL) so the first ten minutes of the call aren't spent on orientation.
5. A weekly report that shows up on its own
In many small companies, reporting means someone collecting screenshots from five dashboards on Monday morning. What you want instead is a dashboard built once and delivered on schedule. According to Google's documentation, Data Studio (formerly Looker Studio) lets you schedule email delivery of a report from the Share menu, including custom repeats such as every Tuesday and Thursday.
The trick isn't the tool, it's the cut: 5–8 numbers the team actually makes decisions on. If nobody has opened a report in months, don't polish it. Turn it off.
How do you roll it out without creating new chaos?
- Write the process down by hand, step by step, before choosing a tool. If it isn't clear on paper, software won't fix it.
- One workflow at a time. Run it alongside a manual check for the first week or two.
- Give it one owner who knows what it does and has access to change it.
- Add an error alert. When a step fails, someone on the team should hear about it before the customer does.
- One page of documentation: what triggers it, what it does, where to check the history.
And remember: if personal data from forms, bookings or invoices flows into yet another tool, your privacy notice needs to reflect that.
When do you actually need custom development?
No-code tools are great while the chain stays short and readable. Once a process spans fifteen steps and four tools, or business rules creep in (custom pricing logic, stock sync between webshop and warehouse, permissions across several systems), a small, purpose-built integration is usually easier to maintain than a clicked-together structure. For webshops this is often decided at build time: plan it so invoicing, couriers and the warehouse can be connected from day one.
Once these basics are in place and your data lands in one clean spot, that's when it makes sense to let AI work with it, which is what our piece on building your own AI marketing assistant is about. The other way round rarely works.
Frequently asked questions
Do I need to know how to code for these automations?
Four of the five (invoicing, payment reminders, booking, reporting) are usually a matter of configuring a tool you already have or switching on a ready-made integration. A no-code connector is enough for enquiry handling. You only need code when the built-in integrations don't cover your process.
Zapier, Make or n8n?
With cloud-hosted tools you don't have to run a server, which is a big plus for a small team. n8n is a good fit if someone can operate it and you want the data to stay on your own infrastructure. Our advice: pick the one someone on your team will own.
What happens when an automation breaks?
Without an error alert, usually nothing visible: the email or invoice simply doesn't go out. That's why every workflow needs failure notifications, and why it's worth checking the run history once a month.
How do I work out whether it pays off?
Multiply how many times a week it happens by how many minutes each run takes, then compare that with setup and maintenance time. Add the cost of errors: a lost enquiry or a wrong invoice often costs more than the time saved.
What shouldn't I automate?
Anything rare, different every time, or requiring judgement: putting together a quote, handling complaints, communicating with key accounts. Templates can help there; automation can't.
If you're not sure which process is your best candidate, or your systems simply don't talk to each other, see how we approach custom software and integrations. We're happy to think it through with you.