DEV Community: DDMarketer

The angriest corners of SaaS, ranked by emotional intensity (1,012 complaints, scored 1 to 5)

DDMarketer — Sat, 05 Sep 2026 23:24:34 +0000

Yesterday I published the broad overview of my complaint corpus: which products get complained about most and where those complaints live. Today I want to zoom in on the single metric I find most commercially interesting: not how often people complain, but how angry they are when they do.

Quick context: I run a pipeline that mines public software complaints (GitHub, Reddit, Stack Overflow, Hacker News, Trustpilot, app stores, X, forums), clusters them into validated gaps, and scores each one. One of those scores is emotional intensity, a 1 to 5 read of how charged the source complaint is, from mild annoyance to business-threatening. Current corpus: 988 validated gaps from 1,012 complaints, recomputed hourly. Numbers below are quoted from the live stats pages as of September 6, 2026.

Which categories have the angriest users

Average emotional intensity per category (categories with fewer than 10 gaps excluded):

Category	Gaps	Avg intensity (1-5)
Finance / Accounting	69	4.1
Real Estate / Local Operations	52	4.1
Security / Compliance	50	4.0
E-commerce	61	3.8
No-Code / Automation	78	3.7
Marketing Operations	47	3.7
Dev Tools / SaaS Infrastructure	387	3.6
Creator Operations	43	3.6
Data / Analytics	161	3.2
HR / Recruiting	29	3.1

Full table and method: Most emotionally intense complaint categories

The pattern is not subtle. The angriest categories are the ones where software touches money, property, or legal exposure. Nobody writes a 4/5-intensity complaint because a dashboard loaded slowly. They write it because their payout is frozen, a client is threatening to sue, or an audit is in two weeks and the export is broken.

The calmest end is instructive too. HR/recruiting (3.1) and data/analytics (3.2) complaints read as frustration and annoyance, not emergencies. Real problems, but nobody's business is on fire.

For calibration, the corpus-wide distribution: 1 gap at 1/5, 48 at 2/5, 370 at 3/5, 468 at 4/5, 101 at 5/5. So 58% of all validated gaps come from complaints scored 4 or higher. The baseline is already angry; finance and real estate sit above even that.

The Stripe signal

The product-level table has one number I keep coming back to. Among the 10 most complained-about products, the average emotion scores look like this at the top:

Product	Complaints	Avg emotion (1-5)
Stripe	20	4.5
Zapier	15	4.2
Airbnb	38	4.1
QuickBooks	24	4.1
Shopify	36	3.9
Claude	18	3.9

Stripe is only 6th by complaint volume but is the angriest product in the top 10 at 4.5 out of 5. MySQL tops the volume ranking at 51 complaints with a 3.4 average. People complain about MySQL constantly and calmly. They complain about Stripe less often and furiously.

That makes sense when you read the underlying complaints: they cluster around account freezes, held payouts, and closures with no recourse. A broken query costs you an afternoon. A frozen Stripe account costs you the business's cash flow, this week, while support sends templated replies.

Why anger is the metric I watch

Here is my practitioner read, and it is an interpretation, not something the classifier outputs: anger is churn energy. A mildly annoyed user files the problem under "things I tolerate." A furious user is already mentally shopping for a replacement. The 4/5 and 5/5 complaints in this corpus routinely contain phrases like "looking for alternatives," "migrating away," "never again." That is willingness to switch, stated in the user's own words, before any vendor talks to them.

The corpus backs the commercial side of this. Overall, 93% of validated gaps show willingness-to-pay signals in the source complaint. And the willingness-to-pay-by-category table overlaps with the anger table in a way that should get a founder's attention:

Category	Avg intensity	Willing to pay
Real Estate / Local Operations	4.1	96%
Security / Compliance	4.0	96%
Finance / Accounting	4.1	91%
HR / Recruiting	3.1	97%

Source: Willingness to pay by category

Angry categories are pay-ready categories. And the one calm category, HR at 3.1, still shows 97% willingness to pay, the highest in the corpus. Which leads to the honest caveat section.

Caveats, because this data has edges

Anger and money are not the same axis. HR complaints are calm but almost universally pay-ready. Emotional intensity tells you how urgently someone wants out of their current situation, not how much budget exists. Use both scores together.
Selection bias is real. People post publicly when they are angriest or when they want leverage on the vendor. The 58% share of 4+ scores partly reflects who bothers to write a public complaint at all. Silent mild annoyance is underrepresented by construction.
Platform mix skews tone. GitHub issues are written for maintainers and read calmer; Trustpilot and Reddit rants run hotter. Category averages inherit the platform mix of that category.
The intensity score is a classifier's 1 to 5 judgment, consistent but not infallible. Sarcasm and non-native-English phrasing are its known weak spots.
Corpus is 988 gaps and recomputes hourly, so quoted numbers drift. Cite with an access date.

