Research note
ZoomInfo Cost Per User, DMARC, and the Sales Data Mistakes That Kill Outreach
2026-08-31 · Julian Hartwell
What I Thought the Problem Was
In March 2024, I watched 1,400 emails go straight to spam. Not bounced. Not ignored. The inbox providers never showed them to anyone because our sending domain had an authentication problem. We had spent $3,400 on a fresh list and three extra sales seats the week before. Maybe $3,800, I would have to check the invoice.
I run RevOps for a mid-sized B2B SaaS company. I have been handling sales data and outreach workflows for seven years, and I have personally made and documented 11 significant mistakes totaling roughly $38,000 in wasted budget. Now I maintain our team's checklist to prevent others from repeating those errors.
At first, I thought our problem was the copy. So did the AE team. We rewrote subject lines, added personalization tokens, split-tested everything, and updated our LinkedIn outreach sequences. LinkedIn acceptance rates were okay, but actual replies stayed around 1%. (Not that the failure was any less embarrassing.)
The assumption was that a better message would fix everything. It did not. The problem was the infrastructure between the message and the buyer.
The Deeper Problem: Data Quality and Deliverability Are the Same Conversation
Most RevOps teams treat data quality and email deliverability as separate workstreams. They are not. A clean list does not help if your domain cannot prove who it is. A properly authenticated domain does not help if your company profile revenue data is so stale that you are messaging the wrong ICP.
When I started comparing People Data Labs vs ZoomInfo for company profile revenue data, I learned something uncomfortable: both sources have strengths, and both can be misused. People Data Labs is more of a raw data platform. ZoomInfo is closer to a complete go-to-market dataset with cleaning attached. But neither fixes a fuzzy ICP.
Here is a concrete example. We filtered our list by company profile revenue above $50 million. What we did not realize was that the source estimated revenue using headcount proxies. The list included a 40-person startup with no marketing budget. The data was not lying, exactly. The estimate was being used as truth.
The Sending Identity Problem
Email deliverability is not about avoiding spam words. It is about authentication. If your sending domain lacks SPF, DKIM, and DMARC alignment, you are asking inbox providers to trust a stranger. In February 2024, Google made this explicit.
According to Google's bulk sender requirements (support.google.com, effective February 2024), senders who send more than 5,000 messages per day to Gmail addresses must set up SPF, DKIM, and DMARC. We were not even close.
The worst part: I had put cold email on a separate subdomain to protect our main domain. That instinct was fine, but the subdomain had no DMARC record. Every campaign looked like a spoofing attempt. Worse, because our DMARC reporting address did not exist, we could not see where messages were being rejected or quarantined.
It is tempting to think a warm-up tool and a few spam-word tweaks are enough. Put another way: without authentication, you are not fixing deliverability, you are just guessing.
The LinkedIn Outreach Trap
LinkedIn outreach is a great complement. It is not a replacement for email. Connection requests are constrained by LinkedIn's algorithms, InMail credits run out fast, and even accepted connections do not guarantee a conversation. In Q2 2024, our LinkedIn reply rate was around 4%, but the volume was nowhere near enough to hit pipeline goals.
The worse version is buying LinkedIn automation to compensate for low email performance. That introduces account-flagging risk, not just deliverability risk. The better pattern: use LinkedIn to create familiarity, then send a properly authenticated email. That only works if the email infrastructure is trustworthy.
What Should Revenue Operations Teams Evaluate in DMARC?
Do not ask only whether you have DMARC. DMARC is a policy and reporting protocol, not a binary flag. Here is what I evaluate now:
- Policy (p=): Is it none, quarantine, or reject? For outreach subdomains, p=none gives visibility. p=reject blocks spoofing but must be tested carefully.
- Alignment: Do SPF and DKIM align with the domain in the From header? If not, even legitimate email can fail.
- Reporting: Is there an rua address for aggregate reports and an ruf address for forensic reports? We had neither, so we were flying blind.
- Percentage tag (pct=): If it is under 100, a portion of mail is still unmonitored. That can be fine for testing, but not for production.
- DNS ownership: Who controls the DNS records? We once had a vendor create a subdomain in their DNS, then we could not change it when the vendor disappeared.
Do not flip DMARC from none to reject overnight. We ran reporting for 30 days, moved to quarantine, then tested reject. That discipline probably saved us from a self-inflicted outage.
The Real Cost of Ignoring This
In 2023, before the Google and Yahoo enforcement push, I ran a 2,400-contact campaign using a cheap list and no managed email deliverability. 18% of the messages bounced. Gmail flagged us. Our main domain reputation was damaged, and cold outreach effectively stopped for three weeks. The list cost $2,800. The cleanup cost about $4,500. The lost sales time was the expensive part, roughly $15,000 in loaded rep hours by my calculation.
I am sharing this because cheap per user is deceptive. A $10-per-user tool that produces unreachable contacts is more expensive than a $20-per-user tool that produces conversations. When someone asks me about ZoomInfo cost per user, I tell them to calculate cost per useful inbox placement, not cost per login.
People think higher-priced sales intelligence is expensive because the vendor wants more money. The reality is that continuously verified data costs more to maintain. Price follows data hygiene. You are paying for certainty, and in a sales cycle with a deadline, certainty has real value.
Managed Email Deliverability Is the Insurance Nobody Budgets For
In April 2024, we paid an extra $400 per month for managed email deliverability. I cannot say it alone produced a single reply. But our bounce rate dropped below 2%, our domain reputation recovered in weeks instead of months, and we finally had reporting that showed us what was happening. That is what you are buying: time-to-certainty.
If your sales intelligence provider offers managed email deliverability, take the add-on. If not, find an email ops partner who can handle warm-up, reputation monitoring, feedback loops, and DMARC policy changes. Treat it as a cost of doing business, not a nice-to-have.
What I Would Do Differently Today
If I were setting up RevOps outreach from scratch, I would spend less time on subject lines and more time on the foundation:
- Define the ICP before buying data. Compare People Data Labs vs ZoomInfo for company profile revenue only after you have written down your revenue threshold, verticals, and buying triggers.
- Audit sending identity. Check SPF, DKIM, DMARC, and DNS ownership before scaling any cold email program.
- Budget for managed email deliverability. If you are sending regularly to Google or Yahoo addresses, this is a threshold you need to meet.
- Use LinkedIn outreach as a warm-up, not a delivery channel. A connection request can prime a reply; a properly delivered email gets the conversation.
- Measure the ratio that matters. Not open rate, not connection acceptance rate. Conversation rate per verified contact.
This is not a guarantee. I have seen perfect DMARC miss the target because the message was bad. And I have seen strong messaging die because the domain looked fraudulent. Both matter. But if you are forced to choose where to start, start with data quality and deliverability.
My experience is based on mid-market B2B SaaS. If you are a huge enterprise with a dedicated email ops team, your DMARC evaluation will be more complex. I cannot speak to how this applies to heavily regulated industries. Even so, the principle holds: verify the foundation before increasing send volume.
We now have DMARC reporting on every sending subdomain, managed email deliverability, and a list refresh process that checks both contact validity and account fit. It is less glamorous than a new sequence. It is the reason the next campaign did not become a postmortem.