How to Use Reddinbox Reports

Most market research tools give you dashboards. Reddinbox gives you intelligence.

There's a difference. A dashboard tells you what happened. A Reddinbox Report tells you what real people said, in their own words, with citations you can click, organized by the angles that matter to your research. It's the difference between reading a press release and reading the actual forum thread where 400 people vented about the product for three years.

Reports are the deepest thing Reddinbox does. If you've been using the Agent for quick conversational searches and haven't run a Report yet, this guide is for you.

What a Report Actually Is

A Report is a structured intelligence document, generated from scratch, based on real posts collected from Reddit and X during a dedicated research run. It's not a summary of a chat session. It's not something you export. It's a fully researched briefing the platform builds for you from the ground up.

Every Report covers a topic you define through a set of research angles — the specific questions or sub-perspectives you want the research to address. The combination of topic + angles is what shapes what gets searched, what gets kept, and what ends up in the final document.

A finished Report includes six sections:

Executive Summary — the high-level "here's what the community is saying"
Key Pain Points — frustrations and unmet needs, weighted by how much the community talked about them
Community Sentiment — the emotional tone across the conversations: frustrated, excited, confused, skeptical
Notable Discussions — the specific posts and threads worth reading for yourself
Trends — patterns that appear across multiple communities or over time
Actionable Insights — concrete things you can do based on what was found

Every claim in sections 1–5 is cited with a link back to the original Reddit post or X thread. Charts are embedded after each section to give you a visual read on the underlying data — platform splits, sentiment distribution, engagement ranges, pain point rankings.

How to Trigger a Report

Reports are started from inside a conversation with the Agent. You don't go to a separate "Reports" page to kick one off — you ask the Agent to do it.

Say something like:

"Generate a full report on what freelance developers complain about with hosting platforms."
"I want a deep-dive report on how founders talk about cold outreach on Reddit."
"Run a report on churn reasons people mention for SaaS tools in r/SaaS and r/entrepreneur."

Any message that signals you want a comprehensive, structured output will do it. The Agent recognizes this and switches into report mode.

Reports are a premium feature. You need an active subscription to generate them. If you're on a free trial, conversational searches still work — reports are locked until you subscribe.

Review the Research Plan Before It Starts

Here's the part most people skip: before the report starts running, the Agent proposes a research plan.

The plan includes:

A restatement of the topic as the Agent understood it
A set of 4–6 research angles it intends to cover

This is your chance to shape the entire direction of the report before any searches happen. Read it. If the angles look right, confirm. If something is off — the framing is too broad, an angle is missing, or one angle is irrelevant to what you actually need — tell it now.

This is the highest-leverage moment in the entire process.

The Agent will run 20–25 diverse search queries based on these angles. The queries are written in natural, colloquial language — the way real people actually phrase Reddit post titles — to surface authentic conversations rather than SEO-optimized content. But the direction of those queries is entirely determined by the angles you approve.

If you want the report to focus on a specific audience (e.g., small teams, solo founders, enterprise IT buyers), say so before confirming. If there's a competitor you want explicitly covered as one angle, add it. If the plan is missing a platform consideration (e.g., you want Reddit-only), this is when to specify it.

What Happens During Generation

Once you confirm the research plan, the report runs in the background. You don't need to stay in the conversation.

Here's what's actually happening under the hood:

Search planning — the AI generates 20–25 queries across all your angles, each with a specified sort order (relevance, hot, top, new) and time range (past hour to all time)
Parallel searching — Reddit and X are searched simultaneously for each query, in batches of five
AI filtering — every raw result passes through a relevance check. Posts that happen to share a keyword but have nothing to do with the actual topic get cut. Only genuinely relevant posts make it through, each annotated with why it matched
Deduplication — if the same post shows up across multiple queries, it's only counted once
Synthesis — a senior analyst model reads all the surviving posts and writes the six sections, with inline citations to every post it references

The status indicator in the conversation tracks where it is in this process. When it flips to complete, the report appears in the Reports section of your dashboard.

If something fails mid-run, the report is marked as failed and you'll see that in the dashboard. In that case, starting a new request usually resolves it.

Reading Your Report

The Executive Summary

Read this first, but don't stop here. It gives you the "so what" in two or three paragraphs, but the depth is in the sections that follow. Think of it as the briefing you'd give to someone who has five minutes — not the whole document.

Key Pain Points

This is often the most valuable section for product and positioning decisions. Pain points are ranked by how frequently they appeared and how much community engagement surrounded them. A pain point mentioned in five posts with 800 total upvotes carries more weight than one mentioned in twenty posts with 30 upvotes.

