Brand Logo
Research note

SPF, DKIM, DMARC, and Decision-Maker Search: A B2B Outbound Scenario Guide

2026-09-23 · Lena Kovacs

Editorial research diagram for SPF, DKIM, DMARC, and Decision-Maker Search: A B2B Outbound Scenario Guide

There's no single answer to "what does my B2B outbound stack actually need?" I've watched teams buy a $20K data platform before they'd even authenticated their sending domain. I've also watched teams run 10,000 cold emails a month through a personal Gmail address. Both eventually hit the same wall — but they hit it from opposite directions.

So here's what I tell people now: figure out which scenario you're in, then fix that one. Everything else can wait.

Why There's No One-Size-Fits-All Answer

It took me about three years and somewhere around 400 outbound campaigns to understand that most deliverability problems aren't what they look like on the surface. Teams assume it's their copy. It's usually DKIM. They assume it's their data quality. It's usually that they're blasting catch-all inboxes. They buy a new decision-maker list, but they never checked whether their domain has a DMARC record at all.

The most dangerous sentence in this space is "our competitor does it this way." Because their send volume, their domain age, and their ICP are probably nothing like yours.

Let me show you what I mean. Below are the three scenarios I see most. Pick the one that sounds like your team, and skip the rest.

Scenario 1: You're Still Asking "What Is a Business Contact?"

Let's get the definition out of the way, because I see it fumbled constantly.

A business contact is a professional identity tied to a specific company — not a personal inbox, not a scraped phone number, but a verified point of contact that maps to an organization.

I break them into three rough categories:

When should a B2B sales team actually use one? Basically in one situation: when the person's role is directly relevant to what you're selling.

If you sell email security to a 50-person SaaS company, emailing their CTO makes sense. Emailing their office manager does not.

The mistake I see way too often: teams buy a list of 5,000 contacts and hit "send." That's not outbound. That's a newsletter nobody signed up for.

Scenario 2: Your Emails Land in Spam and Nobody Knows Why

This one's the most common. And it's the one where I usually annoy people by saying "check your authentication first."

Quick refresher on the three records that matter:

Sounds simple. It isn't.

Last year I worked with a 12-person SDR team that spent eight weeks chasing a "copy problem." It turned out their SPF record had three nested includes sitting right at the 10-lookup limit (RFC 7208). Their DNS provider quietly truncated the chain. No alert. No bounce. The emails just... vanished.

That's the kind of thing no playbook warns you about. It shows up when someone sits down and reads the DNS records out loud, one by one.

If you want the full configuration walkthrough, the okki-go SPF DKIM DMARC guidance covers the mechanics — include limits, key lengths, policy escalation. But here's the honest caveat: every domain is different. Copy-pasting someone else's setup is exactly how you end up with the 10-lookup limit problem.

What to actually check:

  1. Count your SPF includes. Above 10 lookups is a red zone.
  2. DKIM key length. 1024-bit is the floor. 2048 is safer.
  3. DMARC policy. Start at p=none, monitor reports for 2-4 weeks, then move to quarantine.
  4. Alignment. At least one of SPF or DKIM has to align with your From domain.

I've watched an entire domain get blacklisted because someone pushed DMARC to p=reject without ever running reports. Don't be that team.

Scenario 3: You're Scaling and Need Decision-Maker Search + Data APIs

This is the "emergency" scenario. You've got positive replies. You've got inbox placement. What you need now is volume — which means decision-maker data.

This is where something like okki-go decision-maker search fits in, alongside a broader stack of enrichment and verification tooling. But the tool choice matters less than three questions:

1. How fresh is the data?

A 2022 job title is worthless for a company whose VP left 6 months ago. If the API company data you're pulling doesn't come with a "last verified" timestamp, treat it as stale by default.

2. When do you verify?

Verification at send-time is fine for small volumes. Above a few thousand contacts per month, verify at the point of list creation and again right before send. Read the API email verification documentation carefully — some APIs return "unknown" for catch-alls, and teams treat that as valid. It isn't.

3. How many sources are you pulling from?

Waterfall enrichment — stacking multiple providers in sequence — has basically become table stakes in 2024-2025. I'm not 100% sure of the exact number, but industry estimates I've seen suggest a single provider covers somewhere between 50-70% of a typical B2B contact database. It varies wildly by segment.

Take this with a grain of salt: if you're only pulling from one source, you're probably missing a chunk of your target list — and emailing the wrong people at the ones you do have.

How to Tell Which Scenario You're In

Three quick diagnostics:

If you overlap two or three of these, fix them in this order:

  1. Authentication first. No amount of data fixes a spam-foldered domain.
  2. Data second. Bad contacts waste even a perfectly warm domain.
  3. Volume third. Scale only after the first two are stable.

I get why people want to jump straight to the sexy stuff — intent data, agent-native prospecting, sequencing automation. I've done it myself. But the teams I see scaling cleanly in 2025 are the ones who treated the boring layer first.

One Honest Caveat About My Own Experience

My background is mostly mid-market B2B teams — 50 to 500 seats, mostly North America and the EU. If you're running enterprise ABM or you're targeting APAC markets, the rules shift. GDPR sets a much tighter boundary than state-level US privacy laws, and some APAC regions have DMARC enforcement patterns that catch teams off guard.

I've only worked with a handful of enterprise-scale deployments. I can't speak to how these principles behave at that level.

What I can tell you is this: whenever someone asks me "what's the one thing I should fix first?", the answer has been the same for four years running — look at the records before you look at the revenue.

Lena Kovacs
Lena Kovacs

Lena Kovacs is an independent AI sales agent analyst covering AI SDRs, autonomous prospecting, research agents, email writers, personalization systems, sales assistants, and outbound workflow automation. She applies ISO/IEC 42001 governance concepts while testing task completion, factual accuracy, hallucination rate, approval controls, response latency, personalization relevance, escalation behavior, and auditability. Her evaluations help sales leaders determine where agentic workflows can improve productivity, where human review remains necessary, and how to compare automation claims with measurable outcomes.