Back to blog
·4 min readReddit APIs

Reddit product research: count the job, not the loudest thread

All Them APIs

Independent API research

“I would pay for this” is a useful sentence to find. It is not a transaction.

Reddit is good at exposing the work people are trying to finish, the tools that disappoint them and the workarounds they tolerate. It is much less good at telling you how many of those people will buy a particular implementation at a particular price.

A research pipeline should preserve that difference instead of turning every request into a market-size estimate.

Start with a job and a collection boundary

Choose a small problem space and a few relevant public communities. Write down who appears to be doing the job, what triggers it and what a better outcome would look like.

Search for workflow language as well as requests for tools. “I export this every Friday” can be more informative than “someone should build an app.” A repeated manual step supplies a starting hypothesis about frequency and friction.

Keep questions and assumptions separate. If the author's company size or budget is not stated, leave it unknown. Do not infer a commercial buyer from technical vocabulary alone.

Extract observations before assigning themes

Use a consistent research record. Save only the permitted information needed to revisit the evidence, with a source link and a retention decision.

FieldWhat belongs there
JobThe task the author is trying to complete
TriggerThe event that caused the problem to matter
WorkaroundWhat they currently do instead
ConsequenceTime, risk or missed outcome actually described
Payment signalExplicit budget or stated willingness, kept separate from payment
UnknownThe question the discussion does not answer

Several posts saying “reporting is painful” can hide different jobs: reconciling invoices, summarizing support tickets or producing a board update. Cluster by the workflow before clustering by shared adjectives.

Count independent evidence

A highly voted thread is not a count of buyers. Votes can reflect agreement, entertainment or the visibility of the post. Comments can also repeat the original suggestion without adding another real workflow.

Group comments under their discussion before counting themes. Note whether a different source independently describes the same job. Preserve counter-examples: someone may explain that an existing tool already solves it, but only with a setup cost your first reading missed.

The competitor research guide covers the related problem of treating repeated complaints as market trends.

Require the agent to keep uncertainty

An agent can help classify candidate posts and draft job statements. It should not infer willingness to pay from a positive tone or invent missing context.

Read the accepted source discussions and their relevant parent context.
Extract the stated job, trigger, workaround and consequence.
Keep explicit payment language separate from completed purchases.
Leave role, company size, budget and frequency unknown when not stated.
Group comments from the same thread before counting independent evidence.
Attach source links and include contradictory observations.
For each theme, propose one hypothesis and one way it could be false.
Do not infer sensitive personal traits or match identities across sites.
Return a research backlog, not a market-size or revenue forecast.

Turn a theme into a falsifiable next step

Suppose several independent discussions describe manually merging weekly exports. A useful hypothesis is that a specific group needs an automated reconciliation step often enough to adopt a tool.

Unknowns include input formats, acceptable errors, who approves the output and whether the existing workaround is inconvenient enough to replace. A prettier summary of the original posts does not resolve any of those questions.

Choose a small next experiment: a voluntary interview, a task-based prototype, or a clearly described paid offer. Keep the evidence ladder visible: observed problem, stated interest, attempted use, purchase and repeat use are different events.

Do not send unsolicited automated messages to everyone in the source dataset. The Reddit policy restricts commercial use and sensitive profiling; confirm the permitted collection, storage and outreach process before acting.

Make the collection itself reviewable

Record the query set, communities, time window, sort and page limit. Note which requests failed and which discussions were only partly retrieved. If those settings change, mark a new collection version.

Our search and comments guide covers the integration boundary. The monitoring overview covers repeated collection. Neither provider output nor an AI label makes a convenience sample representative.

The final artifact should be a short list of jobs worth investigating, with enough source evidence for another person to disagree. That is more useful than a spreadsheet full of confident opportunity scores.