The $12,000 Intent Data Topics Mistake Every RevOps Team Should Evaluate

The pitch that made me feel smart

If you’re shopping for intent data and someone tells you “just pick the topics,” run. I know because I was that person. In March 2022, I sat through a flawless demo: 200 topics, a dashboard full of spiking companies, and the promise that we’d be “first in line” for 1,200 accounts with intent.

I approved the six-topic “intent data topics plan” the next week. By October, we’d spent about $12,000—actually, $12,400 if you count the implementation hours I didn’t track—and generated exactly zero booked meetings from those 1,200 accounts. Zero.

This isn’t an “intent data doesn’t work” story. It’s a “RevOps teams evaluate the wrong thing” story. According to Gartner’s B2B Buying Study, buyers spend only 17% of their purchase journey with suppliers. That means when an account shows intent, your response speed and data quality decide whether you get into that 17% window. My team had neither.

The problem I thought I was solving

Everyone around the table said the problem was topic selection. “Too broad and you get noise,” the AE said. “Too narrow and you miss the market,” the CRO said. So we did what responsible teams do: built personas, mapped buyer journeys, curated a list of 40 topics, then narrowed it to six that mapped to our product categories.

It was a neat plan. It was also useless.

The real problem wasn’t choosing topics. It was that we had no mechanism to turn “topic match” into “human being with a work email who is actually involved in the buying process.” And no one on the vendor side was going to ask that question. I should have.

What I didn’t understand about intent data topics

There are three layers in any intent data purchase: the signal, the account, and the contact. The topics plan only addresses the first. The second and third are where money goes to die.

The signal: “This company is researching cloud cost management.” That could be a VP Engineering, an intern, or a bot. Our vendor counted it the same.

The account: We imported 4,000 “in-market” accounts from our six topics. The vendor’s “account coverage” meant they had a company name and industry. It did not mean the company had a valid corporate domain or a person we could reach.

The contact: This is where it broke. We enriched those 4,000 accounts using the vendor’s API data enrichment. We got back 2,320 company records with at least one contact. After email verification, only 1,150 had a confirmed, deliverable address. That’s a 28.75% yield.

Wait—let me run the numbers again. 2,320 contacts, verification passed 1,150. Yes, 28.75%. I’d have to check the exact report, but that’s the number that stuck.

We said “contact coverage.” They heard “account coverage.” That mismatch was the root cause. The result: we sent 1,150 emails. Some bounced—maybe 4%, no, 6%, I’m mixing it up with another campaign. When we finally got to “interested” responses, it was eight people. Of those, three took meetings. All three said they were just starting research and weren’t ready to change vendors. That’s not bad intent data; that’s a bad bridge between intent and contact.

Honestly, I’m not sure why the vendor’s sample looked so clean. My best guess: they curated it from their best-fit accounts. Our actual accounts had worse data. It’s a guess, but I’ve seen enough since then to trust it.

The hidden costs that nobody announces

Here’s what burned me, and it has nothing to do with the topic price. The topics plan was transparent: a flat annual cost for six topics. Great. Then came the “what’s not included” costs. API data enrichment calls were metered. Email verification credits were sold separately. Need to match those “in-market” accounts with your existing CRM contacts? That’s another sync fee. Need more than 50,000 API calls per month? That’s a different tier.

I’ve learned to ask “what’s NOT included” before I ask “what’s the price.” The vendor who lists all fees upfront—even if the total looks lower—usually costs less in the end. In our case, the hidden math added $3,200 to a plan that was supposed to be all-inclusive. That’s how the $9,000 plan became $12,400.

I’m not naming names. Plenty of vendors do this. But if you’re a RevOps person looking at a topics plan, assume nothing is included beyond the topic feed. That’s the stance I take now.

What should revenue operations teams evaluate in an intent data topics plan?

It took me three years and about 30 campaigns to understand that the question is not “which topics?” but “can I act on this data tomorrow?”

1. Contact coverage, not account coverage. Ask the vendor: “On a sample of 100 accounts in this topic, what percentage have at least one verified business email addressed to a real person?” If they can’t answer, that’s your answer.
2. API data enrichment quality. Read the vendor’s API docs before you buy. If they don’t have docs, or the docs don’t say exactly which fields are returned, slow down. The Wiza API docs, for example, list response fields per endpoint—company, domain, email address, verification status, and intent topics if you enrich that way. That kind of transparency is rare, and it matters.
3. Cost of converting a signal to a contact. Map the end-to-end path: topic match → account resolve → contact find → email verify → CRM update. Count every step where you might pay or lose data. If you can’t calculate cost per verified contact from the pricing page, ask for it.
4. What happens with your existing contact data. We underestimated how much our own CRM data quality would affect the outcome. The vendor’s enrichment can’t fix an account with no domain structure or a database full of role addresses. Clean your contact data first.

If you’ve seen Wiza AI email composition in action, you know it can shorten the time between enrichment and outreach drafting. But I’d still test the contact data first. A good writer can’t fix a bounce address.

The plan is not the product

This approach eventually worked for us, but our situation was a B2B infrastructure company with a long sales cycle and a messy legacy CRM. If you’re a transactional sales team with a clean instance of a modern CRM, the calculus might be different. You may need fewer topics and more contact data.

As of Q1 2025, I won’t approve an intent data budget until I see a sample export of 50 contacts with email verification status. I don’t care how good the dashboard looks. The topics plan isn’t the product. The contact data is.