What Actually Happens in the 90 Seconds After a Signal Fires - and Why That Gap Is Destroying Your Pipeline?

Last updated: 2026-06-15

Key Takeaways

• Signal routing is a discrete operational layer with its own failure modes - most GTM teams treat it as a natural consequence of signal capture rather than a system that requires its own architecture.
• Speed-to-route and speed-to-contact are not the same thing. Misrouting a signal to the wrong rep, queue, or sequence destroys conversion probability even when response time is fast.
• Fallback logic - what happens when a signal fires for an unowned account, a rep at capacity, or a contact with no CRM match - is where most pipeline value evaporates.
• Routing logic decays over time as territories shift, reps churn, and account ownership drifts. Stale routing rules are a pipeline risk, not a configuration inconvenience.
• Only 38% of go-to-market leaders say their GTM strategy is actually effective (LeanData x Harvard Business Review Analytic Services, 2026). The execution gap - not the strategy gap - is where most of that failure lives.

---

You have intent signals firing. You have a stack that captures them. What you probably don't have is a systematic answer to what happens next - in what order, to whom, and within what timeframe. Signal routing GTM is the discipline that answers those questions. Almost no one has built it properly.

---

Why does the 90 seconds after a signal fires matter more than the signal itself?

The 90-second window is where routing decisions execute. It's where most pipeline value is either captured or permanently lost.

Signal acquisition is a solved problem for most B2B SaaS teams. Signal routing is not.

The GTM conversation in 2025 and 2026 has been dominated by signal quality debates: which intent data provider is most accurate, how to weight first-party versus third-party signals, how many signals constitute a meaningful buying cluster. Legitimate questions, all of them. Also largely the wrong ones to obsess over once your signal infrastructure is in place.

"Pick any signal that should drive revenue: a target account hires a new CRO, an enterprise lead visits your pricing page 3 times, a renewal account goes silent. Can your system act on it within an hour without anyone manually noticing? If the answer involves Slack pings, CSV exports, or 'I'll forward this to the AE,' your stack isn't a system yet." - ZoomInfo Pipeline

That description - Slack pings, CSV exports, manual forwarding - is the routing reality at the majority of B2B SaaS companies operating below £50M ARR.

The signal fires. Someone notices. Someone else is told. A sequence is triggered 3 days later, if at all.

The window has closed.

Teams running signal-based plays report 3x higher meeting booking rates compared to traditional outbound (Signal-Based Marketing: A Buyer Behavior GTM Playbook, 2025). That number assumes the signal reaches the right person, through the right channel, at the right moment. When routing is broken, that multiplier collapses entirely.

---

What is signal routing and why is it a separate discipline from signal capture?

Signal routing is the decision layer that determines what happens to a signal after it fires - which rep, which sequence, which channel, which priority tier, and what fallback applies if the primary route is unavailable.

Signal capture and signal routing are architecturally distinct.

Capture is about data acquisition: which signals you collect, how you score them, how you surface them. Routing is about execution: the logic that converts a scored signal into a specific, time-bound commercial action.

Most GTM stacks invest heavily in the capture layer and treat routing as a configuration afterthought. The result is a system that identifies buying intent with reasonable accuracy and then squanders it through operational ambiguity.

"Strategy alone doesn't drive growth. Execution does, in particular aligning execution to the buyer journey." - Dana Guthrie, Senior Director of EMEA Marketing at LeanData

This distinction matters because the failure modes are different.

A capture failure means you miss a signal. A routing failure means you capture the signal and still lose the opportunity - which is arguably worse, because the data suggests you were doing the right things while the pipeline quietly evaporated.

The operational gap is measurable. Over 500 go-to-market leaders were surveyed in a joint study by LeanData and Harvard Business Review Analytic Services, and only 38% said their GTM strategy was actually effective (LeanData x Harvard Business Review Analytic Services, 2026). The same research identified improved go-to-market execution - not strategy refinement - as the number one driver of increased revenue.

Routing is execution. Execution is the constraint.

---

What does a properly architected signal routing system look like?

A properly architected signal routing system has 4 defined layers: signal classification, routing logic, fallback handling, and SLA enforcement. Each layer has explicit rules, an owner, and a measurable output.

Signal classification

• What it defines: Signal type, source, weight, and account context
• Common failure mode: Treating all signals equally regardless of intent strength

Routing logic

• What it defines: Which rep, queue, or sequence receives the signal and why
• Common failure mode: Routing to territory owner regardless of capacity or fit

Fallback handling

• What it defines: What executes when primary route is unavailable
• Common failure mode: No fallback defined - signal sits in queue unactioned

SLA enforcement

• What it defines: Maximum time from signal fire to first action
• Common failure mode: No SLA exists - response time is entirely rep-dependent

The routing logic layer is where most teams have the thinnest documentation.

Territory-based routing is the default because it's the simplest to configure. It's also the most brittle. A rep who churned 3 months ago may still own 40 accounts in Salesforce. A signal that fires against one of those accounts routes to nobody, or to a manager inbox that nobody monitors, or to a sequence that was paused for a campaign that ended in Q1.

Holly Gage, Director of Marketing Operations at Soldo, noted that building lifecycle tracking inside Salesforce took roughly 12 to 18 months to complete (Holly Gage, Director of Marketing Operations at Soldo, 2026). That timeline reflects the genuine complexity of building routing infrastructure that is both accurate and maintainable - not a project that gets resolved in a sprint.

