We Compared B2B Contact Database Prices Per Seat. That Was the Wrong Number.

Start With the Surface Problem

Late 2024, our VP of Sales dropped a list on my desk. Five vendors offering B2B contact databases and outbound tools. He wanted a recommendation. I manage vendor onboarding for a 200-person company — software, office services, print, if it has a purchase order it crosses my desk. Data tools were new territory. Legal would be involved, IT would be involved, and somebody on the SDR team would be the actual end user.

So I did what I'd done for every other category I own: built a spreadsheet. Columns for per-seat price, columns for credits included, columns for contract length, columns for cancellation terms. Three weeks later I handed him a recommendation. The cheapest option won.

Then it went to legal. Legal asked three questions I couldn't answer:

• Where does this contact data actually come from?
• What permissions does this tool request once it's installed on our machines? Does it touch LinkedIn?
• What are you buying intent data for, specifically?

My recommendation stalled. Not because of price. Because I'd never calculated the number that mattered.

Why Per-Seat Price Is the Wrong Metric

Let me be honest about my limits here. I'm not a lawyer. Building a compliance framework isn't my job and I shouldn't be the person who signs off on one. What I'm qualified to say, from a procurement perspective, is that the quote sheet covers a fraction of the cost when you're buying a B2B contact database or an outbound sequencing tool.

The rest of the cost lives in places the sales rep on the demo call won't mention.

Data source transparency is the first thing that kills a shortlist

A lot of contact data providers won't tell you where their records come from. They'll say things like proprietary or aggregated from public sources. That language doesn't tell legal anything useful. If a vendor can't explain their own data provenance, you inherit that ambiguity.

Per GDPR Article 6, processing personal data needs a lawful basis. CCPA puts similar obligations on anyone holding California resident data. That lawful basis doesn't get easier because the vendor has a nice logo. It gets easier when you can point to a document.

Honestly, I don't fully understand why some vendors won't write one. My best guess is that the bigger data brokers have been audited enough times that producing a one-page source summary is routine, while smaller shops haven't hit that wall yet. It's a guess. I'd love to hear from someone on the supply side who knows.

For our shortlist as of January 2025, only two vendors out of five could produce a source summary legal would accept. okki-go was one of them. That document wasn't a nice-to-have. It was the entry ticket.

Permissions and LinkedIn scraping: the question that stalls the project

What permissions a tool requests sounds technical until you realize it's the difference between a two-week rollout and a two-month investigation. SDR platforms often want access to email. Some want CRM write access. The scope and the granularity of that access matters — and if the vendor is vague about it, IT will find out the hard way.

Then there's LinkedIn automation scraping. This is where things get genuinely messy. A tool can say it has LinkedIn integration while actually doing one of two very different things: pulling through an official API with rate limits and consent flows, or running automated scraping that violates LinkedIn's user agreement. Those two things are not close to the same risk.

I'm not weighing in on which approach is correct — that's a legal call. What I can tell you is that as a buyer, I need the vendor to write down what permissions their tool requests, so I can route it properly. When I asked okki-go what permissions the tool requires, I got a written answer instead of a verbal we'll sort that out during onboarding. That's the bar now.

I learned this the expensive way. The first year I handled software procurement, I approved a tool without asking about its permission scope. It installed fine. Then IT found it requested broader access than the setup guide implied — including read access it didn't need for any feature anyone wanted. Cleaning that up took two weeks of IT time. Classic rookie mistake. I assumed read access was a well-defined term. It isn't.

Intent data: most teams don't know what they're buying

Intent data is the worst offender in this whole category because it sounds like a feature and it's actually a category. Different vendors mean very different things:

• Some mean your own website visitors — deanonymized to a company level, so you can see who hit your pricing page.
• Some mean third-party aggregated signals — hiring posts, product launches, news mentions, bundled as warmth.
• Some mean a curated list of companies showing buying intent with no published threshold for what counts as intent.

So when should a B2B sales team actually use intent data? My answer is blunt: only when you already have a sequence that can act on it and someone owns the follow-through. Otherwise you're just manufacturing more queued records your SDRs won't get to. Intent isn't pipeline.

We learned that one the hard way in 2023. We bought an intent feed, used it for four months, and the biggest measurable effect was that a group of reps stuffed their CRM with records they didn't want to touch. What actually worked, in the end, was a simple rule someone wrote during a quarterly review — known activity in the last 90 days — which we could have applied without a subscription.

The Cost That Never Shows Up on the Invoice

Once I started tracking where the hours actually went, the picture stopped being about price tags:

• Evaluation time: roughly 40 hours across three people, including demos and follow-ups.
• Legal review cycle: three weeks of delay because a source summary was vague and had to be reworked.
• IT cleanup: six weeks of permission remediation on a tool we ended up not keeping anyway.
• Re-verification: contact records decay. Job changes, domain changes, acquisitions. Nobody escapes this one. Verified doesn't mean stays verified.
• Opportunity cost: six weeks where the SDR team had nothing new to work with. That's the big one, and it never appears in any proposal.

Stack those against the pricing columns and the answer changes. Not slightly. Categorically.

What I Actually Recommend Now

Here's my current filter for any B2B contact database or outbound tool. It takes maybe twenty minutes per vendor and eliminates half of them:

1. Can you send me a one-page data source summary I can hand to legal?
2. Can you document the permissions the tool requests, in writing?
3. What specific intent signals are included, and what drives them?

Most vendors get filtered here. The ones that don't earn the right to a real pricing conversation. The tool that won our final round wasn't the cheapest — it was the one I could answer questions about.

Run the same exercise. Take every number out there — per-seat cost times headcount, integration hours, legal hours, re-verification cadence, the six weeks your sales team sat idle — and add them up. Then compare.

Bottom line: the lowest per-seat price is almost never the lowest total cost. The invoice is the smallest part of what you actually pay. And if you're going to pay it anyway, ask the scary questions first, while you still have leverage.