Lead list quality checklist for Founding Operators

This is the lead list quality checklist adapted for founding operators. It exists because spending too much time on admin, and the checklist below is the shape that actually survives contact with how founding operators work day to day.

What this checklist is for

Purpose: verify a lead list before it leaks bounce rate and burns domain reputation. For founding operators specifically, the value is that it turns a recurring admin task into a 5-minute repeatable artifact. This isn't a generic template - the items below are tuned for founding operators and the tools they actually live in.

The lead list quality checklist (checklist)

• ICP match (firmographic, technographic, geographic)
• Contact validity (email format, role, recency)
• Dedup against existing CRM
• Exclusion list (current customers, opted-out, competitors)
• Send-readiness (verified email, no role bot patterns)

Adjustments for founding operators

founding operators typically live in . That changes how this checklist runs:

• Pull the inputs from the apps founding operators actually use, not generic SaaS exports.
• Anchor on recent activity in the prospect or company - it's the highest-signal field for this role.
• Skip items that don't apply to your weekly cadence; this is a starting shape, not a contract.

The most common way to mess this up

Skipping the dedup step - you email existing customers and pay credibility tax. For founding operators, this shows up as spending the saved time on more admin instead of higher-leverage work. Build the checklist into your week, not as a one-off.

How Strawberry runs this checklist

Strawberry can verify emails, dedup against CRM, and run the exclusion list as one chained workflow - not five tools. For founding operators, Strawberry uses your live tabs and connected apps - so the checklist is filled with your real context, not a placeholder.

When to use this, when to skip

Use this checklist when the work recurs (weekly, per-prospect, per-meeting). Skip it when the situation is novel and judgment-heavy - the checklist is a baseline, not a substitute for thinking.

Caveats

Strawberry holds back on sending email, updating CRM records, or changing shared systems until a human approves the action. Treat the agent as a fast first-draft author, not an autopilot.