"outbound performance depends less on messaging refinements and more on structured decision-making." - Ilija Stojkovski, CRO at HeyReach

Structured decision-making is what routing logic provides. The rep receiving the signal doesn't need to decide what to do - the system has already decided. Their job is execution within the defined SLA, not triage.

---

What is routing logic decay and why does it destroy pipeline over time?

Routing logic decay is the process by which routing rules become progressively less accurate as the business changes - through rep churn, territory restructures, account ownership drift, and product line expansion - without corresponding updates to the routing configuration.

This is the most underappreciated failure mode in signal-based GTM.

Teams build routing logic at a point in time, validate it against their current state, and then treat it as infrastructure rather than as a living operational document.

6 months later, 3 reps have left. 2 territories have been restructured. A new product line has created account ownership ambiguity between AEs and CSMs. The routing rules still reflect the org chart from Q4 of last year.

Signals are routing accurately against a business that no longer exists.

The commercial cost is compounding. Companies are now spending £2 in sales and marketing to earn £1 of new ARR - a 14% jump from 2024 (Benchmarkit's 2025 report, 2025). Cold email open rates have dropped from 36% to under 28% in 2 years (Signal-Based Marketing: A Buyer Behavior GTM Playbook, 2025). In that environment, a signal that reaches the wrong rep - or no rep - isn't a minor inefficiency. It's a direct contribution to CAC expansion.

The fix is treating routing logic as infrastructure with a maintenance schedule, not as a one-time configuration. Routing rules should be audited quarterly at minimum, triggered immediately by any rep departure or territory change, and owned explicitly by a named individual in RevOps.

This connects to a broader point made in the GTM architecture piece: the failure of modern B2B sales is rarely a tooling problem. It's an architecture problem. Routing logic decay is an architecture problem that presents as a tooling problem, which is why it persists.

---

What fallback logic should exist when a signal fires into an edge case?

Every signal routing system needs explicit fallback logic for 4 conditions: unowned accounts, rep capacity limits, dormant territories, and contacts with no CRM match.

These aren't edge cases in the statistical sense. They're edge cases in the sense that most routing configurations ignore them - but they occur constantly in any business with normal sales team turnover and a CRM that isn't maintained with surgical precision.

The 4 conditions that require explicit fallback rules:

Unowned accounts - the signal fires against an account with no assigned owner. Without a fallback, the signal routes to a queue that nobody monitors or disappears entirely. The fallback should be an explicit owner (typically a round-robin pool or a named SDR) with a defined SLA.

Rep at capacity - the signal fires against an account owned by a rep who is already at maximum active opportunities. Routing another signal to that rep reduces response quality. The fallback should be a capacity threshold that triggers overflow routing to a secondary rep or queue.

Dormant territories - the signal fires against an account in a territory that has been restructured or is temporarily unassigned. This is the most common consequence of routing logic decay. The fallback should be a territory management protocol that reassigns accounts within 48 hours of any rep departure.

No CRM match - the signal fires against a contact or company that doesn't exist in the CRM. More common than most teams expect, particularly with third-party intent data. The fallback should be an enrichment step that attempts to match and create the record, with a manual review queue for unresolved matches.

"A GTM system turns data and signals into coordinated action across sales, marketing, and customer success. It's the difference between owning tools and operating as one motion." - ZoomInfo Pipeline

Operating as one motion requires that the motion continues even when the primary route is unavailable. Fallback logic is what makes it continuous rather than dependent on human intervention at every exception.

The concentric circle approach to signal-based GTM is relevant here - the warmest audiences (existing customers, active pipeline, recently churned accounts) should always have the most robust routing logic and the tightest SLAs, because the cost of a routing failure is highest where the relationship already exists.

---

How does signal routing connect to the broader GTM execution problem?

Signal routing is a symptom of a larger execution alignment problem. Fixing routing in isolation - without addressing data quality, process definition, and ICP clarity - will produce incremental gains at best.

The research is unambiguous on the execution gap. Improved GTM execution is the number one driver of increased revenue, yet only 38% of GTM leaders say their strategy is effective (LeanData x Harvard Business Review Analytic Services, 2026). Signal routing sits inside that execution gap.

"A lot of teams still seem to be treating execution as operational hygiene rather than the growth lever that it is." - Dana Guthrie, Senior Director of EMEA Marketing at LeanData

When routing is properly architected, the numbers shift materially. Signal-driven GTM execution has been associated with an 86% increase in pipeline, a 2x increase in MQL conversion, and a 39% reduction in routing time (LeanData Signal-Driven GTM Execution eBook, 2025). Rocket Software increased marketing qualified lead velocity by 75% through structured signal routing (LeanData Customer Story, 2025). These aren't signal quality improvements. They're routing and execution improvements.

"even straightforward outreach sent under the right conditions consistently outperforms highly personalized messaging sent at the wrong time." - Webinar on signal orchestration and outbound performance

The conditions are set by routing. The timing is set by routing. The rep is selected by routing.

Personalisation and messaging quality are downstream of all of those decisions - which is why obsessing over copy while leaving routing to chance is a category error.

If you're auditing why your signal investment isn't converting to pipeline, the growth audit framework is worth a look. The most common finding isn't that the signals are wrong. It's that the execution order is wrong - and routing is almost always part of that disorder.

For founders and revenue leaders who want to build this infrastructure without adding headcount, the Custom AI Systems work addresses exactly this problem: building the routing logic, fallback handling, and SLA enforcement as a system rather than a collection of manual workarounds.

---

Frequently Asked Questions