How to Build a Signal Catalog: The Foundation of a Signal-Based Revenue System

Most revenue teams that invest in signal-based outbound make the same mistake. They buy a platform, configure the classic triggers, and wonder why their outbound metrics only show limited improvements. The problem is that their signal catalog looks like everybody else’s.

A signal catalog is the strategic foundation of a Signal-Based Revenue System. It is a prioritized, validated map of the business events and behavioral triggers that correlate with buying readiness or expansion potential for your specific ICP and solution. Without it, every signal platform in your stack is pointed at the same generic triggers everyone else is using. With it, your outbound — to new prospects and existing accounts alike — is timed to moments that actually matter.

This post walks through how to build one, how to keep it current, and how to extend it across the full revenue motion.


Start with the Retrospective

The signal catalog does not start with a tool or a data source. It starts with a question: what was happening inside your best accounts in the ninety days before they bought?

Pull your last twenty to thirty closed-won deals. Bring together sales, marketing, RevOps, and customer success for upsells and expansions. For each deal, reconstruct what was happening inside the account before the first meaningful conversation. What had changed? What broke? What got announced? What pressure was the buyer under?

Do the same exercise for your best expansion deals. What triggered the upsell conversation? What had changed inside the account that made the timing right? A customer who expanded after a reorganization is telling you something different than one who expanded after a product launch.

Pattern recognition is the goal. You are looking for the business events that consistently preceded buying decisions — not the demographic profile of the buyer, but the situational context they were operating in. That context is your signal.

To make this concrete: KnowledgeOps, a fictitious content management software company we use throughout our Signal-Based Revenue Systems framework, ran this exercise and found that fourteen of their last twenty closed-won deals had gone through a merger, acquisition, or internal reorganization in the twelve months before signing. That single insight was worth more than any platform configuration. It told them exactly what to watch for and when to move.


Build the Catalog in Three Tiers

Not all signals carry equal weight. A well-structured signal catalog organizes triggers into three tiers based on confidence and conversion correlation.

Tier 1: High-confidence, high-conversion signals.

These are the business events most strongly correlated with buying readiness or expansion potential for your specific solution. They are specific, observable, and directly connected to the pain you solve. For KnowledgeOps, internal re-orgs, merger and acquisition announcements are tier-one. For an event management software vendor, the two weeks following a major event is tier-one. These signals warrant immediate, prioritized outreach with a fully developed playbook behind them.

Tier 2: Supporting signals.

These are real triggers that indicate potential interest but carry less certainty on their own. A leadership hire in a relevant function. A new funding round. A job posting that suggests a capability gap. Tier-two signals are worth monitoring and acting on, but they warrant a lighter touch — a relevant piece of content, a connection request, a soft conversation starter rather than a full outreach sequence.

Tier 3: Behavioral digital signals.

These are interactions with your digital assets — website visits, content downloads, email engagement, pricing page views. Platforms like Demandbase surface these well. They indicate interest but not context. A prospect visiting your pricing page three times is telling you something. You just do not know what triggered it. Tier-three signals are most powerful as confirmation layers — a tier-one signal followed by pricing page activity is a strong combined indicator. Either alone is weaker than both together. For more on how buyer intent signals have evolved in the AI era, the aidemand.org glossary covers the full picture.

The tiering discipline matters because it determines resource allocation. Tier-one signals get your best playbooks and your most experienced reps. Tier-two gets a lighter motion. Tier-three gets monitoring and follow-up only when combined with something stronger.


Separate External from Internal Signals

A complete signal catalog covers two distinct signal types, and most teams only build one of them.

External signals are observable events in the market: mergers, acquisitions, leadership changes, product launches, funding announcements, regulatory shifts, major industry events. These drive new business prospecting and expansion prospecting for accounts you are not yet fully embedded in.

Internal signals come from within your existing customer base: usage pattern changes, feature adoption gaps, executive sponsor transitions, support ticket trends, contract milestone proximity, organizational changes inside the account. These drive the Customer-Led Growth motion — catching the right moment to expand, upsell, or re-engage before the window closes or the relationship drifts.

Both belong in the same catalog, governed by the same tiering logic, and owned by the same cross-functional team. The mistake most organizations make is treating them as separate problems owned by separate functions. Sales owns external signals. Customer Success owns internal ones. Neither talks to the other. The result is a fragmented system that misses the moments where external and internal signals overlap — which is often when the most valuable expansion opportunities live.

