Detectors and signals: where to watch, what to match 🔎
A detector is a rule that watches one place for one moment. A signal is one real person it caught. Here is every rule worth writing, the places to run it, and how to tell a buyer from noise before you spend an hour on the wrong post.
free library
✏️ make it yours
showing an example product, shipnote. paste your site and we fill it in, or type yours once, and every template, search and message across the libraries switches to it.
Seven fields decide what counts as a match. 🧩
anatomy
Write a detector down in this shape before you build or run it. If you can't fill a field, the detector isn't ready: usually the match is too vague or nobody has checked the source by hand.
1
Moment
The situation it watches for. One detector serves exactly one moment; one moment can have several detectors.
2
Source
The one place it reads: a subreddit, a search, a launch site, a job board, your own payment account.
3
Kind
Phrase, threshold, event, change or your own data. The kind decides how it's built.
4
Match
What has to be true: phrases in the buyer's own words, a field crossing a number, or a dated record appearing.
5
Strength
How sure a single match makes you. Strong means the match shows the moment directly; weak means it needs a second signal.
6
Freshness
How old a match can be before it's useless. The buying window closes; a three-week-old "any recommendations?" has already been answered.
7
Exclude
What throws a match out: the ICP's not-if lines, competitors and their staff, vendors fishing for clicks, your existing customers.
DETECTOREXAMPLE
Moment
Tried it and it failed
Source
Small launch sites
Kind
threshold on a dated record
Match
a launch listing dated in the last 7 days with upvotes < 10
Strength
strong
Freshness
7 days
Exclude
agencies, template sellers, anything that isn't software, makers already in a conversation with you
each match becomes a signallink to the listing · date · maker's name and handle · the matched fields (4 upvotes, Oct 14)
How a detector decides it found something. 🌲
five kinds
Start from where the moment becomes visible. Most moments can be caught more than one way, and the kind decides what the rule can read, how noisy it is and what it costs.
phraseindustry: social listening, keyword monitoring30 in the library
Words in a post or comment, in the buyer's own language.
use when
The moment is said out loud: an ask, a complaint, a vent, a hiring post.
avoid when
The moment never gets written down (a quiet churn), or the words are too common to separate.
noise
cheap to build, noisiest to run
strength
weak to strong; strong only for direct asks
window
3 to 14 days
records
detector_idlinkposted_atauthormatched_text
example
"what do you use for" {job} on a community forum, 7 days, strong
breaks on
Sarcasm, vendors answering themselves, very common pain words.
how it is built
Pull new items from the source on a schedule
Fill placeholders from your product: {job}, {category}, {competitor}
Keep items that hit the any-of and all-of phrases, drop the none-of
Read the survivors yourself (or send them to a judge)
Score strength, check freshness and exclusions, keep
The five kinds compared: what each reads, how noisy it is, what it costs and how long a match stays fresh.
Kind
Reads
Match form
Noise
Cost to run
Typical window
phrase
posts, comments, threads
phrases + negatives + judge
high
feed polling plus a read of every candidate
3 to 14 days
threshold
launch sites, reviews, revenue boards
field compared to a line
low
page or API reads, few reads of your own
7 to 30 days
event
job boards, news, listings
new record of a type, filtered
medium
listing reads, de-duplicating across boards
14 to 60 days
change
competitor pages
diff between snapshots
low
one snapshot per page per day
1 to 7 days
your data
app, analytics, forms, payments
condition across your events
lowest
your own events, no scraping
1 to 60 days
Two kinds beat one. Most moments can be caught more than one way. Two detectors of different kinds on the same person (a low-vote launch listing and a “launched, crickets” post) is the strongest evidence a cold signal can carry. A person reading the match can sit on top of any kind; that changes precision, not the kind.
Every detector, with your words in it. 🔎
Placeholders in braces come from your product: {job} is what it does, {category} is what buyers call it, {competitor} comes from your competitors, {role} is whoever does the job by hand. Fill make it yours at the top and every rule and search below fills itself in.
the library
Kind
Also fill {category} and {role}
Until you type one, this uses what your product does.
"what do you use for" writes release notes from commits · "best tool for" writes release notes from commits · "any recommendations" + writes release notes from commits
site:reddit.com "what do you use for" writes release notes from commits
site:reddit.com "best tool for" writes release notes from commits
site:reddit.com "any recommendations" writes release notes from commits
throw out
vendors answering their own threads; listicle bait
also
the ICP's not-if lines, and anyone already a customer
Where detectors read, and how you're allowed to. 📍
Access changes, so check each source's current terms before you automate it. “By hand” means a person reads it on a schedule, and that is often the right start anyway: it's how you learn what a real match looks like.
source directory
Communities and search
Communities and search: what each source holds, how to read it, its terms, and how many detectors use it.
Source
Holds
How to read it
Cost and terms
Detectors
Reddit
posts, comments
each subreddit's search and new-posts view, read by hand
Access rules change often. Check Reddit's current terms before you automate anything, and follow each subreddit's own rules.
X
posts
X's search by hand; the API for automation
API access is paid, priced by usage tier.
Threads
posts
keyword search through Meta's API
Needs Meta's app review for accounts outside the app's testers.
Hacker News
posts, comments, Show HN
the free HN Search API (Algolia): Ask HN, Show HN, monthly "Who is hiring?"
Free and public. Self-promotion is frowned on in comments.
Indie Hackers
posts
the public forum and milestone posts, read by hand
Public. Follow the community's self-promotion norms.
Discord, Slack and Skool
messages, posts
by hand, as a member
Member-only. Never scrape; ask the admins before anything automated.
LinkedIn
posts, profiles
by hand; Sales Navigator alerts for job changes
No public API for this. Sales Navigator is paid.
Google Alerts
web pages
an alert per phrase, by email or RSS
Free. Finds articles and pages more than people.
Launch sites
Launch sites: what each source holds, how to read it, its terms, and how many detectors use it.
Source
Holds
How to read it
Cost and terms
Detectors
Product Hunt
launches
the public Atom feed; the API with a token
The API's docs say it must not be used for commercial purposes; use the feed.
Uneed
launches
daily pages and a sitemap with lastmod; prints an explicit launch date
Check the site's terms before automating.
PeerPush
launches
a documented launch API with a free key
Rate-limited key; follow the API terms.
BetaList
launches
HTML only, day headings on the index
Check the site's terms before automating.
Other launch sites
launches
Smol Launch, Fazier, TinyLaunch and similar; launchdirectories.com lists 100+
Check each site's terms before automating.
Review sites
Review sites: what each source holds, how to read it, its terms, and how many detectors use it.
Source
Holds
How to read it
Cost and terms
Detectors
G2
reviews
product and category pages, by hand
No open review search for non-vendors. G2 sells buyer-intent data to vendors with a listing.
Capterra
reviews
product pages, by hand
No open review search. Reviewers show a role, industry and company size, rarely a name.
Trustpilot
reviews
company review pages, newest first
Public pages; check the terms before collecting. Reviewers often use a first name only.
App stores
App stores: what each source holds, how to read it, its terms, and how many detectors use it.
Source
Holds
How to read it
Cost and terms
Detectors
Apple App Store
reviews, listings
app pages and their newest reviews
Public pages; no review search API for apps you don't own.
Google Play
reviews, listings
app pages and their newest reviews
Public pages; the review API covers only your own apps.
Shopify App Store
reviews, listings
app pages; reviews name the reviewing store
Public pages; no review API.
Chrome Web Store
reviews, listings
extension pages and their reviews
Public pages; no review API.
Records
Records: what each source holds, how to read it, its terms, and how many detectors use it.
Source
Holds
How to read it
Cost and terms
Detectors
Revenue boards
records
TrustMRR and open-startup pages: verified revenue
Public pages; check terms before collecting.
Job boards
job posts
LinkedIn Jobs, Indeed, Wellfound; saved searches and site: searches
Most have no open search API. Saved-search emails work.
News and funding
articles
tech news RSS; Crunchbase for funding
RSS is free; Crunchbase's API is paid.
Meta Ad Library
ads
search the library's website by advertiser
Free to search. The API covers political and issue ads, and ads shown in the EU.
Competitor pages
pages
pricing page, changelog, status page; a page-change monitor or their RSS
Public pages. Many status pages offer RSS or Atom feeds.
Your own data
Your own data: what each source holds, how to read it, its terms, and how many detectors use it.
Source
Holds
How to read it
Cost and terms
Detectors
Replies and mentions
your posts
replies, mentions, comments and DMs on your own accounts
Your own account's data.
Forms and email list
submissions
waitlist, lead-magnet and newsletter sign-ups
Your own data. Only email people who gave you the address.
Site analytics
page views
PostHog, Plausible, GA4 and similar
Per-person events only for visitors who are logged in or identified.
Your app
product events
your database or product analytics
Your own data.
Stripe
webhooks
webhook events sent to your server
Your own data.
Source access, prices and terms change. This reflects what was generally true in mid-2026. Read only public data, follow each community's rules, and never message a stranger automatically: a detector finds the person, a person sends the first message.
What a match becomes. 📡
signals
A match is only a rule firing. A signal is a real person in the moment. A lead is a person worth a message. Most matches never become signals, and most signals never become leads on their own.
matchA rule fired
A detector found words, a number or a dated record that fits its rule. Nobody has checked it yet. Cheap and noisy.
"any tool for" + "release notes"
signalA real person, in the moment
The match passed freshness, exclusions and the check, and there's a person behind it. It carries the moment, its strength and its evidence.
u/shipfast, asked 3h ago, strong
leadA person worth a message
One or more signals on the same person, merged, who fits the ICP. Leads get scored, tiered and handed to a playbook.
Hot · 2 signals · fits 3 of 3 lines
1
Who
A real person or a small team you can reach, not a brand account, a bot or a news site.
2
What
The exact text, listing or event, frozen at capture. Posts get edited and deleted; the signal keeps what you saw.
3
Which moment
Exactly one moment from the map. A post that shows two becomes two signals.
4
How sure
The detector's strength plus the verdict and how confident it was.
5
How fresh
When it was posted, not just when it was caught. The window closes on the post's clock.
6
Where next
The queue it was routed to, or the reason it was thrown out.
SIGNALEXAMPLE
Text
"is there anything that writes release notes from commits? doing it by hand every friday is killing me"
Source
a community forum · posted 3 hours ago
Moment
Asking for a recommendation
Detector
phrase · strong
Verdict
yes · 0.91 · "asks for exactly the job; solo founder with a live product"
Routed
pain queue
what happens nextmerged with any other signal on the same person, checked against the ICP, then scored as a lead and offered the answering play
The four questions, and where a signal goes
1
Is it the moment? Does the text actually show this buying moment, or does it only share the words? "I built a changelog tool" is not "I need one".
2
Is there a person? Someone reachable who could buy: not a brand account, a bot, a journalist or a vendor fishing for clicks.
3
Is it still open? Posted inside the moment's freshness window, and not already answered or solved in the thread.
4
Does it pass the rules? None of the ICP's not-if lines, not a competitor or their staff, not an existing customer.
Verdicts
yes
It's a signal. Confidence (0 to 1) ranks it among today's signals.
no
A discard, with the reason from the list below. Keep it: discards are the negatives you learn from.
unsure
Goes to a person with the question that couldn't be answered. Their answer becomes a label.
Where a signal goes
pain
Public posts where someone describes the problem the product solves. The main source of cold leads.
engage
Replies to and mentions of your own account: people already talking to you. Each card is logged with the probability it was shown.
listen
On-topic conversation worth reading or joining, without a clear buying moment yet.
launch
Launch posts and listings: someone just shipped and is looking for users.
The order it checks
Is it already a conversation with you?→engageReplies, mentions, DMs and comments go to engage, whatever else they contain.
Is it a launch?→launchLaunch posts and new listings go to launch. For a product sold to founders, a launch is a buying moment.
Does it state the pain?→painAsks, complaints, workarounds and competitor reviews go to pain: the main source of cold leads.
Anything else that passed→listenOn-topic, but no moment. Worth reading or joining, not pitching.
The 24 signal types, each with the play that answers it. 🗂️
signal types
Cold signals come from strangers in public. Warm signals come from people already touching your product. Names in braces fill from make it yours at the top.
24 of 24 signal types
Asking Someone describes the job or asks for help with it.
coldphrasestrong
Asks for a recommendation
any tool that writes release notes from commits? doing it by hand every friday is killing me
"yes, send it over" in reply to step 1 of a sequence
fresh for
24 hours
source
your inbox and DMs
moment
in conversation
the play
The next step of your sequence
Fourteen posts. Signal or noise? ⚖️
you be the judge
The same four questions, on real-looking posts. Pick a verdict first, then see what the rubric says and which question decided it.
Imagine you sell a changelog tool to solo SaaS founders. Read each post and decide what the rubric would say. Four questions: is it the moment, is there a person, is it still open, does it pass the rules.
case 1 of 14
anyone know a tool that turns commits into release notes? tired of writing them by hand every friday
0 of 14 answered
Why a match is thrown out, and what each reason teaches.
discards
Keep every discard with its reason. A detector that throws out most of what it catches for the same reason needs a new exclusion, not a smarter reader.
Ten reasons a match is thrown out, with an example of each and what it teaches.
Reason
What it means
Example
What it fixes
stale
Posted outside the trigger's freshness window.
a "any recommendations?" thread from three weeks ago
the freshness window per type; detection lag
excluded
Hits one of the ICP's "not if" lines.
an agency asking on behalf of a client
ICP lines: which ones throw out real buyers
competitor
A competitor, its staff or its affiliates.
a competitor employee asking what people think of the new pricing
the lead rules' competitor list
vendor
Someone selling, fishing for clicks, or promoting their own tool.
"what tool do you use for X? (asking because I built one)"
detector exclusions; the judge's "is there a buyer" question
customer
Already a customer, or already in a campaign.
a current user asking a support question in public
routing to support or the engage queue instead
no person
A brand account, bot, news site or deleted user.
a newsletter account resharing a listicle
author-snapshot features for the judge
duplicate
The same person, same trigger, inside the window.
the same question cross-posted to three subreddits
person merging; counts as one signal with three sources
not the trigger
Shares the words but not the moment.
"I built a changelog tool, roast my landing page"
the judge's "is it the trigger" question; new negative phrases
answered
Already solved in the thread.
the asker replied "went with X, thanks all"
thread state as a judge input
out of scope
Wrong language, region or platform for the product.
asks for a tool that only works with a stack you don't support
brief fields for supported stack and region
How a match rule runs. 🧪
match rules
Cheap clauses narrow the stream, a person reads the survivors, and strength, freshness and exclusions decide what is kept.
Item
Fill placeholders
Phrases
Negatives
Fields
Judge
Score
Emit
the rule: Tried it and it failed, on a social network
all of: "launched" | "shipped" | "went live"
any of: "crickets" | "0 signups" | "zero signups" | "no sales" | "nobody signed up"
none of: "lol jk" | "#1 product of the day" | "thank you all"
within: 7 days
Cheap clauses first, a person last. Every clause that throws a post out is logged: those are the negatives your rule learns from.
try a post
✓
all of: passes
found: launched
✓
any of: passes
found: crickets, zero signups
✓
none of: passes
It matches. A person reads it next.
Where the words come from
The vocabulary is the most valuable part of a rule and the easiest to get wrong. Each type has a source, and none of them is your own marketing copy.
The seven kinds of word a rule uses, with an example and where each comes from.
Type
What it is
Example
Comes from
ask words
phrases people use when choosing a tool
"what do you use for", "any tool that", "recommend"
audience research, the moment
pain words
the problem in the buyer's own words
"launched, crickets", "0 signups", "nobody knows it exists"
community threads, a founder interview
job and category
what the product does, what buyers call it
{job} = "get my first customers"; {category} = "distribution tool"
your brief
competitors
names, old names, misspellings
{competitor}
market research
ICP markers
words that show fit
"solo founder", "my SaaS", "bootstrapped", a product link in the bio
the ICP's fit lines
negatives
words that show a false match
"we built", "affiliate", "top 10"
every false match you've read
roles
the person who does the job by hand
{role} = "social media manager"
the ICP, job boards
Test a detector by hand before you trust it. 🧰
testing
A detector that hasn't been tested on real data is a guess. Seven stages from draft to retired, and the first few cost an afternoon.
1Draft
Fill all seven fields. If one won't fill, the detector isn't ready.
2Hand test
Run the match by hand on the source for the last 30 days.
3Precision read
Read 20 or more matches and label each: right person, in the moment, fits the ICP.
4Shadow
Let it run without acting on it, and compare to what you would have picked by hand.
5Live
Act on what it catches, with a person sending every message.
6Readout
Which of its catches turned into a reply, a visit or a payment?
7Retire or tune
Add exclusions for every miss, or switch it off after a fair run.
Write the gate first
Decide the pass bar (how many real matches a month, what share must be right) before you look at results, so you can't move it afterwards.
Humans label, the model is tested
You read and label real matches. Any model that judges for you is graded against your labels, never the other way round.
Yield beats precision
A rule that finds 25 real people a month at 60% right usually beats one that finds 3 at 95%. You need people to talk to.
The hand test, about an hour each
1
Search it yourself. Run the match by hand on the source for the last 30 days. Use the site's own search or a site: search.
2
Count the real matches. Twenty or more a month makes it a channel. Fewer than that, and each person gets sold to by hand, which is fine but doesn't need automating.
3
Read 20 of them. Mark each one: right person, in the moment, fits the ICP. If fewer than half pass, tighten the match or add exclusions before going further. (A rule of thumb, not a standard.)
4
Write down the misses. Every false match you saw becomes an exclusion. Every real person you found another way, which it missed, becomes a new phrase.
Strength, in plain terms
strong
The match shows the moment directly. A launch with 4 upvotes; a failed payment; "what do you use for invoice reminders?"
medium
Probably the moment, but check the person against the ICP before acting.
weak
Only useful alongside a second signal on the same person. On its own, it's material for a post, not a message.
After it's running
weekly
Read a sample of what it caught. Add the new false matches as exclusions.
monthly
Check which of its signals became leads, and which leads paid. Detectors whose signals paid get trusted more.
retire
A detector whose signals never turn into a reply or a visit after a fair run (decide the number before you start) gets switched off.
How many labels before you trust it
Labels read against the margin of error on the share that are right.
Labels you read
Margin on “share that are right”
20
±22 points
50
±14 points
100
±10 points
200
±7 points
400
±5 points
With 20 labels, if 70 in 100 look right, the real figure could be anywhere within ±22 points of that. To get within ±10 you need about 97 labels.
The worst case, at 95% confidence. Twenty labels tell you whether a detector is roughly right or roughly wrong, not whether it is 60% or 75%. That is enough to decide to tighten it.
How to use this.
how this works
Pick a buying moment from the map, find its detectors in the catalog, and run the ready-made search by hand on the source for the last 30 days. Count the real matches, read twenty of them, and write down every miss as an exclusion. Only then is it worth running on a schedule.
Each match that survives is a signal: one person, one moment, frozen as you saw it. Two signals of different kinds on the same person is the strongest evidence there is. Score them with the lead score and check what you are about to send with the reply checker.
Source access, prices and terms change, so check each source's current terms before you automate anything. Read only public data, follow each community's rules, and never message a stranger automatically: a detector finds the person, a person sends the first message. Every post and quote here is invented to show the shape.
want this run for you? vibedraft finds the people ready to buy on X and in your own signups, drafts the right move in your voice, keeps your channels posting and learns what pays. you approve everything that goes out.