Community playbooks
Stack Exchange lead generation: intent in Q&A
A Stack Exchange question is the closest thing on the public web to a written requirement, a specific technical problem with named constraints, posted by somebody trying to solve it today.
Nobody asks Stack Overflow what to buy. The rules forbid it.
That one fact reshapes the source. A Reddit thread asks the room for opinions. Over on Hacker News, a comment volunteers what somebody runs and what it costs them. A Stack Exchange question states a constraint, names the version, pastes the error, and lists what the author already tried, because a question that doesn't do those things gets closed.
One honest caveat first. This source is measurably narrower than it was in 2020.
What does Stack Exchange lead generation look like?
Stack Exchange lead generation means reading questions as requirement documents rather than as conversations. You're not hunting for somebody asking which tool to buy, because that genre is off-topic by rule. What you're reading for is the failure modes, ceilings, and blockers that show a purchase decision is already in motion.
The rule is worth reading in full. Stack Overflow's Help Center, under what topics can I ask about here:
Questions asking us to recommend or find a book, tool, software library, tutorial or other off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam.
Read what that deletes. It takes out the entire "what should I use" genre, which is the native format of Reddit and the reason most community lead-gen advice starts there.
What's left behind is sharper in one specific way. Somebody who asks how to make product A talk to product B under constraint C has already bought A, already chosen B, and has handed you the exact thing standing between them and a working system. Budget and authority are settled. The open question is whether the current stack keeps its job.
It's the same class of buying signal you'd look for anywhere. What changes is the stage. This is a failure-mode and migration-blocker surface, not a shortlist-formation one.
Is Stack Overflow still worth watching, given the traffic decline?
Yes, for narrower reasons than five years ago. The decline is real, peer-reviewed, and steep. What's left skews toward harder and more architectural questions, which sits closer to the evaluation stage than the beginner traffic that left. Treat it as a precision source, not a volume source.
Start with the measurements. del Rio-Chanona, Laurentsyeva and Wachs in PNAS Nexus, September 2024, found activity down about 25% within six months of ChatGPT's release relative to four control platforms, with a 15% average across the full window. Burtch, Lee and Chen in Scientific Reports, May 2024, measured roughly a million fewer visitors a day, about 12% of pre-ChatGPT daily traffic.
Question volume tells a starker story. December 2025 saw 3,862 questions posted, down 78% year over year, against a peak above 200,000 a month in early 2014. That figure comes from a public Stack Exchange Data Explorer query reported by devclass, not from Stack Overflow, which publishes no monthly series.
Now for the part that usually gets left out. Volume peaked in early 2014 and fell for eight years before ChatGPT shipped, so the studies isolate a marginal effect on top of a long slide. Over the same period Helic and Santos measured question difficulty rising, and concluded that ChatGPT "has effectively raised the bar for questions on Stack Overflow."
The honest read is not that the source died. Easy questions moved to a chatbot. Hard ones stayed, and hard questions are the ones with a purchase decision behind them.
Which Stack Exchange questions are buying signals?
Five shapes carry most of it: a compatibility question naming two products, a question about working around a documented limit, a migration blocker, an elaborate workaround that has outgrown itself, or a high-view question with no accepted answer. Each one resolves to a different fact about the buyer.
| Signal pattern | What it tells you | How to act |
|---|---|---|
| Compatibility question naming two products | An integration is being built now and both vendors are already in the stack | Write the answer into your own public docs, where search will find it |
| "How do I work around this limit in X" | The incumbent has hit a ceiling in production, with the ceiling named | Highest urgency. That ceiling is a line on your comparison page |
| Migration blocker ("moving from A to B, stuck on") | The switch is already decided and execution is the problem | Watch the tag, not the person |
| Elaborate upvoted workaround | An unmet need somebody paid for in engineering hours | A workaround with heavy upvotes is a feature request with a receipt |
| High views, no accepted answer | A widespread problem nobody has solved, with a count attached | Documentation input first, lead second. See below |
The other thing to get right is where you look. Stack Exchange is a network of per-topic sites, and for most B2B categories the relevant node is not stackoverflow.com. Server Fault carries infrastructure, Database Administrators carries the storage problems, and Information Security is where the compliance-shaped ones land. Per-site volume is low enough to read a week by hand.
Why is a high-view question with no accepted answer the strongest signal?
Because it's a quantified unmet need with a timestamp on it. The view count tells you roughly how many people hit the same wall. A missing accepted answer tells you nobody solved it well enough for the asker to say so. Both numbers keep moving long after the thread goes quiet, because the archive is permanent and ranked.
A Reddit thread about a problem is one person on one day. A question with a high view count is a running census of everyone who searched that exact error and landed on a page that didn't fix it. You're not inferring demand from language. You're reading a counter.
It pairs with the sharpest pattern on GitHub. An issue closed as wontfix is the vendor formally declining to solve a problem, in writing. A high-view question with no accepted answer is stronger in one respect and weaker in another. It's stronger because nobody solved it, not even the community, and there's a number showing how many people cared. It's weaker because no vendor is on the hook and no name is attached to the demand.
There's a discipline that goes with this. Plenty of good answers go unaccepted because the asker solved it and vanished, which is not the same as unsolved. The tell is in the comments under the top answer. When people are still writing "this stopped working on version 14," the problem is live.
Be honest about what this signal is. The person who asked is long gone. This is a market signal, not a lead. It belongs in your documentation and on your comparison page before it belongs in anyone's queue, and the page you write becomes what the next few thousand searchers find.
Can you promote your product on Stack Overflow?
Yes, with a disclosure, every single time. Stack Exchange's Acceptable Use Policy doesn't ban vendors from answering questions. It bans undisclosed ones. A relevant answer that says you build the tool is inside the rule. The identical answer without that line is spam by the policy's own definition.
The Stack Exchange Network Acceptable Use Policy, last updated November 17, 2025:
You may not post content for the purpose of affiliated marketing (e.g., to promote a product, service, or similar in a way that is unsolicited or lacks disclosure of affiliation).
The construction is the whole thing. Unsolicited or lacks disclosure gives you two independent failure conditions, and a disclosed answer to a question somebody asked fails neither.
That makes Stack Exchange the most specific of the four community sources on self-promotion, though not the most restrictive. Hacker News asks you not to use the site primarily for promotion, a ratio rule with no ratio. Reddit delegates almost all of it to individual subreddits. GitHub bans advertising in other users' accounts flatly. Stack Exchange is the only one that names the remedy and then requires it on every post, which is stricter than it sounds. There's no ratio to stay under, so one good disclosed answer doesn't earn you an undisclosed one.
Reading is governed separately. The same policy bans scrapers without express prior written consent, so the public API is the only sanctioned way to read at volume, at a default 10,000 requests a day.
How does Stack Exchange compare to Reddit, Hacker News, and GitHub?
It's the highest-precision and lowest-volume of the four, and the only one where the recommendation question is banned outright. Reddit has the volume, Hacker News has the technical density, GitHub has the post-adoption detail, and Stack Exchange has the requirement and the archive.
| Native question | Self-promotion rule | Cost to read | |
|---|---|---|---|
| "What should I use for this?" | Delegated to each subreddit, with the site rule being to participate authentically | Free Data API tier, 100 queries per minute per OAuth client | |
| Hacker News | "Here's my stack, what would you do?" | Don't use HN primarily for promotion, and sanctions reach whole domains | Official API, no key, "There is currently no rate limit" |
| GitHub Issues | "Your tool does not do X" | No advertising in other users' accounts, banned by name | 5,000 requests per hour with a token, and search caps at five boolean operators |
| Stack Exchange | "How do I make X do Y under constraint Z" | Answering as a vendor is allowed with disclosure of affiliation, every time | Default 10,000 requests per day, and over 30 per second per IP gets banned |
Nobody should tell you these are unwatched. Syften has monitored Stack Overflow, Server Fault and the wider network from $29.95 a month for years. Breadth isn't the scarce thing.
Memory is. Nothing in the standard toolchain remembers which question you already answered, so two people on one team answer the same thread. That's the gap LeadSurface works in. It watches Stack Exchange alongside Reddit, Hacker News, GitHub Issues, and Discourse, classifies each item instead of matching a keyword, deduplicates by URL, and hands back the few worth acting on with the source attached. A human still does the answering.
Test the premise in 20 minutes without any of that. Pick the Stack Exchange site closest to your category, filter to unanswered, sort by views, and read the first page.
That page is a ranked list of the problems your market has not solved, in your buyers' own words, counted.