Segmentation & Routing SOP
Define segment criteria, write per-tier routing rules, and push every contact to the right rep or sequence without manual sorting or CRM guesswork.
Before You Start
Output and prerequisites: 2-3 hours to set up
Output: Documented segment taxonomy, per-tier routing rules, sequence-type assignments, and a repeatable pre-launch checklist. Time: 2-3 hours for initial setup; under 30 minutes per subsequent batch.
ICP firmographic criteria defined, CRM ownership fields populated, and a lead database providing industry, headcount, and country per contact. Add an intent source (6sense, Demandbase) only if routing on intent signals at step 3.
SOP Overview
The 5-step segmentation & routing SOP at a glance
| Step | Action | Tool | Output |
|---|---|---|---|
| 1 | Define segment dimensions and tier criteria | CRM / spreadsheet | Documented segment taxonomy |
| 2 | Score and tag contacts against criteria | Clay / Apollo / CRM | Contacts tagged by tier |
| 3 | Write routing rules per tier | CRM workflow builder / Clay | If-then routing rules doc |
| 4 | Map each tier to a sequence type and message angle | Smartlead / Instantly / Apollo | Sequence assignments per tier |
| 5 | Run pre-launch checklist before each batch | CRM + sequencer | Clean, routed batch ready to launch |
Step by Step
All 5 steps: complete segmentation & routing SOP
- Step 1: Define segment dimensions and tier criteria in writing
Identify 3-5 firmographic dimensions (industry, headcount, geography, persona seniority) and assign each combination to Tier 1 (best-fit, highest effort), Tier 2 (qualified, automated sequence), or Tier 3 (nurture only). Document criteria in a shared location; contacts whose firmographics cannot be confirmed are held for enrichment before routing.
- Step 2: Score and tag contacts against segment criteria
Use Clay conditional columns, Apollo list filters, or CRM scoring rules to output a tier label and a route-ready flag per contact before the batch enters CRM. Contacts missing required firmographic fields output "Pending Enrichment" and are suppressed until enrichment completes.
- Step 3: Write explicit if-then routing rules per tier
Write each rule as a literal if-then: "If tier = T1 and account owner populated, assign to named AE and flag for manual review before sequence activation." Test against 10 real contacts from your last batch and refine any rule that produces an ambiguous output before applying at scale.
- Step 4: Map each tier to a sequence type and message angle
Tier 1: short high-personalization sequence from a named AE, referencing an account-level signal. Tier 2: mid-length multichannel sequence with persona-level personalization. Tier 3: low-volume educational nurture, no hard CTA. Document assignments alongside tier criteria and review every quarter.
- Step 5: Run the SOP checklist before activating every batch
Confirm before every import: tier tag on every contact, no missing firmographic fields, T1 account ownership populated, no active-sequence duplicates, sequence matches tier, reply detection enabled. A batch that skips this gate creates routing conflicts requiring manual cleanup after launch.
Routing a new contact from an account already in an active sequence sends duplicate outreach from two people simultaneously. Add an "account has active sequence" suppression check as the first gate in step 5, before any other checklist item.
Common Failures
3 failure modes and how to fix each one
Stack Notes
Clay, Apollo, Smartlead: tools per SOP step
| SOP Steps | Tool | Role |
|---|---|---|
| 1-3: Segment scoring | Clay | Conditional columns output tier label and route-ready flag; pushes tagged contacts directly to CRM and sequencer |
| 2-4: All-in-one database | Apollo | Database search, segment filtering, list building, and sequence assignment in a single platform |
| 4: Sequence assignment | Smartlead / Instantly | Tag-based imports map directly to tier labels defined in step 1 |
| 3: CRM routing | HubSpot / Salesforce | If-then rules on contact properties; Tier 1 manual-review gates before sequence activation |
A sync lag between Clay scoring and CRM routing creates a window where contacts carry a tier tag in Clay but none in CRM, causing reps to route without the tag. Keep steps 1-3 in the same system and push to CRM only when both the tier tag and route-ready flag are confirmed.
Frequently Asked Questions
5 questions on the segmentation & routing SOP
Three tiers is the operational standard for most outbound teams. More creates routing complexity reps cannot act on consistently; fewer flattens different buyer behaviors into the same action, over-sequencing low-fit contacts.
Confirming no contact in the batch belongs to an account already active in a sequence. Rep conflicts and duplicate outreach are harder to recover from than a missed enrichment field, so this gate belongs first, not last.
Routing on job title alone without firmographic qualification. A VP of Sales at a 10-person startup and at a 500-person company carry the same title but warrant entirely different sequences, rep tiers, and personalization depth.
Quarterly minimum. The practical trigger: when closed-won deal distribution shifts across tier labels, recalibrate the tier boundary criteria before the next batch cycle.
Apollo covers steps 2-5 natively via filters, sequence assignment, and workflow rules. Tier 1 contacts requiring manual AE approval before launch still need a CRM property or manual list as a staging gate, since Apollo has no native "hold for rep approval" step.
SOP documented. Now build the list it runs against.
The ICP to List Building SOP covers how to define and source the contact batches this routing SOP processes.