Back home
Product

Shipping a product solo: what RadFlow taught me

For a year I owned discovery, design, code, infra and go-to-market for a single product. Here’s where doing it all alone pays off — and where it quietly bites.

Diogo Serrano
Diogo Serrano
// product ยท engineering
6 min read

RadFlow started as a question I couldn’t stop asking: how much of a real product can one person still own, end to end, in 2026? A year later I have an answer, and it’s more nuanced than the “solo founder” mythology suggests.

The pitch is seductive. No handoffs. No alignment meetings. The person who decides what to build is the same person typing the code and paged when it breaks at 2am. In theory, that’s the fastest feedback loop you can build. In practice, it’s the fastest loop and the loneliest one.

Where owning the whole loop wins

The biggest surprise wasn’t speed — it was coherence. When the same head holds the product bet and the implementation, decisions stop getting lost in translation. A constraint I discover in the database on Tuesday quietly reshapes the roadmap on Wednesday, without a single ticket.

  • Discovery and engineering share one context, so trade-offs are honest instead of political.
  • I can prototype a risky idea in an afternoon and kill it by dinner — no committee required.
  • Every line of the product reflects one point of view. That consistency is hard to fake with a team.
The fastest way to validate a product idea is to be the person who can both imagine it and build it.

Where it bites

Then reality arrives. Owning everything means you are also the single point of failure for everything. There is no one to catch the blind spot you can’t see, because by definition you can’t see it.

Context-switching has a tax

Shipping a deterministic rules engine in the morning and writing onboarding copy in the afternoon are genuinely different modes of thinking. The switch is never free — some days the tax ate more hours than the work itself.

You become your own bottleneck

With a team, work parallelises. Solo, it queues. Every decision waits for the one person qualified to make it, and that person is also asleep eight hours a day. I learned to protect deep-work blocks like production infrastructure.

The rule I landed on

Automate the boring 80%, obsess over the 20% only a human-in-the-loop should touch. For RadFlow that meant a rules engine for classification, and a radiologist who reviews and owns every report.

What I’d tell past me

Solo isn’t a permanent state — it’s a phase that buys you clarity. Use it to find the shape of the product while the cost of changing your mind is near zero. Then, the moment a decision needs more than one brain, go find the second brain.

RadFlow is still mine, end to end. But the lesson wasn’t “do everything alone forever.” It was that owning the whole loop, even briefly, teaches you exactly which parts you should never hand off — and which parts you can’t wait to.

Diogo Serrano

Written by Diogo Serrano — product manager & fullstack engineer in Lisbon. Building RadFlow. Say hi at hello@diogoserrano.com.