There's no shortage of content about buying signals. You can find posts explaining what they are, why they matter, and which ones to track. But when it comes time to actually do something with a signal, most teams are winging it. A rep sees an alert, makes a judgment call, fires off a generic email. Maybe they follow up, maybe they don't. There's no system.
The gap isn't awareness. It's activation. Teams know signals exist. What they don't have is a clear, documented answer to the question: "When this specific signal fires, what exactly happens next?"
That's what a signal playbook solves. It connects every signal to a specific action, a specific owner, and a specific timeline. No ambiguity, no guesswork, no dropped accounts.
This post gives you a working template you can fill in today. We'll walk through the structure, show you how to build one for the most common B2B signals, and share a few patterns that separate teams who respond to signals from teams who run plays off them.
What a Signal Playbook Actually Is
A signal playbook is a documented set of rules that maps a buying signal to a specific response. It answers five questions for every signal your team monitors:
- What fires? The signal itself, with specific criteria.
- Who qualifies? The ICP filters that determine whether this signal is worth acting on.
- What happens? The exact action taken: email, call, Slack alert, CRM update, ad retarget.
- Who owns it? The person or team responsible for executing.
- How fast? The SLA for the response, from signal to action.
If you can't answer all five for a given signal, that signal isn't operationalized. It's just noise with a label.
The format is simple. Each play reads like a sentence:
When [signal fires] for [ICP criteria], then [action] by [owner] within [SLA].
That's it. No flowcharts, no decision trees, no complicated branching logic. If a signal needs eight conditional steps before someone acts on it, the signal is probably too vague or the play is overengineered. Keep it tight.
The Template: Six Signals, Six Plays
Here are six common B2B buying signals with example playbooks for each. Adapt the specifics to your ICP, your product, and your team size.
1. New Hire in a Target Role
The signal: A company in your ICP just hired someone into a role that typically buys your product. Think VP of Security at a mid-market fintech, or Head of Revenue Operations at a Series B SaaS company.
Why it matters: New hires in decision-making roles have budget pressure and a mandate to make changes. They're building their stack, often from scratch. The first 90 days is when they're most open to conversations, and most likely to sign off on new tools.
Example play:
When a company in our ICP hires a [VP of Security / Head of RevOps / Director of Engineering] and the company has 100-2,000 employees, then enroll the new hire in a 3-touch welcome sequence by the account owner within 48 hours of the signal.
Sequence angle: Reference their new role, acknowledge the transition, and offer something useful for someone in their first month. Not a demo pitch. A relevant resource, a benchmark report, a quick intro call framed around helping them assess the landscape. The goal is to be the first vendor who's actually helpful, not the fifteenth who sends a congratulations email followed by a calendar link.
2. Pricing Page Visit
The signal: A known or identified contact from a target account visits your pricing page.
Why it matters: Pricing page visits are one of the strongest bottom-of-funnel intent signals in B2B. Someone is comparing options and trying to figure out whether your product fits their budget. This is active evaluation, not passive browsing.
Example play:
When a contact from a target account visits the pricing page and they've visited 3+ pages in the last 7 days, then send a Slack alert to the account owner with full context and enroll the contact in a pricing-specific 2-touch sequence within 1 hour.
Sequence angle: Don't pretend you don't know they were on the pricing page. Be direct. "I noticed you were checking out our pricing. Happy to walk you through what most teams in [their industry] end up choosing. Takes about 15 minutes." Directness builds trust. Coyness does the opposite.
3. Champion Job Change
The signal: A past customer, power user, or champion left their company and joined a new one.
Why it matters: A champion who already knows and trusts your product is the single warmest lead your team will ever get. They've already been through the evaluation, the onboarding, and the internal selling process once. If they land somewhere that fits your ICP, they're likely to bring your product with them.
Example play:
When a champion or past buyer moves to a new company and the new company fits our ICP, then send a personal congratulations email from the original AE or CSM within 72 hours, and add the new company to the target account list.
Sequence angle: This one should feel personal, because it is. "Congrats on the new role at [company]. We loved working with you at [old company]. If you're building out your stack there, happy to pick up where we left off." No automation templates here. A real, short, human email from someone they actually know.
4. Competitor Mention or Comparison Research
The signal: A contact at a target account searches for or visits content comparing your product to a competitor, or mentions a competitor in a public forum, community, or social post.
Why it matters: This buyer is actively evaluating. They're in the consideration phase, which means the window is open but it's closing. Every day you wait is a day the competitor's sales team might be further along in the conversation.
Example play:
When a contact at a target account engages with competitor comparison content or mentions a competitor in a public channel, then enroll them in a competitive displacement sequence by the account owner within 24 hours, and flag the account for priority outreach.
Sequence angle: Lead with differentiation, not FUD. "I saw you're evaluating tools in [category]. A lot of teams compare us to [competitor]. The biggest difference is [one clear differentiator]. Happy to show you in 15 minutes." Be specific. One clear reason why you're different, backed by proof, is worth more than a ten-slide battlecard.
5. Funding Round or Expansion Announcement
The signal: A company in your ICP announces a fundraise, an acquisition, or a major expansion.
Why it matters: Capital events create buying urgency. A company that just raised a Series B has a mandate to grow, and they need the tools to do it. An acquisition creates integration challenges and new technology needs. Expansion announcements signal headcount growth, which means new users, new teams, and new budgets.
Example play:
When a target account announces a funding round of $10M+ or a major expansion, then enroll the VP/Director-level contacts in a growth-timing sequence by the SDR team within 1 week.
Sequence angle: Tie your outreach to the expansion, not the fundraise itself. "Congrats on the round. A lot of teams at your stage start investing in [your category] around this point. We've helped [similar company] do [specific outcome]. Worth a quick conversation?" The funding is the trigger, but the value prop is about what they're going to do with the money.
6. Custom AI Signal (Industry-Specific Trigger)
The signal: A company publishes a blog post, changelog, SEC filing, or press release that matches a custom trigger you've defined. For example: "enterprise SaaS companies announcing a migration from on-prem to cloud infrastructure."
Why it matters: These are the signals nobody else is monitoring. While every sales team in B2B has access to the same funding round and job posting data, custom AI signals detect buying motion that's specific to your product and your market. A company disclosing compliance gaps in a 10-K. An enterprise quietly deprecating a legacy tool in their changelog. A prospect announcing a strategic initiative that maps directly to your use case.
Example play:
When a custom AI signal fires for a target account and the signal is verified by ICP and intent scoring, then auto-enroll the best-fit contact in a signal-specific sequence with the trigger context embedded, and alert the account owner via Slack within 30 minutes.
Sequence angle: This is where personalization gets real. Because the signal comes with full context (what was detected, where it was found, why it matters), the outreach practically writes itself. "I saw [company] just announced [specific initiative]. We've helped teams going through the same transition do [specific outcome]. Would it be useful to compare notes?" That's not a template. That's a relevant conversation starter grounded in something the prospect actually said or published.
How to Put Your Playbook Together
You don't need to build all six plays at once. Start with the one or two signals that are most relevant to your sales motion, document them in the template format, and run them for two weeks before adding more.
Here's a practical way to get started:
Step 1: Pick your top signal. Look at your last ten closed-won deals. What was the trigger that started the conversation? A job change? A pricing page visit? A referral? That's your first play.
Step 2: Write the play in one sentence. Use the "When / For / Then / By / Within" structure. If you can't fit it in one sentence, the play is too complicated. Simplify.
Step 3: Assign an owner. Every play needs a name next to it. If no one owns it, no one runs it.
Step 4: Set the SLA. Be specific. "ASAP" is not an SLA. "Within 4 hours during business hours" is. The SLA should reflect the signal's urgency. A pricing page visit needs a faster response than a funding announcement.
Step 5: Build the sequence. Write 2-3 touches that reference the signal directly. Don't use generic templates. The whole point of a signal playbook is that the outreach is specific to what triggered it.
Step 6: Review and iterate. After two weeks, check the numbers. Which plays generated replies? Which ones got ignored? Cut the losers, double down on the winners, and add your next signal.
A Note on Automation
You can run signal playbooks manually. Plenty of teams do, especially at the early stage. But the real value unlocks when the plays run themselves.
When a signal fires and the right contact is automatically enrolled in the right sequence, with the trigger context already embedded in the messaging, you've removed the gap between awareness and action entirely. That's the difference between "we track signals" and "we run plays off signals."
Tools like Avina are built to close that gap. When a signal fires, Avina can automatically find the right contact, enrich their data, score the account for ICP fit, and enroll them in a sequence with the signal context baked in. No manual handoff, no lag, no dropped accounts. But whether you automate with a tool or run the plays by hand, the playbook itself is what matters most. The system of "signal fires, this happens next" is the competitive advantage. The tool just makes it faster.
Why Playbooks Beat Ad Hoc Signal Response
The teams that consistently turn signals into pipeline aren't doing anything magical. They're not tracking more signals, and they're not using better data. They're just more systematic about what happens after a signal fires.
A playbook forces your team to make decisions in advance: which signals matter, who acts on them, how fast, and with what message. Those decisions, made once and documented clearly, compound over time. Reps stop guessing. Managers stop micromanaging. And accounts stop slipping through the cracks because someone was "going to follow up on that."
Your first playbook doesn't need to be perfect. It needs to exist. Write one play this week, run it for two weeks, and iterate from there. That's the whole framework.
Want help building signal playbooks for your team? Reach out at hello@avina.io. We're happy to brainstorm, even if you're not using Avina.
More from the blog
Give your team the edge they need.
Get started in just 30 min and unlock your hidden pipeline with Avina.