One thing I’ve learned from building automation tools:
Writing the code is often the easy part.
The harder part is deciding what the system should do on its own, what should stay under human control, and what should happen if something goes wrong.
A system can work perfectly and still be annoying or even risky if the workflow is badly designed.
These days I think more about reliability and user control than just adding more features.
What do you prefer: full automation, or a system that always asks before taking action?
We’re choosing the motion for an AI analytics product demo, and I can’t decide.
Both clips show the same flow. Someone asks a question in plain English. The agent checks permissions, plans the query, runs it past guardrails and builds the dashboard.
1. A walks you through each step as it happens.
2. B skips the steps and drops you straight onto the result.
A shows the work. B shows the speed. For a landing page I keep going back and forth.
Which one would make you trust the product more? Comment A or B, and tell me why.
A simpler way to build workflows.
Otoma. AI turns plain-language instructions into working automations, helping finance and operations teams handle repetitive tasks while staying in control.