What Should Revenue Operations Teams Evaluate in SPF? The $18K Mistake That Taught Me

In November 2023, we launched a 2,000-contact outbound campaign. Clean sequences. Carefully written copy. A fresh contact database from a provider we'd just subscribed to. And a campaign builder that made the whole operation feel effortless.

The result: a 31% bounce rate, a 0.4% reply rate, and a sender reputation so damaged that our next three months of emails went straight to spam folders.

My first instinct was to blame the data provider. Then the email tool. Then the copy. Classic mistake. I spent six weeks and roughly $1,400 in consulting fees before I found the actual culprit, and it had nothing to do with any of the tools we were using.

It was our SPF record. And it hadn't been touched since 2021.

Let me explain how I got here

Quick context: I run revenue operations for a B2B SaaS company. I've handled outbound prospecting and GTM infrastructure for six years, and in that time I've personally made—and documented—11 significant mistakes totaling roughly $18,000 in wasted budget. I now maintain our team's pre-send checklist so nobody else repeats them. The SPF thing was the most expensive, because it took the longest to find.

In early 2023, we decided to get serious about outbound. We bought a contact database subscription, picked a sales engagement platform with a gorgeous campaign builder, and added a LinkedIn automation tool because, you know, multi-channel. The stack looked professional. The dashboard made us look like we were winning.

To be fair, the tool was solid. The features were impressive. The demo was beautiful. The execution… not so much.

The question everyone asks, and the one nobody does

When I talk to other RevOps folks about this, the conversation always goes the same place: does that contact database have better coverage? Is the campaign builder flexible enough? How many credits come with the plan? All reasonable questions. They're also all missing the point.

Here's the thing: those questions assume the infrastructure underneath your sending is fine. It usually isn't.

SPF—Sender Policy Framework—is an email authentication standard that tells receiving mail servers which senders are allowed to use your domain. It's defined in RFC 7208 and it's one of three core mechanisms, together with DKIM and DMARC, that determine whether your email lands in an inbox or a spam folder. In February 2024, Google and Yahoo started enforcing stricter requirements for bulk senders, including SPF/DKIM alignment and DMARC policy. The writing was on the wall a year earlier. We just weren't reading it.

Most buyers focus on what they can see: campaign builder UI, sequence templates, analytics dashboards. They completely miss sender infrastructure, because it's invisible—right up until the moment everything breaks. Nobody wakes up thinking "my SPF record might be a problem today."

The question everyone asks is "what's the best tool for outbound prospecting?" The question they should be asking is "what's the state of my SPF, DKIM, and DMARC records, and will they survive contact with a new tool?"

What I found when I actually looked

After the third week of terrible campaign performance, I called in a deliverability consultant. His first question caught me off guard:

"When did you last change your SPF record?"

"My what?"

That's when the real conversation started. Our SPF record was a disaster. It listed servers from two email platforms we'd stopped using in 2021 and 2022. It still referenced a marketing automation tool from a previous CMO's era. There was an "include:" entry pointing at a third-party infrastructure we weren't even sure we still belonged to. Total: 16 DNS lookups—past the official limit of 10 set in RFC 7208, Section 4.6.4.

When I say the record was broken, I do not mean "slightly outdated." I mean it was actively damaging us. Every send created confusion at receiving servers. Every campaign increased the chance of authentication failure. The record wasn't helping; it was a liability.

The kicker: fixing it took 20 minutes. A cleaned-up SPF record, DKIM alignment, and a DMARC policy set to monitor. Twenty minutes. Meanwhile, the consultant's first recommendation had been to abandon the domain entirely and start fresh—a plan that would have cost us thousands. Good thing he asked to see the records first. Never expected a DNS record to be our most expensive problem of the year. Turns out it was the easiest one to solve.

The deeper reason this happened

Everyone hears this story and assumes it was a technical failure. It wasn't. The technical failure was a symptom of an organizational one.

Nobody on our team owned email deliverability. IT maintained the DNS records, but they didn't own outbound strategy. Marketing owned the sending platform, but they assumed deliverability was "an infrastructure thing." The SDRs owned the leads but not the pipes. So when a platform got sunset, or a vendor changed, or a new tool joined the stack, nothing got updated. It was everyone's implicit responsibility—which means it was nobody's actual responsibility.

In my experience, that's the real reason outbound programs fail at this level. The tool is usually fine. The data is usually okay. The infrastructure is where the cracks form, because nobody treats it as a living system.

