Less Software, Please: 7 Gaps Where People Are Asking for Fewer Features

Most product roadmaps only go one direction: more. More integrations, more dashboards, more AI. But a specific kind of complaint keeps showing up in the demand we track, and it points the other way. People find a category with twenty shipping products, try a few, and post the same thing: I don't need most of this.

Here are seven gaps where the ask is explicitly for less. Counts are distinct people asking; "rivals detected" is what our competitor scan found shipping, as of September 10, 2026.

The seven

What "less" means in each case

Finance: fewer features, lower price. Twelve people asking for the same thing in a market with nine detected rivals. The quote is the whole brief: they'd pay less for a tool that does less. Subscription budgeting apps are priced on breadth. The gap is depth on one job.

Habit tracking: ownership, not features. Twenty-six rivals detected, and the loudest post is from someone who built their own rather than "rent access to my own checkboxes." That's a pricing model complaint disguised as a feature request. Local-first, one-time purchase, export anytime. Nobody dominant does all three.

Remote desktop: one task, no platform. Twenty-eight rivals is the most crowded row in this list. The ask is an accountant reaching Sage 50 and a folder of spreadsheets. Enterprise remote-access suites treat that as an edge case of their edge cases.

Music player: looks over lists. Six people said some version of "I just want a good looking player." Twenty-one rivals compete on library features. The unmet spec is a UI, which is why it stays unmet: it's hard to put on a comparison chart.

Home Assistant integrations: offline by design. The posts here reject the app and the cloud outright. Nineteen rivals ship with both. "Less" here means no account, no phone home, and the market keeps adding both.

WordPress security: fewer alerts. Someone managing hundreds of sites getting dozens of reports a day. The nine detected tools compete on coverage; the complaint is signal-to-noise. A plugin that fires less often would win this person immediately.

Note organizing: one click. The exception that proves the rule: this ask wants everything pulled in, but through one action. Fourteen rivals each cover a slice and require setup for every slice. Less effort, not less scope.

The pattern

Every row is a crowded market by count. None is solved by the complaint's own definition. That's the same shape we found across the whole dataset in Crowded Does Not Mean Solved: incumbents converge on the feature-maximal version of a category and leave the minimal version empty.

If you're weighing one of these, the validation method we use applies: the ask is already counted. What's left is checking whether "less" is something people will pay for, and in at least one row above, someone already answered by building it themselves.

Honest limits

Our scan misses tools with no web presence, so "rivals detected" is a floor, not a census. Counts are from public posts in English-language communities. Six-to-twelve people is a real signal in our data (most asks never pass three), but it's a small one; treat this as a shortlist to validate, not a verdict.

All numbers from GapMine's live dataset, same pool the site renders. Each row links to the public source posts.