Updated

For SaaS and B2B teams

Customer research for SaaS, from the threads where customers decide to leave.

When customers start looking for alternatives, they say why in public: what broke, what they need from the replacement, and what keeps them stuck. Threadpull pulls the whole thread so you can read your churn reasons before your customers act on them.

How do you find out why customers leave a SaaS product?

Read the threads where people ask for alternatives to it, and count the reasons they give and what stops them switching. In a 437-comment Ask HN thread about alternatives to GitHub, outages started the search, about 21 comments asked whether CI and integrations would carry over, and about 23 said network effects keep teams in place. In a 46-comment r/SaaS thread on whether AI SaaS is too crowded, about 10 comments said it is and about 10 said a specific problem matters more. Threadpull pulls every comment so you can count them.

Six research jobs for a SaaS team

Find your churn reasons

Pull "alternatives to…" threads about you or a rival and count the reasons people give.

Ask HN · r/SaaS

List what a switch must carry over

The integrations and workflows people refuse to rebuild are your migration checklist.

Ask HN · r/sysadmin

Win a competitor's unhappy users

Read the threads where they complain, and answer their exact objections on your page.

r/SaaS · product subreddits

Write comparison pages

Use the comparisons buyers make themselves, in their words, not your feature grid.

Ask HN · r/startups

Test pricing language

See how people describe value, "too expensive" and "worth it" for tools like yours.

r/SaaS · r/Entrepreneur

Prepare sales objections

Turn the reasons people stay put into answers your sales team can give.

Ask HN · r/sales

What the Hacker News thread showed

An Ask HN thread looking for alternatives to GitHub after months of outages, read comment by comment.

Ask HN · pulled 1 Nov 2026

Ask HN: Alternatives to GitHub

news.ycombinator.com/item?id=49331033 ↗
Comments437
People291
Reply depth10

For your retention: outages get customers looking, but integrations and existing workflows decide whether they leave. Your risk is highest once a rival can move those across without a rebuild.

Self-hosting to regain control

about 40 comments
"The key thing that drove our decision to self host gitlab was that WE were the ones in control of when things happened."cortesoft
"To all of those proposing self-hosted GitLab: we did it for 6+ years in my company, and it's not always a smooth sailing."plqbfbv

Network effects keep teams stuck

about 23 comments
"I’ve personally seen a project leave it and then contributions dropped significantly."als0
"I think some cross platforms stars and search would be good."hum3hum3

CI and Actions must carry over

about 21 comments
"If an org is heavily invested in GitHub Actions and GitHub App integrations, is self-hosting GitHub enterprise the only practical option?"CodeAndCuffs

Outages are the trigger to leave

about 19 comments
"Also literally just this morning we’ve had to delay a release due to Github being down."sandcat_
"don’t switch reactively, but use the outages as a trigger to evaluate alternatives and make sure a GitHub outage doesn’t stop critical work."dxbhack

What the r/SaaS thread showed

An r/SaaS thread asking whether it is too late to build an AI SaaS, read comment by comment.

r/SaaS · pulled 1 Nov 2026

Is creating an AI saas too late/oversatured?

www.reddit.com/r/SaaS/comments/1xkm24c/is_creating_an_ai_saas_too_lateoversatured/ ↗
Comments46
People31
Reply depth4

For your positioning: a crowded category worries builders more than buyers. What decides it is one specific problem solved for people you can actually reach.

A specific problem beats a crowded market

about 10 comments
"solves a real, specific problem and you can actually get it in front of people who need it, saturation doesn't matter."theteenyreassurance
"I think we sometimes confuse market saturation with market maturity."uberkitnet

Yes, it is saturated

about 10 comments
"Consider that product hunt gets 300 to 1100 new saas per day"NPSALLEN
"it’s more saturated than it’s ever been."anabatic-bat

Distribution is the hard part now

about 8 comments
"The real advantage is now shifting from the ability to build something to the ability to make people care about what you've built."Academic-Tadpole-964
"An app is easy to built but not to monetize."Remy_Builds

Too many ideas, not too many rivals

about 4 comments
"A dozen prototypes and zero launches, saturation was never the thing in your way."Some-Cantaloupe7497
"Pick one idea and go."That-Measurement-650

The threads in numbers

"Ask HN: Alternatives to GitHub" had 437 comments from 291 people when we pulled it on 1 Nov 2026. 313 of them (72%) were replies to other comments, nested up to 10 levels deep, and the median comment was 29 words long. The theme raised most, self-hosting to regain control, came up in about 40 comments (9% of the thread).

"Is creating an AI saas too late/oversatured?" had 46 comments from 31 people when we pulled it on 1 Nov 2026. 20 of them (43%) were replies to other comments, nested up to 4 levels deep, and the median comment was 25 words long. The theme raised most, a specific problem beats a crowded market, came up in about 10 comments (22% of the thread).

How we did this research

  • Pulled with Threadpull on 1 Nov 2026: every comment still live, at every reply level, from news.ycombinator.com/item?id=49331033.
  • Pulled with Threadpull on 1 Nov 2026: every comment Reddit returned, at every reply level, from reddit.com/r/SaaS/comments/1xkm24c/is_creating_an_ai_saas_too_lateoversatured/. Reddit's own count was 52; it also counts comments that were deleted or removed, which can't be pulled.
  • Read and grouped into themes. A comment can raise more than one theme, so counts are approximate.
  • Every quote on this page is checked word for word against the export, under its author, each time the page is built.