Looking back, I should have audited our infrastructure before buying anything in 2023. At the time, the contract looked great, the feature list looked great, and the demo… the demo was beautiful. But no demo will ever show you what happens on day 40 when your emails stop landing. That's a question you have to ask before you buy.

What this actually costs

Let me put some numbers on it, because "poor deliverability is bad" doesn't capture the damage.

• $1,900 — contact database subscription: six months of credits burned on contacts that never had a real chance of receiving us.
• $2,400 — the sales engagement platform: mostly wasted, because no campaign builder can compensate for broken sending infrastructure.
• $1,400 — the deliverability consultant, who earned every dollar but whose job I should have done myself with two hours and RFC 7208.
• $3,200 — the domain migration and IP warm-up we planned (and almost executed) before we discovered the actual problem.

That's $8,900 in direct, documented waste. The indirect damage was bigger: five weeks of outbound pause, zero pipeline from a 2,000-contact campaign, and a leadership team that quietly concluded outbound "doesn't work" for us. I also believe—though I can't prove it—that some of our best prospects never took us seriously again after watching our emails bounce or vanish into spam.

None of this had to happen. A 30-minute quarterly check of our sender infrastructure would have caught the problem back in early 2023, before we spent a single dollar.

What should revenue operations teams evaluate in SPF?

Given what I went through, here's the checklist I now run every quarter. I keep it deliberately short because short checklists actually get used.

1. SPF record completeness. Pull the record for every domain you send from. Count the DNS lookups. If you're at or near the 10-lookup limit, fix it before anything else.
2. Alignment. Does the domain in your From header match the authenticated envelope domain? If not, the major mailbox providers will treat you as suspicious.
3. DMARC policy. Publish at least a monitoring policy (p=none) and read the aggregate reports. They'll show you which services are sending as you and what's failing.
4. Vendor behavior. Does the sales engagement tool tell you exactly what to add to your SPF record, with clear DKIM setup instructions? If the vendor can't explain its own deliverability requirements, that's a red flag.
5. Email verification before send. B2B contact databases decay somewhere between 20-30% per year by most industry estimates. If your tool doesn't verify emails before sending—real verification, not just "does this look like an email"—you're feeding your sender reputation to the spam filters.
6. Bounce handling. When an email bounces, does the platform suppress it automatically? Or does it keep sending into a brick wall, campaign after campaign?
7. Campaign builder logic. Can you throttle sends, respect time zones, and build multi-touch, multi-channel workflows? Your outreach should behave like a well-trained human rep, not a machine gun.

These seven checks won't guarantee inbox placement—no honest vendor will promise that. They will, however, prevent the dumbest, most expensive category of failure: sending from infrastructure that nobody has looked at in years.

The tool conversation (and, yes, expandi)

Once I'd built the checklist, I went looking for a stack that didn't force me to stitch five tools together. I wanted a contact database that was actually maintained, email verification built into the flow, a campaign builder that didn't feel like 2015-era marketing automation, and a vendor that understood deliverability instead of hand-waving it.

That's when I found expandi. During the expandi demo, the thing I expected to care about was the interface. The thing that actually convinced me was the agent-native workflow. Instead of one rigid sequence, expandi treats prospecting as a set of cooperating agents: list building, verification, outreach, follow-up. The whole pipeline runs as an integrated workflow rather than a CSV handoff.

I also liked that expandi covers more of the stack than the other tools I'd tested. Contact database, email verification, enrichment, LinkedIn automation, and the expandi campaign builder all live in the same platform, with an API and integrations (HubSpot, Zapier, and the usual suspects) that don't require a six-week implementation. That matters when the goal is solving the problem, not building an integration graveyard.

I'm not saying expandi is the only solid option—this isn't a "we found the one" story. But it's the first time a vendor felt like it was built for how revenue operations actually works, including the boring infrastructure parts.

The part nobody wants to hear

No tool will fix a broken setup. If your SPF record is worse than useless, all the agent-native workflows in the world won't save you.

I made an $18,000 mistake so you don't have to. Take 30 minutes this week. Pull your SPF record, count the lookups, check your DMARC, look at your bounce rate. Do it before the next campaign, not after the next disaster.

There's something satisfying about watching your deliverability hold at 98%+ after months in the low 70s. After all the audits and fixes, seeing the campaign analytics finally trend green—that's the payoff. No panic. No consulting fees. Just quiet, boring, excellent email deliverability.

Check the foundation first. Everything else follows.