At first, I just wanted to build my own trading journal

LowFlow didn't start as a company, a piece of infrastructure, or a complete ecosystem.

At first, I just wanted to build my own trading journal.

I wanted something that actually matched the way I worked.

Not just a page where you enter a result at the end of the day.

I wanted to be able to look back at my trades, understand what happened during a session, keep my notes, and start building a history that was truly mine.

And there was already an important idea behind all of it: the trader had to stay in control.

My data had to stay my data

Very early on, I didn't want to build a journal where all of the trader's data had to be sent to an external service.

The trades belong to the trader.
His screenshots belong to him.
His notes belong to him.
His history belongs to him.

So I wanted to go in the other direction: build something around the trader and his own computer.

The software could organize the data, analyze it, and make it useful. But the trader had to remain the owner of his environment.

That idea would become much more important later on. At the time, I didn't yet know how far it would take me.

A journal meant to serve before, during, and after trading

I didn't just want to know how much I had made or lost. I wanted to understand how I got to that result.

What had I planned before the session?
Which trades did I take?
Why did I enter?
Did I follow my plan?
How was my execution?
What did I see on the chart?
And what could I learn from that day later on?

So the journal had to gradually bring together several pieces of the trader's process.

Preparation.
Execution.
Notes.
Results.
Screenshots.
Analysis.

The idea was simple: when I looked back on a trading day, I wanted to be able to find its story. Not just a number.

Trader Chooses

Over time, this philosophy would end up having a very simple name: Trader Chooses.

The software provides the tools. But the trader decides.

He chooses what he wants to analyze.
He chooses his accounts.
He chooses his data.
He chooses how he organizes his environment.
He chooses what he wants to keep.

Today, this principle exists in a huge number of parts of LowFlow. But at the beginning, it wasn't a slogan. It was simply the way I wanted to build my own journal.

And then the journal started to grow

Like many projects, LowFlow could have stayed something very simple. But as soon as the first journal became usable, one thing became clear: every answer created a new question.

Recording trades was one thing. Analyzing them properly was another. Adding screenshots brought new problems. Keeping more data brought even more.

And very quickly, what was supposed to be a small journal started becoming something else.