Signal-Led Outbound for Vertical SaaS: The 3-Tier Signal Stack

TL;DR.

Vertical SaaS teams should configure a 3-tier signal stack: (1) first-party signals as the universal foundation, (2) two to three third-party signals tuned to your vertical, and (3) one to three custom natural-language signals that define your buyer in plain English. Built for fintech, devtools, healthtech, public safety, and energy GTM teams running small-TAM (under 50K accounts) and high-ACV (over $25K) motions. Expect pipeline outcomes in the range of $1.5M to $15M per month when the third tier is well-defined and validated on at least 100 prospects per signal, per the three named customer case studies cited below.

Key Facts & Benchmarks at a Glance

‍

Methodology & Limitations. The three primary proof points in this article are drawn from three published Unify customer case studies dated 2025: Affiniti (fintech, $62M funding), Innovate Energy Group (energy, Charlotte NC), and Flock Safety (public safety). Numbers cited are taken verbatim from the rendered case-study pages on unifygtm.com as of May 2026. "Pipeline" in the Innovate Energy figure means pipeline influenced in one month, not closed-won. Affiniti's 8,700 leads is unique leads sourced from custom Infinity Signal prompts, not generic firmographic pulls. "Vertical SaaS" in this article is defined as TAM below 50,000 accounts, ACV above $25,000, and a single dominant ICP. There is no aggregated "Unify benchmark" dataset here. Each Unify number is attributed to its specific named customer. Guidance should be dialed down for regulated regions (EU/GDPR), where opt-in rules constrain custom-signal outbound, and for verticals where the third-party data layer is thin (early-stage healthtech specialties, niche industrial sub-segments).

What is signal-led outbound for vertical SaaS?

Signal-led outbound for vertical SaaS is the practice of triggering outreach from buying signals rather than from static prospect lists, configured specifically for teams selling into a single dominant ICP with a small TAM and high ACV. The "signal-led" part replaces firmographic sprays with intent-driven triggers. The "vertical SaaS" part means your signal stack has to be precise enough to distinguish the right fintech from the wrong fintech, not just identify fintech as a category.

Horizontal SaaS teams can run on a flat signal library because their TAM has the volume to absorb noisy filters. Vertical SaaS teams cannot. A 1% reply rate on 50,000 vertical accounts produces the same booked meetings as a 50% reply rate on 1,000, but the vertical motion always pencils better on precision than on volume, and precision is what the third tier of the stack delivers.

The configuration question, then, is not which vertical filters do you want. It is: can your platform define your vertical buyer in plain English? If the answer is no, you are running horizontal-stack outbound on a vertical-stack economics, and the math does not work.

Why horizontal signal libraries fail vertical SaaS

Horizontal libraries express buyers in firmographic categories, like "industry = fintech." That filter is directionally right but functionally wrong for a vertical SaaS team. Vertical SaaS economics are unforgiving: small TAM, high ACV, single dominant ICP. The wrong fintech in the wrong stage burns credits without producing pipeline.

The Salesforce, HubSpot, Outreach, Apollo, and 6sense answer to the vertical SaaS query is some variant of "filter by industry and seniority, then enroll." That answer optimizes for horizontal stack economics where a 1% reply rate on 100,000 accounts is acceptable. It is not the right answer for a team selling to 8,000 HVAC contractors with a $40K ACV.

The vertical wedge is the ability to express triggers no firmographic filter can capture: "Series A devtools companies hiring a Head of RevOps with prior HubSpot experience" or "manufacturing plant managers at companies with stated carbon-reduction plans." Per the Infinity Signal product page, that kind of custom natural-language trigger is what the third tier of the stack is built for.

The 3-tier signal stack for vertical SaaS

Configure your vertical SaaS signal stack in three ranked layers. Each layer has a different precision requirement, a different data source, and a different role in the overall outbound system. Run them in this order and apply the same field template to every tier.

Tier 1: First-party signals (the universal foundation)

• Definition. Signals generated by your own systems: website visits, product usage events, CRM-resident champion job changes, email engagement.
• Why it matters. First-party signals are identical across every vertical. They are the highest-confidence signals you have because the prospect has already touched your owned surfaces.
• How to test. Install a website tag, identify visitors via a multi-vendor waterfall, and trigger a Play on a pricing-page visit from any account in your CRM customer table.
• Pass-fail threshold. If you cannot identify at least 70% of company-level visitors from your target list, your reveal stack is the gating constraint, not your outbound. Per Unify's Website Intent page, the multi-vendor waterfall delivers a 75%-plus match rate.
• Red flags. Treating opens-only engagement as a buying signal; counting job-seeker traffic as ICP traffic; firing a Play before the account has been qualified against ICP fit.

