What running Fortify Labs, a Web3 startup studio, taught us about building products
Where Keystone Lab and Panora began: the clarity problem we kept seeing while running our Web3 startup studio.
This is where Keystone Lab, and Panora, began. It first appeared on
tzapac.com, and we are reposting it here to open this series, because the why comes before the how.
The pattern we kept seeing
After years working with founders through various incubators and through Fortify
Labs, our Web3 startup studio, we kept running into the same thing in the teams
that struggled. They were rarely short on talent or commitment.
The teams that struggled most were rarely short on talent or commitment. They were short on clarity.
It was not that founders did not know things. They often knew, sometimes
painfully, that they had drifted from the problem they set out to solve. The
issue was scattered context: decisions whose reasoning had been lost, and
conversations that lived only in people's memories instead of anywhere you could
go back to.
Three lessons
Alignment over speed. Velocity came from alignment, not aggressiveness. The
teams that moved fastest were the ones where everyone knew the current thinking,
the current priority, and the reasoning behind the current direction.
Cutting is a skill. The ability to abandon a failing approach cleanly turned
out to be valuable and underdeveloped in equal measure. Teams struggled to stop
work even when the signals had turned, because stopping felt like admitting
failure.
Institutional memory is fragile. Small teams lose context fast — a person
leaves, or a year of undocumented meetings piles up — and you end up asking the
same questions over and over, slowing everything down.
What we built
These were not distant observations. We lived them while running Fortify Labs.
When we could not find a tool that actually solved the problem, we started
Keystone Lab, a product studio that applies founder discipline to our own work.
Our first product is Panora: an AI meeting assistant that preserves the context
of your conversations, so a team can go back and ask what was decided, and why,
with the full picture intact.
Why this opens the series
Everything else in Building Panora is about the how — how your recordings stay
on your phone, how cloud processing works when you choose it, what deletion
really does. This post is the why. Panora exists because we felt the cost of
lost context ourselves, and decided to build the thing we wished we had.
