About
fl0w started with a habit I noticed in myself. In sessions with Claude Code, I kept doing the same things over and over: the same string of bash commands, the same research steps, the same check of Linear tickets every morning. Each time, I was the one who had to open my laptop and kick it off.
AI is more than capable of handling that on its own now. It can write the branching logic we used to wire up by hand in tools like Zapier, write code, and take actions in other tools. So I built a way to turn those sessions into workflows that run in the cloud on a schedule, from a webhook, or from a form, with my laptop closed.
I'm Jack, and I built fl0w. I started in data science around 2020, back when “AI” mostly meant regression models built for one narrow job. Since then I've been a software engineer, a developer marketer at a YC startup, and now I work on product for an SDK at Plaud. My last big side project was VimNotion. I'm still proud of it, but it taught me that people don't really want Vim in their Notion. They want things that save them time.
I've been reading The Beauty of Everyday Things, about Japanese craftsmanship, and how plain, useful objects still carry the soul of whoever made them. That's what I want fl0w to be: not flashy, just useful, and made with care, even if a lot of it was written with AI.
What I believe
AI should be a machine, not a coworker.
I don't want AI talking to people for me. The words we write to each other should stay ours.
Automate with intention.
Some tedious work is how you learn. Automate it once you know it by heart.
Quiet and reliable.
Good tools don't need to be loud. They just need to work, every time.
If there's a routine you already know by heart, let AI take it from here. Be intentional about what you hand off, and spend the time you get back on the work only you can do.