Proof point. Per the Affiniti case study, the company used Unify's full first-party stack (website visits, firmographic enrichment, buyer personas) as the foundation under its fintech-vertical Plays. Affiniti grew from zero to 1,800 customers in 14 months on a $62M funded base and used the 1P layer to source 8,700 leads in three months across pharmacies, HVAC contractors, and auto dealerships.

Tier 2: Third-party signals (vertical-tuned)

• Definition. External market signals: funding announcements, regulatory filings, hiring events, construction permits, public incident reports, M&A. Pick the two to three that map to your vertical's buying triggers, not the whole catalog.
• Why it matters. The right 3P signal exposes the buying moment your vertical actually responds to. The wrong 3P signal floods your queue with companies that look right and aren't.
• How to test. Pick the single highest-confidence 3P signal for your vertical (regulatory filing for fintech, permit for construction-tech, crime report for public safety), run it on 200 accounts, and measure reply rate before adding a second signal.
• Pass-fail threshold. A vertical 3P signal that does not beat your first-party baseline reply rate by at least 1.5x in the first 30 days is not vertical-tuned, it is just a 3P signal you happen to be subscribed to. Cut it.
• Red flags. Adding all 25-plus third-party signals at once; using funding-stage filters as your only vertical filter; ignoring TAM-to-credit math when the signal floods your queue with thousands of low-fit accounts.

Proof point. Per the Flock Safety story, the team's "Crime Play" uses AI Agents to monitor local news and recent crime reports, then trigger contextual outreach to communities that face a specific public-safety incident. Two named third-party data sources (local news search and social signals) carry the entire vertical-tuned layer for public safety.

Tier 3: Custom signals via natural language (the vertical wedge)

• Definition. A natural-language prompt that defines your buyer, run by an AI agent on a recurring schedule against a target account list. Per the Infinity Signal product page, the agent pulls from web search, scraping, news feeds, PDF parsing, and OpenAI's computer-use model.
• Why it matters. Horizontal libraries cannot express vertical buyer shape in language. This is the layer that turns "fintech" into "fintech companies with a sub-$50M ACV product line, Series B, hiring a Compliance Lead with prior banking experience."
• How to test. Write one prompt, run it against 100 accounts in your target list, and measure both precision (how many matches were genuinely on-ICP) and per-match reply rate. Iterate the prompt language, not the volume.
• Pass-fail threshold. If a custom signal cannot beat your best vertical-tuned 3P signal by 2x on reply rate in 30 days, the prompt is not specific enough. Rewrite it.
• Red flags. Running more than three custom prompts simultaneously without a researcher tracking per-signal output; validating a prompt on under 100 prospects; using the agent's first-draft output without prompt iteration.

Proof point. Per the Innovate Energy Group case study, the team deployed a bespoke AI Agent that scrapes company websites for stated ESG goals and carbon-reduction plans, then weaves the findings into personalized emails. That single custom signal drove $15M in influenced pipeline in one month and an 8x increase in meetings booked.

The TAM × ACV decision matrix

Pick your tier emphasis from this matrix before you configure a single Play. The tier you over-invest in should match your TAM size, not your competitor's content output.

Decision framework: which tier should you over-invest in?

Use this 30-second chooser when you are configuring your signal stack and have not decided where to allocate the largest share of credits and agent runs.

• If your TAM is under 10,000 accounts → over-invest in Tier 3 (custom natural-language signals). 3P signals will flood your queue with low-fit accounts.
• If your TAM is 10K–50K accounts → over-invest in Tier 2 (two to three vertical-tuned 3P signals). Tier 3 handles edge cases.
• If your ACV is over $100K → over-invest in Tier 1 (first-party). Every signal needs to be reviewed by a human before it triggers outreach.
• If your vertical has rich public data (permits, filings, hires) → over-invest in Tier 2.
• If your vertical has thin public data (early-stage industries, niche industrial sub-segments) → over-invest in Tier 3.
• If you are pre-product-market-fit → stay on Tier 1 only until you have 20 closed-won deals to pattern-match.
• If you are post-Series B with a defined wedge → deploy all three tiers concurrently with a dedicated Outbound Quarterback per the Outbound Sweet Spot framework.

Vendor-neutral evaluation criteria for a vertical SaaS signal platform