Look for the top two or three — those are the ones worth building around.

Community Sentiment

Sentiment isn't just positive or negative. The report breaks down the emotional tenor more granularly: frustration, skepticism, enthusiasm, confusion, resignation. Understanding the flavor of sentiment tells you something different than just knowing the valence.

For example: if the dominant sentiment around a competitor is "skeptical but curious," that's a different positioning opportunity than "frustrated and actively looking for alternatives."

Notable Discussions

These are the specific threads the AI flagged as particularly relevant or high-signal. Click through to the original posts. Read the comment sections. The report synthesizes, but the raw threads often contain nuance — and outlier perspectives — that the synthesis doesn't fully capture.

Trends

This section surfaces patterns across the full collection of posts. If the same frustration is appearing in five different subreddits, or if the language around a topic has shifted recently, that's a signal worth paying attention to.

Actionable Insights

Concrete recommendations derived from what was found. These are specific — not "improve your onboarding" but "people specifically cite not knowing what to do after the first login as a drop-off point." Treat this section as a direct brief for your next product or marketing decision.

The Citations Matter

Every specific claim in the report links back to the original post. This isn't decoration — it's how you verify and extend.

If a pain point is cited with a link and you click through, you can:

Read the full thread and its comment section
Check whether the post is representative or an outlier
Find the exact language people use (which is often the language you should use in your copy)
Discover related threads in the subreddit

Don't treat the report as the final destination. Treat the citations as doors.

Report vs. Conversational Search: When to Use Which

Use conversational search when you want:

A quick answer to a specific question
To explore an unfamiliar topic before committing to a full research run
To follow a thread of curiosity without a defined research scope
To cross-reference a finding from a previous session

Use a Report when you want:

A comprehensive, multi-angle view of a topic you'll make decisions from
Something you can share with a co-founder, team, or client
Structured data visualizations alongside the analysis
A document you'll reference over time, not just in the moment

The Agent is good at depth on a narrow thread. Reports are good at breadth across a full research scope. They're complements, not substitutes — the best workflow is often a few quick searches to pressure-test your angles, then a Report once you know what you're looking for.

Tips for Better Reports

Write angles like research questions, not topics

A weak angle is a topic: "pricing." A strong angle is a question: "What do people say drove them to switch tools after a pricing change?" The more specific the question, the more targeted the searches — and the more useful the findings.

Three to five angles usually beats six or more

More angles doesn't mean better coverage. It means thinner coverage per angle. If you have six angles and only 25 total searches running, each angle gets roughly four queries. Be ruthless about what actually matters for this specific research goal.

Name your audience explicitly

If your research only matters for a specific type of user — indie founders, DevOps engineers, mid-market sales teams — say so in the topic or angles. The search queries get written in natural language, and the filtering model prioritizes relevance. The more precisely you define who you care about, the more precisely the results target them.

Use a prior conversation as context

If you've already done exploratory searches in a conversation that surfaced something interesting, start your report request in that same conversation. You can pass context to the Agent — "Based on what we found earlier about onboarding friction, generate a full report focused specifically on that." — and it'll factor that context into the research plan.

Common Research Use Cases

Product validation

"What are the most upvoted frustrations with project management tools on Reddit?" — Run this before you build. The findings tell you whether the pain you're solving is real, how widely shared it is, and how it compares in priority to other problems people have.

Positioning and messaging

"How do founders describe the difference between tools they love and tools they hate?" — The language in these threads is the language you should use in your landing page. Not metaphors. Not marketing copy. The actual words.

Competitive intelligence

"What do users on Reddit and X say about [competitor]? Cover both praise and complaints." — Organic, unfiltered customer opinions. No NPS survey, no review site curation. Just what people actually say when they think they're talking to each other.

Content and SEO strategy

"What questions do people ask most often in r/marketing and r/SaaS that don't have good answers yet?" — Finds the gaps in existing content. The threads where people are asking questions and getting mediocre answers are the exact topics to write for.

Investor and market narrative

"How has the conversation around AI coding tools changed on Reddit over the last year?" — Useful if you're preparing a fundraise narrative or competitive landscape section. Shows you where the market sentiment is heading, not where it was.

Reports are what you use when the stakes are high enough that you need to be sure — before you commit to a positioning, build a feature, or walk into a conversation. Start from a good research plan, confirm the angles deliberately, and then actually read what it finds.

The signal is in the threads.