The threads at a glance
Hacker Newsr/SaaS
Score on the post64937
Comments43746
Top-level comments12426
Replies313 (72%)20 (43%)
People commenting29131
Comments by the original poster04
Deepest reply level104
Median comment length29 words25 words
Comments from the 5 most active people38 (9%)19 (41%)
Themes, by share of all comments
ThemeThreadCommentsShare
Self-hosting to regain controlHacker Newsabout 409%
Network effects keep teams stuckHacker Newsabout 235%
CI and Actions must carry overHacker Newsabout 215%
Outages are the trigger to leaveHacker Newsabout 194%
A specific problem beats a crowded marketr/SaaSabout 1022%
Yes, it is saturatedr/SaaSabout 1022%
Distribution is the hard part nowr/SaaSabout 817%
Too many ideas, not too many rivalsr/SaaSabout 49%

The words they used

How many comments used each word or named each product. Counted from the export each time the page is built; a comment counts once however often it repeats the word. Variants count together, so "self-host" includes "self-hosted" and "self hosting".

The Hacker News thread

Words and phrases
Word or phraseCommentsShare
self-host7216%
CI5513%
pull request or PR327%
migrate153%
private repo143%
GitHub Actions143%
federation143%
open source133%
Products and tools named
NameCommentsShare
Forgejo6114%
Gitea5212%
GitLab4911%
Codeberg4410%
Tangled215%
Fossil133%
SourceHut92%
Radicle82%
Bitbucket72%

The r/SaaS thread

Words and phrases
Word or phraseCommentsShare
saturated1226%
idea1226%
problem715%
compete or competition511%
distribution or marketing49%
local models49%
B2B or B2C37%
customer37%

Where the conversation happened

Comments per reply level. The deep chains are often where people disagree, and a skim of the top-level comments misses them.

Comments per reply level in the Hacker News thread. Top level: 124, Level 1: 96, Level 2: 93, Level 3: 60, Level 4: 33, Level 5+: 31.Top level124Level 196Level 293Level 360Level 433Level 5+31
Hacker News: 220 of 437 comments (50%) were top-level or direct replies, and the deepest chain went 10 levels. Half the comments arrived within 4.8 hours of the post, and 90% within 24 hours.
Comments per reply level in the r/SaaS thread. Top level: 26, Level 1: 10, Level 2: 7, Level 3: 2, Level 4: 1.Top level26Level 110Level 27Level 32Level 41
r/SaaS: 36 of 46 comments (78%) were top-level or direct replies, and the deepest chain went 4 levels. Half the comments arrived within 2.9 hours of the post, and 90% within 17 hours.

Using churn threads

Where do customers say why they're leaving?

In "alternatives to…" and "what do you use for…" threads on Ask HN, and in subreddits like r/SaaS and r/sysadmin. People explain what broke, what the replacement must have and what keeps them stuck, and others reply with their own switches. The Ask HN thread above holds hundreds of reasons.

What turns an outage into churn?

In the Ask HN thread above, outages started the search but didn't settle it. One commenter advised using outages as a trigger to evaluate alternatives rather than switching on the spot. What decided it was whether CI, integrations and contributors would come along.

How do you use a churn thread for retention?

List what people say a replacement must have, and check each item against your product. The ones you already have become retention messaging. The ones you lack, where rivals have them, are your risk list.

Can these threads help win a competitor's customers?

Yes. Pull the alternatives thread for a rival, list the reasons people want out, and answer each one on a comparison or migration page, in the words they used.

Is a crowded market a reason not to build?

The r/SaaS thread above split evenly. About 10 comments said AI SaaS is saturated, one citing 300 to 1,100 new launches a day on Product Hunt, and about 10 said that doesn't matter if you solve a specific problem for people you can reach. About 8 said distribution, not building, is now the hard part.

What should you ask before building another SaaS?

The questions one commenter put to the poster make a good checklist: how many potential customers you've spoken to, what they do today to solve the problem, what it costs them, and whether anyone has offered to pay.

Where SaaS buyers talk

Threads worth pulling, by what you're trying to learn.

  • Ask HN"Alternatives to…" and "what do you use for…" threads
  • r/SaaSFounders and buyers on pricing, churn and tools
  • r/sysadminIT buyers: outages, migrations and vendor lock-in
  • r/startupsEarly teams choosing their stack, and why
  • r/EntrepreneurSmall-business owners on what they pay for
  • Product subredditsYour rivals' own communities, where users complain first

How to find threads like these

Searches that turn up the threads worth pulling. Open one, then pull it with Threadpull.

SearchWhereWhat it finds
"Ask HN" alternatives tohn.algolia.comChurn threads: reasons to leave and what a replacement needs
site:reddit.com "switched from" plus a rivalGoogleSwitching stories about a competitor
site:reddit.com/r/SaaS "cancelled"GoogleWhy people cancel, in their own words
"Advice on migrating from"hn.algolia.comWhat people need carried over before they move

Threads worth pulling next

Comment counts as of 2 Nov 2026.

The prompt for churn threads

Pull an "alternatives to…" thread, choose Send to AI, and turn it into a retention brief.

These are every comment from a thread where people discuss leaving a software product.
1. List the reasons for leaving, with a count for each.
2. List what a replacement must have, with a count for each.
3. Rank the alternatives named by how often they come up.
4. List what keeps people from switching.
5. Quote the five most specific sentences, word for word.
6. Suggest three changes that would make our customers less likely to leave.

SaaS research FAQ

Can I pull threads about my competitors?

Any public thread you can open, you can pull. Threadpull only reads; it never posts, votes or messages anyone.

Does it work on Hacker News and Reddit?

Yes. Reddit threads work without an account. Hacker News threads and Reddit profiles need a free account.

Can I keep the research for later?

A free account saves every pull in History in your browser, searchable, so you can compare threads over time.

Your churn reasons are already in a thread.

Add to Chrome, it's free