OpportunityMarket home
Other opportunities·tracked since 18 Sept 2026·evidence from 17 Sept 2026·scored 30m ago

Feature request addressing user problems

There is a recurring issue regarding the identification and articulation of problems related to feature requests. This indicates a need for clearer communication and understanding of the underlying challenges that users face.

18 people in 23 posts across 1 source · demand moderate, pain moderate, competition moderate

Pain pointEmerging🔥 HotEvidence: medium
Index score
49.0
ahead of 100% of the rest of this market
100.0%signals / 7d
Demand
45.8moderate
Momentum
87.5high
Pain
52.8moderate
Competition
59.5moderate
lower is better
Monetization
19.0low
Market size
43.4moderate
Evidence
58.9moderate

The pain

shares of 23 quoted posts

What goes wrong, and for whom

Who
18 different people
What goes wrong
Not classified into a failure type — read the posts below.
How bad
100% of posts are complaints · pain score moderate (53/100)
Since
17 Sept 2026 → 23 Sept 2026

Is this a startup idea?

Not directly. These are complaints about a product or service people already use — the fix belongs first to that provider.

Products named
fleetbase
Looking for something else
0% want an alternative · 0% ask the provider for a feature
What the numbers say
Almost nobody is looking for a different product — people want this provider to fix it, not a new option.
Build a prototype from thisA landing page written from these 23 complaints by 16 people.50 credits · sign in →
1

The pain — what people say

Their asks, who is writing, and the posts themselves

People are asking for

In their own words — asks pulled from the evidence, most-repeated first

  1. Feature request.

What people were doing

Every post behind this page, by what its author was doing — and when each one was written

23posts
  • Complaint23100%
17 Sept 202623 posts23 Sept 2026

Sources

23 signals · 1 sources

GitHub23
Only public content is collected, author names are stored as one-way hashes, and every excerpt links back to its original post.

Evidence

Raw public posts behind this opportunity — click through to the original

  • GitHubanmol098/waka-readme-stats·12h ago·Complaintsource ↗

    FEAT Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise…

    Frustrated
  • GitHubmicrosoftgraph/microsoft-graph-explorer-v4·2d ago·Complaintsource ↗

    Rapid g Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise…

    Frustrated
  • GitHubmicrosoft/WSL·4d ago·Complaintsource ↗

    contribution and power AI Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A…

    Frustrated
  • GitHubscrulleb/fleetbase·1d ago·Complaintsource ↗

    Kawsar Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise…

    Frustrated
  • GitHubscrulleb/fleetbase·1d ago·Complaintsource ↗

    +8801406555497 Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and…

    Frustrated
18 more evidence rowsSign in — it's free
2

Market and score

Products already there, how the score moved, and what it is made of

Existing solutions

Products people named in the evidence · high competition does not automatically mean a bad market

Opportunity history

Every score change is stored as a snapshot — click a sub-score to overlay it

Why did it move?

Score 48.9 → 49.0 · 23 Sept 2026, 11:00 → 12:15 UTC

Score attributionSign in — it's free
How the score was measured
39 measured values behind the seven sub-scores · each shows the value, then the points it earned out of 100
Show ↓
Market size
Distinct people affected18 39
Distinct communities16 69
Distinct sources1 35
Regions / languages1 28
Adjacent categories1 32
Competition
Existing products9 64
New entrants (90d)1 26
Funded players1 28
Feature coverage100 100
Market maturity11.3 89
Incumbent activity65.3 65
Momentum
Period-over-period growth100 95
Latest period growth100 96
Sustained trend12.2 64
Acceleration45.4 91
Monetization
Stated willingness to pay21.3 21
Existing paid products4 45
Pricing complaints0 0
Business context0 0
Pain
Complaint intensity68.1 68
Complaint frequency100 100
Negative sentiment-83.3 83
Willingness to switch0 0
Urgency7.8 8
Willingness to pay21.3 21
Repeat complaints25 25
Evidence
Evidence volume23 39
Source diversity1 35
Extraction confidence61.8 62
Source credibility78 78
Duplicate rate32.4 68
Freshness0.4 98
Cluster cohesion91.7 92
Demand
Mention volume23 43
Explicit requests23 60
Distinct people16 43
Alternative searches0 0
Questions asked0 0
Feature requests23 57

Questions about this idea

Is Feature request addressing user problems a startup idea?
Not directly. These are complaints about a product or service people already use, and the fix belongs first to that provider. The page shows what is frustrating users and how badly — not an open market to start a company in.
How many people have this problem?
18 different people described it independently, in 23 mentions, the earliest from 17 Sept 2026 and the most recent from 23 Sept 2026. The quotes, with dates and links to the originals, are in the Evidence section.
Is this problem getting worse?
Current status: emerging — newly appearing in the evidence. Momentum is 88/100, measured as how often it is mentioned recently compared with before.

Adjacent opportunities

Nearest neighbours by embedding similarity

Discussion

Written by readers. Not part of the evidence above and not counted in any score.

Sign in to join the discussion.

No comments yet

If you have run into this problem, what did you try?