The Myth of Fully Automated Lead Gen for Auto Wreckers
WRIO Autoparts is a process automation platform that helps auto salvage yards detect buyer requests in their inbox and auto-reply with inventory matches.
We sell automation. Naturally, we tried to automate our own sales. We scraped 1,000+ leads from Google Maps, set up an email sequence, and prepared to hit "Send All".
Then we stopped. And thank god we did.
The "Delivery Status Notification (Failure)" Nightmare
We ran a small test batch. 10 emails.
Result:
- 3 Bounces (30% failure rate)
- 1 "Wrong State" (Lead was in Michigan, we targeted Ohio)
- 1 Generic "Info@" bucket (Never opened)
If we had sent 1,000 emails, we would have had 300 bounces. AWS SES (our email provider) bans accounts with a bounce rate > 5%. We would have burned our domain reputation in 10 minutes.
The Problem with "Verified" Scrapers
We used a top-tier Google Maps scraper. It gave us "Verified Emails".
But "Verified" in scraping terms just means "The regex found an @ symbol on the website."
It doesn't mean:
- The business is still open.
- The email
deforestusedparts@aol.comis checked by a human. Universal Auto Partswebsite hasn't been down for 6 months.
We learned this the hard way today. Just minutes ago, danddcap@aol.com bounced. Technically valid format, but dead inbox.
Lesson: In the Auto Wrecker industry, digital presence is rustic. AOL addresses are almost always a red flag.
The Pivot: The "Manual Grind" Protocol
We decided to do the unscalable thing. We implemented a Strict Verification Workflow.
Why? Because we aren't just sending "Check out my demo" spam. We are sending real buyer leads (money) to these yards. If we send a hot lead to a dead email, we are burning cash.
Step 1: AWS SES Verification (The Tech Check)
Before any email enters our draft list, we run it through a script that pings the AWS SES VerifyEmailIdentity API.
// scripts/verify-emails.ts
const result = await verifyEmail('sales@uap-oh.com');
if (!result.valid) {
console.log('REJECTED: Invalid Format / Domain');
}
This catches typos and dead domains immediately.
Step 2: The "Eyeball Test" (The Relevance Check)
We automated the opening of websites using a custom script:
npx tsx scripts/find-fresh-bait.ts "Business Name" "City"
We manually check each tab for 10 seconds:
- Is it a Wrecker? (Or just a mechanic who buys parts?)
- Is the site live? (Universal Auto Parts failed this today).
- Is the email specific? (
sales@is better thaninfo@).
The Result: 10 Perfect Emails
Today, we prepared a batch for Ohio. Our initial list had 10 scraped leads.
- We rejected Universal Auto Parts (Site Down).
- We rejected R&A Auto Salvage (Connection Refused).
- We rejected Deforest Used Auto Parts (AOL Bounce).
We replaced them with Marshall's Auto & Truck Parts and Stricker Auto Parts—both validated, active businesses with strong websites.
We sent 10 emails. 100% Delivery.
Why This Matters
In B2B SaaS, especially for niche industries like Auto Salvage, trust is the only currency. Spamming a 20-year-old family business with a broken template sent to a dead AOL address is the fastest way to be ignored.
Sending a precise, relevant email to a verified business address? That's how you start a conversation.
We treat your inbox with this much respect. Imagine what our software does for your customer's requests.
Frequently Asked Questions
WRIO Autoparts sounds cool, but do I need to verify emails manually too?
No! WRIO Autoparts handles incoming buyer emails. Your customers are already emailing you. We just automate the reply.
Why use AWS SES instead of Mailchimp?
Cost and control. AWS SES costs pennies per 1,000 emails. But you are responsible for your own reputation. That's why we verify so strictly.
Can I use your verification scripts?
verify-emails.ts script is part of our internal automation suite. We plan to open-source select lead-gen tooling later this year.
How many leads can you process this way?
About 20-30 per hour manually. It's slow. But 30 "Yes" conversations are worth more than 3,000 "Unsubscribes".
Is manual verification scalable?
No, and that's the point. Doing things that don't scale (a la Paul Graham) allows us to build genuine relationships and protect our domain health in the critical early stages.
