A founder buying a contact database for the first time almost always asks the same question first: why does this cost so much more than the list I found online? It is a fair question. It is also the wrong question, because it assumes both lists are the same thing measured in different amounts of money.
They are not. A scraped list and a verified database differ in almost every dimension that matters — except the one dimension most buyers check first, which is the price per record. Judged only on that number, the scraped list always wins. Judged on anything else, it rarely does.
Consider what actually happens after either list is purchased. A team receives five hundred contacts. They begin outreach — calls, emails, WhatsApp messages, whatever the channel. Within the first week, a pattern emerges. Some numbers are disconnected. Some emails bounce. Some contacts have changed roles, or companies, or left the industry altogether. Some were never real decision-makers to begin with — a generic inbox, a switchboard number, a name pulled from a directory listing that was itself years out of date.
The cost that never appears on the invoice
None of this shows up on the invoice for the list. It shows up later, spread across a sales team's time, a founder's attention, and a pipeline that quietly fills with dead weight. A contact that cannot be reached is not a discount. It is a cost that has been moved from the seller's ledger to the buyer's calendar.
This is the part the price-per-record comparison hides. The real unit being purchased is not a contact. It is a probability — the probability that reaching out to this specific name, at this specific number, about this specific business, will lead somewhere. A scraped list can offer volume. It cannot offer that probability, because nobody has checked.
| What is being compared | Scraped list | Verified database |
|---|---|---|
| Price per record | Low | Higher |
| Source | Directory, aggregator, old export | Confirmed against current trade activity |
| Named decision-maker | Often a generic inbox | Named person, defined role |
| Currency of role | Unknown | Confirmed via independent sources |
| Contact reachability | Untested | Checked before delivery |
| Real cost to the buyer | Hidden in wasted outreach time | Priced in upfront |
The economics only look confusing because the two costs are being paid at different times. The scraped list defers its cost to the future, and disguises it as the buyer's own inefficiency — a slow sales cycle, a low response rate, a team that "just needs to work harder." The verified database prices the cost honestly, upfront, before a single call is made.
A contact database purchased at five rupees a record becomes expensive the moment a team spends a week outreaching to sixty percent of it that is wrong.
What verification actually means
Verification is not a marketing word. It is a specific, checkable claim: that before a record is delivered, someone confirmed the organisation genuinely operates in the relevant category, identified a named person with real authority over the decision, confirmed that person still holds the role through more than one independent source, and tested that the contact detail actually reaches them. Four checks. Any one of them failing means the record does not ship.
This is slower to produce than scraping a directory. It is also the entire reason the record is worth anything. A founder is not paying for a name and a phone number. They are paying for someone else to have already absorbed the cost of finding out whether that name and phone number lead anywhere real — so the founder's own team does not have to discover it the expensive way, one dead call at a time.
There is a version of this argument that sounds like a sales pitch, and Sol Gravitas is wary of that version. The honest version is simpler: a free or cheap list is not free. It has simply moved its true cost somewhere the price tag does not show it. Every founder who has run a team through five hundred contacts and watched the response rate has already paid this cost once. The only question is whether they pay it before the list is built, or after.
Think with Insights.