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.
7 articles in this threadReset filters
Operating model · Jul 5, 2026
Quarterly reviews for a solo business: ninety minutes that steer the next ninety days
The quarterly review as a solo operator actually runs it: a short metric set, an unsentimental kill/keep/double-down sort of every project, three written bets for the next quarter, and structural guardrails against vanity retrospectives.
Novus Stream Solutions (hub)
Operating model · Jul 4, 2026
A simple CRM in a spreadsheet: the one-tab pipeline for a tiny operation
A working spreadsheet CRM for a tiny operation: the seven columns that matter, four right-sized pipeline stages, follow-up cadences that actually run, and the graduation signals for moving to real CRM software.
Novus Stream Solutions (hub)
Operating model · Jun 9, 2026
From scattered feedback to a roadmap, without a PM
A practical method for turning scattered feedback into a roadmap when you have no PM: getting all the inputs into one place, clustering raw requests into underlying themes, weighing each theme by frequency and pain against effort and fit, and sorting the result into build now, watch, or decline, across multiple products without drowning.
Novus Stream Solutions (hub)
Operating model · Jun 8, 2026
A go-live runbook for a serverless browser app
A practical, ordered go-live runbook for an app with no backend: verifying the build and assets, confirming metadata and share previews, checking performance and the offline path, making sure analytics and error reporting are live before traffic arrives, and knowing exactly how to roll back. Less a philosophy than a checklist that has earned its place.
Novus Stream Solutions (hub)
Operating model · Jun 7, 2026
Why we shelved Novus Stream Studio: a second-screen idea that was really several apps
A kill-decision retrospective: how an appealing single product turned out to be a bundle of apps, and why that made it the wrong thing to keep building solo.
Operating model
Operating model · Jun 7, 2026
Why we retired Novus Stream Tools: generic utilities that didn't earn their place
A kill-decision retrospective on building utilities that work fine but have no real reason to exist, and the test that should have caught it sooner.
Operating model
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