B2B data is information about businesses and the people who work in them, organized so that sales, marketing and RevOps teams can identify, prioritize and reach the right accounts. It combines company data, contact data and contextual signals, and it only stays useful while someone keeps maintaining it.
This guide explains what a B2B data record contains, where the information comes from, how a database is built and kept current, what data quality means in practice, what verification can and cannot prove, and how to judge a provider and use the data responsibly.
B2B data is a structured description of the commercial world: which companies exist, what they look like, who works there and what is changing inside them. A useful record connects a person to a company, so a contact is never just a name and an email address but someone in a role, inside an organization that has attributes of its own.
That connection is why B2B data is better understood as a maintained information system than as a list. A list is a snapshot exported on a given day. A system has sources, matching rules, verification steps and an update cycle, and its value depends on how well those parts keep working after the export.
The distinction shows up quickly in practice. Two files can hold the same number of records and the same columns, yet one produces conversations while the other produces bounces and wrong-person replies. The difference usually sits in what a spreadsheet does not show: how each field was sourced, when it was last checked, and whether it was observed or estimated.
Most B2B data falls into three layers: company data, contact data and contextual or signal data. Each layer answers a different question, and a complete record links all three.
Company data, often called firmographic data, describes the organization. Typical fields include the legal and trading name, website domain, industry classification, headquarters and other locations, employee count, revenue, ownership and parent-subsidiary relationships. This layer answers the first question in any account plan: is this company worth pursuing at all?
Firmographic fields differ a great deal in how well they can be known. A registered name or address can often be checked against an official record. Revenue for a privately held company usually cannot, because in many jurisdictions private companies are not required to publish it, so the figure in a database is often an estimate built from other signals.
Contact data describes the people: name, job title, function, seniority, work email address, phone numbers, location and often a professional profile URL. Phone fields need their own scrutiny, because a direct dial, a mobile number and a company switchboard lead to very different conversations. This breakdown of how direct dials, mobile numbers and switchboard lines differ is useful if calling is part of your motion.
Job titles deserve particular care. Titles are not standardized across companies, so a database usually maps raw titles such as “Head of Growth” or “VP, Demand” into normalized functions and seniority levels. That mapping is useful for filtering, but it is an interpretation of the title, not something the person stated.
The third layer describes what is happening around the account. It includes technographic data (the software and infrastructure a company appears to use), intent signals (evidence that an account is researching a topic) and events such as hiring activity, funding announcements, leadership changes, expansions and acquisitions. For the first of these, see how technographic data is found and put to use.
Signals are time-bound in a way that most company and contact fields are not. A funding announcement or a spike in research activity matters most soon after it happens and loses meaning as it ages, so every signal needs a clear date attached to it.
Across all three layers, some attributes are observed and others are modeled. An observed attribute was seen directly in a source: a title on a company website, an address in a company registry, a technology detected on a domain. A modeled attribute was inferred: an estimated revenue band, a predicted buying stage, an intent score or a guessed email pattern.
Both have a place, but they should not be used the same way. A sound working rule is to build hard segmentation, such as including or excluding accounts by country or industry, on observable fields, and to treat modeled fields as scoring signals that raise or lower priority. Good providers label which fields are estimated, and buyers should ask when they do not.
Company data describes an organization, contact data describes a person inside it, and the two differ in how fast they change, how they are checked and how privacy law treats them.
| Factor | Company data | Contact data |
|---|---|---|
|
What it describes |
The organization as an entity |
An individual in a professional role |
|
Typical fields |
Name, domain, industry, size, locations, revenue, ownership |
Name, title, function, seniority, work email, phone, location |
|
What makes it change |
Mergers, acquisitions, rebrands, relocations, growth, closure |
Job moves, promotions, title changes, reorganizations |
|
How it is checked |
Registries, filings, company websites, domain records |
Email and phone verification, website and profile checks |
|
Common weak spot |
Estimated fields for private companies, such as revenue |
Whether the person still holds the role |
|
Privacy status in the EU and UK |
Data about a legal entity is generally outside GDPR |
Data that identifies a person is personal data, even at work |
In practice the two layers of B2B data drift apart. A company record can stay accurate for years while the people attached to it change, and a contact’s email can keep accepting mail after the person has moved into a different role. Maintenance logic should reflect this: company records and contact records need separate refresh rules, set by how quickly each field changes and how the data will be used.
The legal difference is just as real. The European Commission states that EU data protection rules do not govern data about companies or other legal entities, but do apply to personal data about people acting in a professional capacity, including name-based business email addresses and employees’ business phone numbers. The UK Information Commissioner’s Office takes the same position on identifiable business contacts under UK GDPR.
B2B data is assembled from several kinds of sources, and each is strong on some fields and weak on others.
Because no single source covers every field well, many teams combine several. The gain can be large. In a vendor case study, Clay reports that OpenAI’s RevOps team moved inbound lead enrichment from a single provider to a sequential multi-provider “waterfall” and raised enrichment coverage from the low 40% range to the high 80% range. That is one company’s result, published by the vendor, and it measures coverage (how many records received a value), not accuracy.
Combining B2B data sources also creates work. Providers format the same company differently, disagree on titles and employee counts, and can hold two records for one person. Every multi-source setup needs normalization rules, deduplication logic and a conflict-resolution policy that decides which source wins for which field, and why.
A usable B2B database is the output of a repeating lifecycle rather than a one-time collection exercise. These are the stages raw information passes through before a team can act on it.
Two distinctions in this sequence cause most of the confusion in buying conversations. Enrichment and verification are different operations: a provider can fill a phone field without ever confirming that it connects. Verification and validation are also different: an email address can be deliverable and still belong to someone at a different company from the one the record names. If you are assembling data yourself rather than buying it, this walkthrough on building a verified B2B contact list covers the practical steps.
High-quality B2B data is data that is fit for the specific job you need it to do. That means quality has several dimensions, and accuracy is only one of them.
The idea has a long research history. In their 1996 study Beyond Accuracy: What Data Quality Means to Data Consumers, published in the Journal of Management Information Systems, Richard Wang and Diane Strong defined data quality as data that is fit for use by data consumers and grouped 15 dimensions into four categories: intrinsic, contextual, representational and accessibility. IBM’s current guidance on data quality dimensions lists six core dimensions in wide practical use: accuracy, completeness, consistency, timeliness, validity and uniqueness.
Applied to B2B data, those dimensions look like this:
A record can be complete and wrong, or sparse and right. A contact with every field filled, including a mobile number, a revenue figure and a list of technologies, is still a bad record if the person left the company. A record holding only a name, a title and a verified work email may be exactly what an email program needs. Fill rates describe how often a field contains a value; they say nothing about whether the value is true.
A recent update date does not guarantee a correct value. A field can be refreshed yesterday from a source that was itself out of date, and a record untouched for a year can still be right. Freshness is most useful as a property of each field rather than of the whole database: knowing that an email was verified last month while the title was last confirmed long before tells you far more than a single “database updated” date.
Because quality depends on context, a large database is not automatically a useful one. A provider with very large global record counts can still have thin coverage of, say, mid-sized manufacturers in Germany or procurement roles in regional hospitals, if that is your market. The useful number is how many accurate, current and relevant records exist for your ICP and geography, and that can only be checked against your own target list.
Poor data quality is expensive in general. Gartner research from 2020 estimated that poor data quality costs organizations at least $12.9 million a year on average. That figure covers data quality across whole organizations, not B2B contact data specifically, but the mechanisms will be familiar to any revenue team. For a sector view, see what bad B2B data costs manufacturing sales teams.
B2B data becomes outdated because the business world it describes keeps changing, and every change makes some stored value wrong until it is checked again. The most common causes are:
These changes do not hit every field equally. Company attributes such as legal name or headquarters change less often than personal attributes such as title or employer, and signal data loses relevance fastest of all. That is why a single decay rate for a whole database is a weak planning number.
Many B2B data decay statistics circulate in the industry, and they deserve caution. Most come from vendor analyses, measure different things (email validity, job changes or any field change), cover different segments and rarely publish their full method. A more reliable approach is to measure your own decay: track bounce rates, wrong-person replies and re-verification failures by segment and by record age. The mechanics are covered in more depth in why B2B email databases lose accuracy over time.
Email verification tells you whether an address is likely to accept mail. It does not tell you whether the right person reads it, whether they hold the role you expect, or whether they want to hear from you. A typical verification process checks:
Each check has limits built into how email works. The SMTP standard, RFC 5321, allows mail servers to disable the command that confirms whether a mailbox exists, for security reasons, and notes that some servers do not check recipients until after a message has been received, returning a failure notice later. A server can also be set up to accept mail for every address on its domain. In each case, an address that passes at the time of checking can still bounce, and an accept-all result is better read as unknown than as valid.
More importantly, a deliverable address answers only the first of several questions a revenue team cares about:
Reading a “verified” label as an answer to all six is one of the most common misunderstandings in B2B data. For practical ways to reduce bounces, see how to find business contact details without bounces, and for checking the rest of a record, this guide to verifying company contact information field by field helps. Teams without the tooling to run these checks in-house sometimes hand the step to an outside service, such as eSalesClub’s data validation services.
Sales, marketing and RevOps teams use B2B data for different jobs, and each job tolerates different kinds of imperfection.
Sales teams use it to research accounts, find the people involved in a buying decision, plan territories and prepare outreach. Role accuracy and reachable contact details matter most to them, because every wrong-person call or bounced email costs selling time.
Marketing teams use it to build segments and account-based audiences, personalize campaigns, and enrich inbound form fills so that forms can ask for less. They need consistent firmographic and job-function fields to segment reliably, and deliverable addresses for email programs.
RevOps teams use it to match leads to accounts, route records to the right owner, score and prioritize, keep the CRM clean and size the total addressable market. Matching and routing depend on clean company identifiers such as domains, while market sizing can tolerate modeled fields as long as everyone knows they are estimates.
The reason to separate these uses is that “good enough” changes with the job. An estimated revenue band can be fine for sizing a market and wrong for excluding accounts from a campaign. Agreeing which fields are trusted for which decisions settles most internal arguments about data quality before they start.
B2B data turns an ideal customer profile (ICP) from a description into a filter: it lets you find the accounts and people that match the profile, and shows where your data cannot tell.
An ICP usually works at two levels. At the account level it describes the companies you serve best, typically by industry, size, geography, technology and business model. At the contact level, buyer personas describe the functions and seniority levels involved in buying. Company data serves the first level, contact data the second, and signal data helps decide which matching accounts to approach first.
Two working rules help when filtering B2B data against an ICP. First, build hard filters on fields that can be observed, and use modeled fields to rank rather than exclude, so that an estimate does not quietly remove good accounts. Second, remember that coverage shapes what you see: if a source is weak in a region or segment, your ICP will look smaller there than it is. Comparing counts against a list of accounts you know exist is a simple way to expose those gaps.
B2B data is the raw material, a prospect is a record you have chosen to pursue because it fits your ICP, and a lead is a person or account that has shown some interest or engagement.
The terms are used loosely, and many companies define their own lead stages, such as marketing-qualified and sales-qualified leads. The useful distinction is that buying B2B data gives you records, not interest. A contact becomes a prospect when someone decides it fits, and becomes a lead only when that person replies, engages or asks for something. Keeping the terms apart keeps reporting honest: a campaign sent to 5,000 purchased records reaches 5,000 prospects at most, not 5,000 leads.
Evaluate a B2B data provider against your own ICP, geography and use case, and against how it builds and maintains its data, rather than against headline database size. Useful questions to ask include:
The most reliable test of B2B data is a sample checked against reality. Ask for records that match a slice of your ICP, make sure they include accounts you already know well, and measure the bounce rate, the wrong-person rate and how many known accounts are missing. For a deeper set of criteria, see this guide to choosing a B2B contact database for global outreach. The comparisons of B2B data providers in the USA and providers serving the UK and London market apply similar questions to specific vendors.
Responsible use of B2B data depends on where you and your contacts are, what type of information you hold and which channel you use, so there is no single global rule. The points below summarize regulator guidance in three jurisdictions. They are a starting point, not legal advice.
The FTC’s CAN-SPAM compliance guide states that the law makes no exception for business-to-business email. Commercial messages must not use false or misleading header information or deceptive subject lines, must identify themselves as advertisements, must include a valid physical postal address and must explain how to opt out, with opt-out requests honored within 10 business days. Responsibility cannot be contracted away to a third party that sends on your behalf.
The FTC states that each separate violating email can carry a penalty of up to $53,088, and its September 2026 notice confirmed that its civil penalty amounts remain at 2025 levels for 2026. Calls and text messages fall under separate rules. This explainer on how CAN-SPAM applies when you buy email lists in the USA covers the practical side.
The ICO’s guidance on business-to-business marketing explains that PECR treats companies, limited liability partnerships, Scottish partnerships and some government bodies as corporate subscribers, while sole traders and some other partnerships are individual subscribers with stronger protection. The PECR rule on marketing by electronic mail does not apply to corporate subscribers, but you must still identify yourself and give a valid address for opting out.
UK GDPR still applies whenever you process information that identifies a person, such as a named contact’s phone number or a firstname.lastname work email. Business contacts have an absolute right to object to direct marketing, and the ICO recommends adding objectors to a suppression list rather than deleting them, so they are not contacted again. If you buy or sell business contact lists, the ICO says your use must comply with UK GDPR, including telling people that you have obtained their data. The ICO notes that this guidance is under review following the Data (Use and Access) Act, so check the current version before relying on it.
The European Commission explains that the GDPR does not cover data about companies but does cover personal data about people in a professional capacity, such as name-based business email addresses and business phone numbers. Rules on electronic marketing to businesses are not identical across member states, so each market needs its own check rather than an assumption carried over from UK or US practice.
Across all three jurisdictions, the operational habits are the same: record where each contact came from, honor opt-outs and objections quickly, keep a suppression list that every tool and vendor respects, and confirm the rules for each country and channel before a campaign, not after.
B2B data is easiest to judge once you stop treating it as a file and start treating it as a system with sources, rules and a maintenance cycle. The questions that matter stay the same: which layer of data is this, was it observed or estimated, when was it last confirmed, what does “verified” cover, and does it fit the accounts and people you sell to? Teams that ask those questions of their own CRM and of every provider they evaluate get more from the same budget and meet fewer surprises when a campaign goes out.
B2B data is information about businesses and the people who work in them, used by sales, marketing and RevOps teams to find, prioritize and reach target accounts. It usually combines company data such as industry and size, contact data such as name, title and work email, and contextual signals such as technology use, hiring or funding activity.
B2B data is the set of records that describe companies and their contacts. A lead is a person or account that has shown interest, for example by replying, booking a meeting or filling in a form. Buying B2B data gives you records you can approach; it does not give you leads until someone engages.
B2B data comes from first-party sources such as your CRM and forms, official records such as company registries and filings, company websites and press releases, public professional profiles, third-party data providers, and models that estimate values such as revenue or intent. Most databases combine several sources, which requires normalization, deduplication and rules for resolving conflicts.
Accuracy varies by provider, field, region and segment, so no single industry-wide figure is reliable. Email addresses and phone numbers can be tested directly, while fields such as private-company revenue are often estimates. The best way to judge accuracy is to test a sample against accounts you already know and measure bounce and wrong-person rates.
There is no universal schedule. Update frequency should follow how quickly each field changes and how the data is used. Contact details and job titles generally need checking more often than company attributes such as legal name or headquarters, and records should be re-verified before a major campaign. Rising bounce or wrong-person rates show when a segment needs refreshing.
B2B data verification means testing whether specific data points work in the real world, such as whether an email address can receive mail or a phone number connects. It is narrower than validation or qualification: a verified email does not prove that the person holds the stated role, fits your ICP or is interested in buying.
Generally yes, but the rules depend on the jurisdiction, the channel and the type of information. In the US, CAN-SPAM applies to business email with no B2B exemption. In the UK and EU, information that identifies a business contact is personal data under GDPR. Check the rules for each country and channel before outreach, and take legal advice where needed.