What I would build from the angry end

Three live gap dossiers from the high-intensity categories, each with the source complaints, scores, and evidence attached:

Stripe account freezes: dispute and payout recovery - the exact complaint cluster behind that 4.5/5 Stripe signal. Frozen funds, ignored support tickets, real cash-flow damage.
Airbnb host defense against unverified guest claims - real estate/local operations is tied for the angriest category at 4.1, and host-versus-platform disputes are a big reason why.
TurboTax for SOC 2 that skips the $50k consultant - security/compliance at 4.0 average intensity, where the anger is really fear: audits, deadlines, and consultants priced out of reach for small teams.

If I were picking a market on this data alone, I would look where intensity and willingness to pay are both high and the incumbents are the ones generating the complaints. That intersection is the whole thesis of the project.

Method note: every gap links back to the underlying public complaints, and the scoring pipeline is described on the stats pages. The data is free to quote with attribution.

I analyzed 1,012 real SaaS complaints across 8 platforms. Here is what people actually complain about

DDMarketer — Sat, 05 Sep 2026 20:35:31 +0000

I run a small data pipeline that reads public software complaints: GitHub issues, Reddit threads, Stack Overflow questions, Hacker News comments, Trustpilot reviews, app store reviews, public forums, and posts on X. It clusters them into validated gaps and scores each one for commercial intent. The corpus just passed 1,000 underlying complaints, so I published the aggregate stats and spent an evening staring at them. Some of what came out surprised me.

Current state: 988 validated gaps distilled from 1,012 underlying complaints, recomputed hourly. Everything below is quoted from the live stats pages as of September 5, 2026.

The most complained-about products

Ranked by how many validated complaints name the product:

#	Product	Named complaints	Avg emotion (1-5)
1	MySQL	51	3.4
2	Airbnb	38	4.1
3	Shopify	36	3.9
4	Elasticsearch	34	3.5
5	QuickBooks	24	4.1
6	Stripe	20	4.5
7	Excel	18	3.4
8	Claude	18	3.9
9	GitHub Actions	16	3.6
10	Zapier	15	4.2

Full table with method notes: Most complained-about SaaS tools

Two things stand out to me. First, MySQL at 51 named complaints is a volume story: a huge user base repeatedly hitting the same sharp edges, at moderate emotion (3.4/5). Second, anger is decoupled from volume. Stripe is only sixth by count, but its complaints average 4.5/5 in emotional intensity, the highest in the top ten. People are not mildly annoyed about Stripe; they are describing frozen payouts and account shutdowns. QuickBooks (4.1) and Zapier (4.2) follow the same pattern: money-adjacent tools produce money-adjacent rage.

Obvious caveat, printed on the page too: these counts reflect where complaints were collected, not market share, and products with fewer than 5 mentions are not ranked.

Where complaints actually live

Platform	Gaps	Share
GitHub	302	31%
Reddit	290	29%
Stack Overflow	208	21%
Hacker News	76	8%
Trustpilot	59	6%
X (Twitter)	28	3%
App Store	14	1%
Public forums	11	1%

Full breakdown: Where SaaS complaints live

If your idea validation process is "search Reddit", you are reading 29% of the complaints and missing the other 71%. And the split is not uniform across markets. E-commerce complaints are 82% Reddit. Data and analytics complaints are 70% Stack Overflow. Dev tools complaints are 58% GitHub. Real estate complaints are 94% Reddit. The platform you read determines the market you think exists.

This is also a quiet argument against single-source research tooling in general: any pipeline built on one platform's API inherits that platform's coverage bias and its policy risk.

Anger and willingness to pay

Every complaint is scored 1 to 5 for emotional charge. The most emotionally intense categories (categories with fewer than 10 gaps excluded):

Finance / Accounting: 4.1/5
Real Estate / Local Operations: 4.1/5
Security / Compliance: 4.0/5
E-commerce: 3.8/5
Dev Tools / SaaS Infrastructure: 3.6/5 (the biggest category at 387 gaps is also one of the calmest)

