A feature that customers love after buying, like 24/7 Slack access, may not be a primary driver for the sale itself. If it consumes significant founder time and prevents scaling, it should be eliminated to improve business health without significantly impacting new customer acquisition.

Related Insights

In early stages, the key to an effective product roadmap is ruthlessly prioritizing based on the severity of customer pain. A feature is only worth building if it solves an acute, costly problem. If customers aren't in enough pain to spend money and time, the idea is irrelevant for near-term revenue generation.

Entrepreneurs rush to market with an MVP, often giving away the 20% of features that drive 80% of customer willingness to pay. They then spend time building the less valuable 80%, inadvertently training customers to expect more for less and making future monetization difficult.

Adopt an "unshipping" culture. If a feature doesn't meet a predefined usage bar after launch, delete it. While a small subset of users may be upset, removing the feature reduces clutter and confusion for the majority, leading to a better overall user experience.

Figma learned that removing issues preventing users from adopting the product was as important as adding new features. They systematically tackled these blockers—often table stakes features—and saw a direct, measurable improvement in retention and activation after fixing each one.

Businesses often get bogged down by tactical feature requests, especially commitments for a single customer. This consumes precious capacity that should be allocated to strategic initiatives, allowing competitors with a clear vision to gain an advantage.

Saying yes to numerous individual client features creates a 'complexity tax'. This hidden cost manifests as a bloated codebase, increased bugs, and high maintenance overhead, consuming engineering capacity and crippling the ability to innovate on the core product.

Many founders become too attached to what they've built. The ability to unemotionally kill products that aren't working—even core parts of the business—is a superpower. This prevents wasting resources and allows for the rapid pivots necessary to find true product-market fit.

Adding numerous features to a service offering can hurt retention. Customers who don't use every component feel they aren't getting full value, creating a perception of waste that leads to cancellations. It's better to offer fewer, high-impact deliverables that ensure high utilization.

The strategy of eliminating the "worst 20%" applies across the business. Beyond firing unprofitable customers, analyze your product lines and even your team. Discontinuing low-margin, high-hassle products or removing toxic employees can free up immense resources and improve overall business health just as effectively.

Mature software products often accumulate unnecessary features that increase complexity. The Bending Spoons playbook involves ruthless simplification: eliminating tangential projects and refocusing R&D exclusively on what power users "painfully needed." This leads to a better, more resilient product with a lower cost base.