Ingest discussions
The corpus begins with source-specific connectors. Hacker News, Stack Exchange, GitHub Issues, and other compliant sources are collected through explainable paths rather than generic scraping. Each stored post keeps its original source URL so the final report can point back to the discussion.
Collect from explainable sources
Naerru starts with public sources that can be named and audited: APIs, feeds, structured metadata, and source-specific connectors.
Clean and retrieve relevant posts
Raw posts are normalized, embedded, and searched semantically so the report starts from discussions that match the query.
Rank signals
A query first retrieves a candidate pool from the processed corpus. Naerru then re-ranks the candidates with local relevance signals: semantic match, keyword overlap, likely competitors, and pain-oriented language.
For product or domain queries, each result can also be tagged by origin: direct product mention, competitor mention, or category-level discussion. That split keeps sparse evidence honest instead of pretending every signal is equally direct.
Synthesize reports
Synthesis happens after retrieval and scoring. The model receives the selected discussions and returns structured outputs: pain points, competitors, and product gaps.
The output contract requires evidence for the claims. Naerru validates the response shape and renders the cited source links beside the finding they support.
Score before synthesis
The backend blends semantic, keyword, competitor, and pain signals before the paid synthesis call sees the final evidence set.
Generate a sourced report
The report groups pain points, competitors, and product gaps, with cited discussions attached to the claims they support.
What you get
Running an analysis is free and unlimited — Naerru never paywalls the search itself. A free report shows the three strongest pain points for your query, each with its cited discussions, so you can feel whether a market has real friction.
A Pro subscription unlocks report depth: the complete ranked list of pain points and the product-gap analysis — where the evidence points to something users want that no tool serves well yet. That gap section is what turns a market scan into a build-or-skip decision.
Search scope
Naerru does not search the entire web. Its reports are limited to the sources the system explicitly ingests and can cite back to: public discussion platforms, issue trackers, and source-specific APIs that fit the evidence standard.
That limited scope is intentional. It keeps the report auditable, avoids generic web scraping, and makes it clear when a conclusion comes from direct mentions, competitor discussions, or broader category evidence.
Keep sources visible
The report is designed so the reader can move from conclusion back to discussion. Pain points include evidence links, product reports show whether cited signals are direct or inferred, and cached report URLs stay shareable for later review.