Translate the brief
Extract likely communities, keywords, intent phrases, competitor names, and exclusion filters from natural language.
Closed research preview · Reddit demand evidence
Weekly demand signals for builders who need proof, not vibes.
Lead Radar turns a market brief into source-linked Reddit evidence, then forces the part most tools skip: human review, usefulness status, and a next action you can actually test.
Current stage: validated workflow prototype. Not pretending to be a fully self-serve SaaS yet.
The useful question is not “can we build it?”
It is whether strangers are already describing the pain clearly enough to justify your next week — or your next invoice.
Method
A market brief goes in. A reviewed evidence artifact comes out.
Lead Radar is intentionally narrow: fewer vanity metrics, more inspectable claims. The point is not another dashboard. The point is a decision memo you can use for interviews, outreach, positioning, or killing a weak idea.
Scan public conversations
Collect recent Reddit posts, deduplicate them, and keep the raw source link attached to every candidate.
Rank for commercial behavior
Score pain, workaround cost, urgency, buying language, and repeated requests — not keyword volume alone.
Review before trusting
Mark signals as useful, not useful, contacted, replied, or converted. Without that feedback loop, it is just a pretty report.
Signal taxonomy
Not every complaint is demand. The report separates noise from commercial signal.
Pain
Broken workflows, wasted time, repeated frustration, and expensive mistakes.
Buying intent
People asking for paid tools, recommendations, consultants, or replacement products.
Workarounds
Spreadsheets, scripts, Zapier chains, and duct-tape processes doing real business work.
Switching
Users comparing competitors, complaining about pricing, or looking for a way out.
Repeated requests
The same feature or pain showing up across communities, threads, and time windows.
Urgency
Language that points to budget, risk, deadlines, revenue loss, or operational pressure.
Validation loop
The scanner is not the product. The useful loop is.
Lead Radar only becomes valuable when raw posts turn into reviewed signals, conversations, and revenue evidence. The current preview is built around measuring that loop, not hiding it.
Raw public threads collected from the target communities.
Rule-ranked candidates filtered for pain, help-seeking, and buying language.
Human review marks useful / not useful before anyone trusts the output.
The best signals become interview prompts, outreach angles, or kill criteria.
Only revenue, replies, booked calls, or saved time count as proof.
Output
A decision artifact, not a dashboard to babysit.
The point is to leave with a readable research memo: what hurts, who said it, how strong the signal is, what still needs manual review, and what to do next.
Read a simulated report format →validation_report.md · simulated format
# Weekly Demand Scan: Shopify inventory forecasting ## Market summary Scanned public Reddit-style conversations across Shopify and ecommerce communities. The strongest demand signal is not “inventory management” broadly — it is cash-flow stress caused by manual reorder planning. ## Ranked evidence 1. [Buying intent: High] [Review: pending] “I’d pay for something that tells me when to reorder based on velocity.” 2. [Pain: High] [Review: pending] Spreadsheet forecasting breaks whenever lead times change during Q4. ## Next action Interview merchants doing $500k–$3M/year who still plan replenishment in Sheets. ## Limitation This sample illustrates report shape. Real reports must include source links and review status.
Access / pricing
Closed preview, priced like research before it is priced like SaaS.
Charging early is the anti-toy filter. If a scan cannot save time, sharpen positioning, or create a real conversation, it should be killed before we build more software around it.
Prices are provisional while the review loop is being validated. Early users should expect manual review, direct feedback, and fewer self-serve bells and whistles.
Research preview
Niche research report
One market brief, one manually reviewed Reddit demand report, delivered as source-linked Markdown.
$49 / scanRequest a scanResearch preview
Weekly lead radar
A weekly scan for one automation or SaaS niche, with reviewed signals, next actions, and review-status tracking.
$199 / monthJoin research previewManual Reddit search
Tabs, anecdotes, and context loss.
You can find useful threads manually. The problem is keeping evidence ranked, deduplicated, and exportable.
Generic SaaS dashboard
Looks serious. Often avoids the hard question.
Charts are cheap. Reviewed, source-linked evidence that changes a decision is the scarcer thing.
Lead Radar preview
Brief → evidence → review status → next action.
Useful only if it helps someone save research time, contact better leads, or kill a weak market faster.
FAQ
Quiet by design. Skeptical by default.
Is Lead Radar a finished self-serve SaaS?
No. It is currently a closed research preview: a Python scanner, review workflow, and manual-quality layer wrapped by a public landing page. That is deliberate — the next validation target is paid usefulness, not more dashboard chrome.
What does Lead Radar analyze?
Public Reddit posts and comments related to your market brief. It looks for pain, workaround behavior, buying intent, repeated requests, and source-linked evidence.
Are the sample reports real scans?
No. They are simulated examples that show the report format. Real customer reports must include source links and review status before being treated as evidence.
Is this a replacement for customer interviews?
No. It is the step before interviews: use it to kill weak ideas early and bring sharper language into the conversations that remain.
Does it use private Reddit data?
No. Lead Radar is designed around publicly accessible conversations only. No private messages, no private subreddits, no creepy enrichment.
What do I get back?
A Markdown research report with market summary, pain clusters, ranked evidence, representative snippets, source links, suggested next actions, and review-status notes.
Stop asking the idea to flatter you.
Run a small scan, review the evidence, and measure whether anything moves: replies, calls, saved research time, or revenue.