LeadGrow
Pipeline ready

Your outbound pipeline is live

19,323 qualified homebuilders scraped. 650 pulling permits right now. Here's exactly what to do next to get campaigns live.

19,323
Builders Scraped
~10,400
Emails Found
3,987
Priority-State Ready
650
Active Permit Pulls
1
Pull the latest

The repo already has everything. Just pull and install dependencies.

cd david-lancaster-coaching
git pull origin master
pip install -r requirements.txt
2
Add your API keys

Create a file called .env in the repo root. It's gitignored — never gets committed.

MILLION_VERIFIER_API_KEY=your_key_here    # millionverifier.com/api
SMARTLEAD_API_KEY=your_key_here           # app.smartlead.ai → Settings → API

Get your Million Verifier key at app.millionverifier.com/api
Get Smartlead key at app.smartlead.ai → Settings → API Keys

3
Validate your email lists

Before anything goes to Smartlead, validate the emails to kill hard bounces. Run this on each priority-state file:

python validate_emails.py \
  --input ../temp/lancaster-data/smartlead_ready/community_developer_priority_state.csv \
  --output ../temp/lancaster-data/validated/community_developer_priority_state_validated.csv

Repeat for each file in ../temp/lancaster-data/smartlead_ready/. Keep rows where _mv_status is ok or catch_all. Drop invalid.

4
Write your email sequences with Claude

Open Claude Code in the repo folder and paste this prompt exactly:

I'm Dave Lancaster, a capital markets broker at Cushman & Wakefield. I coach custom and spec homebuilders on financing — specifically revolving credit facilities that replace the 5-lender stack builders usually juggle (land loan, lot dev loan, construction loan, etc.) with a single facility. I need to write a 3-email cold outreach sequence targeting community developers — private regional builders doing 40–200 lot projects in FL, TX, GA, NC, TN, and AZ. My case study: Park City luxury infill builder, $3.65M all-in, $5.75M sale, 15 months. Single facility covered land + construction. ~1% fee = ~$30K/deal for me. Read the files in `company/` before we start — `offer.md`, `dave_lancaster.md`, and `case_studies.md` have everything about my situation and what I'm selling. Once you've read those, help me write Email 1 of 3 for community developers. Hook angle: the problem with juggling 5 lenders. Keep it short, direct, no fluff. I'll review and we'll refine from there.

Claude will read your offer doc, your ICP, and your case studies — then help you write and refine all 3 emails. It'll run spam checks automatically and add Smartlead-ready spintax when you're happy with the copy.

5
Create a branch and PR for your copy

Once copy is finalized, save it to the repo and create a PR so Mitch can review before it goes live:

git checkout -b copy/community-developer-sequence-v1
# Claude will save the copy files for you — just commit what it creates
git add .
git commit -m "feat(copy): community developer sequence v1"
git push origin copy/community-developer-sequence-v1

Then open a PR on GitHub. Mitch reviews, approves, and handles the Smartlead upload.

Three things we need from you

Teams recording — community developer case studies
You mentioned these on our onboarding call. Send the recording link and we'll pull the deal numbers for copy angles. This is the difference between generic copy and copy that lands.
Close CRM export — 293 existing contacts
Export so we don't cold email anyone you're already working. In Close: Settings → Export → All Contacts → CSV. Drop it in the repo or email it to Mitch.
Sending domains — what are you warming up?
Let us know what domains you're using in Smartlead and we'll verify SPF/DKIM/DMARC are configured before first send.
First campaign target
community_developer_priority_state.csv
124 contacts — all priority states, all validated. Small, tight, high-signal. Perfect first batch. Once copy is approved, we upload as a Smartlead draft and you review before anything sends.