This is where product decisions get uncomfortable. A customer representing a significant portion of your revenue wants
Indie hackers and solo founders running small SaaS products who face feature requests from a customer that represents a significant portion of revenue, and who must balance customer happiness against roadmap protection.
A lightweight web app where a founder enters a feature request, answers a short guided questionnaire about the customer's underlying problem, and receives a structured maintenance cost estimate and a one-page decision memo. No integrations; manual entry only.
Existing discussion is a single Reddit thread (score=3) that frames the dilemma but offers no tool. No project in the evidence provides a maintenance cost estimator or a decision dashboard for this specific conflict. The gap is a missing structured process that turns the thread's questions into a repeatable workflow.
Platform: a web app built with a modern JavaScript framework. Hardest problem: reliably estimating long-term maintenance and support cost from a short feature description without historical data. Reusable open-source pieces are not mentioned in the evidence.
One-time purchase for the MVP, with an optional subscription for teams that need ongoing request triage and decision history.
The estimator may be perceived as guesswork without real maintenance data, and founders under revenue pressure may skip the tool and default to the customer's request. The product must be fast enough to use during a live negotiation.
No existing project in the evidence builds this. The only signal is a Reddit thread (score=3) discussing the dilemma, with no linked tool or product.
A single-page form that captures the feature request, asks the problem-vs-solution question, and outputs a maintenance cost estimate and a decision memo. No accounts, no integrations.
Producing a credible maintenance cost estimate from limited input. The evidence gives the pain (two-week build, years of overhead) but no data model, so the tool must rely on structured heuristics and clear caveats.
The problem sits between sales and engineering, and most teams handle it ad hoc. The evidence shows the pain is real but only discussed in a single thread, suggesting founders lack a shared vocabulary and tooling for this decision.
Every quote on this page was matched against its original post on Hacker News, GitHub, DEV.to or Product Hunt, and each claim links to that thread. Unverifiable items are discarded before publication.
See all 20 evidence-backed needs this week β updated daily, every trend traced to original posts and exact quotes.
Subscribe $19.99/mo βNot sure what to build first? See the ten worth a look →