Intent to Routing to Outbound Workflow
5 steps to convert account-level intent signals into active outbound sequences, with routing rules that stop reps from wasting time on unqualified accounts.
Before You Start
Output: a live intent-to-sequence pipeline in 2 to 4 hours
What you build: accounts route to the right rep tier and activate contact-level outreach with no manual hand-off after initial setup. Replication per additional signal source takes under 30 minutes once routing rules are defined.
Active intent platform (6sense, Demandbase, or Terminus) with account-level signal export enabled. CRM with account ownership fields populated. Access to a contact enrichment tool (Clay or Apollo) and at least one sequencer (Smartlead, Instantly, or Apollo Sequences). ICP firmographic criteria documented before starting step 1.
Workflow Overview
5 steps from signal to live sequence
| Step | Action | Tool | Output |
|---|---|---|---|
| 1 | Define intent tiers and signal taxonomy | 6sense / Demandbase / Terminus | 3-tier signal classification |
| 2 | Score accounts against ICP criteria | CRM / Clay | Qualified account list with tier label |
| 3 | Apply routing rules by tier | CRM / Clay conditional logic | Accounts assigned to rep or sequence type |
| 4 | Enrich and verify contacts at routed accounts | Clay / Apollo / Findymail | Verified contacts with signal context fields |
| 5 | Activate sequences with signal personalization | Smartlead / Instantly / Apollo Sequences | Live sequences per segment |
Step by Step
All 5 steps: intent tier definitions to live sequence activation
- Step 1: Define intent tiers before building any routing rule
Map signal types to three tiers: High (active evaluation, multi-stakeholder activity), Medium (single-stakeholder research), Low (awareness or competitor searches). Document tier criteria before touching CRM or routing logic. A routing rule built on undefined signals cannot be debugged.
- Step 2: Score accounts against ICP criteria and suppress below-threshold accounts
Cross-reference signaling accounts against firmographic ICP: industry, size, tech stack, geography. Suppress accounts that show intent but miss fit criteria. Routing unfit accounts trains reps to ignore the entire alert feed.
- Step 3: Route by tier to the correct rep or sequence type
High-intent ICP accounts go to a named AE or senior SDR with a manual review step. Mid-tier accounts enter a semi-personalized SDR multichannel sequence. Low-tier accounts enter a lighter automated nurture. Never route to a generic rep pool without confirmed ownership.
- Step 4: Enrich and verify contacts at routed accounts
Pull buyer personas via Clay waterfall enrichment (150+ providers), Apollo direct database, or Findymail per-domain search with catch-all handling. Attach signal tier and category to each contact record before pushing to the sequencer.
- Step 5: Activate sequences with signal personalization fields mapped
Map signal tier and category as merge fields in your sequencer. Reference the buying signal category in the first touchpoint without citing the exact data source. Set reply and OOO detection to pause sequences on any response.
If an account is unassigned in CRM when a contact is pushed to a sequence, two reps may sequence the same prospect simultaneously. Add an "account owner populated" condition as a hard gate before the sequence activation step fires.
Common Failures
4 failure modes and their fixes
Stack Notes
6sense, Clay, Apollo, Findymail: which tool covers which step
| Stage | Tools | Notes |
|---|---|---|
| Signal tiers (Step 1) | 6sense, Demandbase, Terminus | Terminus adds Bombora intent + first-party CRM data for ABM teams |
| Routing + enrichment (Steps 3-4) | Clay | Waterfall across 150+ providers; handles routing logic and enrichment in one workflow |
| Email verification (Step 4) | Findymail | Per-domain search with catch-all handling; bounce rate below 5% guaranteed |
| All-in-one (Steps 3-5) | Apollo | Combined database, sequencer, dialer; lower enrichment coverage on niche domains |
Teams that define tiers in one platform and score accounts in another introduce sync lag that makes the tier label stale by the time routing fires. If your intent platform supports ICP filtering natively (6sense and Demandbase both do), run step 2 inside the same platform before exporting to CRM.
Frequently Asked Questions
5 questions on intent tiers, Clay vs Apollo, and what breaks first
No. First-party signals (CRM visits, G2 page views, job-change alerts via Clay) replace a third-party intent feed at lower cost and lower volume. The tier structure and routing logic stay identical.
Three: High, Medium, Low. More creates routing complexity reps cannot act on consistently. Fewer flattens buying behaviors and over-sequences low-intent accounts.
Six gates: tier definitions documented, ICP scoring in CRM, routing rules with named ownership per tier, enrichment tool with fallback provider, sequence templates with signal merge fields, reply and OOO detection enabled. Test 10 accounts through all 5 steps before activating the full workflow.
Yes. Apollo covers steps 3-5 natively. The tradeoff: Clay's waterfall (150+ providers) returns higher coverage on niche domains. Add Clay if enrichment hit rates on your ICP fall below 60%.
Routing every signal without tier definitions (alert fatigue), routing before ICP filtering (reps work unfit accounts), and sequencing without signal context attached to the contact record (outbound reads as generic cold email).
Workflow built. Now pick the right intent platform.
Compare 6sense, Demandbase, and Terminus side by side to choose the intent source that fits your ICP and budget before connecting it to this workflow.