What Running Six Products Taught Me About Saying No
Six live products means a constant stream of feature requests, partnership pitches, and "quick" ideas. Saying no to almost all of them turned out to be the actual skill.
Running six products alone means a constant stream of inbound: feature requests from users who are right that the feature would help them, partnership pitches that are individually reasonable, "quick" ideas from my own head that would take a weekend and derail the actual roadmap for two. None of these are bad ideas in isolation. Saying yes to enough of them is how a one-person studio quietly stops shipping anything that matters. The actual skill I didn't expect to need this much turned out to be saying no, constantly, to things that were individually fine.
The Requests That Are Hardest to Say No To
The feature request from a real, engaged user. This is the hardest category by a wide margin, because the person asking is right — the feature would genuinely help them, and they're not wrong to want it. Saying no here doesn't feel like protecting focus. It feels like disappointing someone who took the time to ask. I still say no to most of these, because "this would help one engaged user" and "this is the right next thing to build" are different questions, and conflating them is how a roadmap gets built by whoever emails loudest instead of by what actually matters most.
The partnership pitch that's individually reasonable. Cross-promotion, an integration, a co-marketing idea — these show up regularly, and almost none of them are bad on their own terms. What they cost isn't the initial time to set up. It's the ongoing maintenance and coordination overhead that a one-person studio can't actually absorb six times over without something else quietly going neglected.
My own ideas. This is the one that surprised me most. The ideas that are hardest to say no to are the ones I generate myself, at 11pm, convinced a specific weekend project is the thing that unlocks something. Some of them are genuinely good ideas. The discipline isn't rejecting bad ideas — it's rejecting good ideas that aren't the current priority, which is a much harder version of the same skill.
What Actually Made This Easier
A short, explicit list of what's actually in progress. Not a full roadmap, just the two or three things actually being worked on right now. Any new request gets held against that list specifically: does this displace something already committed to, or does it just add to an infinite backlog. Most requests fail that test immediately once it's asked directly instead of evaluated in isolation.
Treating "not now" as a complete answer, not a soft no that needs justifying. Early on, every no came with an explanation, a justification, sometimes an apology. That's exhausting to sustain across six products and constant inbound, and it also invites negotiation — a justified no gets argued with in a way a plain one doesn't. "Not right now, but I hear you" is a complete sentence. It doesn't need defending every time.
Remembering that yes is the expensive option, not no. The natural framing treats saying no as the cautious, limiting choice and yes as the generous one. In practice, for a one-person studio, it's inverted: every yes is a permanent addition to what has to be maintained forever, across six products, by one person. No is actually the default that keeps the whole thing sustainable. Yes is the one that needs to earn its way in.
What This Actually Costs
I'm not going to pretend there's no real loss here. Some of the ideas I've said no to were genuinely good, and a few of them I still think about. Some of the partnerships probably would have worked out fine. The honest tradeoff isn't "saying no has no cost" — it's that saying yes to everything has a cost that's harder to see because it doesn't show up immediately. It shows up as six products that are all slightly worse maintained a year later, instead of a smaller number that are actually well cared for.
The Bottom Line
Running six products didn't teach me to have better ideas. It taught me that having good ideas was never the constraint — attention was, and every yes spends attention that doesn't come back. Saying no, plainly and without over-explaining, to things that were individually reasonable turned out to be the actual discipline that keeps six products running instead of six products quietly rotting at the same time.