Your Tier-1 ABM list is 50 accounts. Your AEs run bespoke plays against each one. That is manageable.
Tier-2 is the next 500 to 3,000 accounts. The ones that fit your ICP perfectly but are too many to run with hand-crafted plays. Traditionally those accounts get ignored or dropped into a generic nurture that treats them the same as cold list pulls.
This post is a 20-minute setup to give Tier-2 accounts a programmatic version of the Tier-1 treatment: real-time signal, dedicated alert routing, and automated first-touch outreach, without the manual overhead.
I am Elene on the Leadpipe team. I have seen this setup move the needle for dozens of sales teams. The mechanics are simple. The discipline is in the list curation, not the tooling.
The answer up front
Tier-2 ABM at scale has three layers:
| Layer | What it does | Time |
|---|---|---|
| 1. Account list | Curate 500 to 3,000 accounts that match Tier-2 criteria | 10 min |
| 2. Visit signal | Leadpipe tags identified visitors from those accounts | 5 min |
| 3. Programmatic action | Alert + automated sequence triggered by tagged visit | 5 min |
Total: 20 minutes of setup, with two follow-up hours for copy.
The key insight: Tier-2 does not need bespoke plays per account. It needs one good play that triggers on a signal. The signal (an identified visit from the account) is what makes it warm. Your job is to make the play good.
The playbook
Step 1: Build the Tier-2 list (10 minutes)
Tier-2 is defined by ICP fit, not by strategic account status. It should be mechanical, not aspirational. Use three inputs:
- Firmographic fit. Industry, size band, geography. These are the same filters you use for your Orbit audiences.
- Technographic fit (if available). Uses a specific CRM, a specific category of tool, a specific tech stack.
- Signal of buying-committee size. Companies with enough scale to actually close a deal at your ACV.
Pull from one of these sources:
- Your existing Salesforce database filtered to not-yet-engaged accounts matching the filters above
- Clay / Apollo / ZoomInfo firmographic pull
- A hand-built list from industry directories
Target size: 500 to 3,000 accounts. Below 500 and you should be running Tier 1. Above 3,000 and your filters are too loose.
Example Tier-2 list spec for a mid-market RevOps tool:
Tier-2 list v1 - April 2026
Industry: SaaS, Fintech, Martech
Company size: 50 to 500 FTE
Geography: US, CA, UK
Tech stack: Salesforce OR HubSpot present
Exclusions: existing customers, active opps, closed-lost <6mo,
competitors
Result: ~1,800 accountsSave the spec. You will re-refresh the list quarterly and you need to remember how you built it.
Step 2: Tag the list in Leadpipe (5 minutes)
In the Leadpipe dashboard, upload the account list under the “Target Accounts” feature with a tag:
tag: tier_2_abm_saas_v1Every time Leadpipe identifies a visitor from one of these accounts, the webhook payload carries the tag. This is the same mechanism the track target accounts playbook describes, just applied to a larger list with programmatic handling.
For EU/UK accounts on the list, Leadpipe will default to company-level data. Visits will surface the account but not necessarily a named person. That is still actionable at the account grain, it just shapes the outreach channel (account-level LinkedIn ad, not 1-to-1 email).
Step 3: Configure the alert and routing (5 minutes)
Tier-2 alerts should not wake up a rep at 3am. They do not need the 7-minute SLA that Tier 1 pricing visits demand. But they should not land in a general inbound queue either.
Recommended structure:
Tier-2 ABM alert routing
Priority page (pricing/compare/demo):
→ Slack DM to territory AE, 1-hour SLA
→ Automated first-touch queued for AE review
Product/case-study page:
→ Channel post in #alerts-tier-2, 4-hour SLA
→ Automated first-touch queued for SDR review
Blog/help page:
→ Daily digest to SDR team
→ Rotate into warm outbound sequenceRoute based on page_url from the webhook. Keep the logic simple. Three branches is usually enough.
Step 4: Write the automated first-touch template
The Tier-2 first-touch is automated-but-personalized. It fires from the rep’s address. It references the account and the role, not the specific page or timestamp.
Subject: [Company Name] + [category]
Hi [First name],
I work with [3 similar-sized] [industry] teams on [specific problem
in their category]. If [Company Name] is anywhere near evaluating,
I can share how they are thinking about it.
Worth a 15-minute call, or happy to just send a one-pager.
- [Rep first name]The template should be identical to the warm outbound sequence touch 1, because that is what this is. The differentiator is that you already know the account is in your Tier-2 ICP, so the copy can be a bit more directed without being presumptuous.
Step 5: Schedule the quarterly refresh
Tier-2 lists go stale. Companies grow out of the size band, new companies enter it, competitors get acquired, techstacks change.
Set a calendar recurrence for every 90 days:
- Re-pull the firmographic filter
- Diff against the current list
- Add new matches, remove out-of-band accounts
- Re-upload to Leadpipe with version tag (v2, v3, etc.)
A quarterly cadence is enough for stability. Monthly is overkill. Annually is too slow.
Sample alert for a Tier-2 visit
:chart_with_upwards_trend: Tier-2 ABM visit - 1 hr SLA
Who: Alex Chen · Head of Operations · Orion Labs (145 FTE)
List: tier_2_abm_saas_v1
Page: /pricing (1m 45s)
/integrations/salesforce (35s)
Intent: tier_2_priority_page
Owner: @tara (territory: Central US)
Template queued: "tier-2-first-touch-v2"
Send or hold: :thumbsup: to send, :x: to holdThe :thumbsup: reaction fires the pre-drafted email from the rep’s address. The rep reviews it in 10 seconds, reacts, done. That is what makes Tier-2 scalable: the rep is not writing, they are approving.
What Tier-2 ABM is NOT
This setup is not a replacement for Tier-1 account-based plays. Tier-1 accounts are the 20 to 100 companies your team runs bespoke plays against, with dedicated research, custom landing pages, executive engagement, and named-account sprints.
Tier-2 is the layer below that, where the economics do not justify manual effort per account but where generic cold outbound leaves signal on the table. The setup in this post solves the Tier-2 layer specifically.
This is also not a replacement for inbound. Tier-2 runs alongside inbound. An inbound demo request from a Tier-2 account gets treated as inbound. A silent visit from a Tier-2 account gets treated as Tier-2 signal.
Common failure modes
List too broad. “All mid-market SaaS” produces 15,000 accounts. Your filters are not actually filtering. Tighten.
List too narrow. 150 accounts is a Tier-1 list, not a Tier-2. Either move it to Tier-1 or expand the filter.
No quarterly refresh. Your v1 list from last year still has 200 accounts that churned or got acquired. Rotate quarterly.
Forgetting suppression. Tier-2 list includes current customers because the filter didn’t exclude them. See the exclusion post for the pattern. Leadpipe’s native suppression applies to target account lists too.
Same template for Tier-1 and Tier-2. Tier-1 deserves a bespoke message. Tier-2 deserves a templated-but-good message. Do not use the same copy for both.
Alert fatigue. Tier-2 list of 3,000 accounts with a permissive page filter produces 40 alerts a day. Reps stop reading them. Either tighten the list, tighten the page filter, or batch alerts into a daily digest for lower-priority pages.
Ignoring the signal. You set up Tier-2, the alerts fire, nobody owns the response. Assign a rep per territory and make Tier-2 response part of their weekly review.
Over-manual handling. A rep rewrites every Tier-2 template from scratch. That is Tier-1 workflow pretending to be Tier-2. The point of Tier-2 is template + approval. Use the template.
Measurement: how to know it is working
Instrument Tier-2 as its own pipeline source in the CRM (source: tier_2_abm).
Track:
| Metric | Target (after 60 days) |
|---|---|
| Visits from Tier-2 accounts per month | 5 to 15% of the list |
| Alerts generated per week | Scales with visit volume |
| Reply rate on Tier-2 automated first-touch | 8 to 12% |
| Meetings booked per 100 Tier-2 alerts | 4 to 8 |
| Tier-2-sourced pipeline as % of total | 8 to 20% by day 90 |
If reply rate is below 6%, the template is too templated. Add more role-specific variants.
If meetings per 100 is above 8, the list is tight and the timing is right. Consider expanding the Tier-2 list carefully.
If Tier-2 pipeline is not measurable as a distinct source in your CRM, add the source tag. You cannot manage what you cannot see.
Why this beats “tier-less” outbound
Most teams run one outbound motion: cold list pulls, bulk sequences, uniform copy. They do not distinguish between accounts that matter and accounts that don’t. The result is low reply rates across the board and reps who stop believing in outbound.
Tiering segments the work by how warm the signal is. Tier-1 gets hand-crafted. Tier-2 gets signal-triggered automation. Below that goes to nurture. The rep’s time concentrates where warmth concentrates.
Visitor identification is what makes Tier-2 work. Without it, you are guessing which Tier-2 accounts are in-market. With it, you know, in real time. That is the whole game.
On US B2B traffic Leadpipe identifies 30-40%+ of visitors deterministically. The independent accuracy test scored Leadpipe at 8.7/10, RB2B at 5.2, Warmly at 4.0. Accuracy matters especially on a programmatic Tier-2 workflow, because a mis-match on a tagged account triggers outreach from a rep who believes the account is in-market when it isn’t.
Leadpipe identifies 30-40%+ of your US B2B visitors with full contact data on the Pro plan at $147/mo. No credit card to start the 500-lead trial. Start identifying visitors →
