Company
7 min read
What we learned from 12 private beta teams
Twelve companies, six months and a lot of honest feedback. These are the lessons that changed our roadmap.
NV
Nadia Voss
Co-founder & CEO
Our private beta started with twelve teams across finance, support and operations. We asked each of them to bring one workflow they were tired of running by hand.
People want to see the work
The most common request was not speed. It was visibility. Teams wanted to know what ran, what was skipped and why. That feedback shaped the run log and the approval trail, which are now two of the most used parts of Cinder.
Start small, then grow
Teams that began with one narrow workflow added three more within a month. Teams that tried to automate everything at once stalled. We now guide new teams toward a small first win.
Thank you to every beta team. You made the product better and kept us honest.
Questions or ideas? Email hello@cinder.ai and we’ll write back.
Keep reading
Another articles
Finance Ops
↗
Oct 28, 2026
6 min read
Why invoice intake is the best first workflow
It is repetitive, rule-based and easy to measure. Here is why most teams start here and what they learn along the way.
NV
Nadia Voss
Product
↗
Oct 14, 2026
5 min read
How approval thresholds keep humans in the loop
Automation should pause exactly where judgment is needed. Thresholds make that pause predictable.
EK
Elias Kade
Automation
↗
Sep 16, 2026
5 min read
A simple way to map a manual handoff
Before you automate a process, draw it. A short mapping exercise will show you what to build and what to skip.
DO
David Okafor
Cinder
AI workflow automation for teams that would rather do the work that matters.
All systems operational