What Counts as a Buying Signal
Outcome: a shortlist of the signals worth watching for your product, each with a stated freshness window and a reason it predicts a purchase.
- Surface
- App and MCP server
- Level
- Intermediate
- Uses
- No actions — planning lesson
- Credits
- 0
- Prerequisite
- SyncGTM 101
The three-part test
A trigger is worth building a play on only if all three hold:
It implies a change in need
Something is now true that was not true last month, and it makes your product more relevant. A new VP of Sales needs tooling decisions made. A company that has always been 40 people does not suddenly need anything.
It implies budget or authority
Funding unlocks spend. A new executive has a mandate and a window to use it. Headcount growth in a specific function implies that function has a budget line.
It is fresh enough to mention
If it happened five months ago, referencing it signals that you have a list and you are slowly working it — which is worse than not mentioning it.
Most things called signals fail the first test. A company using a competitor is a fit attribute, not a trigger — it was true last year and tells you nothing about timing. Fit belongs in TAM Sourcing; this course is about timing.
Signals worth watching
| Signal | Why it predicts | Window |
|---|---|---|
| Funding round | Budget just appeared, and there is pressure to deploy it | ~6 weeks |
| New executive in a relevant function | New mandate, new tooling decisions, wants early wins | ~8 weeks |
| Hiring for a team you serve | The function is being resourced, so it has a budget | While roles are open |
| Champion changed jobs | A known advocate now has a new stack to influence | ~4 weeks |
| Headcount growth in a function | Scale is breaking whatever they do manually | ~1 quarter |
| Product or market launch | New motion, new needs, public commitment to it | ~4 weeks |
Windows are guidance, not rules. What matters is that you have one per signal — a play with no expiry keeps sending, and the messages get progressively stranger.
Detection lag is real. A funding round is reported days to weeks after it closes, and a job change appears when the person updates their profile, not when they start. Treat the window as starting from detection, and prefer signals your sources catch quickly.
Combining signals
One signal is a reason to look. Two signals at once is a reason to prioritize.
Funding alone tells you they can spend. Funding plus three open roles in the function you sell into tells you what they are spending it on. That pairing is the entire premise of the scoring model in lesson 07 — score on signal count and recency, not on any single trigger.
Referencing a trigger without being creepy
There is a line, and it is not subtle once you know where it sits.
| Fine | Not fine |
|---|---|
| Publicly announced company news — funding, launches, hires | Anything implying you monitor an individual |
| Open job listings the company published | Someone’s personal activity described back to them |
| A change in scale you could infer from their own site | Anything you could only know from tracking |
The practical test: would the recipient be able to guess where you got it? Funding announcements, job posts and press releases pass — they published them on purpose. “I noticed you’ve been looking at…” does not.
Reference the company’s situation, not the person’s behavior. That single rule keeps trigger-based outreach on the right side of the line.
Do this now
Write down, for your product:
- The three signals from the table above most likely to precede a purchase
- For each, why it implies need — one sentence, and it has to be specific to what you sell
- For each, the freshness window you will enforce
If you cannot write sentence 2 without hedging, that signal is noise for your product. Drop it. Two well-chosen signals beat six that fire constantly.
Check your work
- Does each signal on your list pass all three parts of the test?
- Does each have a window, and do you know how you would enforce it?
- Would a prospect be able to guess where you learned the trigger?
Where this breaks
The failure that damages a domain is a play with no expiry and no suppression list. Signals re-fire — a company raises again, a role reopens, a profile updates twice — and without a record of who was already contacted for which trigger, the same person receives the same play repeatedly. Before building any play in this course, decide where contact history lives and how a row gets excluded once it has been worked.
Further automation
Once your shortlist exists, lessons 03 to 05 build a detection column per signal, and lesson 07 combines them into one weighted score. If you would rather receive signals as a digest than work them in a table, AI for RevOps covers the scheduled version.
Next lesson
02 — Signal types in Sync GTM, mapping each signal above to the action that detects it and what that detection costs.
Reference for this lesson: Signals, How enrichment works.