I Self-Host My Automation. Here's Why My Clients Should Too.
n8n on my own server runs my three companies — here’s the honest maths.
Read the essay →Insights · Automation
Every new app adds a login, a bill and a new place for work to get lost.
By Rokib Rana — CEO of FlowRevo, BotPori & MegaHut
Last year I counted the tools my own companies were using. A messaging app here, a spreadsheet there, one tool for social posts, another for links, another for email — each one perfectly reasonable on its own. Together, they were a second job. Every tool had a login, a monthly bill and, worst of all, its own small pile of work that lived nowhere else.
This is the app pile, and almost every growing business I meet has one. The symptoms are always the same. The same customer information gets typed into three different places. A lead arrives in one tool and quietly dies there because nobody moved it to the next. Two people look at two different dashboards and argue about which number is true. Nothing is exactly broken — and yet the whole operation depends on somebody remembering everything, every day.
When I started MegaHut and was managing everything myself, I lived inside that pile. It taught me the lesson this essay is about: the problem was never a missing app. The problem was a missing system.
Here is the definition I work with. A system has four parts: a trigger (what starts it), an action (what happens, every time, the same way), an owner (who is responsible for it) and a measurement (how you know it worked).
An app usually gives you only the action — and only while a human is standing there pushing it. The moment the human gets busy, goes on holiday or simply forgets, the “system” stops. That is not a system. That is a task with a subscription.
A real system is a promise your business keeps without you in the room. A new enquiry arrives at 2 a.m., and it still lands in one inbox, still gets a first response, and is still waiting — organised — when your team starts work. Nobody had to remember anything. The system remembered.
My own stack is deliberately boring, and it covers most of what my companies do. First, one inbox: BotPori exists because my customer messages were once scattered across Facebook, Instagram and TikTok, with a slow Business Suite on top. One place for every conversation replaced three apps and a daily headache.
Second, one automation hub: a self-hosted n8n instance that moves data between the tools I already use — leads, orders, notifications, follow-ups — so information is never re-typed by a human. Third, one calendar: Postiz schedules and publishes content across my brands’ channels from a single plan, instead of somebody posting in a panic at midnight.
Notice what happened there. I did not end up with more software than before. I ended up with fewer, connected pieces — each one with a trigger, an action, an owner and a measurement. The apps did not disappear. They were demoted, from being the system to being parts inside one.
So here is the rule I now apply to my own companies and to every client engagement. Before you buy the next tool, answer three questions about it. What triggers it — what real event in your business sets it off? What does it hand off to — where does its output go, automatically? And who owns the result — how will you know, in numbers, whether it worked this week?
If you can answer all three, you are probably buying a system, or at least a part that fits inside one. If you cannot, you are buying another pile — another login your team will forget, another bill that renews itself, another place for a customer to get lost.
Businesses do not slow down because their people stop working hard. They slow down because their effort is spent carrying information between tools instead of serving customers. Fix the carrying, and the effort you already spend starts to count.
Start with the free checklist I use when I audit a business — 25 systems to automate or secure first.
Get the free checklistKeep Reading
n8n on my own server runs my three companies — here’s the honest maths.
Read the essay →Marketing gets the credit. Infrastructure decides whether you keep it.
Read the essay →