A search becomes an enriched, deduplicated, CRM-checked list in a live campaign, without a spreadsheet in the middle.
The outbound list build is the most-automated workflow in B2B and still, in most companies, the one with a CSV in the middle of it. Somebody exports a search, somebody else enriches it, a third person checks it against the CRM by eye, and a week later a version of that file becomes a campaign. Every step is automatable and the one that matters most is the one people skip.
That step is the CRM check. Sequencing a live customer, an open opportunity or someone another rep contacted last month is the failure this workflow exists to prevent, and it is the only failure here that costs you something you cannot get back. The enrichment is what makes the list worth sending to. The CRM check is what stops it embarrassing you.
Read what your Sales Navigator contract permits. LinkedIn's terms constrain what may be extracted from search results and how, and the constraint is contractual rather than technical, which means it does not announce itself when you cross it. This page describes the shape of the pipeline; what your agreement allows at each step is yours to answer first.
5 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.
Sales Navigator filters are the most precise targeting most teams have access to. Save the search rather than exporting it, so the definition lives somewhere reviewable instead of in a filename.
The table is the workbench for everything that follows: enrichment, the CRM check, the conditional branches and the push to the sender. Nothing leaves it as a file.
Profile URL or email in, a structured record out: current role, company, headcount, location, confidence. This is what turns a list of names into a list you can write a first line for.
A Lookup against every row. Already a customer, already an open deal, already contacted in 90 days, already owned by another rep: each one is a suppression rule, cheap to write and expensive to omit.
Create the contact so the CRM knows this person is in a sequence, then push to the campaign. Smartlead's webhooks fire on every reply and bounce, so the timeline stays honest without a second sync.
Each one is a single conditional in the table. Together they are the difference between a list and a liability.
Each one of those is a single conditional, and the reason to write them before the first send rather than after it is that every one of them is cheaper to add now than to apologise for later.
This workflow ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it, and how to check it worked. Point an agent at it and it has what it needs without reading 5 sets of vendor docs first.
--- name: outbound-list-suppression description: Build an outbound list pipeline that enriches a prospect list, checks ever y row against the CRM for customers, open deals, recent contact and existing... --- # Signal to sequenced contact ## What you are building ## Prerequisites ## The tools, and how to call them → Reverse Contact, Clay, HubSpot, Smartlead, LinkedIn Sales Navigator ## Build it → 6 steps ## Gotchas ## What breaks, from the vendors' own docs ## How to verify it works → 5 checks
mkdir -p .claude/skills/outbound-list-suppression curl -o .claude/skills/outbound-list-suppression/SKILL.md https://www.reversecontact.com/integrations-hub/skills/outbound-list-build.md
For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it https://www.reversecontact.com/integrations-hub/skills/outbound-list-build.md directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.
9 of the joins in this chain have a full guide behind them, Clay and LinkedIn and LinkedIn and Reverse Contact among them. The chain crosses 5 of the seven layers a stack splits into, from the prospecting layer outward, which is why no single vendor owns it.
Documented by one of the vendors in the chain, and easier to design around than to discover.
All five are documented by a vendor rather than observed by us, which is the useful part: a limit you can read is a limit you can design around before it costs you a week.
What each component bills on, and which line actually scales with your volume.
| Component | Billing | What drives it |
|---|---|---|
| Sales Navigator | Per seat | Core, Advanced or Advanced Plus. This workflow needs a seat, not the Advanced Plus CRM Sync edition. |
| Clay | Per action | Rows multiplied by columns, charged on the attempt. The lever is conditional runs. |
| Reverse Contact | Per credit | One call per row that reaches the enrichment step, 2 credits for a reverse lookup. Nothing for a freshness check first. |
| HubSpot | Any tier | Lookups and writes go through Clay, so no Data Hub requirement. |
| Smartlead | From $39/mo | Off a plan slider. Confirm the tier for your mailbox count. |
The cheapest change you can make to this bill is the order of the columns. Suppression before enrichment means you never pay to enrich a row you were going to drop, and on a list with an established CRM behind it that is routinely a third of the rows.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score your logic can branch on. The free trial takes no card and runs until the 500 credits a new account starts with are spent, which is enough to run this end to end before anyone signs anything.
Free trial, no card required, and 500 credits to start.
Because every row you drop after enriching is a credit and an action spent on somebody you were never going to contact, and on a list built against an established CRM that is often a third of the file. The only reason to enrich first is if a suppression rule depends on an enriched field such as company domain, and in that case enrich only the field the rule needs.
Yes, and it will be cheaper per row. What you lose is the ability to look at 5,000 rows and see which ones resolved, which is how you find out a segment does not enrich well before you send to it. For a repeated, stable list build n8n is the better home. For an exploratory one, the table is doing real work.
For the suppression rules, yes, and they are the part that justifies the build. Without a CRM to check against, this is a list build with enrichment on it, which is useful but is not what makes the difference. The same shape works on Salesforce, with the org's validation rules to think about.
Nobody can tell you, including us. Reverse Contact publishes 70%+ identity match as a global figure and that is not a promise about your segment. Run 500 rows from the actual search you intend to use, count what resolved, and build the economics from that number. It takes an afternoon and it is the only reliable input.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.