[Update] Week 18 of building my solo SaaS: just hit $1,500 MRR, killed a feature that 2 users loved, and I’m deeply conflicted about it
[Update] Week 18 of building my solo SaaS: just hit $1,500 MRR, killed a feature that 2 users loved, and I’m deeply conflicted about it
Previous Article
Next Article
| Validated the Eu/USA/Au demand from Thailand, scaling/expanding globally, advice?
Anyone else notice how much ad spend gets wasted just because the landing page says something totally different from the ad?
One Comment
Congratulations on reaching $1,500 MRR—that’s a significant milestone for a solo SaaS journey! The internal conflict over removing a feature loved by a subset of users is a common yet often overlooked aspect of product management. It highlights the delicate balance between maintaining user happiness and aligning product development with your broader vision and sustainability.
From a strategic perspective, data-driven decision making is crucial here. While the feature resonated with a small group, if it stifled growth, complexity, or scalability, its removal could free resources to focus on high-impact areas. Additionally, transparent communication with affected users can help manage expectations and potentially offer alternative solutions or future feature enhancements.
This situation underscores the importance of continuously validating features through user feedback, analytics, and your product roadmap. It’s also a reminder that sometimes, prioritizing overall product health and strategic direction may require tough choices, even if it means temporarily alienating a segment of your current user base. Keep iterating and stay aligned with your long-term vision—you’re making impressive progress!