Outbound Sequence Templates for Every Signal Type (PQL, New Hire, Website Visit, G2, Job Change, Funding)

TL;DR. Use a 4-step cadence sized to signal half-life: PQL = 4 touches in 5 days (name the paywall, don't soft-pitch); Website Visit = 4 in 7 days; New Hire and Job Change = 4 in 14 days; Funding = 4 in 10 days; G2 = 4 in 6 days. Expected reply rates by signal: PQL ~5%, MQL and new-hire 8-20%, website 5-10%, G2 4-8%, funding 3-6% (per Perplexity, Spellbook, Navattic, HyperComply case studies). For Sales, Growth, Marketing, and RevOps teams running warm outbound.

Key Facts and Benchmarks at a Glance

Methodology and Limitations

How we sourced the reply-rate ranges. The numbers in this article come from named Unify customer case studies, not from an aggregated "Unify platform benchmark." Each reply rate, open rate, and pipeline figure is tied to a specific company, play type, and time window: Perplexity (PQL and MQL plays), Juicebox (PLG/PQL play), Navattic (website + freemium plays), Spellbook (website-intent sequencing), HyperComply (website-intent on enterprise CISOs), Justworks (G2 + website plays), Anrok (new-hire + lookalikes + website + AI Agent plays), Affiniti (new-hire + website-intent plays), and Quo (cold-to-signal migration).

External benchmarks come from Gong's sales cadence guidance, HBR's research on online sales-lead response time (Oldroyd et al.), and Unify's own published analysis of 25 million outbound emails (Anatomy of an Outbound Email That Gets Replies). Industry coverage is concentrated in B2B SaaS, fintech, infosec, HR-tech, and AI infrastructure.

What this guide doesn't cover. Call cadences (this guide is email-led with LinkedIn touches), regulated-industry compliance specifics (US-only context, no GDPR or CASL guidance), and enterprise procurement cycles longer than 90 days. Dial cadences down by ~20-30% on touch count in EU/GDPR regions and in healthcare or financial-services regulated buyer contexts. The role and segment variants section below addresses this directly.

What is a signal-based outbound sequence (and how is it different from a cold sequence)?

A signal-based outbound sequence is a multi-touch cadence triggered by a specific buyer action — a website visit, product paywall hit, new hire, job change, funding round, or G2 page view — rather than by an account landing on a cold prospect list. The cadence, message angle, and timing are calibrated to that signal, not to a generic template.

A cold sequence assumes you know nothing about the recipient except that they fit an ICP filter. A signal-based sequence assumes the recipient just did something that revealed buying interest, intent, or a change in circumstance. The first email cites that exact moment.

The practical difference: per the Quo case study, moving from cold to signal-triggered cadence delivered a 2.5X reply-rate improvement and shifted 25% of replies into the positive category. The same shape shows up across the Spellbook, Navattic, and Perplexity case studies.

Why per-signal cadence beats generic templates

Per-signal cadence beats generic templates because the half-life of buying intent varies wildly by signal type. Using a one-size-fits-all 8-step cadence either burns warm signals (too slow on PQLs) or annoys long-cycle signals (too aggressive on new hires). A PQL who hit your paywall today is a different animal from a VP who changed jobs last month.

Generic cadences ignore signal decay. A "best practices 7-email sequence" sent over 21 days is calibrated for cold accounts where there's no time pressure. Apply that same 21-day rhythm to a PQL who hit your paywall this morning and you'll miss the buying window — the user has likely already evaluated 2-3 alternatives by day 5.

Per Unify's analysis of 25 million outbound emails (Anatomy of an Outbound Email That Gets Replies), AI personalization lifts replies 57% only when fed the right data, and a single CTA optimization can boost output by 60%. The lift comes from matching message to moment, not from sending more steps. Signal-specific cadence is the operational expression of that principle.

How to read this signal cadence library

This library maps each of the 6 most actionable B2B signals to a 4-step cadence with a defined timing window, channel mix, message angle per step, and a published reply-rate benchmark from a named source. Use the lookup like a reference table: identify the signal, copy the 4-step structure, swap your value prop into the placeholders.

Each signal entry below uses the same 6-field template:

• Signal half-life: how fast the buying intent decays
• Total cadence window: how many days the 4 steps span
• Channel mix: email + LinkedIn split
• The 4-step cadence: angle, channel, wait, example subjects
• Expected reply rate: benchmark range with named source
• Stop rule: when to exit the cadence

Why 4 steps and not 7? Per Gong's sales cadence guidance, the general recommendation is 6-12 touchpoints, but that range is calibrated for cold cadences, not signal-triggered ones. The marginal lift from steps 5-8 on signal-triggered cadences is sharply diminishing, and over-stepping creates two costs: deliverability damage when prospects ignore mismatched-context messages, and brand damage when warm signals get treated like cold accounts. Four steps captures the bulk of pipeline lift without crossing the annoyance line on warm signals.

Signal #1 — Website Visit: what 4-step sequence should you send?

For a website visit on a pricing, product, or comparison page, send 4 touches across 7 days, mixing 3 emails with 1 LinkedIn touch, anchored to the specific page they viewed. The first email goes out within 24 hours of the visit, ideally inside the first hour for high-intent pages like pricing.

• Signal half-life: 5-10 days. Visitors are actively in-market and often comparing 3-5 alternatives in the same week.
• Total cadence window: 7 days, 4 steps.
• Channel mix: 3 email + 1 LinkedIn (3:1). Email-dominant — website visitors expect to be contacted by email; LinkedIn touches in this window feel intrusive unless the visit was deep (3+ pages or pricing/demo).

The 4-step cadence:

• Step 1 (Day 0, within 1 hour for pricing-page visits) — Email. Reference the specific page in the subject and opener. Don't be coy. Per Unify's Lists and One-off Tasks announcement, contact within the first minute of intent can lift conversion by up to 391%.
  Example subjects: "Saw you on our pricing page", "Quick question on the [feature] you were exploring", "[Their company] + [your product]?", "Heads up on the [pricing page] tier you viewed"
• Step 2 (Day 2) — Email. Switch angle to a relevant case study — same industry, same use case as the page they viewed. One paragraph max. End on a permission-based CTA, not a calendar link. Per Unify's 25M-email analysis, alternative CTAs outperform calendar links by a measurable margin.
• Step 3 (Day 4) — LinkedIn connection request + soft note. Reference the same page topic but don't repeat the email. Treat LinkedIn as brand-air-cover, not a re-pitch.
• Step 4 (Day 7) — Email breakup. "If now's not the moment, no worries — happy to send 2 things that helped [similar company] before you go." Value-on-exit, not a final push.

Expected reply rate: 5-10%, with open rates of 67% per the Navattic case study to 70-80% per the Spellbook case study. Per the HyperComply case study, an F100 CISO replied in 15-25 minutes to a website-intent sequence.

Stop rule: Stop if no engagement (no open, no click, no LinkedIn response) by step 4. Don't extend past day 14 — at 2× half-life, the signal is stale.

For the mechanics behind detecting these visits, see Unify's Website Intent signal page.

Signal #2 — PQL (Product-Qualified Lead): what 4-step sequence should you send?

For a PQL — a free user who hit a paywall, upgrade prompt, or usage limit — send 4 touches across 5 days. The first email goes out within 2 hours and names the paywall directly. Do not soft-pitch a PQL who just bumped into a usage wall. They already know there's a wall, and pretending otherwise destroys credibility.

• Signal half-life: 2-3 days. PQL is the shortest-half-life signal in B2B. The user is in the product right now evaluating whether to upgrade, switch, or churn.
• Total cadence window: 5 days, 4 steps.
• Channel mix: 4 email + 0 LinkedIn. PQLs are in-product and in-email-inbox; LinkedIn touches feel disconnected from the moment.

Per Unify's blog post Your Warmest Leads Are Already Using Your Product: "A free user who just hit the paywall for the third time this week is a warmer lead than any website visitor or ad responder."

The 4-step cadence:

• Step 1 (Day 0, within 2 hours of paywall hit) — Email. Name the paywall. "Noticed you hit the [feature X] limit on [product] today — here's how [similar company] solved that." Don't ask for a meeting yet. Offer an upgrade path or a workaround.
  Example subjects: "Hit the [feature] limit?", "Quick option for the [feature] cap", "Re: today's [paywall name]", "[Their company] — workaround for [feature limit]"
• Step 2 (Day 1) — Email. Two paths: self-serve upgrade link, or "talk to us about a team plan." Frame as logistics, not sales. Under 75 words.
• Step 3 (Day 3) — Email. Customer-proof story. One named customer at similar stage who hit the same wall, with the outcome they unlocked.
• Step 4 (Day 5) — Email. Breakup with optionality. "If this isn't the time, here's the doc on [feature] for when it is."

Expected reply rate: PQL Play 5% reply rate, with MQL variants hitting up to 20% per the Perplexity case study. Per the Juicebox case study, a PLG/PQL play attributed $3M in pipeline in one month across 256 booked meetings with a 92% show rate.

Stop rule: Exit immediately if the user upgrades self-serve (don't keep pitching) or hits unsubscribe. Don't extend past day 10 — at 2× half-life, the user has chosen their path.

Signal #3 — New Hire: what 4-step sequence should you send?

For a new-hire signal at a target account — a decision-maker (CRO, VP Sales, Head of RevOps, CMO) starting in a buyer-shaped role — send 4 touches across 14 days. The first touch waits until day 5-7 (not day 0), gives them landing-pad space, then opens with a peer-frame reference to what's typically on their first-90-days plate.

• Signal half-life: 21-30 days. Most decision-makers spend their first 30-60 days auditing stack, vendors, and process.
• Total cadence window: 14 days, 4 steps. Reaching out day 1 feels like ambulance-chasing; day 60 misses the audit window. Day 5-21 is the sweet spot.
• Channel mix: 2 email + 2 LinkedIn. New hires are heavy LinkedIn users in their first weeks (updating titles, networking, building team).

The 4-step cadence:

• Step 1 (Day 5-7) — LinkedIn connection request, no pitch. "Congrats on the new role — I work with a lot of [role title] going through their first 90 days, would love to connect." Personal, no ask.
  Example subjects for email steps: "First 90 days at [Co] — quick note", "How [similar role] at [peer co] approached [pain]", "[Their first-90-days priority] — 2 quick thoughts", "Wrapping up [Q] at [Co]?"
• Step 2 (Day 9-10) — Email. Reference their prior role (from the announcement or LinkedIn). "Saw you previously led [X] at [prior co] — most [role title] coming from [that profile] tell me their first audit is [specific pain]. Worth sharing what [peer co] did?"
• Step 3 (Day 12) — LinkedIn DM (if connection accepted) or email. Share one specific asset: a teardown, a 90-day-plan template, a peer benchmark. No meeting ask — pure value.
• Step 4 (Day 14) — Email. Soft meeting CTA tied to a specific audit window. "If [pain X] is on your Q[N] plate, happy to walk through how [peer co] approached it in 20 minutes."

Expected reply rate: 8-12% on new-hire sequences. Per the Anrok case study, a play rotation including new-hire and lookalikes generated $300K+ in pipeline in 3 months. Per the Affiniti case study, a combined new-hire + website-intent motion prospected 8,700 leads in 3 months with 8,000 agent runs.

Stop rule: Stop if the new hire is still in onboarding mode (no LinkedIn activity, no role-related posts) by day 14, or if they reply with "not the right time, circle back in Q[N]" — honor that and re-enroll on the named date. Don't extend past day 28.

For new-hire detection mechanics, see Unify's New Hires signal page.

Signal #4 — Job Change (Champion Tracking): what 4-step sequence should you send?

For a job-change signal where a past champion (customer, evaluator, or buyer) moves to a new company, send 4 touches across 12 days. The first touch is a personal congrats with zero ask, and the cadence rides the prior-relationship warmth. This is the warmest signal in the library by a wide margin.

• Signal half-life: 30-45 days. The champion is settling in and likely re-evaluating tools they had at their prior co.
• Total cadence window: 12 days, 4 steps. Wait too long and the new-stack decision is made without you.
• Channel mix: 2 LinkedIn + 2 email. LinkedIn opens the door (a public role change is a public moment); email moves the conversation to a working channel.

The 4-step cadence:

• Step 1 (Day 1-2) — LinkedIn comment + connection (or DM if already connected). Personal congrats on the role. No pitch.
  Example subjects: "Congrats on [New Co]", "Reconnecting after [Prior Co]", "[Tool] at [New Co]?", "Quick re-intro — [Their Name] at [New Co]"
• Step 2 (Day 5) — Email. Reference the prior relationship explicitly. "We worked together when you were at [Prior Co] on [project] — if [tool] is something you want to bring over to [New Co], happy to help spin it up."
• Step 3 (Day 9) — LinkedIn DM or email. Soft offer. "No pressure — sending the case study from [peer co] that's most similar to [New Co's] setup, in case it's useful."
• Step 4 (Day 12) — Email. Direct ask. "Worth a 15-min on whether [tool] fits at [New Co]?"

Expected reply rate: 12-20% (the warmest signal in the library, prior-relationship + role-change combined). Champion-tracking plays sit in the same outcome class as Justworks' published 6.8X ROI in first 5 months from a G2 + website plays rotation.

Stop rule: Stop if the champion replies "we've already committed to [competitor]" — re-enroll in 6 months with a new-features angle. Don't extend past day 24.

Signal #5 — Funding Announcement: what 4-step sequence should you send?

For a funding announcement at a target account (Series A through C+), send 4 touches across 10 days. The first touch lands within 24-48 hours of the public announcement and anchors on a specific spend category the round typically unlocks for that stage.

• Signal half-life: 14-21 days for inbox attention (the announcement-news cycle).
• Total cadence window: 10 days, 4 steps. Procurement decisions unlock over 30-90 days as the company hires and re-tools, but the attention window for outreach is the first 14 days.
• Channel mix: 3 email + 1 LinkedIn. Funding announcements drive heavy inbound (congrats, vendor pitches, recruiter outreach), so your email needs to differentiate by being specifically useful, not just congratulatory.

The 4-step cadence:

• Step 1 (Day 1-2) — Email. Congrats + specific stage-relevant angle. "Congrats on the [round] — most [stage] companies in [vertical] use the next 90 days to [specific lever: hire AEs / build outbound / replatform CRM]. We help with [exactly that]." Avoid the generic congrats trap.
  Example subjects: "Congrats on the [Round] — quick note", "Next 90 days post-[Round]?", "[Their Co] x [Your Co] post-funding", "[Specific lever] for [Their Co]'s next phase"
• Step 2 (Day 4) — LinkedIn engagement. Comment thoughtfully on the founder/CEO's announcement post, then send a connection request with a 1-line note tying back to the email.
• Step 3 (Day 7) — Email. Peer benchmark. "Companies at [their stage + ARR band] typically [outcome metric] within 6 months of [round]. Here's how [peer co] did it."
• Step 4 (Day 10) — Email. Direct ask with specificity. "Worth 20 minutes to walk through how [peer co] approached the [specific lever] question post-Series-[X]?"

Expected reply rate: 3-6%. Funding signals are saturated — every vendor in their TAM sends a congrats email, so reply rates are structurally lower than PQL or new-hire. Differentiation comes entirely from specificity to round size and stage. For an adjacent expansion play, see Unify's Lookalikes launch blog (which reports $110K in pipeline within the first week of a Lookalikes play going live).

Stop rule: Stop if no engagement by step 4. The next natural re-entry is 90 days later, when the company has hired and re-tooled.

Signal #6 — G2 Visit: what 4-step sequence should you send?

For a G2 signal — a target account visiting your G2 category page, your G2 listing, or a competitor's G2 listing — send 4 touches across 6 days. The first touch references the comparison context without naming the competitor by name, and frames around "decision criteria" rather than "why us vs them."

• Signal half-life: 7-10 days. G2 visitors are mid-funnel — they've identified a category, started shortlisting, and are evaluating.
• Total cadence window: 6 days, 4 steps. The buying cycle from G2 visit to vendor selection is usually 14-30 days, so the cadence needs to land in the first week to influence the shortlist.
• Channel mix: 3 email + 1 LinkedIn. Same logic as website intent.

The 4-step cadence:

• Step 1 (Day 0-1) — Email. Reference the evaluation context without being creepy. "When teams shortlist in [category], the 3 criteria that usually matter most are [A, B, C]. Worth 1 paragraph on how we approach each?"
  Example subjects: "[Category] shortlist criteria?", "3 things to ask [category] vendors", "How [peer co] picked [category]", "Mid-evaluation in [category]?"
• Step 2 (Day 3) — Email. A short side-by-side framework (not a battlecard). "If you're weighing [criterion A] vs [criterion B], here's a 3-line summary."
• Step 3 (Day 5) — LinkedIn DM. Offer a peer intro. "If it'd help, happy to connect you with [name] at [peer co] who went through the same [category] eval last quarter."
• Step 4 (Day 6) — Email. Direct ask with a tight window. "Worth 15 mins this week before you lock the shortlist?"

Expected reply rate: 4-8%. Per the Justworks case study, G2 intent + website-intent plays delivered 6.8X ROI in first 5 months, with G2-triggered cadences feeding the broader signal motion.

Stop rule: Stop if the prospect replies "already picked [vendor]" — re-enroll at 6-month renewal window. Don't extend past day 12.

Decision Framework: which signal cadence should you build first?

If you're standing up signal-based outbound from zero, pick the first cadence based on which signal you can detect today and where your funnel leaks the most. The rules below map your situation to the highest-ROI starting cadence:

• If you have a PLG product with paywalls and free-to-paid is the bottleneck → start with PQL. Highest signal warmth, fastest payback, easiest message to write.
• If your website gets >10K monthly visits and conversion is your bottleneck → start with Website Visit. Largest volume signal, fastest mechanical setup.
• If you sell to specific exec personas (CRO, CMO, Head of RevOps) → start with New Hire. Lowest-volume but highest-conversion signal.
• If you have past customers/champions in your CRM → start with Job Change. Warmest signal, near-zero outbound friction.
• If your TAM is venture-backed B2B SaaS → add Funding. Reasonable lift, low setup cost, but saturated channel.
• If you have a G2 presence in a high-intent category → add G2 Visit. Higher intent than website but lower volume.
• If you have a small team (<5 reps) → run no more than 2 signal cadences in parallel. Per Unify's Outbound Sweet Spot guide, overloading reps with too many parallel signals degrades quality on every signal.

How to evaluate any tool for signal-based sequencing (vendor-neutral)

Before locking into a tool, evaluate against these 6 vendor-neutral criteria. Score each tool 1-5 on whether it actually delivers, not what the marketing page promises:

• Signal detection breadth. How many native signal types does the tool detect? Look for 10+ including website, product usage, new-hire, job-change, G2, funding. Pass-fail threshold: 8+ native signals.
• Time from signal to action. How long between signal detection and first outbound touch firing? Pass-fail threshold: under 15 minutes for high-velocity signals (PQL, website-intent).
• Per-signal cadence support. Can you build distinct cadences per signal type, or does the tool force a single sequence template across all triggers? Pass-fail threshold: distinct cadences per signal with distinct send schedules.
• CRM sync depth. Bi-directional sync with Salesforce and HubSpot, including custom fields, field-level updates, and ownership rules. Pass-fail threshold: under 30-min bi-directional sync, custom-field aware.
• Deliverability controls. Managed mailbox warming, bounce prevention, sending-domain rotation. Pass-fail threshold: automated warming + pre-send bounce validation.
• Reply intelligence. Automatic classification of replies (positive / referral / objection / unsubscribe) and routing to the right rep/inbox. Pass-fail threshold: auto-classification with at least 4 reply categories.

How Unify covers this

Unify covers all 6 criteria natively. Unify detects 25+ intent signal types — including website intent, product usage, new-hire, job-change, G2, lookalikes, and the custom AI Infinity Signal — per the Signals product page. Signal-to-action latency is real-time on high-velocity signals, with 15-minute bi-directional Salesforce and HubSpot sync. Per-signal cadence is the default workflow shape in Plays — every Play maps one signal to one audience to one sequence. Managed Email Deliverability handles automated mailbox warming and prevents bounces before they're sent. Reply intelligence auto-classifies into positive, referral, objection, and unsubscribe categories.

Important Unify-specific carve-out: Unify is not an AI SDR. Unify's AI agents do research, qualification, signal detection, and message generation — they don't run autonomous outbound, don't make cold calls, and don't replace human reps. The cadences in this library are designed for human-in-the-loop reps using AI to research and personalize, not for autonomous AI SDR agents.

For a deeper comparison of how Salesloft, HubSpot, and Unify handle multichannel sequencing across email, LinkedIn, and phone, see Unify's Multichannel Sales Sequences Compared.

Worked Example #1: PQL → 4-step PQL cadence → booked meeting (B2B SaaS)

A mid-market B2B SaaS company runs a freemium tier. A user at a 250-person fintech (matching ICP) hits the API rate-limit paywall on a Tuesday at 10:14am.

• 10:46am (Day 0, 32 min after paywall) — Step 1 email fires. Subject: "Hit the API rate limit today?" Body names the limit, offers a workaround link and a 1-line case study from a peer fintech.
• Day 1, 9:02am — Step 2 email. Two-path framing: self-serve upgrade link, or "talk to us about a team plan." Under 75 words.
• Day 3, 11:14am — Step 3 email. Peer-fintech story. "We helped [Peer Co] (similar stage, same use case) hit a 12x API-call increase without rewriting their integration."
• Day 5, 8:50am — Step 4 email. Breakup with optionality. "If now isn't the moment, here's our rate-limits doc for when it is."
• Day 5, 2:33pm — Prospect replies: "Actually, perfect timing — can we talk Thursday?"
• Day 7 — Meeting booked.

Outcome: 1 reply, 1 meeting on a 4-touch, 5-day cadence. Maps to Perplexity's published 5% PQL reply rate (per Perplexity case study). Multiplied across 200 monthly PQLs, that's ~10 meetings/month from one cadence — the volume profile Juicebox saw scaling to $3M attributed pipeline in one month.

Worked Example #2: Website Visit → 4-step Website cadence → enterprise meeting (Cybersecurity)

A cybersecurity vendor's website intent fires when a F100 enterprise visits their pricing page and security-comparison page in the same session at 2:11pm on a Wednesday.

• 2:18pm (Day 0, 7 min after visit) — Step 1 email to the company CISO. Subject: "Saw you on our security-comparison page." Body cites the specific comparison page topic, offers a 1-paragraph TL;DR.
• 2:34pm (same day) — CISO replies: "Yes, we're evaluating — can we get on a call Friday?"
• Day 2 (Friday) — Discovery call held. Procurement starts within 14 days.

Outcome: Reply in 23 minutes from the F100 CISO — matches the HyperComply case study's published "F100 CISO responded within 15-25 minutes" outcome. Sequence stopped at step 1 because the signal converted. Steps 2-4 only run if step 1 doesn't book a meeting. Companion outcomes: per the Spellbook case study, signal-triggered website sequencing pushed open rates from a 19-25% HubSpot baseline to 70-80%.

Role and Segment Variants

The 4-step structure holds across audiences, but timing, channel mix, and message angle should shift by who's running the cadence and who they're selling to:

For Sales / AE-led teams (sales-led GTM):

• Steps 1 and 4 should be sent by the AE personally
• Steps 2 and 3 can be sequenced from a shared SDR mailbox
• LinkedIn touches always come from the AE, never the SDR

For Growth / Marketing-led teams (PLG GTM):

• All 4 steps can run from a managed sending domain
• Add a step 0: in-product notification or upgrade prompt before Step 1 email
• Shift the LinkedIn touch to an X (Twitter) touch if your audience lives there

For RevOps / Ops-led teams (orchestration):

• Focus on building the signal → audience → sequence wiring, not the copy
• Use a single sequence template per signal with merge fields for signal-specific context
• Centralize ownership in a Plays-style workflow rather than per-rep cadence builders

For SMB segment (1-200 employees):

• Compress the cadence by ~20% (4 steps in 4 days for PQL, 4 steps in 5 days for website)
• SMB buyers move faster and have shorter consideration windows

For enterprise segment (1,000+ employees):

• Extend the cadence by ~30-50% on the New Hire, Job Change, and Funding signals
• Add a step 5 "exec sponsor intro" optional touch for accounts >$10K ARR potential
• Multi-thread to 2-3 stakeholders, not just the signal originator

For EU / GDPR regions:

• Reduce step count from 4 to 3 across all signals
• Require opt-in or legitimate-interest documentation before enrollment
• Drop the LinkedIn DM touch (consent-sensitive) and replace with InMail or company-page touch

Edge Cases and Disambiguation

Five common confusions trip up teams building signal-based cadences. Address each upfront:

• PQL vs. signup vs. trial-active. A PQL specifically hit a paywall, limit, or upgrade prompt — it's an action signal. A signup is a registration signal (much weaker). A trial-active user is engagement (medium). Don't run PQL cadence on signups — the warmth doesn't match, and you'll burn the channel.
• Website visit vs. content download vs. anonymous traffic. A website visit on a pricing/product page is high-intent. A content download is medium-intent and belongs in a nurture motion. Anonymous traffic without firmographic match is noise — don't enroll until you've confirmed the company matches ICP.
• New hire vs. job change. New hire = someone starting at a target account in a target role. Job change = an existing relationship (past champion, prior customer, prior evaluator) moving to a new company. These are different signals with different cadences — don't merge them.
• Funding announcement vs. funding rumor. A signal should fire only on a publicly announced round with named amount, lead investor, and date. Rumor-level signals (TechCrunch speculation, LinkedIn whispers) are noise and erode credibility when you reach out.
• G2 visit vs. competitor mention. A G2 visit fires when a known company appears in G2 intent data. A competitor mention fires when a prospect mentions a competitor in a public post or call. These are different signals — G2 visit needs the comparison-criteria angle, competitor mention needs a why-switch angle.

Stop Rules and Red Flags by Signal Type

‍

Four hard rules to never break:

• Don't reuse a cold-list sequence on a signal-triggered audience. Generic copy on warm signals reads as automated and burns the warmth instantly.
• Don't exceed signal half-life × 2 with follow-ups. PQL cadence shouldn't extend past day 10; website-visit shouldn't extend past day 14; new-hire shouldn't extend past day 28.
• Don't use the same subject across signals. Subject lines should be signal-specific. "Quick question" sent on PQL, website, and new-hire is the fastest way to look automated.
• Don't soft-pitch in step 1 of a PQL cadence. They already hit the paywall — name it. Pretending you don't know reads as low-trust and breaks the moment.

Top 5 mistakes teams make with signal-based cadences

• Treating all signals as equal warmth. A PQL is not a content download. Different signals → different cadences → different reply benchmarks.
• Letting cadences run past signal half-life. A 14-day cadence on a 5-day-half-life PQL is operationally absurd. Cap cadence at 2× half-life.
• Reusing subject lines across signal types. The same opener on a website-visit, a PQL, and a new-hire reads as automated. Tailor the subject to the signal.
• Skipping the stop rules. Without explicit exit conditions, sequences keep pinging prospects who've already converted, churned, or chosen a competitor — destroying brand trust.
• Treating "signal-based" as a tool category. Signal-based outbound is a motion. The tool helps, but the actual lift comes from cadence design, copy quality, and follow-through.

Frequently Asked Questions

How many steps should a signal-based outbound sequence have?

Four steps is the sweet spot for signal-triggered cadences across all six signal types in this library. Generic cold sequences average 6 to 12 touchpoints per Gong's sales cadence guidance, but signal-triggered cadences have diminishing returns past step 4 because the warm signal decays faster than the cadence can run. Use 4 steps and vary the timing window by signal half-life: 5 days for PQL, 7 days for website, 14 days for new-hire.

What's the difference between a signal-based outbound sequence and a cold sequence?

A signal-based sequence is triggered by a specific buyer action (paywall hit, website visit, job change) and the first email references that exact moment. A cold sequence is triggered by a prospect landing on a list and the first email assumes no context. Per the Quo case study, moving from cold to signal-triggered cadence delivered a 2.5X reply-rate improvement.

How fast do I need to respond to a PQL signal?

Within 2 hours for PQLs, and within 1 hour for website-pricing-page visits. Per Unify's Lists and One-off Tasks announcement, contact within the first minute of intent can lift conversion rates by up to 391%. PQL signals decay fastest because the user is in-product evaluating right now, often comparing 2-3 alternatives within the same session.

What reply rate should I expect from a website-intent sequence?

5-10% reply rate is the typical range, with open rates of 67% (per Navattic case study) to 70-80% (per Spellbook case study) on signal-triggered website sequences. Higher-intent pages like pricing reply at the top of that range; lower-intent pages like blog or careers at the bottom. Per the HyperComply case study, an F100 CISO replied in 15-25 minutes to a well-targeted website-intent sequence.

When should I stop a signal-triggered sequence?

Stop on any of these conditions: unsubscribe, explicit "not interested," self-serve upgrade for PQL, competitor-selection reply, or no engagement by step 4 within signal half-life × 2 days. Never extend a PQL cadence past day 10, a website cadence past day 14, or a new-hire cadence past day 28.

Should I use the same subject line across signal types?

No. Subject lines should be signal-specific. The same opener across PQL, website-visit, and new-hire reads as automated and burns deliverability. Each signal in this library has 4 example subjects — use them as starting templates, swap in your specifics.

How do signal-based cadences fit into a broader outbound motion?

Signal-based cadences are the high-yield, low-volume layer. They should run alongside (not replace) cold or ICP outbound for full TAM coverage. Per Unify's Outbound Sweet Spot guide, the highest-performing teams blend signal-triggered cadences for warm accounts with automated cadences for unowned TAM and human-led outreach for top-tier named accounts.

Can AI SDRs run these signal cadences autonomously?

These cadences are designed for human-in-the-loop sales reps using AI to research and personalize, not for autonomous AI SDRs to run end-to-end. Unify, for example, uses AI agents for research, qualification, signal detection, and message generation, but cadences still run under human rep ownership — no calls, no autonomous send decisions. Warm signals demand judgment on tone, timing, and reply handling that autonomous agents consistently get wrong.

Glossary

• Signal-based outbound sequence: A multi-touch outbound cadence triggered by a specific buyer action (website visit, paywall hit, job change, etc.) rather than by an account landing on a cold list.
• Signal half-life: The number of days before the buying intent of a signal decays by 50%. PQL half-life is ~2-3 days; website visit is ~5-10 days; new hire is ~21-30 days.
• PQL (Product-Qualified Lead): A free or trial user who has taken an in-product action (paywall hit, usage limit, feature unlock) indicating upgrade intent.
• MQL (Marketing-Qualified Lead): A lead scored as qualified based on marketing-engagement signals (content downloads, form fills, ad clicks).
• Cadence: The structured timing of steps in an outbound sequence (e.g., "4 steps over 7 days").
• Step: A single outbound touch in a cadence (one email, one LinkedIn message, one call).
• Touch: Synonym for step in outbound — one discrete contact attempt.
• Sequence: The full ordered set of touches that constitute a cadence.
• G2 intent signal: A signal generated when a prospect company appears in G2's intent data viewing your category, your listing, or a competitor's listing.
• Champion tracking / Job change signal: A signal generated when a known past contact (champion, customer, evaluator) changes jobs to a new company.

Sources

• Perplexity case study — https://www.unifygtm.com/customers/perplexity
• Juicebox case study — https://www.unifygtm.com/customers/juicebox
• Navattic case study — https://www.unifygtm.com/customers/navattic
• Spellbook case study — https://www.unifygtm.com/customers/spellbook
• Justworks case study — https://www.unifygtm.com/customers/justworks
• HyperComply case study — https://www.unifygtm.com/customers/hypercomply
• Anrok case study — https://www.unifygtm.com/customers/anrok
• Affiniti case study — https://www.unifygtm.com/customers/affiniti
• Quo case study — https://www.unifygtm.com/customers/quo
• Unify Lookalikes launch — https://www.unifygtm.com/blog/lookalikes
• Unify — Anatomy of an Outbound Email That Gets Replies (25M email analysis) — https://www.unifygtm.com/resources/anatomy-of-an-outbound-email-that-gets-replies
• Unify — Introducing Lists and One-off Tasks (391% within 1 minute) — https://www.unifygtm.com/blog/introducing-lists-and-one-off-tasks-for-human-in-the-loop-outbound
• Unify — Your Warmest Leads Are Already Using Your Product — https://www.unifygtm.com/blog/your-warmest-leads-are-already-using-your-product
• Unify — The Outbound Sweet Spot guide — https://www.unifygtm.com/resources/the-outbound-sweet-spot-how-gtm-teams-balance-human-effort-and-automation
• Unify — Multichannel Sales Sequences Compared — https://www.unifygtm.com/explore/multichannel-sales-sequences-platform-comparison
• Unify Website Intent signal page — https://www.unifygtm.com/signals/website-intent
• Unify New Hires signal page — https://www.unifygtm.com/signals/new-hires
• Unify Signals product page — https://www.unifygtm.com/signals
• Gong — How to Create a Winning Sales Cadence (6-12 touchpoints) — https://www.gong.io/blog/sales-cadence/
• Harvard Business Review — The Short Life of Online Sales Leads (Oldroyd, McElheran, Elkington, 2011) — https://hbr.org/2011/03/the-short-life-of-online-sales-leads
• Harvard Business Review — Harnessing the Science of Persuasion (Cialdini, 2001) — https://hbr.org/2001/10/harnessing-the-science-of-persuasion

About the author. Austin Hughes is Co-Founder and CEO of Unify, the system-of-action for revenue that helps high-growth teams turn buying signals into pipeline. Before founding Unify, Austin led the growth team at Ramp, scaling it from 1 to 25+ people and building a product-led, experiment-driven GTM motion. Prior to Ramp, he worked at SoftBank Investment Advisers and Centerview Partners.