Novus Stream Solutions

Category

Operating model

Our operating model (build, ship, measure, keep-or-kill), plus low-overhead operations, the free-first ad-supported model, and honest retrospectives on the products that did not fit.

17 articles

About the Operating model thread

How a small free-apps studio actually runs: how something gets picked up, how it gets shipped, how it gets maintained, and (the part most operators skip writing about) how it gets killed.

The retrospectives are the honest core of this cluster. A sports-odds project was built and then shut down, not because it failed technically but because it needed constant real-time data and therefore a permanent cost floor incompatible with a portfolio that has to run at nearly zero marginal cost. An AI-agent ecosystem was shelved for a related reason. Publishing those decisions with the reasoning intact is more useful than another launch post, and it is where the operating model becomes legible.

Alongside that sit the unglamorous mechanics: quarterly reviews that actually change something, turning scattered feedback into a roadmap without a product manager, and running support for products nobody pays for.

What this topic covers

  • How apps get chosen, shipped, and maintained across a portfolio
  • Structural "no" as a product filter: killing work that cannot exist cheaply
  • Retrospectives with the reasoning intact, including the projects that were shut down
  • Quarterly reviews for a solo business, and turning feedback into a roadmap without a PM
  • The economics underneath a free-tool portfolio

Who it's for

Solo founders and small teams running multiple products, and anyone curious how free apps stay funded.

17 articles in this thread, newest first. Every one is free to read with no signup.

Browse every topic in the resource hub