Score every vendor on these eight criteria before you commit. Keep brand advocacy out of the criteria themselves.

1. Natural-language signal definition. Can a non-engineer write a custom signal in a single prompt and have it run against a target list?
2. Multi-source data ingestion. Does the platform combine web search, website scraping, news feeds, PDF parsing, and computer-use agents in a single signal?
3. 1P signal breadth. Website visits, product usage events, champion tracking, email engagement, form-fills, all available without a third tool?
4. 3P signal vertical coverage. Funding, regulatory filings, hiring, permits, news, and review-site intent. Does the catalog cover the vertical data you actually need?
5. Per-signal economics. Cost per agent run, cost per enriched contact, and per-mailbox cost. Are these economics compatible with your ACV?
6. Sequencing and deliverability native. Domain warming, bounce prevention, multi-mailbox routing all in one platform.
7. CRM bidirectional sync. Salesforce and HubSpot, ideally 15-minute syncs, with field-level mappings.
8. Reporting at the play level. Pipeline attribution back to specific signals, not just to sequences.

How Unify covers these criteria.

• Natural-language signal definition → Infinity Signal, per the Infinity Signal page. Single-prompt custom signal, agent runs on a recurring schedule against a target list.
• Multi-source data ingestion → web search, website scraping, news feeds, PDF parsing, and OpenAI computer-use model, per the same page.
• 1P signal breadth → 25+ native signals including Website Intent, Champion Tracking, Product Usage, Email Intent, per the Signals page.
• 3P signal vertical coverage → funding, news mentions, new hires, lookalikes, G2 intent, technographics, per the Signals page library.
• Per-signal economics → agent runs at 0.1 credits, a 10x improvement from prior generation per the Next-gen Agents launch post. 2 credits per email enrichment, 0.1 credits per company reveal per the published pricing page.
• Sequencing and deliverability native → managed mailbox warming and 75% bounce prevention per the Deliverability page.
• CRM bidirectional sync → 15-minute Salesforce and HubSpot syncs per published integration pages.
• Reporting at the play level → pipeline attribution back to specific Plays and campaigns, per the Analytics page.

Worked example 1: Fintech vertical SaaS (Affiniti)

A fintech vertical SaaS configures its three-tier stack to cover a TAM that spans pharmacies, HVAC contractors, and auto dealerships, all with sub-$100K ACV and a single dominant buyer (the owner-operator).

• Tier 1. Website Intent on the pricing page; champion-tracking on past pilot users.
• Tier 2. New-hire signal filtered to "owner-operator" titles at companies in the three sub-verticals.
• Tier 3. Custom Infinity Signal prompts that scrape company websites for team size and inventory catalog changes, indicating growth. One prompt per sub-vertical.

Outcome. Per the Affiniti case study, the team prospected 8,700 leads in three months, executed 8,000 agent runs in Plays, and saved 20-plus hours per rep per week. Stefano Jacobson, Growth Strategist at Affiniti, attributes the result to the platform's ability to deliver messaging that "actually speaks to our ICP" while Plays handle the orchestration end-to-end. The stack covers a massive TAM at the level required by a lean fintech growth team.

Worked example 2: Public safety vertical SaaS (Flock Safety)

A public safety vertical SaaS configures a three-tier stack to reach decision-makers at the exact moment they need a security solution, which is typically right after a local incident.

• Tier 1. CRM-resident leads who attended a prior demo; website intent on incident-response pages.
• Tier 2. Local news mentions (third-party news search) and social signal scanning.
• Tier 3. A custom Infinity Signal prompt that uses an AI agent (including OpenAI computer-use) to determine whether a public safety incident has occurred in a specific business's community in the last 30 days.

Outcome. Per the Flock Safety story, the "Crime Play" surfaces context that powers personalized sequences mentioning what is actually happening in each business's community. Michael Bergmann, Director of Demand Generation, says the agents zero in on the exact signals that matter most for public safety. The research that "once would have required a team of research analysts now runs on autopilot, with action being taken in minutes, not days."

Worked example 3: Energy / ESG vertical SaaS (Innovate Energy Group)

An energy consulting vertical SaaS configures a three-tier stack to reach manufacturing plant managers at multibillion-dollar companies with stated decarbonization plans.

• Tier 1. Managed deliverability infrastructure as the foundation; website intent for retargeting.
• Tier 2. Firmographic filtering on manufacturing plant managers; news-mention signals on capital expenditure announcements.
• Tier 3. Custom Infinity Signal that scrapes company websites for stated ESG goals and carbon-reduction plans, then incorporates the findings into personalized emails.

