Everyone talks about subject lines and segmentation like those are the hard parts of email marketing. They are not. Real problems start when email never reaches the inbox. No sugarcoating this: poor deliverability ruins campaigns faster than bad creative. The qualification criteria you use to accept a prospect reveal whether you will succeed or crash after onboarding. If you want predictable campaigns, you need a strict checklist up front and a process that treats deliverability as a technical problem, not a creative one.
Why agencies and in-house teams keep shirking deliverability checks
Most teams ignore deliverability because it is messy, technical, and invisible until something goes wrong. Sales teams want quick wins and large lists. Account managers sell volume. Marketing leaders chase growth numbers. Deliverability engineers are thin on the ground. When everyone is rewarded for short-term gains – opens, clicks, list size – no one asks whether the emails actually arrive.
Here is the practical consequence: you onboard a prospect with a big, cold list and three weeks later the sending IP is on a blacklist, your ESP suspends the account, and everyone points fingers. That was preventable if the prospect had been checked against a qualification rubric that prioritized reputation, authentication, and list provenance.
The real cost of poor deliverability – why it matters right now
Bad deliverability hits https://highstylife.com/link-building-outreach-a-practical-guide-to-earning-quality-backlinks/ beyond a single campaign. It damages your sending domain, hurts other clients on shared IPs, triggers additional compliance overhead from your ESP, and can force you to migrate IPs or switch providers. The cost is not just lost opens. It is time, reputation, and revenue: lost sales this quarter, replacement of tainted IPs, and hours spent cleaning lists instead of creating offers.
There is also a timing problem. ESPs and mailbox providers tighten filters periodically. A practice that worked in June can fail in September. That means any team that ignores deliverability is running on borrowed time. You need to treat deliverability as urgent because once a reputation is damaged, recovery is slow and expensive.
3 reasons most prospect qualification processes fail to catch deliverability risk
Here are the three most common mistakes I see when teams qualify prospects for email programs.
-
1. They focus on list size instead of list health
Sales will celebrate a 500k list. A technical review reveals 30% hard bounces, a bunch of spam trap hits, and 70% entirely inactive addresses. Size is vanity. Engagement is survival. If your qualification criteria reward list volume above health, you will burn IP reputation quickly.
-
2. They assume authentication is “set it and forget it”
Prospects often claim SPF, DKIM, and DMARC are configured. In practice, records are partial, multiple senders conflict with SPF limits, or DKIM keys rotate unpredictably. A missing or misconfigured record allows mailbox providers to mistrust your messages. That mistrust compounds over weeks of sending.
-
3. They ignore sending history and complaint signals
Donor lists, event lists, and purchased lists each carry different risks. Complaint rates, unsubscribe trends, and prior blacklisting are predictive of future problems. Teams dismiss past behavior as irrelevant to a new campaign. It is not. Past complaints often forecast future ISP punishment.
How qualification criteria reveal whether a prospect is a future liability or a partner
Qualification criteria do two things: they surface technical risk and force honest conversations up front. When you ask precise questions – where did the list come from, what percent of addresses are verified, show me DMARC reports – you get fewer prospects but fewer disasters. If you only ask for a revenue target and a list size, you will hire headaches.
Here are the categories a good qualification process must cover: ownership and provenance of the list, sending authentication status, recent sending volume, engagement metrics (opens, clicks, complaints), bounce history, blacklist checks, and business model signals like incentives or deceptive subject lines. These are not optional. Each item maps to a cause-and-effect link: poor provenance – more spam traps; missing authentication – lower inboxing; high complaint rate – downstream ISP throttling.
How to introduce deliverability checks without killing the sales pipeline
Pitch this to sales as risk reduction, not gatekeeping. Your job is to protect campaign performance and the agency’s reputation. Introduce a light-touch audit in discovery that becomes a hard requirement before any production sends. Make the audit quick and objective so it does not slow legitimate business down.
Here is a practical approach I use: a short, scored checklist that yields green, yellow, or red status. Green prospects proceed. Yellow prospects require a remediation plan and pilot. Red prospects get a firm “not now” until issues are fixed. That triage keeps sales happy because most good prospects are green and problematic ones are addressed before money changes hands.
5 steps to implement a deliverability-focused prospect qualification process
Below are five concrete steps you can embed in onboarding. These are battle-tested – I learned them the hard way after onboarding a client with a 40% bounce rate that got our shared IP suspended for six weeks. That downtime cost us tens of thousands and a lot of client trust.
1. Discover: ask precise provenance questions
Don’t accept vague answers. Ask where each segment came from, when it was collected, and if opt-in records exist. Request a sample of 10k addresses for analysis. Ask about incentives used to collect emails and the last time a re-permission campaign ran.
2. Audit: run technical checks and a small warmup send
Check SPF, DKIM, DMARC, MX records, and domain age. Run sample sends to seed lists across major providers to check inbox placement and spam folder placement. Use bounce and complaint simulations. If the domain fails basic checks, stop and fix first.
3. Score: apply objective thresholds
Use a scoring rubric. Example rules: complaint rate under 0.1% passes, hard bounce under 2% passes, authentication fully configured passes, list > 90 days old and engaged passes. Score each area and produce a total. If a prospect scores below threshold, require remediation.
4. Pilot: run a low-risk, high-value test
Before full roll-out, run a small campaign segment to measure real-world behavior. Use the most engaged segment and send conservative content. If the pilot shows acceptable delivery and low complaints, expand. If not, pause and apply fixes.
5. Enforce: require fixes or decline the work
Make remediation non-negotiable. If prospects will not fix authentication, cannot provide provenance, or refuse to clean lists, decline the project. It’s a hard stance, but necessary. Each time you accept a risky list, you set up future failures.
Practical scoring table you can copy today
How to use it: sum weights for passing items. Set a pass threshold, for example 70/100. Use this to quickly decide who goes to pilot and who needs remediation.
What to expect after enforcing qualification – realistic outcomes and timelines
Be blunt: if you start enforcing these criteria today, you will lose some prospects. That is good. You will also shield your teams from long outages and rebuilds. Here is a realistic timeline and expected outcomes after you start enforcing deliverability checks.
-
Week 0-2: immediate triage
Run audits and assign scores. Expect 20-40% of prospects to be flagged yellow or red. For the flagged ones, work with prospects on quick wins – fix DMARC, add proper SPF includes, remove obvious bounce-heavy segments. This phase reduces immediate risk but might not fully repair reputation.
-
Week 3-6: pilots and warmup
Run small pilots for green and remediated prospects. For new sending, use IP warmup if you have dedicated IPs, and throttle sends on shared IPs. You should see inbox placement stabilize and complaints either confirm issues or show acceptable behavior. If a pilot fails, you loop back to list cleaning and stricter segmentation.
-
Month 2-3: scale and monitoring
Gradually scale volumes. Expect to see open rates improve if you focused on engaged segments. Complaint rates should fall under 0.1% with clean lists. Blacklist incidents should drop to near zero if the scoring is enforced. If prior reputation issues existed, full recovery can take 90 days or more depending on ISP memory and the depth of the problem.
-
Month 4-6: stable operations
Your deliverability should become predictable. You will have playbooks for remediation, a tracked scorecard, and fewer emergency escalations. Revenue becomes more reliable because campaigns actually reach inboxes. At this stage, you can afford to iterate on copy and creative with confidence.
Thought experiments to test your qualification rules
Run these in your next team meeting. They are cheap mental models that reveal holes in your process.
-
Thought experiment 1: The 500k “great lead”
Imagine a prospect offers a 500k list with the argument that “we just need volume.” Apply your scoring rubric. What happens if the list fails the bounce threshold? Does your team revert to volume-based incentives or block the send? If you would accept the list, your qualification rules are softer than you think.
-
Thought experiment 2: The legacy sender
A client has been sending for years but never enforced DMARC. Their open rates are average. You run a DMARC report and see spoofing attempts. If you require immediate DMARC enforcement, will the client comply or push back? If they push back, are you willing to decline? This reveals your enforcement tolerance.
-
Thought experiment 3: The “cleaner” promise
Prospects sometimes promise to clean lists after you start. Simulate a scenario where they delay cleaning for six weeks. What is the cost to your current deliverability? If the cost is high, require cleaning before any send. If it is low, document why. These thought experiments force policy clarity.
Expert-level insights from rebuilding deliverability after failures
I once took on a tech client who insisted their 1.2 million list was fine. They had never removed bounced addresses. After the first send our SPF was flagged and an ESP blocked us. We had to migrate to a new sending domain, implement DKIM rotation, and run a slow warmup on a clean segment. Lessons learned:
- Do not assume technical competence. Verify it. A client can be very successful in their business and still misconfigure DNS records.
- Prepare an off-ramp. Have a migration plan to a new domain or subdomain when reputation is irreparably damaged.
- Document everything. When an ESP asks why you sent to a bad list, show proof of the audit and the client’s consent. That reduces penalties.
Those steps cost time and money. They would have been avoided with a hard qualification gate. After that incident, our close rate dropped because we lost some prospects, but our campaign uptime and client satisfaction improved significantly. The trade-off was worth it.
Final practical checklist to start today
Use this quick checklist in discovery calls. If a prospect answers no to any two of these, flag them for a deep audit.
- Can you provide clear opt-in records for the list?
- Are SPF, DKIM, and DMARC fully configured and validated?
- Is your 30-day hard bounce rate under 2%?
- Is your 30-day complaint rate under 0.1%?
- Can you share recent sending volumes and engagement metrics?
- Are you willing to run a 5-10k pilot before scaling?
If you want one take-away: make deliverability a gate, not an afterthought. Qualification criteria are your best early-warning system. They stop bad prospects before they burn your IPs, your time, and your clients’ trust. Implement the checklist, score prospects, and insist on pilots. It feels strict, and it is supposed to. Your inbox placement and campaign results will improve because you treated deliverability like the technical risk it is.