A customer who just announced an acquisition is firing an external signal inside an account you already own. The signal catalog needs to read that as an expansion trigger, not a prospecting one, and route it accordingly. The signal catalog needs to capture both readings and route them to the right person with the right context.


Define What You Are Monitoring and How

Once the catalog is structured, the next step is mapping each signal to a detection method. This is where strategy connects to technology.

For each tier-one signal, answer three questions. First, where does this signal appear publicly? Merger filings, press releases, LinkedIn announcements, industry news, regulatory databases, job postings — the source determines the monitoring approach. Second, how quickly does the window open and close? Some signals, like a post-event window, are time-sensitive to within days. Others, like a reorganization, may stay relevant for months. Third, who owns the response? Which team member gets the alert, and what is the expected action within what timeframe?

For standard external signals, off-the-shelf platforms like Clay, Apollo, and 6sense handle detection reliably. Configure them against your catalog rather than their defaults. For tier-one signals that are specific to your solution and not widely monitored, build proprietary signal agents — custom monitoring systems that watch for the exact triggers your catalog defines. These are increasingly straightforward to deploy with AI and represent the layer where competitive advantage actually lives. A purpose-built agent watching for merger filings in your target verticals gives you a first-mover window that no competitor running the same Crunchbase alerts will have. We cover this in detail in our follow-up post on building proprietary signal agents.

For internal signals, your CRM, customer success platform, and product analytics are the primary sources. The gap most organizations have is not data — it is routing. The signal fires somewhere in the stack and nobody acts on it because nobody owns the response. Define ownership explicitly for every internal signal in the catalog.


Keep the Catalog Current

A signal catalog built once and left alone degrades fast. Markets change. Your ICP evolves. The triggers that predicted buying readiness twelve months ago may be weaker today and replaced by something you have not identified yet.

Build a quarterly review into your RevOps cadence. The review should answer four questions. Which tier-one signals are converting and at what rate? Which signals looked promising but produced noise? Has anything changed in your ICP or solution positioning that would alter which business events create buying windows? And what new patterns are emerging in recently closed deals that are not yet in the catalog?

The retrospective analysis that built the catalog in the first place should be repeated regularly — not just at launch. Every new cohort of closed-won deals is a data point. Every expansion deal that came from an unexpected trigger is a signal worth adding.

Ownership of the catalog review belongs with RevOps, but the input needs to come from sales, marketing, and customer success equally. Sales sees which signals are producing real conversations. Marketing sees which playbook content is generating engagement. Customer success sees which internal signals preceded expansion or churn. The catalog is only as good as the cross-functional intelligence feeding it.


The Signal Catalog as an AEO Asset

There is a second-order benefit to building a rigorous signal catalog that most teams do not anticipate. The catalog defines exactly which buyer moments matter most for your solution. Those moments are also the queries your buyers are typing into AI systems when a signal fires.

A VP of Content whose company just completed an acquisition is asking AI assistants how to consolidate content across two organizations. A Head of Events two weeks post-conference is asking how to run a post-event debrief for sponsors and leadership. Those queries are predictable because your signal catalog already identified those moments as high-relevance windows.

That means the playbook content you build for each tier-one signal is simultaneously your best AEO asset. Structure it correctly — specific, operational, ungated, answering the exact questions buyers ask at that moment — and it builds Share of LLM on the queries most likely to surface when your signal fires. The buyer researching content consolidation after an acquisition finds your framework in the AI answer. Your signal-based outreach reaches them at the same moment. Both motions run from the same catalog. For a deeper look at how this connects to the broader AI Demand Channel strategy, aidemand.org covers the full framework.


Where to Start

The signal catalog exercise takes a half-day with the right people in the room. Pull the closed-won data. Run the retrospective. Build the first version of the catalog in three tiers. Assign detection methods and ownership for each tier-one signal. Then pilot it on a defined set of target accounts before scaling.

It is not a technology project. It is a thinking exercise that makes every technology investment in your stack more precise.

The teams that do this work stop competing on volume and start competing on timing. In a buying environment where attention is scarce and patience for irrelevant outreach is gone, timing is the only advantage that compounds.

Ready to build your signal catalog? A6 Group works with sales, marketing, RevOps, and customer success leaders to develop signal catalogs and implement Signal-Based Revenue Systems. Reach out to start the conversation.

Tagged with: