Clients always ask for "just one more thing" in a project scope an extra report, another revision, or an additional strategy call. If you keep saying yes, your core service loses focus and efficiency.
It's tempting to add more to justify a higher price, but usually, less is more.
And I assume it s similarly tricky for software builders. Users constantly request new settings, integrations, and custom options. But adding every requested feature turns a clean tool into a complex, confusing mess.
How do you decide when to say "no" to feature requests to protect simplicity?
Currently trying to get the first 10 paying customers for my SaaS. I ve been doing outreach and demos, but curious how other founders got their first few customers. What actually worked for you, cold outreach, communities, ads, referrals, or something else?
I have recently seen platforms, including some CRM systems, that operate almost entirely through chat and MCP connections rather than traditional menus, dashboards and settings.
It made me question how software platforms should be built going forward.
I ve been thinking about this after seeing how quickly AI is changing the way products are built.
As a data analyst, I m used to looking at how quickly things change, and right now it feels like the speed of building has gone up a lot. A small team can test an idea and launch it much faster than before.
But if everyone can build faster I m wondering where the real advantage comes from.
When you're bootstrapping multiple products, there's this physical feeling that shows up and nobody ever talks about it. Your stomach is somehow empty and full at the same time. This knot that just sits there while you're trying to figure out which project needs you most.
I run Sparkum, Biteme, and LifeLines all under Onyx Labs. No investors. Every dollar is ours. Some days that's exciting. Other days it's just heavy.
A few things that actually help me:
Get specific. The "everything is overwhelming" feeling is almost never true. It's usually one or two things hiding behind everything else. Name them. The rest gets lighter.
I was reading about a developer whose 10-agent setup started acting up over the past few weeks. The more freedom they got the worse the output became adding bloat and getting trapped fixing low priority issues no one asked for.
I ve noticed a similar wall when letting AI handle full features solo. It often prioritizes tiny edge cases over keeping the core codebase clean.
For those running agentic workflows, what guardrails do you use to force them back on track?