Why I built a trading journal as a solo founder

Most posts on this blog are practical — how to journal a Robinhood trade, how to compute profit factor, which broker integration to use. This one is different. It's the story of why I built TradeFlow Quantum in the first place, what was wrong with the existing options, and what I learned about the difference between "useful" and "loved" in trader tools.

The 18 months of trying everything

Before TradeFlow Quantum existed, I spent about 18 months cycling through journal tools. Tradezella for 4 months. Tradervue for 6 months. Edgewonk for 3 months. A custom Google Sheets template for the rest. None of them stuck for the same reason: they all assumed I'd be willing to spend more time on the journal than on trading.

Tradezella's UI was polished but every trade still took 60-90 seconds to log manually. Tradervue's social features I never used. Edgewonk's configurability rewarded patient power users; I'm not a patient power user. The spreadsheet broke every time I changed brokers.

The specific moment

The specific moment I decided to build my own was a Friday afternoon in early 2025. I had taken 14 trades that day. I had logged 6 of them in real time. The other 8 I was supposed to backfill from memory. I sat down at 5pm with a glass of water and tried to reconstruct the rationale for trade 9. I couldn't. The trade was already an abstraction — "I think I was waiting for the VWAP reclaim" — instead of a memory.

The lessons from those 8 unlogged trades were gone. That's the whole point of a journal: to capture the lesson before the rationalization sets in. If the tool you use makes you backfill from memory, the tool isn't a journal. It's a record.

The hypothesis

My hypothesis was that the friction of journaling — the 60-90 seconds per trade of typing into a form — was the actual barrier to consistent journaling. Not lack of discipline. Not lack of analytics. Just the friction of moving structured data from your head to a form, while the next setup is forming in front of you.

So I started with the question: what if logging a trade took 10 seconds instead of 90? What would have to be true?

• Broker OAuth for as many brokers as possible. The structured data (symbol, side, qty, entry, exit, P&L) should come from the broker, not from you typing.
• SnapTrade aggregation for the rest. When a broker has no direct OAuth (Robinhood, Webull, Fidelity), SnapTrade's read-only connection pulls the fills in automatically.
• Mobile-first journaling. The trader is at their desk during the trade and on their phone right after. The phone is where the journal needs to be.

What I gave up by being solo

Building solo means TradeFlow Quantum will be less polished than Tradezella for a while. Their team is 10+ people; I'm one. They have a designer; I do my own design. They have customer support that responds in minutes; I respond in hours.

What I keep by being solo: every product decision is mine. There's no "let's add a leaderboard because the growth team asked" — there's no growth team. The product stays a journal, not a community, not an advisory service, not a signal feed. The constraints solve themselves.

What this means for users

You get a product that's more opinionated than a team-built one. You get faster shipping (I deployed something today; the bigger journals shipped something last quarter). You get a founder who reads every feedback message personally (and replies to most). You get less polish than the leaders, more focus, and a real human at the other end.

Whether that trade is right for you depends on what you value. If you want enterprise-grade polish, Tradezella might be a better fit right now. If you want a tool built by someone who actually uses the tool every day for their own trading, TradeFlow Quantum is what I built for myself first.