If you run a 10-100 person company, you probably face it every day: your team spends valuable hours on repetitive tasks. Copying invoices between systems, manually categorizing emails, piecing together reports in Excel. This article is about how to eliminate these bottlenecks, step by step, with real examples and specific tools.
This isn't a theoretical textbook. We've compiled the lessons from automation projects we've built for Hungarian SMBs over the past years. From the Mindwell webshop automation to the Balazs Kicks sneaker wholesale, the pattern is always the same: first you identify the biggest time drain, then you gradually automate, and you measure the results along the way.
Business owners and managers who feel that too much time is spent on repetitive admin work but don't know where or how to start automating. No programming knowledge is required. Most solutions presented here can be built with no-code tools.
Why automate? The numbers don't lie#
Automation is not a fad and not a tech experiment. It has three very concrete business outcomes:
1. Time savings. A typical SMB spends 10-20 hours per week on repetitive administration. Annually, that's 500-1,000 work hours, equivalent to half a full-time employee's salary. Automation can replace 60-80% of this.
2. Fewer errors. Manual data entry has an error rate of 2-5%. A mistyped account number, a forgotten reminder, a missed status update. These errors cost money: late payments, complaints, lost customers. In automated processes, the error rate drops below 0.5%.
3. Scalability. If the company grows, manual processes don't scale. Two people can handle 20 orders a day by hand. But not 100, and hiring another person is more expensive than automating.
The question isn't whether automation is worth it, but which process to start with. By the end of this article, you'll have a clear answer.
What can you automate? 8 process types worth examining#
1. Invoicing and finances#
The most common starting point. Automatic invoice issuance after an order, payment reminders at 3, 7, and 14 days overdue, receivables report at month-end, NAV online invoice sync.
In the Murabau Kft. project, we automated incoming invoice processing with Mistral AI OCR. The result: processing time per document dropped from 5-10 minutes to less than 1 minute. For the detailed solution, read our AI OCR invoice processing case study.
Typical savings: 2-4 hours/week
2. Order management#
If you run a webshop, order management is one of the biggest time sinks. Categorizing incoming orders (payment method, shipping, product type), automatic status updates, generating packing task lists, shipping notifications.
At the Mindwell webshop, we built 24 n8n workflows that automatically handle everything from order to delivery. Daily admin time dropped from 3-4 hours to under 10 minutes. You can read the full case study here.
Typical savings: 1-3 hours/day (depending on volume)
3. Email management and customer communication#
Automatic categorization of incoming emails (inquiry, complaint, invoicing), sending templated replies, forwarding to the right colleague, follow-up reminders. A 20-person company receives 30-60 emails daily, and half contain similar questions: "When does my order arrive?", "Can I get a quote?", "How can I pay?". If you generate automatic responses for these (personalized with order data), your team only needs to handle the unique questions.
The Gmail + Make.com combination works particularly well here: Make.com categorizes the incoming email based on subject and content, and sends the appropriate template reply. If the email doesn't fit any category, it forwards it to the right colleague based on the topic.
Typical savings: 30-60 min/day
4. CRM and customer tracking#
Automatic reminders for follow-up calls, lead scoring (who's most interested), pipeline updates based on communication, status change notifications. If you currently track your customers in Excel, this is one of the best starting points.
Typical savings: 3-4 hours/week, plus fewer lost customers
5. Reporting and dashboards#
Automatic weekly/monthly report assembly, live dashboards with real-time data, anomaly alerts (e.g., sudden revenue drop). Instead of spending hours every week collecting data, the system compiles and sends it by email automatically.
The most common solution: Google Sheets + Looker Studio + Make.com. Make.com collects data from various sources once a week (webshop, CRM, invoicing, bank account), loads it into Google Sheets, and Looker Studio visualizes it. The result is a browser-accessible, always-fresh dashboard the team can check anytime, plus a weekly email summarizing the key numbers.
Typical savings: 2-4 hours/week
6. Inventory management#
At the Balazs Kicks project, we built automatic barcode generation, real-time inventory sync (Airtable-Shopify), and critical stock level alerts. The manual inventory tracking error rate dropped from 10% to under 1%.
Typical savings: 2-3 hours/week, plus zero overselling
7. Appointment scheduling and calendar management#
Online booking calendar, automatic reminders (24 hours, 1 hour before the meeting), Google Calendar sync, confirmation email. If you schedule client meetings, you know the back-and-forth emailing: "Are you free Tuesday?" / "Unfortunately not, how about Wednesday?" / "Morning or afternoon?" / "Morning works, but only after 10." This cycle often takes 4-5 email exchanges before a single appointment is confirmed.
Calendly (or the open-source Cal.com) solves this: the client clicks the link and picks an available slot, your calendar updates automatically, and both parties get a confirmation. That's it. No emailing, no conflicts, no forgotten meetings.
Typical savings: 5-10 minutes of back-and-forth emailing per meeting
8. Document processing#
Automatic reading, categorizing, and recording of incoming documents (invoices, contracts, delivery notes). AI OCR technology already works with 95%+ accuracy on Hungarian-language documents. Mistral AI, for example, natively handles PDFs, understands the document's logical structure, and returns data in structured JSON that the workflow can process immediately.
This is especially useful if you work with many suppliers, each using a different invoicing system (Szamlazz.hu, Billingo, manually filled invoices). The system works format-independently; it doesn't matter where the document comes from.
Typical savings: 5-15 minutes per document
If you automate just 2-3 of these processes, that's already 10-15 hours saved per week. Annually, that's 500-750 work hours. We wrote more about each area in the 5 processes any SMB can automate article.
The tools: Make.com, n8n, Zapier comparison#
Among no-code automation tools, three stand out in the Hungarian SMB market. Each has its strengths, and the choice depends on your specific situation.
| Factor | Make.com | n8n | Zapier |
|---|---|---|---|
| Pricing | Execution-based (ops) | Free (self-hosted) or cloud | Task-based |
| Monthly cost (SMB) | $9-29 | $0 (own server) or $20+ | $19-49 |
| Hungarian language | Interface in English, but handles Hungarian content | Interface in English | Interface in English |
| Number of integrations | 1,800+ | 400+ (but extendable with any API) | 6,000+ |
| Visual editor | Excellent, intuitive | Good, but more technical | Simple, linear |
| Complex logic | Good (router, filter, iterator) | Excellent (any branching, loops) | Limited |
| Self-hosting | No | Yes | No |
| Data storage | EU server available | You decide (own server) | US server (by default) |
| Webhook handling | Good | Excellent | Limited |
| Learning curve | Medium | Higher | Low |
When to choose which?#
Make.com is the best general choice for most SMBs. Its visual editor is intuitive, its integration selection is extensive, and its pricing is predictable. For simpler automations (email management, CRM updates, reporting), Make.com is a perfect fit.
n8n is worth it if your company's data cannot leave your own server, or if you need to implement complex, multi-step logic. For the Mindwell project and Balazs Kicks, we chose n8n because webhook handling and complex branching are the most flexible here. If you have a technically minded colleague on your team, n8n is the most powerful tool.
Zapier is the easiest entry point. If you want to connect two apps (e.g., "when a new Google Form submission arrives, create a row in Airtable"), you can do it with Zapier in minutes. However, for complex logic, it quickly becomes expensive and limited.
We use Make.com in 60% of projects, n8n in 35%, and Zapier in 5%. Make.com covers most needs, we bring in n8n when self-hosting is required or the logic is very complex. We typically use Zapier for prototypes that we later migrate to Make.com or n8n. For more on the no-code vs. custom development question, we go into the decision logic in more detail in that article.
Complementary tools#
Besides the automation engine, you'll need these tools:
| Tool | Purpose | Monthly cost |
|---|---|---|
| Airtable | Central database, CRM, task management | Free - $20 |
| Google Sheets | Simple data management, reporting | Free |
| Notion | Documentation, internal wiki, simple CRM | Free - $10 |
| Calendly | Appointment scheduling | Free - $12 |
| Szamlazz.hu / Billingo | Invoicing API | Existing subscription |
| Slack / Telegram | Notifications | Free |
Implementation guide: how to get started#
Audit: assess your current processes
For one week, note down how much time you spend on each repetitive task. No need to overcomplicate it: a simple table is enough (task, frequency, time required, error potential). Ask your team members to keep their own logs too.
At the end of the audit, you'll have a list showing where the most time is being spent. Our experience is that teams underestimate their own time by 30-50%, so it's worth actually measuring rather than guessing.
Prioritize: pick the first process
From the audit results, choose the process that:
- Takes the most time per week
- Can be described with relatively simple rules (if X happens, do Y)
- Doesn't require human judgment at every step
For most companies, invoicing, email categorization, or reporting is the best starting point. Don't start with the most complex process.
Tool selection and prototype
Choose a tool (see the comparison table above) and build the first automation prototype. Most tools have a free version that's perfectly adequate for this.
The prototype doesn't have to be perfect. It just needs to cover the basic process. If you're automating invoicing, start with automatically issuing an invoice after an order. Reminders, reports, and NAV sync can come later.
Testing with real data
Test the automation with real data, but initially run it in parallel with the manual process. This way, if something goes wrong, there's no downtime. After two weeks of parallel operation, you'll see whether it works reliably.
Pay attention to edge cases: what happens if a field is empty? What if a system is unavailable? An automation is only as good as its error handling.
Go live and team training
If the automation worked reliably during testing, switch off the manual process. Show the team how the new system works and where to turn if something doesn't seem right.
Team involvement is crucial. Most automation projects don't fail because of technology, but because people don't accept the new workflow. If the team participates in the design, they're more likely to embrace the change.
Measure and expand
Track how much time the automation saves each week. Once you have the first successful result, move on to the next process. Our experience is that after the third automation, the team starts looking for new opportunities on its own.
Costs: how much does an automation project cost?#
This is one of the most common questions we get. The answer depends on what and how you automate.
If you do it yourself#
| Item | Cost |
|---|---|
| Automation tool (Make.com / n8n) | $0-30/month |
| Complementary tools (Airtable, Calendly, etc.) | $0-30/month |
| Your time (learning, building) | 20-40 hours for the first automation |
| Total (first year) | $0-720 + your time |
This is a good option if you're building simple automations (2-3 step workflows) and have time to learn. Most no-code tools have good documentation, and there are plenty of tutorials on YouTube.
If you hire an expert#
| Project type | Typical cost | Timeframe |
|---|---|---|
| Simple automation (1-2 workflows) | 100,000-300,000 HUF | 1-2 weeks |
| Medium project (3-5 workflows, integrations) | 300,000-800,000 HUF | 2-4 weeks |
| Complex system (10+ workflows, custom logic) | 800,000-2,000,000 HUF | 4-8 weeks |
| Monthly maintenance and support | 50,000-150,000 HUF/month | Ongoing |
The Mindwell project, for example, involved 24 workflows, which falls in the complex category. The Murabau AI OCR system is in the medium category because, while technically complex, there are fewer workflows.
If your company doesn't have a technically minded employee, or if the process is complex (multiple systems, complex logic, error handling), it's worth working with an expert. A self-built automation is cheaper to start, but if built poorly, the cost of fixing it and the lost time exceeds what the expert's fee would have been. You can read more about our business automation service.
ROI calculation: when does it pay off?#
Let's calculate with a concrete example.
Starting point: a 25-person trading company where 12 hours per week go to repetitive administration (invoicing, order management, reporting).
| Item | Calculation | Amount |
|---|---|---|
| Time saved/week | 12 hours x 60% automatable | 7.2 hours/week |
| Time saved/year | 7.2 x 48 weeks | 345 hours/year |
| Hourly rate (employer gross) | Average office worker | 4,000 HUF/hour |
| Savings/year | 345 x 4,000 | 1,380,000 HUF |
| Automation cost (tools) | Make.com + Airtable | ~180,000 HUF/year |
| Automation cost (implementation) | Expert, medium project | ~500,000 HUF (one-time) |
| Payback period | ~6 months |
This is a conservative calculation. It doesn't include savings from reduced error rates (fewer complaints, fewer late payments), additional revenue from increased capacity, or the fact that the team is happier when they don't have to spend hours daily on boring admin work.
Second example: a 15-person service company where 6 hours per week go to CRM management, email responses, and appointment scheduling.
| Item | Calculation | Amount |
|---|---|---|
| Time saved/week | 6 hours x 70% automatable | 4.2 hours/week |
| Time saved/year | 4.2 x 48 weeks | 201 hours/year |
| Hourly rate (employer gross) | 4,500 HUF/hour | |
| Savings/year | 201 x 4,500 | 905,000 HUF |
| Automation cost (tools) | Make.com + Calendly | ~120,000 HUF/year |
| Automation cost (implementation) | Expert, simple project | ~200,000 HUF (one-time) |
| Payback period | ~4 months |
It's worth it for smaller companies too. Payback typically ranges from 3-8 months, depending on company size and process complexity. The main rule: the more repetitive tasks there are, the faster the payback.
The 7 most common mistakes SMBs make when automating#
1. Trying to automate everything at once#
The biggest mistake. If you try to automate 8 processes simultaneously, none of them will be done properly. Start with one, test it, stabilize it, and only then move to the next.
2. Not measuring results#
If you don't measure how much time you save, you can't prove it was worth it. Keep a simple log: date, task, manual time, automated time. After two weeks, you'll see the difference.
3. Skipping error handling#
Automation works as long as everything goes well. But what happens when an API is down? When a field is empty? When the internet drops? Error handling is not optional. Every workflow should have at least an "if something goes wrong, notify the team" branch.
4. Not involving the team#
If you push the new system on the team from above, you'll meet resistance. Ask your colleagues which task they hate the most and start there. If they participate in the design, they'll take ownership.
5. Building overly complex automations#
If the automation has 25 steps and nobody understands what's happening inside, that's a problem. Better to have multiple smaller, simpler workflows that communicate with each other. This is why we chose many small workflows instead of one big one at the Mindwell project.
6. Forgetting documentation#
A month from now, you won't remember why you created that filter in step 3. Write short comments in every workflow: what it does, why, and what to check.
7. Not thinking about scaling#
The automation that works fine with 50 orders might break at 500. Think ahead: what happens if traffic grows? If there's more data to handle? If a new integration needs to be added?
The most expensive mistake isn't the cost of automation, but not doing it at all. Every month spent on manual administration is money left on the table. Six months of procrastination at a 25-person company can easily mean 600,000-700,000 HUF in missed savings.
Summary: automation is not a project, it's a mindset#
Automation isn't a one-time project you complete and you're done. It's a mindset: continuously look for opportunities where the machine would do the job better, faster, and more reliably than a person.
The key takeaways:
- Start small. One process, one tool, one week. If it works, move to the next.
- Measure the results. What you don't measure, you can't prove. Track the time saved and the reduced error count.
- Involve the team. Automation is the team's tool, not a force working against them.
- Don't be afraid to ask for help. If you're unsure, a 30-minute consultation can reveal where the biggest potential lies.
| Process | Time saved/week | Difficulty | Recommended tool |
|---|---|---|---|
| Invoicing | 2-4 hours | Medium | Make.com + Szamlazz.hu |
| Order management | 5-15 hours | Advanced | n8n + Airtable |
| Email management | 3-5 hours | Easy | Make.com + Gmail |
| CRM/customer tracking | 3-4 hours | Medium | HubSpot / Airtable |
| Reporting | 2-4 hours | Medium | Looker Studio + Make.com |
| Inventory management | 2-3 hours | Medium | n8n + Shopify/Airtable |
| Appointment scheduling | 1-2 hours | Easy | Calendly |
| Document processing | 3-6 hours | Advanced | n8n + AI OCR |
Total: up to 20-40 hours saved per week. That's 80-160 hours per month, equivalent to a full employee's capacity.
Related articles and resources#
- 5 processes any SMB can automate - if you're just starting, begin here
- How we automated an entire webshop's order management - a real case study from the Mindwell webshop
- No-code vs. custom development: which should you choose? - when is no-code enough, and when do you need a custom solution
- Business automation service - if you'd like us to handle it
- Ready-made business systems - if you're looking for a proven solution that can be deployed quickly