Reddit Lead Tagging Taxonomy

The score should explain why a thread deserves attention. It should not hide the judgment behind a number or push every relevant keyword toward outreach.

Use the score to decide the next action: prioritize fast review, inspect the context, route to an owner, save as research, or archive the match.

Start with tags for the type of signal: recommendation request, alternative request, competitor complaint, comparison thread, budget question, timeline urgency, or implementation pain.

Intent tags help your team see why a post mattered before anyone opens the full thread.

Use competitor tags when the post mentions a current tool, migration, pricing frustration, feature gap, or replacement search.

Use category tags when the thread belongs to a broader workflow, such as CRM, analytics, support, automation, security, or developer tools.

Urgency tags should separate immediate needs from research, future projects, and evergreen threads. Fit tags should mark ICP, possible ICP, poor fit, and unknown fit.

These tags make routing faster because the owner can see whether a lead needs action today or just belongs in research.

Reply-risk tags catch posts where the commercial angle may be sensitive: strict subreddit, no links, personal topic, vendor-hostile thread, or high chance of sounding spammy.

A high-intent post can still be a bad reply candidate when the community context is wrong.

Keep reporting tags boring and consistent: source, status, owner, replied, archived reason, meeting booked, trial started, and won or lost.

The more disciplined the taxonomy, the easier it is to prove which Reddit signals are creating real pipeline.

Descriptive tags capture source, topic, competitor, pain, role, and intent stage. Decision tags capture priority, owner, response type, risk, and lifecycle status. Mixing them makes reporting ambiguous and automation brittle.

Define allowed values, examples, ownership, and retirement rules. Audit unused and overlapping tags quarterly so the taxonomy stays small enough for reviewers to apply consistently.

Review criteria becomes useful when each item has evidence, an owner, and a recorded outcome.

Confirm the post shows a real problem, not only a keyword.

Check whether the author has enough context to qualify.

Lower priority for stale, vague, or unsafe threads.

Route strong posts into reply, CRM, or research workflows.

Choose one narrow signal lane, define the evidence required for action, assign an owner, and review real outcomes before expanding coverage.