Corpus-wide, 58% of complaints score 4 or 5 out of 5. The full distribution is 1/5: 1 complaint, 2/5: 48, 3/5: 370, 4/5: 468, 5/5: 101. Details: Emotional intensity by category

Willingness to pay is the more interesting number. A complaint gets flagged when the person signals they would pay for a fix. Across the whole corpus, that flag is on for 93%. By category:

HR / Recruiting: 97%
Real Estate / Local Operations: 96%
Security / Compliance: 96%
Marketing Operations: 96%
No-Code / Automation: 90% (the lowest ranked)

Details: Willingness to pay by category

Honest note on that 93%: there is a selection effect. The corpus is validated gaps, not random internet grumbling, so a high overall rate is partly by construction. What I find informative is the spread and which categories sit on top: recruiting, real estate, and security complaints tend to be people describing problems that cost them money this week.

How the numbers get made

Short version, because the method matters more than the charts. The pipeline reads public posts across the 8 platforms, an LLM classifier extracts structured complaints, dedup collapses repeats across distinct authors so one viral thread does not look like a market, and a second pass clusters complaints into gaps. Each gap gets a commercial intent score (0 to 100), an emotional intensity read (1 to 5), and the willingness-to-pay flag. Product mentions are matched on word boundaries. Categories with fewer than 10 gaps are excluded from rankings because a percentage over two or three rows is noise, not signal. Every stat page recomputes hourly from the live corpus.

Two biases I cannot remove. One: developers complain in public, in writing, on platforms with APIs, so dev tools are over-represented (387 of 988 gaps). Two: collection coverage is not market share, anywhere in this data. I would rather publish with those caveats on the page than pretend the corpus is a random sample of all software pain.

Full writeup: methodology

What I would build from this

Three gaps from the corpus that line up with where the stats point:

1. Airbnb host protection from fraudulent cleanliness claims (intent 80/100). Airbnb is the number 2 most complained-about product at 4.1/5 emotion, and real estate is the most emotionally intense category at 96% willingness to pay. The gap: hosts getting hit with fake cleanliness claims from guests fishing for refunds, with no good evidence trail on their side. Read the full gap dossier

2. SMB IT disaster recovery for non-technical management (intent 80/100). Security and compliance sits at 4.0/5 emotion with 96% willingness to pay, and these complaints come from office managers, not sysadmins: the person who got handed "the IT" and just realized there are no tested backups. Read the full gap dossier

3. WooCommerce plugin bloat killing checkout conversion (intent 80/100). E-commerce complaints are 82% Reddit-sourced and 92% willing to pay, and this one is the classic: 40 plugins deep, checkout takes six seconds, the owner knows it is costing sales but cannot tell which plugin does it. Read the full gap dossier

Each dossier includes the underlying complaints, an MVP scope, suggested pricing, competitors, and risks.

The caveat that matters

Complaint volume is not demand. Someone raging about QuickBooks does not mean they will pay you to fix it. Data like this narrows where to look; it does not replace talking to people. If you want to query the corpus yourself, the search tier is free, and the stats pages above are free to cite with attribution (they recompute hourly, so cite the access date).

10 software problems people are actively complaining about right now (with the scores)

DDMarketer — Sun, 30 Aug 2026 18:14:06 +0000

I run a pipeline that reads public complaints — Reddit, Hacker News, GitHub, Stack Exchange, Trustpilot, app store reviews, product forums, X — and scores each recurring one for commercial intent. Two LLM passes, deduplication across distinct authors so one loud thread does not look like a market, then an editorial gate. 942 have cleared it.

Here are the ten highest-scoring right now, with the raw numbers. Commercial intent is a 0-100 estimate of willingness to pay; confidence is how sure the scoring is.

1. Automate 40% of property manager calls, cut after-hours costs

intent 100/100 · confidence 90/100 · Real Estate / Local Operations · surfaced from reddit

Read the problem and the evidence

2. Stop Stripe Connect fraud before platform shutdown

intent 100/100 · confidence 90/100 · Security / Compliance · surfaced from reddit

Read the problem and the evidence

3. AWS Marketplace usage fraud detection and remediation

intent 100/100 · confidence 80/100 · Security / Compliance · surfaced from reddit

Read the problem and the evidence

4. 60-second mobile-first e-signatures, no account needed

intent 90/100 · confidence 95/100 · Legal / Practice · surfaced from twitter

Read the problem and the evidence

5. Podcast download validation that filters bots reliably

intent 80/100 · confidence 80/100 · Creator Operations · surfaced from reddit

Read the problem and the evidence

