GuardrailAI: Human-in-the-Loop Checkpoint Infrastructure for AI Apps

Mine was assuming people wanted the ai to be autonomous. Built a thing that replies to customer messages on its own and the first thing every single user asked for was a way to see what it was about to send before it sent it. Took me a while to get why. It wasnt distrust of the output quality, the replies were fine. It was that a wrong message goes out under their name to their customer, and they carry that, not me. Once you understand it that way the approval step stops feeling like a downgrade. So same shape as yours really. The value ended up being in the queue and the drafts, not the sending.

This matches what we've seen too. The assumption that more automation equals more value breaks down fast once the output has to be trusted by someone else, a customer, a compliance team, whoever is on the other end of that email. The moment AI starts taking actions that are hard to undo, sending something, charging something, committing to something, the cost of a wrong decision goes up much faster than the cost of a slow one. Your three line principle is close to how we think about it as well: the system should always show its work and let a person approve the consequential step, rather than just executing because it technically could. Disclosure: I build Base (withbase.ai), an operating layer for early stage founders covering CRM, contracts, invoicing and the rest. We made the same call you did, human directed rather than autonomous, for exactly the reason you describe here.