What workflow automation solves for small businesses
Many small businesses run on manual work that doesn't need to be manual. A new client fills in a form and you type the same data into your calendar, your accounting software and your email list. An appointment is booked and you manually send a confirmation. An invoice goes out and you remind the client about payment two weeks later yourself.
None of these feel like big problems individually. But together they cost you a few hours per week that you could spend on your actual work, your clients, or just switching off. And they go wrong regularly: a reminder you forget, a client who gets the wrong information, data that differs between two systems.
Workflow automation fixes this by connecting those repetitive steps. Not by changing how you work, but by taking over the boring switching work between your tools.
Processes I typically automate for SMEs
These are the most common patterns I see at small service businesses:
- ▸Appointment booking: a new booking via Calendly or your own form automatically triggers a confirmation, a reminder 24 hours before, and a calendar update in Google Calendar or Outlook.
- ▸Client form to CRM: a completed intake form on your website automatically adds the client to your CRM, sends a welcome message, and creates a task for the first follow-up.
- ▸Invoice to bookkeeping: a new invoice in your accounting package automatically triggers a payment reminder after 14 days if it stays outstanding.
- ▸Photo upload to cloud: images clients send via WhatsApp or email are automatically sorted and saved in a shared folder in Google Drive or OneDrive.
- ▸Lead follow-up: an enquiry via your contact form immediately sends an automatic first reply with practical information, so the client doesn't wait hours for a response.
- ▸No-show management: a missed appointment triggers an automatic rescheduling message and updates your calendar accordingly.
These are examples, not fixed menus. Every business works differently. I always start by understanding how you work now, not by imposing a standard package.
Before and after: what automation actually changes
Here is the difference per process, expressed in real steps and time:
My approach: understand your process first
I don't start with tools. I start with a conversation about how you work now. Which steps do you go through every day? Where do you feel like you're doing things twice? Where does something occasionally go wrong because you forgot it?
Based on that conversation I map out the processes that cost the most time and are easiest to automate. Then I choose which tool fits best: sometimes that's n8n, sometimes a direct API connection, sometimes something very simple like a form with an automatic reply. The tool follows from your need, not the other way around.
- ▸Intake conversation: I listen to how you work, not how tools would want you to work.
- ▸Process map: I create an overview of automatable steps and what each one concretely delivers.
- ▸Tailored tool selection: I choose the lightest solution that works. No overkill, no expensive subscriptions if unnecessary.
- ▸Building in steps: I deliver working automations, not half-finished projects. You see results before I move to the next step.
- ▸Handover with explanation: I explain how the automation works so you know what to do if something changes.
Tools I typically connect for SMEs
I work with the tools you already use or that fit well with your type of business. Here are the most common combinations:
- ▸Google Workspace: Gmail, Google Calendar, Google Drive, Google Forms.
- ▸Microsoft 365: Outlook, Teams, OneDrive, SharePoint.
- ▸Accounting packages: Moneybird, Exact Online, Snelstart, Twinfield.
- ▸Appointments: Calendly, SimplyBook, Acuity Scheduling, or your own form.
- ▸Payments: Mollie, Stripe, PayPal.
- ▸CRM: HubSpot Free, Pipedrive, or a spreadsheet you already use.
- ▸Email marketing: Mailchimp, ActiveCampaign, Brevo.
- ▸Communication: WhatsApp Business API, Slack, Teams for internal notifications.
Using something not on this list? No problem. If there's an API or webhook available, connecting it is almost always possible. I check what's technically feasible first and am honest when something isn't.
-- Example case
A physiotherapy practice in Twente: 16 hours saved per month
A physiotherapy practice with three therapists was processing appointments manually. Every new booking via the website resulted in a manual email, a calendar update per therapist, and a reminder the day before the appointment that the receptionist sent herself. With 25 to 30 new bookings per week, that added up to more than 4 hours of administrative work per week.
I connected the booking system to Google Calendar and an automatic email flow. New booking: confirmation goes automatically to the client, the right therapist gets a notification in their calendar, and 24 hours beforehand an automatic reminder follows. Cancellations or rescheduling the client handles themselves via a link in the confirmation email.
The receptionist now manages exceptions, not the standard flow. If a client calls to reschedule, she handles it. Everything else runs automatically. The system runs on n8n, hosted on the practice's own server, so client data doesn't pass through external cloud services.
What I don't do
Being clear about what I don't do is as important as what I do:
- ▸I don't call everything AI. A form with an automatic reply is not AI. I only use the word when there is actually a language model or intelligent decision process involved.
- ▸I don't advise complex enterprise software for a five-person business. If a simpler solution does the same thing for less money, I say so.
- ▸I don't turn your way of working upside down. If you like to check invoices yourself before they're sent, I build a step that makes that possible.
- ▸I don't deliver projects you don't understand. I explain how it works and make sure you know what to do when something changes with your tools.
- ▸I don't connect twelve tools if three are enough. The simpler the automation, the more reliable it is.
What does this cost?
That depends on how many processes you want to automate and which tools you use. I always look at your situation first before naming a figure.
On request
Schedule a short conversation. I'll ask a few questions about how you work now and give you an honest picture of what's possible and what it costs.