Signal Plays

signal-plays.md

Markdown 8 KB 100 lines 7 sections

Signal Plays

A list tells you who could buy. A signal tells you who might buy now. This reference turns signals into outbound plays: which signals to trust, how fresh they need to be, what to do when one fires, and how much effort each account deserves.

Signals are a timing and relevance filter. They don't replace ICP fit. A strong signal at a company outside your ICP is still a skip, and a great-fit account with no signal can still get a well-aimed message built on its situation.

Rank signals by how close they are to you

The closer the signal is to your product and your past customers, the better it converts. Work down this list and stop where you have enough volume:

RankSignalWhy it worksTypical source
1Your own product usage: a signup from a company domain, a plan limit hit, a big upload, a team inviteThey already chose you onceYour product analytics, billing
2Past champions changing jobsFormer users bring the tool with them; vendors report win rates roughly double when the buyer has used the product beforeCRM contacts + job-change tracking (UserGems, Clay, manual LinkedIn checks)
3High-intent website visits: pricing, comparison, integration pagesActive evaluationVisitor identification (RB2B, Warmly, Vector), your analytics
4Engagement with you or a competitor: comments on your posts or a competitor's, community questionsPublic interest in the problemTrigify, Common Room, social listening
5Hiring in the function you serve, or a new leader in itNew budget and a mandate to change thingsJob boards (TheirStack, PredictLeads), LinkedIn
6Funding, launches, expansionBudget, plus pressure to grow fastCrunchbase, news, press releases
7Tech stack changes: adding or dropping a tool next to yoursA related decision is in motionBuiltWith, Wappalyzer, job-post tech mentions
8Generic third-party intentWeakest, and noisyBombora-style intent feeds, review-site intent

Stack signals before acting on the weaker ones. Hiring a lifecycle marketer plus an ESP in the stack plus a fit score above your threshold is worth a sequence. Any one of those alone usually isn't.

Freshness windows

A signal decays. Act inside these windows or downgrade it:

SignalAct withinAfter that
Product usage spike, limit hitSame day (ideally within minutes)Treat as a normal product-qualified lead
Pricing or comparison page visit24 hoursDrop to the general list
Champion job change30–90 days in the new roleThey've already chosen their stack
New leader in the functionFirst 90 daysPriorities are set
Job post for the functionWhile the post is open, up to ~60 daysHire made, budget allocated
Funding announcement30–60 daysOld news; don't congratulate on it
Tech install or removal30 daysDecision done

Record the signal date on every lead. A lead sheet without signal dates can't be prioritized.

From signal to play

Every signal you track should map to a specific play, so nobody improvises the angle at send time:

SignalPlayOpening angleChannel order
Product limit hitSales-assistOffer to help them get more from the plan they're outgrowingEmail from a founder or account owner within minutes, then LinkedIn
Champion job changeReunionReference the work they did with you before; ask how the new team handles itLinkedIn first (they're updating their profile), then email
Pricing page visit (identified)Evaluation helpDon't mention the visit. Lead with the decision they're probably weighingEmail, then call for Tier 1
New leader in the functionFirst 90 daysThe thing new leaders in that role usually fix first, with proofLinkedIn connect, then email
Hiring for the functionBridge the gapWhat they can get done before the hire lands, or what the hire will needEmail
Competitor engagerAlternativeThe problem they engaged with, not the competitorLinkedIn, then email

Write the angle as the problem the signal implies. "Saw you raised a Series A" is a fact everyone else sent. "Most teams that just raised are told to double pipeline in two quarters, and the site usually becomes the bottleneck" is a reason to reply.

Two worked examples

A services agency selling to B2B SaaS (for example, a CRO and landing page agency)

  • Signals: funding in the last 60 days; a new VP Marketing or head of growth; open roles for growth or performance marketers; a redesigned site or new pricing page; paid search or paid social campaigns launching.
  • Play: value first. Offer a short teardown of their actual page. Send it only after they say yes. See the cold-email skill's outbound plays reference.
  • Volume: about 50 well-researched accounts a week beats 5,000 generic sends. Agencies rely on depth.

A self-serve SaaS tool (for example, an email verification product)

  • Signals: signups from company domains; credit or plan limits hit; large list uploads; team invites. Off-product signals include companies hiring lifecycle, RevOps, or SDR roles and cold-email tools appearing in their stack.
  • Play: product-led outbound for usage signals, problem-led cold outbound for the rest. The outbound plays reference covers both.
  • Volume: usage signals are few but hot. Cold lists can be larger, but every send has to model the deliverability the product sells.

Account tiers

Tiers decide how much research and how many channels each account gets. Assign the tier before writing anything.

TierAccountsResearchChannelsCopy
Tier 1 (1:1)Top ~25–50 by fit and signalA full account brief (see account-research.md), mobile numbersEmail, LinkedIn, phone, video, possibly direct mailWritten per person; a human reviews every message
Tier 2 (1:few)Segments of 20–200 sharing one specific painSegment research plus one personal lineEmail + LinkedInWritten per segment, with a personal opener; a human reviews a sample
Tier 3 (1:many)Everyone else who fitsThe segment definition is the researchEmailWritten per segment; relevance comes from how tightly the segment is defined

Keep campaigns small. Several vendor and agency datasets show reply rates falling as campaign size grows, with campaigns of 50 or fewer recipients replying at roughly twice the rate of campaigns over 1,000.

Tools for detecting signals

Signal typeOptionsAgent access
Job postings and hiringTheirStack, PredictLeads, LinkedIn Jobs (manual)TheirStack has an MCP; PredictLeads has an API
Job changesUserGems, Clay job-change tracking, manual checks of past championsClay MCP
Website visitorsRB2B (US, person-level), Warmly, Vector, KoalaMostly webhooks into your CRM or a Zap
Social and community engagementTrigify, Common RoomBoth have APIs and MCPs
Funding and newsCrunchbase, news search, ExaExa MCP; Crunchbase API on paid plans
Tech stackBuiltWith, Wappalyzer, tech mentions in job postsAPIs
Product usageYour own analytics and billing eventsWebhooks into your CRM

See the tools registry for setup. A scheduled sweep of these sources is the signal-sweep loop in the marketing-loops skill.

Common mistakes

  • Treating any funding round as a buying signal for everything.
  • Opening with the signal itself ("Congrats on the raise"). Use it to choose the angle, then talk about their problem.
  • Acting on stale signals. A six-month-old job change is just a job.
  • Mentioning website visits that the prospect doesn't know were tracked. It reads as surveillance.
  • Running every account at the same depth. Tier first.

Other references

From the same skill.

View all 10 →

Related skills

More from the same category.

View all