- Home
- Product blog
- Operating model
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.
Sub-topic
Type
17 articles in this thread
Operating model · Jun 7, 2026
Why we killed our sports-odds project: the real-time data bill we couldn't make cheap
A kill-decision retrospective on a product that was structurally incompatible with our cost model: the data had to be fresh every minute, and fresh-every-minute is expensive.
Operating model
Operating model · Jun 6, 2026
Keeping monthly overhead low while running a portfolio of apps
The infrastructure cost discipline behind running a multi-app portfolio solo, and why the architecture is what keeps it cheap.
Operating model
Operating model · Jun 4, 2026
Keep, kill, or shelve: a structural "no" as a product filter
An operating note on using a structural constraint (must run almost for free) as an honest product filter, not a failure of execution.
Operating model
Operating model · May 29, 2026
The cadence behind a site you can trust
An operating note on why a steady publishing cadence matters, and the code-as-content architecture that makes it sustainable solo.
Operating model
Operating model · May 28, 2026
A weekly operating rhythm for a solo operator
Why solo operators drown in the reactive, building a weekly rhythm with themed days, a weekly planning and review ritual, protected deep-work blocks, and room for the unexpected.
Novus Stream Solutions (hub)
Operating model · May 1, 2026
How we ship and test small apps without a full team
The operating model behind how NSS builds, ships, and decides what to keep.
Novus Stream Solutions (hub)
Operating model · Mar 29, 2026
Why novusstreamsolutions.com is built as a single front door for the stack
How novusstreamsolutions.com ties together NSS Background Remover, Novus Visualizers, and future products: one place to explain the ecosystem, find docs, and read product updates.
Novus Stream Solutions (hub)
Operating model · Mar 29, 2026
First clicks: a URL map for the entire Novus ecosystem
Bookmark this orientation: novusstreamsolutions.com, BG Remover, Visualizers, docs, and product blog.
Novus Stream Solutions (hub)
Page 2 of 2