6. 24/7 M365 phishing response for BYOD education

intent 80/100 · confidence 80/100 · Security / Compliance · surfaced from reddit

Read the problem and the evidence

7. Recover failed Stripe payments for Laravel apps

intent 80/100 · confidence 80/100 · Finance / Accounting · surfaced from reddit

Read the problem and the evidence

8. Stop metadata drift across Glue and other data catalogs

intent 80/100 · confidence 80/100 · Data / Analytics · surfaced from reddit

Read the problem and the evidence

9. Secure occupied home showings for property managers

intent 80/100 · confidence 90/100 · Real Estate / Local Operations · surfaced from reddit

Read the problem and the evidence

10. Stripe dunning that counts all retry attempts

intent 80/100 · confidence 90/100 · Finance / Accounting · surfaced from reddit

Read the problem and the evidence

What I notice looking at this list

Security and compliance is over-represented at the top. Three of the ten are fraud or abuse response. That was not true of the corpus as a whole — across all 942, security is 7th by volume. It is a this-week artifact, and I mention it because it is exactly the kind of pattern that looks like a trend if you only read the top of a list.

The good ones are boring. Automating after-hours property manager calls scores 100. Nobody is going to tweet about building that.

My corpus has a bias I cannot fully remove. Dev tools are 44% of everything I hold, and my biggest single source is GitHub (563 items) ahead of Reddit (299). Not because developer problems are worth more — because developers complain in public, in writing, on platforms with APIs. Anyone mining public text inherits this.

Querying this from your editor

There is a free MCP server, so your coding agent can search the corpus without leaving the editor:

claude mcp add --transport http ddmarketer https://www.ddmarketer.com/api/mcp

Three tools need no key and no account: search_gaps, get_top_gaps, and validate_idea. That last one scores an idea you already have, and it returns a weak verdict when it only finds loosely related complaints rather than pretending a near-miss is validation.

A dependency-free reference client is on GitHub if you want to see exactly what goes over the wire — about 50 lines of plain fetch, no SDK.

The caveat that matters

Complaint volume is not demand. Somebody being annoyed on Reddit does not mean they will pay to fix it. This narrows where to look. You still have to talk to people before you build.

My highest-value data category was starved because of how I ranked ingest targets

DDMarketer — Sat, 29 Aug 2026 16:03:26 +0000

I run a pipeline that mines public complaints and scores them for commercial intent. Last week I pulled approval rates by category and found something that had been quietly costing me the best data I had.

Here is the table that started it:

category                approved/total   rate   mean intent
HR / Recruiting              28/  38      74%      80.1
Data / Analytics            177/ 242      73%      73.9
Dev Tools / SaaS Infra      560/1001      56%      71.9
Finance / Accounting         86/ 206      42%      75.6

HR and recruiting has the best approval rate and the highest mean commercial intent of any category with real volume. It also has the smallest candidate pool by an order of magnitude: 38 against dev tools' 1,001.

My first assumption was that the classifier or the editorial gate was rejecting HR items. It was not. 74% of them get approved, the highest rate in the corpus. They were simply never being fetched.

The actual cause

The ingest walks a list of targets per source, and a per-source time budget cuts the tail. So target ordering decides what the corpus is made of.

The ordering was: protect the proven high-priority targets, then rotate everything else by staleness. That is a reasonable design — it stops unproven targets displacing measured ones at random, which an earlier jitter-based approach did (the newly-reached targets measured 65% in scope against 80% for the established ones).

But there were 9 protected targets against roughly 13 reachable slots per run. So about 4 rotating slots, against 105 never-fetched targets on that source. r/humanresources and r/recruiting were sitting in a queue roughly 26 weeks deep.

11 of the 13 HR targets on active sources had never been fetched once.

Why the fix is priority 8 and not 9

The obvious move is promoting them into the protected band. That is wrong: the protected band was already 9 of ~13 slots, so adding three more would consume the rotation entirely and recreate the same starvation for everything else.

The rotating pool sorts by staleness ascending, then priority descending. Every never-fetched target ties at staleness 0 — so priority is the tiebreak among them. Setting the HR targets to 8, one below the protected threshold, moves them to the front of the unfetched queue without displacing the protected head or the rotating tail.

UPDATE source_targets t
SET priority = 8
FROM sources s
WHERE t.source_id = s.id
  AND s.status = 'active'
  AND t.is_active = true
  AND t.last_fetched_at IS NULL
  AND t.priority < 8
  AND ( ... explicit target list ... )

