Why we built FlowLens
Why FlowLens exists, what we believe about owning your own AI and your own workflow data, and where things stand today.
01 · The origin
One afternoon that should have been a good day.
It started on a day that was going fine. Then a workflow that had been running without a problem just stopped working.
I didn't know why. I opened it, stared at the nodes, and had no idea what had changed or where to even start looking. So I did what most people do: searched forums, searched Google, asked an AI for help, tried things, backed them out, tried other things. A few hours later, it was fixed. I never did find a clean answer for why it had broken in the first place, just enough of a trail to patch it and move on.
That one afternoon turned a good day into a workday I hadn't planned on. And the thing that stuck with me wasn't the bug itself: it was how much of that time went into just figuring out what changed, before I could even start fixing anything.
I built FlowLens so that part doesn't have to happen to someone else the same way it happened to me.
02 · What we believe
What we believe
The problem that shows up months later
We think the "AI workflow copilot" category has mostly been built around generatingworkflows faster: describing what you want in plain English and getting a workflow back. That's useful, but it's a different problem from the one that shows up months later: a working workflow that quietly stops working, with no record of what changed.
Your data, your AI provider
We also think workflow data shouldn't have to pass through someone else's AI service by default. A lot of what a workflow JSON file reveals (which systems talk to which, what triggers a payment, how a lead gets routed) is close to the shape of how a business actually runs. That's why FlowLens supports bringing your own AI provider key instead of requiring one shared service everyone's data funnels through.
03 · Where things stand
Where things stand today
Just startingWe're just starting. FlowLens doesn't have a long customer list or years of track record yet: it exists because one specific bad afternoon convinced one person this problem was worth solving properly, and it's being built for anyone who's had that same afternoon.
Get in touch
Questions about how FlowLens handles your workflow data, which AI providers it supports, or whether it fits your setup: reach out rather than guessing from the docs.