Automation has a subscription problem.
Every little task seems to come with another tool, another plan, another upgrade wall, and another $50/month charge hiding behind the word “scale.” Before long, the automation that was supposed to save you time has turned into a stack of invoices and a dashboard you are afraid to touch.
I like automation. I do not like paying rent on every tiny workflow.
The Subscription Tax Nobody Talks About
The monthly price is only part of the cost. The real cost includes setup time, maintenance, usage limits, failed runs, vendor changes, and the mental overhead of remembering where the workflow lives.
A $20/month tool is not expensive if it saves five hours every month and never breaks. A free tool is expensive if you spend Saturday afternoon fixing it twice a month.
Automation is math. Not religion.
What I Actually Automate
I look for work that is repetitive, rules-based, annoying, and easy to verify.
- Moving data from one place to another.
- Generating drafts from a known template.
- Checking whether something changed.
- Sending reminders based on a date or status.
- Creating reports from existing data.
I do not automate work that still needs judgment every time. That is how you create a fragile system with a fancy name.
The $0 Stack: Tools You Already Have
Before buying anything, check what you already have.
- Email filters and templates.
- Calendar reminders.
- Spreadsheet formulas.
- Operating system scheduled tasks.
- Shell scripts.
- WordPress scheduled posts.
None of that sounds exciting. Good. Boring tools are easier to understand when they break.
The Cheap Stack: When You Need a Little More
Sometimes you need a real workflow tool. That is fine. Just do not start there.
The cheap stack is for workflows that need webhooks, API calls, scheduled runs, or multiple services talking to each other. This is where tools like n8n, Make, Zapier, Pipedream, or a small script on a server can make sense.
The question is not “Which tool is best?” The question is “Who is going to own this when it fails?”
The Self-Hosted Option: Worth It or Maintenance Trap?
Self-hosting can save money, but it moves the cost somewhere else. Now you own updates, backups, monitoring, certificates, storage, and whatever weird thing happens after a container restart.
If you enjoy that work or already run infrastructure, self-hosting can be a great fit. If you just want a reminder email, do not build a miniature platform.
Three Automations Worth Building First
- Daily summary: pull tasks, calendar items, and important reminders into one note.
- Draft generator: turn a repeatable content idea into a structured first draft.
- Status checker: watch a page, feed, service, or report and alert only when something meaningful changes.
Those are useful because they save attention, not just clicks.
The One That Broke
Every automation eventually breaks. An API changes. A token expires. A vendor moves a button. A field comes back empty. A cron job runs at the wrong time because time zones are evil.
The mistake is pretending breakage is rare. It is not. The fix is to design for it.
- Log every run.
- Alert on failure.
- Keep manual fallback steps.
- Document where credentials live.
- Review whether the automation is still worth maintaining.
Maintenance Reality
The best automation is not the one with the prettiest diagram. It is the one you can understand at 11:30 PM when it stops working.
Automate the task. Track the cost. Keep the fallback. And do not subscribe to another tool until the math says it earns its keep.