For months, almost all of my work on LowFlow happened behind a screen. Code. Tests. Fixes. Builds. Integrations.
By dint of building, you almost end up forgetting one thing: no one sees any of that. A user doesn't see the thousands of decisions made behind the product. They see what happens when they open LowFlow.
And that's when I understood that the next step was no longer just to build. I had to start showing.
A feature list doesn't really tell the story of a product
I could write: automatic screenshots, replay, plans, statistics, multi-account, imports, add-ons. But a list doesn't show how it all works together.
A video of a few minutes can sometimes explain more than a full page. You see the trader open the journal. You see the trades appear. You see the screenshots. You see the day take shape. You see how to come back to it. And suddenly, it's no longer a feature list. It's a tool you understand.
The first testers changed my perception
I started having LowFlow tested by traders who were already using journals from big competitors. That was important to me. They already knew this kind of product. They had habits. Points of comparison. And above all, they had no reason to be impressed simply because I had built something.
Their reaction struck me a lot. They loved their experience with LowFlow. Not just one specific feature. The whole thing. The way of navigating. The fact that the data stays local. The way the elements are grouped. The control left to the trader.
And for me, that was an important validation.
Building alone, you lose some perspective
When you spend months in the same product, you know every screen by heart. You mostly see what isn't finished yet. The bug to fix. The detail to improve. The next feature.
A user, on the other hand, arrives without all that baggage. They simply see the experience. And sometimes, their perspective lets you understand that something already works much better than you thought.
It's also another test for the product
When I prepare a demonstration, I have to look at LowFlow like someone who doesn't know it. Is the path clear? Do you immediately understand what's happening? Does a feature require too much explanation? Can I show its value in a few seconds?
Wanting to explain a product quickly reveals what is still too complicated.
Videos will be part of the next step
Not to promise trading results. Not to explain to people how to trade. But to concretely show what LowFlow does. How a day is recorded. How the platforms communicate with the journal. How the screenshots are used. How you find your history. How you review.
The product has to be able to speak for itself.
After months of building in the dark, this changes a lot
I worked for a long time on things no one could see. Now, I'm starting to reach the point where I can simply open LowFlow and say: here it is. Here is how it works. Here is why I built this. Here is what the trader can do with it.
And when traders used to other journals tell me they loved the experience, it confirms one thing for me: LowFlow is no longer only interesting to me. It's starting to prove itself in the hands of others.
And somewhere, that's where the project really changes dimension.