Signal Methodology

Signals complement deep-dive reports. Their purpose is not to explain everything at once, but to identify opportunities worth deeper study with higher frequency and lower reading cost.

What we look for in a signal

New

There should be a fresh window, emerging demand, or a new product behavior worth noticing.

Real

The signal should be grounded in a real product, real growth, or real user behavior rather than recycled commentary.

Verifiable

Whenever possible, it should include sources such as product pages, rankings, traffic tools, founder posts, or screenshots.

Useful

The signal should help members decide what deserves more attention or research next.

How to read a signal

1. Start with the category and title to see if it matches your interests
2. Read the short description to understand what actually changed
3. Use growth, revenue, and timing metadata to decide whether to open a report

When not to over-interpret a signal

• Heat exists but monetization is unclear
• The pattern looks like short-term noise
• The source is too weak to support a strong conclusion