Lead Databases vs Live Search: Which Gives Fresher B2B Leads?
Why B2B lead databases go stale, when a database is still the right call, how to compare cost per usable contact, and a checklist to choose.
By the Glintscout team9 min read
On this page
Live search gives fresher leads by design: it reads a public source (a map, a directory, a page of search ads) at the moment you run it, while a database returns whatever was true when its records were last checked. That doesn't make databases the wrong choice. If you need people by job title, company size or revenue, a database is usually the practical option; if you sell to local businesses and small companies you can describe by what they do and where, live search tends to win on freshness and on cost per contact you can actually use.
Two ways to get a list
A lead database is a pre-built collection of company and contact records that you filter and export. Contact databases, data vendors and one-off bought lists all work this way: records are compiled from many sources over time and refreshed on the vendor's schedule.
A live search queries a public source when you need the list: Google Maps, a directory like Yelp, the ads on a search results page, online stores. Emails are found and verified during the same run. You get what exists today, limited to what that source shows.
The real difference is when the checking happens. With a database, it happened some time before you bought. With live search, it happens now.
How a database goes stale
No record is stale on the day it's collected. What matters is how long ago that day was, and whether anyone has checked the record since. Meanwhile, the businesses behind the records keep changing:
- Businesses close, move, merge and rebrand. The US Bureau of Labor Statistics publishes survival tables for new establishments by the year they opened, and every yearly group shrinks as the years pass. Each closure leaves a record that looks fine and leads nowhere.
- Domains change. A rebrand moves email to a new domain. The old one may keep accepting mail for a while, forward it, or start bouncing.
- People leave. When someone changes jobs, their mailbox is usually closed. The address bounces, or a catch-all domain swallows your message and nobody reads it.
- Details drift. Phone numbers, owners, services and locations change, and nobody tells the vendor.
- "Verified" has a date. A record marked verified was checked at some point. If the export doesn't say when, you can't tell a check from last week from one from years ago.
Decay shows up in your campaign in two ways. The visible one is bounces, which count against your sending domain (see what a good email bounce rate is and how to lower it). The invisible one is wrong targets: the company still exists but changed what it does, or the person you named has left, and your email reaches someone it doesn't fit.
For named contacts in the EU and the UK, staleness is also a legal question: the GDPR requires personal data to be "accurate and, where necessary, kept up to date" (Article 5(1)(d)).
Where each one fits
| Your situation | Better fit | Why |
|---|---|---|
| You target people by job title, seniority or department | Database | Live search finds businesses and their business emails, not people by role |
| You need filters for revenue, headcount or industry codes | Database | Public listings rarely show these |
| You sell to local businesses: trades, clinics, salons, agencies | Live search | They list themselves where customers look, by keyword and city |
| Timing matters: advertising now, running a tool now, newly opened | Live search | These signals change fast, and a snapshot misses them |
| Your niche is narrower than an industry code | Live search | A keyword can say "mobile dog groomer"; a code list often can't |
| Your market is outside the countries vendors cover best, or in small towns | Test both | Coverage varies, so ask for a sample for your exact cities |
| You're building an account list for account-based selling | Database first, then live signals | The database gives structure, live search gives current signals |
The industry code point is easy to underestimate. In NAICS, the classification used in North America, dog groomers share code 812910 with pet sitters, boarding kennels and trainers. If you sell grooming software, a database filtered by that code can hand you everyone in pet care, and a per-row price means paying for the rows you throw away. A keyword search for "dog groomer" in each city returns the businesses that describe themselves that way.
For local businesses, Google Maps is the natural live source because it lists businesses in nearly every country. If live search fits your market, our guide to building a B2B lead list by city and niche walks through the whole process.
The hidden costs on both sides
The sticker price is the smallest part of the comparison.
Databases
- You pay per row, per seat or per month, for good rows and bad ones, and for months you don't use.
- Cleaning takes time: removing out-of-target rows, deduplicating against your CRM, verifying.
- License terms can limit exports and decide what happens to the data when you cancel. Read them before you build a process on top.
- You inherit the vendor's collection practices, and regulators expect you to check them. The UK's ICO tells organizations that buy marketing data to ask when it was collected and how old it is, and warns that "it is not enough to simply accept a third party's assurances that the information they are supplying to you is compliant" (ICO guidance).
Live search
- You think in keywords and cities, and you set up the combinations yourself.
- Coverage is limited to what the source lists, and wording matters: "roofer" and "roofing contractor" can return different businesses.
- Small businesses mostly publish generic addresses (
info@,office@) rather than named people. - Results take minutes rather than seconds, because the source is read while you wait.
- A tool that prices per search charges the same for a thin search as for a full one. In Glintscout, a search costs the same whether it finds 8 companies or 100 (see pricing), so a thin niche in a small town costs more per contact than a dense one in a big city.
Compare cost per usable contact, not price per row
A row you can't use isn't cheap at any price. Count what's left after the filters that matter:
Cost per usable contact = total cost ÷ usable contacts
A contact is usable when it's in your target, verified as valid, not already in your CRM and not on your suppression list.
Put everything in the total: the subscription or purchase, verification, and the hours spent cleaning, at your real hourly cost.
A worked example with made-up numbers, only to show the math: a list costs $500 including the cleaning time. It has 2,000 rows, so the invoice says $0.25 per row. After filtering, 1,400 rows fit your target. Of those, 1,050 verify as valid, and 150 are already in your CRM. That leaves 900 usable contacts at about $0.56 each, more than twice the per-row price.
Run the same worksheet for a live search of the same segment. Then, after a test send, go one step further and divide the cost by replies. Cost per reply is the number that decides whether a source is worth using again.
Run a side-by-side test
Arguments about data quality end quickly when you test on your own market. The setup takes a day or two; the replies take a couple of weeks.
- Pick one segment you know well, for example dentists in Leeds or roofers in Phoenix.
- Pull it from both sources: the database export and a live search of the same cities and keywords.
- Measure the overlap by domain: businesses in both lists, only in the database, only in the live search.
- Verify both lists with the same verifier on the same day, so neither gets an unfair advantage.
- Spot-check 20 rows from each by hand. Does the business still exist at that address? Does the website work? Is the named person still there?
- Send the same message to a sample of each, and compare bounces and replies after two weeks.
The source that gives you more usable contacts per dollar and more replies wins that segment. It may not win every segment, which is why a mix often makes sense.
Questions to ask a database vendor
- When was each record last verified, and how? Is that date in the export?
- What happens when records bounce: credits, refunds or nothing?
- Where does the data come from, and what were people told when it was collected?
- Can I get a sample for my exact segment and cities before I buy?
- What do the license terms allow: exports, seats, use after I cancel?
- How are opt-outs handled and passed on?
If the answers are vague, assume the data is older than the sales page suggests.
Decision checklist
| Question | If yes |
|---|---|
| Do you need people by job title or seniority? | Database, or research by hand |
| Do you need revenue or headcount filters? | Database |
| Are your buyers defined by what they do and where they are? | Live search |
| Does timing matter (ads running now, a tool in use now, newly opened)? | Live search |
| Is your niche narrower than any industry code? | Live search |
| Do you send at a steady, high volume every month? | A subscription may pay off; for bursts, pay as you go |
| Either way | Verify right before sending, and never re-add an opt-out |
When you sell to both larger accounts and local businesses, a sensible split is a database for named decision makers at the larger accounts, live search for local and small-business segments and for time-sensitive signals, and one verification step before anything is sent.
FAQ
How often do B2B databases update their records?
It varies by vendor and by record. Ask for the last-verified date of each record rather than a general refresh promise, and re-verify anything you haven't sent to recently. Our guide on how to verify an email address without sending an email explains what that check can and can't tell you.
Is it legal to email a list I bought?
It depends on where the recipients are and what the list contains, and buying a list doesn't transfer the vendor's compliance to you. In the UK, the ICO expects due diligence on bought-in data. Under the GDPR, when you hold personal data you didn't collect from the person yourself, Article 14 requires you to tell them, at the latest when you first contact them. This is general information, not legal advice.
Do I need to verify a list the vendor says is verified?
Yes. Verification is a snapshot too. Re-verify right before you send, not when you buy.
Can live search find decision makers by name?
Sometimes a name comes with the address, for example when the owner's email is on a small business website. But live search finds businesses and their business emails, not people by job title. For roles, use a database or research by hand.
Keep reading
All articlesLead generation
How to Find Shopify Stores That Use a Specific App or Chat Tool
Spot Shopify stores and the chat or helpdesk tool they run, build a store list by keyword, and open a switch campaign with the tool they already use.
11 min read
Lead generation
How to Find Companies Running Google Ads (and What to Pitch Them)
Find the companies running Google Ads in any city: search by keyword and location, check the Ads Transparency Center, then pitch what you saw.
9 min read
Lead generation
How to Use Yelp and Yellow Pages for B2B Prospecting
What Yelp and Yellow Pages listings contain, which niches each covers best, and how to turn listings into verified business emails for outreach.
9 min read