Industrial-grade operations automation as a subscription — does this make sense?
Hey Indie Hackers — I’m Urmat, founder of Anymore.
I’m testing a simple idea:
Designjoy made design requests feel like a subscription. I want to apply the same model to operations automation — but with an industrial automation mindset.
When people hear “workflow automation”, they often think of Zapier, Make, n8n or Power Automate.
Those tools are useful for connecting apps.
But that is not really how we think about automation.
My brothers and I come from engineering and industrial automation environments, where automation means deterministic systems: production pipelines, process logic, validations, exceptions, logs, approvals and reliable outputs.
I want to bring that mindset to business operations.
A lot of serious office/operations work still runs through:
ERP exports
Excel files
PDFs
emails
service reports
KPI reporting
manual data cleanup
back-office processes
These are often not simple “if this, then that” automations.
They are messy operational pipelines:
collect data → clean it → validate it → transform it → generate output → review → approve → archive/send/update
That’s what Anymore is focused on.
Not Zapier-style app connections.
More like:
deterministic automation systems for operations teams.
The model is simple:
Send a workflow → we map the process → build the automation → test it → you review/use it → request the next one.
One workflow at a time, subscription-based.
Positioning I’m testing:
“Automation subscriptions for operations teams.”
Or:
“Industrial-grade operations automation as a subscription.”
Or simpler:
“Designjoy for operations automation.”
What I’m trying to figure out:
Is “industrial-grade operations automation” clear, or too heavy?
Does the factory automation mindset make the positioning stronger?
Would “one workflow at a time” make sense for operations teams?
Does this sound more like productized service, automation studio, or SaaS?
Would love honest feedback.
