MyNeedEcho
Home β€Ί Your biggest SaaS customer wants a feature. Your engineers t
Updated 2026-11-04

Your biggest SaaS customer wants a feature. Your engineers t

The opportunity: Founders and product teams lack a structured way to evaluate custom feature requests from major customers, especially when engineering warns of long-term maintenance costs. The core pain is that a two-week build can create years of testing, support, and compatibility work, yet teams must decide under pressure without a repeatable process.

This is where product decisions get uncomfortable. A customer representing a significant portion of your revenue wants

πŸ”₯ Heat 103.55 1 evidence posts 3 pain points 2026-11-04
Mention 1.5 Β· 1 sources

Product brief: how to build it

Who it is for

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.

What it does

Start here: the MVP

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.

How it beats what already exists

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.

Technical path

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.

How it makes money

One-time purchase for the MVP, with an optional subscription for teams that need ongoing request triage and decision history.

Biggest risk

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.

Evidence (1 posts)

Pain points (3)

β€œA feature that takes two weeks to build might introduce years of testing, support, and compatibility work.”
β†’ A tool that estimates the long-term maintenance and support cost of a requested feature before committing to build it.
β€œIs the customer asking for a specific feature, or are they trying to solve a problem we could address differently?”
β†’ A discovery tool that helps teams separate a customer's underlying problem from their proposed feature solution.
β€œAnd the founder is stuck between keeping the customer happy and protecting the roadmap.”
β†’ A decision-support dashboard that weighs revenue at risk against roadmap impact to resolve sales-vs-engineering conflicts.

Sub-directions

Customer-request triage and prioritization frameworksFeature maintenance cost and technical debt estimationSales-engineering alignment on roadmap decisions

Related needs

FAQ β€” Your biggest SaaS customer wants a feature. Your engineers t

Who already builds this?

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.

What is the smallest shippable version?

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.

What is the hardest part to build?

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.

Why is it still unsolved?

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.

How is this data collected and verified?

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 →