Why I Built FloFactor
My AI engineers got faster than I could.
I started building FloFactor because of a problem I ran into building my own products.
The engineering wasn't the bottleneck anymore. I was.
The bottleneck moved
The problem kept moving upstream.
I haven't personally written code in nearly three years.
I build with AI. The better the engineering became, the more obvious the requirement: if I wanted great output, I needed a great implementation plan.
A great plan needs a great product specification. A great specification needs product understanding. And that requires something harder still:
You have to decide what should actually be built.
- 01Implementation plan
- 02Product specification
- 03Product understanding
- 04Product judgment
Engineering got faster. Figuring out what to build next didn't.
Product judgment had become the bottleneck.
Holding it together
I became the system holding it together.
All the information existed. But the product understanding didn't.
- AI conversations
- Customer feedback
- Research
- Specs
- Previous decisions
- People's heads
- Conversations that existed nowhere except someone's memory
I had to remember what we had decided, which assumptions were still assumptions, and what still mattered.
The system of record was my head.
Meanwhile, the AI engineers were getting faster.
They would finish the work and turn back to me:
Done. What's next?
What I needed
That's why I built FloFactor.
The tools I had started after the decision was already made.
Issue trackers manage issues. Documents store documents. AI generates more analysis. My problem existed before the ticket.
I didn't need another place to store product work. I needed a system that could turn product knowledge into product understanding.
FloFactor shouldn't force people to document more. It should make it almost effortless for what people learn to become part of the product's living understanding.
FloFactor does the reasoning work required to bring the right decisions to me. I retain the authority.
The question that remains
What should we build next?
Engineering has already changed. Product has to keep up.
Put FloFactor to work on your product.
If this is the bottleneck you're in, check out the product, or apply to work with us.