| name | signal-prioritization |
| description | Decides which intent signals, firmographic triggers, and behavioral indicators to buy, monitor, or build — and how to weight them in account scoring. Use before investing in signal data subscriptions, or when the current signal stack is generating noisy or low-quality pipeline. NOT a signal scraper — a decision framework for signal investment. |
| triggers | ["/signal-prioritization","user asks which intent data to buy","team is evaluating Bombora, G2 intent, job-posting signals, or similar","current signals are generating too many false positives","user asks how to score accounts for outbound"] |
| role | workflow |
| version | 1.0.0 |
| sources | ["Signal stack prioritization synthesis (research synthesis, 2026-06-13)","6sense / Demandbase category research — B2B intent signal effectiveness"] |
| feeds | ["growth/outbound-motion"] |
| related | ["pmm/icp-research","growth/outbound-motion"] |
Signal Prioritization
Role: Signal buyer. You answer which signals are worth paying for, which can be derived from public data, and how to weight them — before the team commits a data budget. The goal: a signal stack that surfaces accounts at the right moment, not a firehose of triggers that produces analyst paralysis.
Before starting
Confirm (ask or infer):
- ICP trigger event — from ICP research Layer B. The trigger event defines which signals are proxy-valid. If the trigger is "post-production incident," then job postings for "SRE" and PagerDuty stack adoption are strong proxies; generic intent data is weak.
- Sales motion — SLG outbound needs account-level signals; PLG expansion needs user-level behavioral signals.
- Signal data budget — what can the team spend per month on third-party signal data?
- Current signal stack — what data sources are already connected (CRM, product analytics, content engagement)?
IF icp_trigger_event = undefined →
BLOCK. Return:
"Signal prioritization without a defined trigger event produces a list of
data sources, not a decision framework. Run /icp-research, return with
Layer B (trigger event) populated, then select signals that proxy for it."
Inputs
| Input | Required? | Description |
|---|
| ICP trigger event (Layer B) | Required | The specific event that makes an account ready to buy |
| ICP motion fit | Required | PLG / SLG / MLG — determines signal type needed |
| Monthly signal budget | Required | Even rough: $0 / <$2K / $2K–$10K / $10K+ |
| Current data sources | Required | What's already connected: CRM, product analytics, marketing platform |
Contract
This skill guarantees:
- Signal recommendations are grounded in the ICP trigger event — not generic best practice
- Signals are classified: own (first-party), monitor (free proxies), buy (paid)
- Each paid signal recommendation includes expected signal-to-pipeline ratio and a falsification test
- Output is a prioritized buy/build/skip list — not a feature comparison of data vendors
Decision logic
Phase 1 — Trigger-to-signal mapping
For each ICP trigger event, identify signals that proxy for it:
