DATA INTELLIGENCE / Custom Contact Data

Nobody Sells A List Of Exactly Who You Need.

Prepackaged lists are built for the average buyer. If your audience is narrow, a niche specialty, a specific job function, a certain size of company running a certain tool, that list will be mostly people you cannot use. Custom data starts from your spec instead of a shelf.

What You Ask For, And What You Get

You describe the audience in plain language. We turn that into a build spec, then a file. Here is what that exchange looks like, and every field you can choose from.

What you tell us

Who to reachQuality and regulatory leaders at device makers
WhereUnited States and DACH
How bigMid sized, not the giants
Must haveA phone number we can actually call
Leave outAnyone already in our CRM

What comes back

Records4,182 contacts across 1,140 companies
FieldsYour chosen set, up to 75 per record
VerifiedEmail and phone checked before delivery
SuppressionYour exclusion file applied
FormatCSV, Excel or straight into your CRM
Fields you can choose from Pick any combination. Availability varies by region.
Person and role
NameFirst, last and greeting
Job titleFull title as held today
SeniorityLeader, manager, individual
Job functionStandardised function code
Reporting lineWho they report into
LinkedInProfile URL
Contact and reach
EmailBusiness address, verified
PhoneCompany and direct line
Phone typeLandline or mobile
AddressFull postal address
SocialCompany profiles by channel
FaxWhere still in use
Company
EmployeesHeadcount range
RevenueTurnover range
SICCode and description
NAICSCode and description
OwnershipPublic or private, parent, subsidiary
ListingStock exchange and ticker
Location and site
Site typeHeadquarters, branch or single site
City and stateStandardised
CountryISO code
ZIPPostal or ZIP code
CoordinatesLatitude and longitude
FootprintSquare footage of the site
Technology and web
Business appsCRM, HRMS, marketing tools
Web stackCMS, frameworks, web server
HostingHost, nameserver, CDN, SSL
TrackingAnalytics and advertising tools
ScaleNumber of tools, PCs in use
CommerceEcommerce and payment flags
Signals and behaviour
EventsShows exhibited at and attended
CompetitorsTop three named rivals
Peer countSimilar titles at rival firms
CreditCredit score code
FoundedYear established
Signal fields have thinner coverage outside the United States.
Ask for six fields or sixty. You pay for the audience and the depth you actually use. See a sample file

Reach Or Relevance. Pick The One Your Campaign Needs.

A prepackaged list is cheaper per name and fine when you want volume and brand recall. Custom is the better buy when a wrong name costs you more than a missing one. Most teams need both at different moments, so the question is which job this campaign is doing.

A prepackaged list

Pick a segment Buy the block Filter it down Use a slice

Fast and cheap for wide reach. You take the whole block and pay for names outside your target, then trim by hand.

A file built to your spec

Define Build Verify Deliver

Slower to produce and narrower by design. Every record clears your criteria before it reaches you, so your team works a list they can trust.

75+Intelligence fields
740M+Data records
30+Industries mapped
180+Countries covered

Coverage of the LakeB2B people and company database.

How A Custom Build Works

Step 1

You describe the audience

Industry, titles, geography, company size, technology in use, and anyone you want left out. Send your best customer list instead if that is easier. We can work backwards from what already closed.

Step 2

We build and check it

Records are assembled from public filings, directories, trade show lists, subscriptions and opt in sources, then matched and verified. Hard fields get checked by hand. Anything we cannot confirm is left out rather than filled in.

Step 3

You approve a sample first

A slice of the file comes to you before the rest. Check the fit and the field quality. If the spec needs tightening, we tighten it and rebuild, then deliver in your format.

It All Comes Back To One Thing. Everyone On The File Fits.

No paying for wasteA block of 50,000 where 4,000 fit is not cheap. It just moves the cost somewhere you do not measure.
Sharper messagingWhen every reader holds the same job in the same kind of company, you can write one email that lands.
Reps stop filteringNobody has to open a row and decide whether this person was ever worth calling.
Cleaner reportingReply rates mean something when the denominator is people who could realistically buy.
An aviation manufacturer put 700K dollars of sales through a custom LakeB2B database.

Narrow sector, small buying population, no list on the market that matched it.

Read the case

Frequently Asked Questions

What is custom contact data?

It is a contact file built to a specification you set, rather than a segment pulled off an existing list. You define the industry, titles, geography, company size and any other criteria that matter. We build only the records that meet them.

How is this different from buying a list?

A prepackaged list already exists, so you buy a block and filter it down. A custom file is assembled against your criteria, so filtering happens before delivery instead of after. Volume buyers usually prefer the first. Teams selling into a narrow audience usually get more out of the second.

How many fields can I ask for?

Up to 75 intelligence fields per record across person, contact, company, location, technology and signal groups. Most teams use somewhere between eight and twenty. Ask for what your campaign or scoring model will actually read.

Where does the data come from?

Public records and government listings, annual reports and regulatory filings, trade shows and attendee lists, business directories, publication subscriptions, postal service updates, and opt in campaigns and surveys. Records are then matched and verified before they reach you.

How long does a build take?

It depends on the size of the audience and how hard the criteria are to confirm. A straightforward industry and title build moves quickly. Rare specialties or unusual technology filters take longer. We confirm a timeline with you once the spec is agreed, before any work starts.

Is the data compliant?

Yes. Collection and processing follow GDPR and CCPA requirements, with careful handling for healthcare records. Opt out requests are honoured, and we can sign a data processing agreement covering how the file is produced, delivered and stored.

Can I see it before I commit?

Yes. A sample of the file comes to you before the full delivery, so you can check that the records match your spec. There is also a general sample file you can download to see the field layout.

Describe Your Audience. See What Comes Back.

Tell us who you are trying to reach in one or two sentences. We will build a sample against that spec so you can judge the fit before anyone talks about budget.

LakeB2B