Built by one person who kept rebuilding the same automations

I build web products for agencies and small businesses, and Flows came out of that work: the same handful of automations, rebuilt by hand for every client, that deserved to be a product.

Most automation tools are built for operations engineers who enjoy dragging nodes around a canvas. The businesses I work with do not have that person. They have an owner who knows exactly what should happen when a lead comes in, and no time to wire it up.

Flows is my answer: describe the process in plain English, connect the apps you already use, and let it run. When something breaks, the assistant explains it like a colleague would and offers the fix.

It is a small, independent product. You are talking to the person who built it when you email support, and your feedback shapes what ships next.

What I optimise for

• Plain language first

  If a business owner cannot read a workflow top to bottom and understand it, it is not finished.

• Quiet by default

  Alerts only when something needs you. Automation should reduce noise, not add to it.

• Your data, your accounts

  Every connection is your own, encrypted at rest and revocable from the vendor in one click.