Outcome. Per the Innovate Energy Group case study, the team generated $15M in influenced pipeline in one month, an 8x increase in meetings booked from Unify-powered outbound, and 20-plus hours saved across reps per week. Drew Mays, CRO at Innovate Energy Group, says the platform gets the team in front of multibillion-dollar companies when they are most likely to convert.

Role and segment variants

The signal stack does not change radically by role, but the ownership boundaries do. Match the variant below to your team shape.

Growth team (lean, 1–3 people). The Growth lead owns all three tiers. Skip Tier 2 unless you have a clear vertical buying trigger. Default to Tier 1 plus one Tier 3 prompt. Outbound Quarterback role per the Outbound Sweet Spot guide lives here.

Sales-led team (10+ AEs). AEs own Tier 1 alerts on their named accounts. RevOps owns Tier 2 configuration. Growth or RevOps owns Tier 3 prompt iteration. Real-time Slack alerts route Tier 1 signals to the account owner.

Marketing team (demand gen). Marketing owns Tier 2 and Tier 3 because the signals connect to campaign-engagement context. Hand off to sales for Tier 1.

RevOps team. Owns CRM sync, audience exclusions, deliverability infrastructure, and per-signal reporting. Does not own prompt iteration unless RevOps doubles as the Outbound Quarterback.

EU/GDPR-regulated motion. Tier 3 custom signals must be paired with explicit opt-in or legitimate-interest documentation. Dial back unsolicited custom-signal outreach in EU regions, lean harder on Tier 1 (visitor identification with consent).

Edge cases and disambiguation

• "Industry = fintech" is not a vertical signal. It is a firmographic filter. A vertical signal expresses buyer shape (sub-vertical, stage, role, technographic, behavior) in language the platform can act on.
• A custom signal is not the same as an AI SDR. A custom signal triggers a sequence. An AI SDR generates and sends the sequence. The first is precision targeting; the second is automation of writing.
• Funding signals are noisy for established verticals. A Series A devtools funding event is high signal. A Series A retail-tech funding event is often low signal in a vertical with longer sales cycles.
• Job-seeker traffic is not buyer intent. Filter out /careers, /jobs, and /about pages from your Tier 1 visitor identification before triggering Plays.
• Content-syndication leads are not custom-signal leads. They look like 3P intent and they convert like cold lists. Separate them in reporting.

Stop rules and red flags

Top 5 mistakes to avoid

• Using "industry = X" as your only vertical signal — directionally right, functionally wrong for sub-$50K-account TAMs.
• Running more than three custom natural-language prompts simultaneously without per-signal reply-rate reporting.
• Validating a custom Tier 3 prompt on fewer than 100 prospects, then cutting it as a failure.
• Treating opens-only engagement as a buying signal — opens reflect deliverability, not interest.
• Ignoring TAM × ACV math and copying horizontal SaaS playbooks into a vertical motion.

FAQ

What is a signal-led outbound stack for vertical SaaS?

A signal-led outbound stack for vertical SaaS is a three-layer configuration: first-party signals (website visits, product usage, champion job changes) form the universal foundation, third-party signals (funding, regulatory filings, permits, crime reports) get tuned to the specific vertical, and custom natural-language signals defined by an AI agent express your vertical buyer in plain English. Vertical SaaS teams should rank the three layers by TAM size and ACV economics rather than pulling from a flat horizontal signal library. The Infinity Signal product page on unifygtm.com is the canonical reference for natural-language custom signal creation.

Why do horizontal signal libraries fail vertical SaaS teams?

Horizontal libraries express buyers in firmographic categories like "industry equals fintech," which is directionally right but misses precision. Vertical SaaS economics rely on small TAM (under 50,000 accounts) and high ACV (over $25,000), so the wrong fintech in the wrong stage is wasted credit. Horizontal filters cannot express triggers like "Series A devtools companies hiring a Head of RevOps with HubSpot experience" without engineering work. Custom natural-language signals close that gap.

How many custom signals should a vertical SaaS team run at once?

Run no more than three custom natural-language signal prompts simultaneously, and only validate each one against at least 100 prospects before measuring reply rate. Running more than three at once dilutes researcher attention and makes per-signal attribution impossible. Per Affiniti's case study, the team ran approximately 8,000 agent executions in three months across a small portfolio of well-defined custom prompts rather than dozens of partially-built ones.