Guarded on last_fetched_at IS NULL and priority < 8 so it is idempotent, and scoped to an explicit list of target values so it cannot touch anything else. 11 rows.

The part that generalises

If your pipeline has a budget that cuts a tail, the ordering of that queue silently decides what your data is about. Mine had produced a corpus that was 44% developer tools, and I had been reading that as a finding about where the opportunities are. It was not a finding. It was an artifact of which targets the budget happened to reach.

Two things worth checking in your own pipeline:

What fraction of your configured sources have never run? Mine was 79%. Some of that was deliberate (a source disabled because its content was a decade old), but most of it was queue depth.
Is your highest-yield segment also your smallest? That combination usually means starvation, not a real ceiling.

The corpus is at ddmarketer.com if you want to see what came out of it, and there is a free MCP server so your agent can query it directly — claude mcp add --transport http ddmarketer https://www.ddmarketer.com/api/mcp. But the pipeline lesson is the transferable part.

I scored 942 user complaints for commercial intent. The data embarrassed me.

DDMarketer — Sat, 29 Aug 2026 15:35:00 +0000

I have abandoned enough side projects to accept that my ideas were the problem. So instead of having ideas, I spent a few months reading other people's complaints: Reddit, Hacker News, GitHub, Stack Exchange, Trustpilot, app store reviews, product forums, X.

The pipeline is six stages.

Source from public complaints only. No surveys, no private data.
Prefilter the obvious noise with keywords and heuristics, before spending money on inference.
Deduplicate. This mattered far more than I expected. One thread with 200 upvotes is one person's problem amplified 200 times, not 200 people with the problem. Frequency across distinct authors and sources is the actual signal.
Two LLM passes. The first confirms it is a real, software-shaped problem. The second extracts the opportunity, the persona, and what people currently do instead.
Score for commercial intent, confidence, and willingness to pay.
Editorial gate. Nothing publishes automatically. I read every one.

942 have cleared that.

Three things in the data I did not expect

My corpus is mostly about developers, and that is a bias, not a finding.

Dev Tools and SaaS Infrastructure is 44% of everything I have. My single largest source is GitHub with 563 items, ahead of Reddit at 299. That is not because developer problems are the most valuable. It is because developers complain in public, in writing, on platforms with APIs.

Anyone mining public text has this skew. I had it for weeks before I went looking for it.

The highest-intent category is the one I have almost nothing in.

HR and recruiting averages 80.1/100 commercial intent, the highest of any category with meaningful volume. I have 28 items in it. Dev tools averages 71.9 across 560.

When I dug into why, the answer was worse than "not enough sources". The HR targets existed and were enabled. 11 of the 13 on active sources had never been fetched once, because the ingest budget kept getting consumed by the same high-priority targets every run. I had been mining where it was easy, and the ranking made that permanent.

The good ones are boring.

Top of this week:

[intent 100 / confidence 90]  Automate 40% of property manager after-hours calls
[intent 100 / confidence 90]  Stop Stripe Connect fraud before platform shutdown
[intent  90 / confidence 95]  60-second mobile-first e-signatures, no account

Nobody is going to tweet about building after-hours call automation for property managers. The ideas that sound exciting score badly, over and over.

Querying it from the editor

Your agent can already build almost anything, so the bottleneck moved to deciding what to build. I put the corpus behind an MCP server so I can ask while I am already in the editor:

claude mcp add --transport http ddmarketer https://www.ddmarketer.com/api/mcp

Or in any MCP client config:

{
  "mcpServers": {
    "ddmarketer": {
      "type": "http",
      "url": "https://www.ddmarketer.com/api/mcp"
    }
  }
}

Three tools need no key and no account: search_gaps, get_top_gaps, and validate_idea. That last one scores an idea you already have, and it will tell you when there is nothing there — it returns a weak verdict when it only finds loosely related complaints, rather than pretending a near-miss is validation.

What this does not do

Complaint volume is not demand. Somebody being annoyed on Reddit does not mean they will pay to fix it. The corpus narrows where to look. You still have to talk to people.

The scores come from a language model. They are consistent enough to rank against each other, but I would not read 80 vs 75 as meaningful.

And the editorial gate is one person, which is a quality gate, not peer review.

The question I cannot answer

How do you separate "people complain about this" from "people would pay to fix this"? I score willingness to pay as its own dimension, but I have no ground truth to check it against, and one paying customer is not a validation set.

If you have solved this, I would genuinely like to hear how.