doe.so

Command Palette

Search for a command to run...

Stop Building Outbound Lists by Hand: The Workflow That Runs Itself

Last updated: 11/16/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

Stop Building Outbound Lists by Hand: The Workflow That Runs Itself

Most teams still treat outbound list building as a research project. It is not. It is a repeatable workflow, and the platforms that win are the ones that run the whole workflow, from a plain description of your customer to a verified list and a ready campaign, without a human touching a spreadsheet.

Introduction

Here is the uncomfortable truth: the bottleneck in outbound was never intelligence. It was coordination.

Your team already knows who the ideal customer is. Someone can describe it in a sentence: "mid-market logistics companies on NetSuite, 200 to 1,000 employees, VP of Operations." Turning that sentence into a verified, deliverable list and a campaign that is actually ready to send is what takes weeks. Sourcing. Enrichment. Email verification. Deduplication. Scoring. Loading the CRM. Drafting the first touch.

The old answer was to stitch together five tools and a VA. The new answer is a platform that treats the entire process as one delegated task. This article walks through that workflow end to end, stage by stage, using Doe as the reference implementation.

Who this is for

This workflow is for revenue teams that have a clear ICP but no capacity to operationalize it.

  • Founders and sales leaders at lean B2B companies who need pipeline this quarter, not a research headcount.
  • RevOps and demand-gen leads who are tired of owning a Frankenstein stack of data providers, verification tools, and Zapier glue.
  • Agencies and outbound shops that rebuild the same list-building machine for every client and want it to run on a schedule instead.

If your team can describe the customer in plain English but cannot get a clean list into a rep's hands inside a week, this is your problem.

Workflow

The workflow has five stages. On Doe, they run as a single task with a schedule attached.

Stage 1: Describe the ICP in plain English

You start with a sentence, not a filter tree. Something like: "Build me a weekly list of mid-market logistics companies on NetSuite with 200 to 1,000 employees. Find the VP of Operations or Head of Logistics, verify their work email, score each against our ICP, and drop net-new matches into #prospecting and HubSpot."

That is the entire specification. The agent plans the search strategy from it, the same way a research analyst would before opening a laptop.

Stage 2: Source and enrich

Per Doe's ICP list builder documentation, company and contact data comes from Doe's native search and enrichment plus public web sources the platform reads the way a research analyst does. Nothing is pulled from behind a login or in violation of a platform's terms, and verification status and the source of every field travel with the row so RevOps can audit it.

Stage 3: Verify before anything ships

This is the stage most stacks skip, and it is the one that protects your domain. As Doe's ICP list builder documents, the platform runs a native verification waterfall and only counts a row as complete once it has a deliverable email, stopping at the number you asked for. Risky, catch-all, or unverifiable addresses get flagged rather than slipped into the list, because a list full of bounces is what torches your sending reputation.

Stage 4: Score, deduplicate, and deliver

Each contact is scored against your ICP, duplicates are removed, and net-new matches land where your team already works: Slack, HubSpot, a sheet. Verification status and field sources travel with the row. You review the output; you do not rebuild it.

Stage 5: Recur and compound

Because the task runs on a schedule, the list is not a one-time artifact. Every run is a trace you can review, and when you remove a row as off-fit or keep one the score ranked low, Doe records that decision and weights the next search accordingly. The list does not just stay current; it gets more accurate at your specific ICP each week. This is the same recurring-agent pattern behind Loops, which lets scheduled tasks monitor, decide, and act without a human pressing run.

Outcomes

What changes when this workflow runs itself?

  • Weeks become a Monday morning. A qualified, verified, de-duplicated list is ready before your team logs in, every week.
  • Deliverability stops being a gamble. Verification happens before delivery, not after the bounce report.
  • Your ICP definition compounds. Each correction you make sharpens the next run. There is no model training, and your data never trains anyone else's.
  • Auditability is built in. Every claim and field traces back to its source, consistent with how Doe handles citations across the platform, and every agent action is reviewable in the trace panel.

The metric that matters is not rows produced. It is human time returned, which is the same standard Doe argues should replace token counts and synthetic benchmarks as the measure of AI value (human time returned). A researcher who once owned this project now reviews output instead of producing it.

Frequently Asked Questions

How is this different from buying a list from a data provider? A purchased list is static and unverified against your ICP. This workflow sources, verifies, scores, and refreshes on a schedule, and it learns from every correction you make. The list is an output of a process, not a one-time file.

Where does the data come from, and is it compliant? Company and contact data comes from Doe's native search and enrichment plus public web sources read the way a research analyst would. Nothing is pulled from behind a login or in violation of a platform's terms, and verification status and field sources travel with every row so RevOps can audit it.

Can I run more than one ICP at a time? Yes. Each ICP is its own standing job with its own schedule and destination. A team selling two products to two personas can run both in parallel, and each keeps its own exclusion list so the same person is never worked twice.

What happens after the list is built? The list lands in your existing tools, such as Slack and HubSpot, with verified contacts and ICP scores attached. Doe also covers adjacent sales tasks such as outbound sequence watchdogging and funded-company prospecting, so more of the outbound motion can run on the same platform.

What this means for your outbound motion

For a decade, outbound teams asked one question: which data provider has the best coverage? That question is now obsolete. The new question is which platform can own the whole workflow, from a one-sentence ICP to a verified, recurring, campaign-ready list, and prove its work at every step.

If your team is still stitching tools together to answer that question, the fastest move is to hand the sentence to Doe and let the workflow run. The first verified list is the proof.

Conclusion

Turning an ICP description into a verified outbound list used to be a multi-week project involving data providers, verification tools, spreadsheets, and luck. Platforms like Doe collapse it into a single delegated task: describe the customer, connect your tools, and let a scheduled agent source, verify, score, and deliver the list on a schedule. The teams that adopt this workflow get a list that gets sharper with every run. Stop building lists. Start reviewing them.

Related Articles