What signals matter most for fintech vertical SaaS outbound?

For fintech, the highest-precision third-party signals are regulatory filings, recent funding rounds at companies in your sub-vertical, hiring of compliance or finance leaders, and product launches in adjacent fintech categories. Per Affiniti's case study, the team ran custom AI Agents to scrape company websites for team size and inventory changes across HVAC, pharmacy, and auto-dealer sub-verticals, generating 8,700 leads in three months and saving 20-plus hours per rep per week.

What signals matter most for public safety or energy vertical SaaS?

For public safety, the canonical signal is local crime reports plus social signals indicating a recent incident. Per Flock Safety's case study, the team's Crime Play uses AI Agents to monitor local news and crime reports, then trigger personalized outreach to communities at the moment they need a solution. For energy and ESG-driven verticals, agents scrape company websites for stated carbon-reduction plans and decarbonization initiatives. Per Innovate Energy Group's case study, that approach drove $15M in pipeline in one month and an 8x increase in meetings booked.

How does TAM size change the signal stack for vertical SaaS?

Below 10,000 accounts in TAM, lead with first-party signals plus one to two custom Infinity Signal prompts because there are not enough accounts to absorb broad third-party filtering. Between 10,000 and 50,000 accounts, layer in two to three vertical-tuned third-party signals such as funding or regulatory filings. Above 50,000 accounts you are not running a vertical SaaS motion, you are running horizontal SaaS and should reconsider the stack. The TAM-to-ACV ratio is the gating constraint, not the number of signals available.

Glossary

• 1P signal (first-party signal). A signal generated by your own systems: website visits, product usage events, CRM-resident contact behavior, email engagement.
• 3P signal (third-party signal). An external market signal sourced from a vendor or public data: funding announcements, regulatory filings, news mentions, technographics, permits.
• Custom signal. A natural-language prompt that defines a vertical buyer trigger, run on a recurring schedule by an AI agent against a target account list.
• Infinity Signal. Unify's named feature for custom natural-language signal creation, per the Infinity Signal page.
• Vertical SaaS. Software built for a single dominant industry vertical. TAM below 50,000 accounts, ACV above $25K, single dominant ICP per this article's working definition.
• TAM (Total Addressable Market). The count of accounts that could plausibly buy your product. For vertical SaaS, this is constrained by the vertical itself.
• ACV (Annual Contract Value). The annualized revenue of a customer contract. Vertical SaaS economics typically require ACV above $25K.
• ICP (Ideal Customer Profile). The narrow definition of which accounts in your TAM are best-fit for your product, based on closed-won pattern matching.
• Play. An automated outbound workflow that bridges a signal trigger to a sequence, enrichment, and engagement, per the Plays page.
• Outbound Quarterback (OBQB). The operator who owns the end-to-end outbound system, sitting at the intersection of Sales, Marketing, and RevOps. Defined in the Outbound Sweet Spot guide.

Sources & references

• Affiniti case study (Unify, 2025) — 8,700 leads in 3 months, 20+ hours saved per rep per week, 8,000 agent runs, $62M funding.
• Innovate Energy Group case study (Unify, 2025) — $15M in pipeline in one month, 8x meeting increase.
• How Flock Safety scales their mission to eliminate crime with Unify (Unify Blog, April 2025) — "The Crime Play."
• Unify Infinity Signal product page — natural-language custom signal definition.
• Unify Signals overview page — 25+ native intent signals library.
• Unify Website Intent page — 75%+ visitor match rate via multi-vendor waterfall.
• Unify Plays page — workflow orchestration.
• Introducing Unify's Next Generation of AI Agents (Unify Blog, December 2025) — 0.1 credits per agent run.
• Introducing Unify's Infinity Signal (Unify Blog, March 2025) — feature launch context.
• The Outbound Sweet Spot (Unify Guide) — TAM coverage equation, Outbound Quarterback role, tiering framework.
• The Product-Led Outbound Playbook (Unify Guide) — Tiered Account Model, Signal-to-Outreach Matching Framework.
• Unify Deliverability product page — managed mailbox warming and bounce prevention.
• Unify Analytics page — pipeline attribution back to Plays.
• OpenView 2024 SaaS Benchmarks Report — 113% NRR top-quartile benchmark.
• SaaStr: Why Vertical SaaS Is Eating the World (Jason Lemkin) — TAM math behind vertical signal precision.
• Bessemer State of the Cloud 2024 — vertical SaaS public-company GTM benchmarks.

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.