What 22,529 user complaints reveal about software marketplaces
A data-backed look at recurring software pain across 79 marketplaces — and what the complaints can and cannot tell you about what to build.
Most product advice starts with an idea and then looks for evidence. We tried the reverse: start with a large body of public user complaints, group the recurring problems, and only then ask which opportunities deserve attention.
The result is a snapshot of 22,529 source-linked quotes behind 7,368 pain cards across 79 software marketplaces. Of those cards, 2,919 passed the publication checks used by VettedGaps.
This is not a list of 22,529 ideas. It is a map of repeated friction — and a way to separate one person’s bad afternoon from a pattern that may be worth investigating.
The largest recurring categories
Four categories stand out in the current published corpus:
| Category | Pain cards |
|---|---|
| Performance & reliability | 568 |
| Billing & pricing | 526 |
| Integrations & API | 452 |
| UI & UX | 350 |
These numbers are a snapshot taken on August 21, 2026. The corpus grows continuously, so they should be read as measured counts, not permanent market shares.
The ordering is useful, but the category names alone are not enough to choose a product. “Integrations & API” can describe dozens of unrelated jobs, buyer types, and platform constraints. The useful unit is the pain card underneath: a specific problem supported by independent voices, dates, and links back to the source.
Repetition changes the meaning of a complaint
A single angry review proves that a person had a problem. It does not prove that a market exists.
VettedGaps only treats a pain as recurring after it has evidence from at least three distinct authors. Similar complaints are clustered into one card instead of being counted as separate opportunities. That distinction matters: fifty posts describing the same broken workflow should strengthen one finding, not create fifty product ideas.
This approach also makes weak evidence visible. A cluster may be broad but old. It may be recent but confined to one marketplace. It may have dozens of complaints and no sign that anyone pays to solve it. Those are different situations and should lead to different decisions.
Marketplace-specific pain is more actionable
The same complaint changes when it is attached to a distribution channel.
“Reporting is painful” is vague. “Shopify merchants repeatedly cannot reconcile a particular report with their fulfillment workflow” points toward a user, an ecosystem, existing competitors, and a place where a solution could be distributed.
The current corpus includes several marketplace-level concentrations that are large enough for deeper analysis, including Shopify, Autodesk, Grafana, SketchUp, OpenAI, Cursor, and Asana. The count is only the starting point. A useful niche analysis still needs to inspect the underlying functions, evidence dates, existing solutions, and search demand.
What complaint data does not prove
Complaint volume is evidence of friction, not evidence of a business by itself.
There are at least four questions the corpus cannot answer alone:
- Will users pay? Complaints can coexist with zero purchasing intent.
- Is the problem still alive? Old evidence may describe something the platform has already fixed.
- Can a third party solve it? Some pain is real but locked behind platform policy or missing APIs.
- Is the market already served? A recurring complaint may point to a crowded category rather than an open gap.
That is why VettedGaps keeps separate signals separate. User complaints, paid work, search interest, and competitor coverage each answer a different question. Combining them is useful; pretending one can substitute for all the others is not.
A better first question than “what should I build?”
Instead of asking for an idea immediately, begin with three narrower questions:
- Which problems repeat across independent users?
- Which of those problems are recent and tied to a reachable marketplace?
- Where do payment, search, or competitor signals support — or contradict — the complaints?
This does not remove uncertainty. It makes the uncertainty inspectable.
The strongest opportunity is rarely the category with the largest headline number. It is the specific recurring job where the evidence is fresh, the affected user is identifiable, distribution is possible, and the existing solutions leave a visible gap.
See how VettedGaps turns source evidence into pain cards and product research.