agentleFS
Frontal-soFrontal-so/outbound-skills/skills/list-building-tips/SKILL.md

list-building-tips

Skill8 starsChanged 4 months agoMITView on GitHub

Pro tips for B2B list building - source mixing, enrichment workflow, template usage, and efficiency principles. Use when building prospect lists, optimizing data quality, or improving prospecting efficiency.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't rely on just one data provider

    line 11
  2. Distinctive:

    Start with proven templates

    line 24
  3. Distinctive:

    Don't rebuild from scratch

    line 26
  4. Distinctive:

    Use existing Clay templates

    line 29
  5. Distinctive:

    Before launching any campaign:

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

List Building Pro Tips

Core Principles

1. Mix Sources

  • Don't rely on just one data provider
  • Each source has different strengths/coverage
  • Combine for maximum coverage

2. Scraping = Step 1

  • Raw scraped data is just the beginning
  • Still need Clay enrichment for:
    • Email verification
    • Phone numbers
    • Company data
    • Custom signals

3. Templates Are Modular

  • Start with proven templates
  • Adjust for specific campaign goals
  • Don't rebuild from scratch

4. Don't Reinvent the Wheel

  • Use existing Clay templates
  • Modify rather than create
  • Learn from what works

Data Quality Hierarchy

1. Verified email (bounced < 2%)
2. Direct phone number
3. Recent activity signal
4. ICP fit confirmed
5. Company enrichment complete

Efficiency Benchmarks

TaskManual TimeWith Clay
100 prospects8-10 hours30 min
500 prospects40+ hours1-2 hours
1000 prospects80+ hours2-3 hours

Quality Checklist

Before launching any campaign:

  • Email bounce rate < 2%
  • At least 70% email coverage
  • ICP criteria verified
  • Recent signals tagged
  • Duplicates removed
  • Competitor customers flagged
  • Do-not-contact list checked

Common Mistakes

  1. Single source reliance - Limits coverage
  2. Skipping verification - Kills deliverability
  3. Over-filtering - Shrinks TAM too much
  4. Under-filtering - Wastes outreach on bad fits
  5. Ignoring signals - Missing hot prospects

Combines with

SkillWhy
lead-sources-guideChoose right sources
clay-enrichment-9stepFull enrichment workflow
email-metrics-benchmarksTrack deliverability
clay-buying-signals-5Add signals to lists

Example prompts

Review my list building workflow against the quality checklist.
What's the fastest way to build a 500-prospect list for fintech CFOs?
How do I diagnose why my email bounce rate is above 2%?

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.