A copy-paste Claude prompt that takes the 9-cell audience matrix and produces explicit signal-driven escalation rules — tier upgrades, tier downgrades, paid-only→outreach-active activations, outreach→AE handoffs. The operational runtime layer that makes the audience matrix behave like a real ABM program rather than a quarterly snapshot.
A B2B SaaS team has the full Track 03 stack: ABM Audience Builder produced the 9-cell matrix, ABM Sequence Designer produced sequences per cell, ABM Account Forecast measures pipeline outcome per cell. Quarterly setup is sophisticated. Then mid-quarter, a T2-Influencer account hits 3 ad clicks within 14 days and downloads two case studies. They've behaved exactly like a T1 account. But there's no rule that escalates them — they stay in the T2 sequence (5 touches, lower personalization), miss the T1 voice-note touch and the AE preview, and the deal stalls. Or: a T1-DM account goes silent for 30 days mid-sequence — but stays in the T1 cell consuming SDR effort that should be reallocated. Static cell assignment is a quarterly snapshot; account behavior is daily reality. Without explicit rules, escalation either doesn't happen (account underperforms) or happens reactively based on individual SDR judgment (inconsistent, no learning compounds).
The deeper problem is that most B2B SaaS ABM programs have the snapshot pieces but lack the runtime layer. Audience Builder + Sequence Designer + Forecast were quarterly snapshots; they describe the static structure. The dynamic layer — the rules that move accounts between cells based on observed behavior — is missing across most teams. This isn't a tooling problem; HubSpot workflows can implement these rules. It's a definitions problem: nobody has written down which signals trigger which transitions, so the rules don't exist to implement.
This workflow runs structured rule production. Claude takes the 9-cell matrix + your signal taxonomy + your sales handoff criteria and produces 12-15 explicit escalation rules across 4 transition types. Each rule specifies the signal threshold (e.g. "3+ ad clicks within 14 days AND 1 high-intent page view"), the time-bounded window, the post-transition action (move to which cell, trigger which sequence, notify which person), and the priority tier (P1 ship this week / P2 ship 30 days / P3 ship 60 days). Run quarterly; pair with HubSpot workflows for implementation.
The gold variables — your brand, audience matrix, signal taxonomy, sales handoff criteria — are the parts you edit. Run quarterly to recalibrate as signals evolve and account behavior patterns shift.
HubSpot Workflows + Operations Hub for complex multi-signal conditions.Sample output for a hypothetical mid-market B2B SaaS brand with 9-cell matrix and standard signal taxonomy. Router produces 13 rules across 4 transition types: 5 upgrade, 2 downgrade, 3 activate, 3 handoff. Total HubSpot setup time: ~125 hours across 6-8 weeks.
Generating escalation rules across 4 transition types. Calibrating thresholds to your 84-day sales cycle and standard signal taxonomy.
13 rules generated. Distribution: 5 upgrade · 2 downgrade · 3 activate · 3 handoff. Priority: 6 P1 (ship this week) · 4 P2 (ship 30 days) · 3 P3 (ship 60 days). Total HubSpot setup time: ~125 hours across 6-8 weeks. Highest-volume rule: T3-DM → T2-DM upgrade (estimated 35 accounts/quarter). Highest-leverage rules: 3 AE handoff rules (directly drive pipeline; all P1).
AND ICP score ≥ 70OR 1 high-intent page viewAND 1 high-intent page view OR 1 form fillOR 1 form fillAND 1 high-intent page viewad_clicks_last_14d ≥ 2high_intent_page_views_last_14d ≥ 1 (pricing, demo, case-study, roi-calculator)tier = "T2", last_transition_at = now()tier = "T3" AND role = "DM" AND time-since-last-transition ≥ 30 days.ad_clicks_14d ≥ 2 OR high_intent_pv_14d ≥ 1 → execute action sequence above.outreach_reply_count ≥ 1 (any channel: LinkedIn DM, email, phone)icp_score ≥ 70stage = "AE-active", ae_assigned_at = now()icp_score ≥ 70 AND stage != "AE-active".days_since_last_engagement ≥ 30 (no ad click, page view, email open, reply)active_sequence = true (account is mid-sequence, not pre-sequence or post-sequence)tier = "T2", last_transition_at = now(), downgrade_reason = "30d_silence"Run quarterly. Pair with ABM Audience Builder + Sequence Designer (upstream) and ABM Account Forecast (downstream measurement). Re-run after major signal taxonomy changes or sales handoff process updates.
Escalation rules govern movement BETWEEN cells. The cells need to exist first — Audience Builder produces the matrix; Sequence Designer produces the sequences accounts move through. Don't skip these: rules without an audience matrix or sequences have nothing to move accounts to.
Run ABM Audience Builder →Edit the gold variables — your brand, audience matrix, signal taxonomy, sales handoff criteria. Most important variable is signal taxonomy — define which signals indicate engagement, high intent, and disengagement. If you've run Track 05's Signal Quality Audit, paste the validated taxonomy. If not, use the standard B2B SaaS taxonomy and validate post-deployment.
Workflow takes 18-25 minutes. Claude produces the rule library with priority + trigger volume estimates per rule, plus detailed HubSpot workflow specifications for the top 3 priority rules. Output is the rule library + 3 detailed specs — ready to hand to RevOps.
Hand rules to RevOps. Tier 1 (this week): implement 6 P1 rules (3 AE handoffs + 3 high-volume upgrades/activates). ~70 hours setup. 14-day shadow mode per rule before live deployment to validate trigger volume. Tier 2 (30 days): implement 4 P2 rules. Tier 3 (60 days): implement 3 P3 rules. Re-run router quarterly to recalibrate as signals evolve.
Same 4-transition framework, different account dynamics. Pick the variant that matches your sales motion and signal infrastructure.
Short-cycle B2B SaaS (under 30-day cycles, often PLG with self-serve activation) needs faster rule windows. Standard 14-day windows cause stale signal usage. Short-cycle variant compresses all time windows by 50% and adds product-engagement signals to AE handoff triggers.
Enterprise B2B SaaS (180+ day cycles) needs longer rule windows. Standard 30-day downgrade windows trigger premature downgrades on slow-moving committee deals. Enterprise variant extends all time windows by 50% and adds buying-committee signals (multiple-stakeholder engagement) as upgrade triggers.
If Track 05's Google Offline Conversions + LinkedIn CAPI setup isn't live yet, AE handoff rules can't reliably fire (no signal feed from sequence reply → HubSpot lifecycle update). No-CAPI variant produces upgrade + downgrade + activate rules only, deferring AE handoff rules until offline conversions are configured.
Most B2B SaaS ABM programs have the snapshot pieces but lack the operational runtime. Accounts get assigned to a cell at quarterly setup and stay there. Run the router quarterly. Ship 6 P1 rules this week. 4 P2 rules in 30 days. 3 P3 rules in 60 days. Or have senior GrowthSpree operators run the quarterly router cycle and coordinate RevOps + SDR execution — the same operating motion run across 300+ B2B SaaS accounts.