What Is Firmographic Data?
Firmographic data is a set of attributes that describe a business or organisation. Think of it as demographics, but for companies. Where demographics tell you a person's age, location, and income — firmographics tell you a company's industry, headcount, revenue, and legal structure.
These attributes let you classify, filter, and segment businesses into groups that matter for your use case. Whether you're building an ICP for outbound sales, screening vendors for compliance, or sizing a market for investment decisions — firmographic data is where it starts.
Here's the key distinction most articles miss: firmographic data is only as useful as the source behind it. A revenue figure scraped from a blog post and a revenue figure pulled from an official filing at Companies House are not the same thing. One is a guess. The other is a fact.
That's why registry-sourced firmographic data — pulled directly from government business registries — is becoming the standard for enterprise teams that can't afford to work with bad data. Global Database connects directly to 400+ government registries across 200+ countries, covering firmographics, financials, directors, shareholders, UBO data, and corporate linkage.
Who Uses Firmographic Data?
Firmographic data isn't just for sales teams. It's the shared foundation across every team that touches company data — each with different depth requirements.
Sales and marketing teams typically need core firmographic attributes — industry, size, location. Compliance, risk, and investment teams need to go deeper: financials, ownership, director data, and corporate linkage.
Types of Firmographic Data
Firmographic data alone isn't enough. Enterprise teams need company intelligence that goes far beyond basic firmographics. Here's the full stack — starting with core firmographics and expanding into the deeper layers.
Core Firmographic Data
| Attribute | What It Tells You | Why It Matters |
|---|---|---|
| Company Name | Legal registered name | Entity identification, matching |
| Registered Address | Official address on file | Territory planning, jurisdiction |
| Registration Number, VAT, EIN, LEI | Unique legal identifiers issued by government authorities | The only way to confirm a company is real and legally registered. Essential for KYB, deduplication, and entity resolution |
| Incorporation Date | When the company was formed | Stability assessment, risk scoring |
| Status & Legal Form | Active/dormant/dissolved + Ltd, GmbH, LLC | Don't onboard dead companies |
| SIC/NAICS Codes & Local Classifications | Industry classification — international and local | Segmentation, ICP matching, regulatory reporting |
| Employee Count (Actual) | Headcount from official filings or registry records | Verified company size for compliance, credit, and deal qualification |
| Employee Count (Estimated) | Headcount inferred from LinkedIn, job postings, or modelling | Directional sizing when filings aren't available. Not suitable for compliance |
| Revenue (Filed) | Revenue from official financial statements | Verified budget qualification, growth assessment |
| Revenue (Estimated) | Revenue inferred from web traffic, headcount, or industry models | Useful for prospecting. Not audit-ready |
| Business Description | What the company does | ICP matching, personalisation |
| Industry Tags | Normalised classification | Cross-border segmentation |
| Websites & Social Profiles | Digital presence | Outreach, research |
Why Local Industry Codes Matter
Most articles only mention SIC and NAICS — the US-centric classification systems. But if you're targeting companies across Europe, these codes often aren't enough. Each country maintains its own official industry classification, and local regulators, tax authorities, and procurement systems rely on them.
| Country | Local Classification | Example |
|---|---|---|
| Italy | Codice ATECO | 62.01.00 — Software development |
| Germany | WZ (Wirtschaftszweig) | 62.01 — Computer programming |
| Spain | CNAE | 62.01 — Computer programming activities |
| France | Code NAF / APE | 62.01Z — Computer programming |
| EU (general) | NACE Rev. 2 | 62.01 — Computer programming activities |
| UK | UK SIC 2007 | 62012 — Software development |
| US | NAICS / SIC | 541511 — Custom computer programming |
If you're segmenting Italian companies by NAICS codes, you'll miss most of them — Italian businesses file with Codice ATECO, not NAICS. The same applies to Germany's WZ codes, Spain's CNAE, and France's NAF codes. A provider that only offers SIC or NAICS is blind to how companies are classified in local registries.
Global Database maps between all major classification systems — NAICS, NACE, SIC, Codice ATECO, WZ, CNAE, NAF, and other local codes — and adds normalised industry tags on top. Your filters work consistently whether you're searching in Milan, Munich, or Madrid.
Registration Numbers and VAT IDs: The Only Way to Confirm a Company Is Real
A company name is not an identity. There are thousands of companies called "Global Solutions Ltd" registered in different jurisdictions. Without a unique legal identifier, you can't confirm the company you're dealing with actually exists, is legally registered, and is the specific entity you think it is.
That's what registration numbers and VAT IDs are for. They're issued by government authorities and tied to a single legal entity in a specific jurisdiction:
| Identifier | Issued By | Purpose |
|---|---|---|
| Company Registration Number | National registry (e.g. Companies House, Handelsregister, KRS) | Confirms the entity is legally incorporated |
| VAT Number | Tax authority | Confirms the entity is registered for tax — strong signal it's operationally active |
| EIN | IRS (US) | US tax identifier — required for hiring, banking, operations |
| LEI | GLEIF-accredited issuer | Global standard for financial transactions |
For compliance teams, a registration number or VAT ID is the minimum requirement to begin a KYB check. Without one, you can't verify the entity against the official registry. You can't confirm its legal form. You can't check if it's active or dissolved. You're taking a company's word for it — and in regulated industries, that's not acceptable.
Global Database returns registration numbers, VAT IDs, EINs, and LEIs as part of every company record — verified against the source registry. If a company claims to be "XYZ GmbH in Germany," you can check its Handelsregister number against the official record in seconds.
Employee Numbers: Estimated vs. Actual — And Why It Matters
Employee count is one of the most used firmographic attributes. Sales teams use it to gauge deal size. Compliance teams use it for risk scoring. Investors use it to benchmark growth. But there's a critical difference most providers don't surface: is the number real, or is it a guess?
Actual Employee Count (Filed)
In many jurisdictions, companies report headcount in annual filings. This is the actual number — disclosed under legal obligation, typically audited, tied to a specific reporting date.
Example: A German GmbH files its annual accounts with the Bundesanzeiger and reports 347 employees as of December 2025. That's a fact.
Estimated Employee Count (Modelled)
When filings aren't available, providers estimate. Common methods: counting LinkedIn profiles, tracking job postings, or applying statistical models based on revenue and industry benchmarks.
Example: A US SaaS company doesn't file headcount publicly. A provider scans LinkedIn and finds 280 profiles. They report "~300 employees." But LinkedIn profiles lag — people don't update when they leave. The real number might be 220.
Global Database distinguishes between registry-sourced employee counts (from official filings) and enriched estimates (from validated models) on every record. You always know which number you're working with and where it came from.
Beyond Firmographics: The Intelligence Enterprise Buyers Actually Need
Most providers stop at the table above. That's fine for basic prospecting. It's not fine for compliance, credit decisions, or investment screening.
Directors / Officers
| Attribute | What It Tells You | Why It Matters |
|---|---|---|
| Full Name & Role | Who holds which position | Decision-maker targeting, compliance |
| Service Address | Official registration | Sanctions screening, jurisdiction |
| Date of Birth & Nationality | Personal identifiers | PEP screening, AML compliance |
| Employment History | Career trajectory | Relationship mapping, due diligence |
Financials — Up to 20 Years
| Attribute | What It Tells You | Why It Matters |
|---|---|---|
| Balance Sheet (Digitised) | Assets, liabilities, equity | Credit decisions, financial health |
| Profit & Loss | Revenue, costs, margins | Deal qualification, growth |
| Cash Flow | Liquidity position | Risk scoring, payment reliability |
| Capital & Reserves | Financial buffer | Stability assessment |
| KPI & Ratios | Performance metrics | Benchmarking, monitoring |
Corporate Linkage
| Attribute | What It Tells You | Why It Matters |
|---|---|---|
| Global Corporate Linkage | Full group structure | Duplicate outreach, buying centres |
| Ultimate Parent | Top of ownership chain | Enterprise deal routing |
| Subsidiaries | Entities owned | Risk exposure mapping |
| Ownership Path | How control flows | UBO identification, sanctions |
| Historical Parent Chains | Past ownership | Due diligence, M&A research |
Shareholders & UBO
| Attribute | What It Tells You | Why It Matters |
|---|---|---|
| Shareholder Name & Shares | Ownership breakdown | KYB, control mapping |
| Share Type & Value | Nature of holdings | Risk, voting control |
| UBO | Ultimate beneficial owner | AML compliance, regulatory |
| DOB & Address | UBO identifiers | Sanctions, PEP checks |
Firmographic vs. Technographic vs. Intent Data
These three data types answer fundamentally different questions. Understanding where each one starts and stops will save you from building campaigns on the wrong foundation.
Firmographic Data — "Who is this company?"
Firmographic data tells you the facts about a business: its legal name, where it's registered, what industry it operates in, how big it is, and whether it's still active. This is the company's identity. Without it, you don't know who you're talking to.
Example: A compliance team needs to onboard a new supplier in Germany. Firmographic data tells them the company is registered as a GmbH in Munich, has a Handelsregister number, was incorporated in 2012, operates in logistics (WZ code 52.29), has 450 employees, and is currently active. That's the foundation — everything else builds on top of it.
Technographic Data — "What tools does this company use?"
Technographic data describes a company's technology stack — what software, platforms, and infrastructure they've adopted. It's collected by scanning websites, job postings, and code signatures. It answers questions like: do they use Salesforce or HubSpot? Are they on AWS or Azure? Have they installed a competitor's product?
Example: A SaaS company selling a Salesforce integration only wants to target companies that actually use Salesforce. Technographic data filters out the 80% of companies that don't — saving the SDR team from pitching to irrelevant prospects.
Technographic data is useful for product-fit targeting. But it says nothing about whether the company is financially healthy, legally active, or worth your compliance team's time. It's a targeting layer, not a verification layer.
Intent Data — "Is this company looking to buy right now?"
Intent data tracks buying signals — content consumption, search behaviour, website visits, review site activity. It tries to answer the hardest question in sales: when is someone ready to buy? The idea is that if a company is researching "KYB automation software" across multiple channels, they're probably evaluating solutions.
Example: Your marketing team sees that a mid-market bank in the Netherlands has consumed 12 pieces of content about KYB compliance in the last two weeks. Intent data flags them as "in-market." Your SDR reaches out with relevant timing.
The catch: intent data is only as good as the firmographic layer underneath it. If that mid-market bank was dissolved three months ago — or if the entity consuming the content is a 5-person subsidiary, not the parent — your perfectly timed outreach is wasted. Intent tells you when. Firmographics tell you who. You need both.
How They Work Together
| Data Type | Question It Answers | Source | Best For |
|---|---|---|---|
| Firmographic | Who is this company? Are they real? Are they active? | Government registries, official filings | Segmentation, qualification, compliance, KYB |
| Financial | Can they afford what we sell? Are they financially healthy? | Filed accounts, balance sheets | Credit decisions, deal qualification, risk |
| Ownership / UBO | Who actually controls this entity? | Shareholder records, registry filings | KYB, AML, sanctions screening |
| Corporate Linkage | Who's the parent? Are there subsidiaries? | Registry cross-references, filings | Dedup, deal routing, risk mapping |
| Technographic | What software/tools do they use? | Web scraping, job postings, code analysis | Product-fit targeting, competitive displacement |
| Intent | Are they actively looking to buy? | Content consumption, search behaviour | Timing outreach, prioritising pipeline |
| Demographic | Who's the right person to contact? | LinkedIn, directories, CRM enrichment | Personalisation, contact targeting |
The critical takeaway: firmographic data is the only layer that confirms a company actually exists, is legally active, and is who they say they are. Technographic and intent data can tell you what tools a company uses and whether they're researching solutions — but they can't tell you if the entity is dissolved, under sanctions, or a shell company. For enterprise teams working in compliance, risk, or regulated industries, firmographic data isn't just the foundation. It's the one layer you can't skip.
How Teams Use Firmographic Data: 5 Real-World Examples
The Problem
Cybersecurity company targeting mid-market financial services firms in Germany, Austria, and Switzerland. Need: 200–2,000 employees, revenue above €20M.
How They Solved It
Filtered by NACE codes, employee/revenue bands, DACH jurisdictions, excluded dissolved entities. Data from Handelsregister and Firmenbuch.
The Result
The Problem
Fintech onboarding payment partners across UK, Netherlands, Singapore.
How They Solved It
Pulled firmographic data (status, legal form, address) and ownership intelligence (directors, shareholders, UBO) via Global Database's KYB API.
The Result
The Problem
PE fund targeting manufacturing in Poland, Czech Republic, Romania, Hungary. €10M–€50M revenue, positive margins, <500 employees.
How They Solved It
Pulled financial data (digitised filings) and firmographic attributes from government registries. Ranked by 3-year revenue growth.
The Result
The Problem
B2B SaaS (ERP) needs different messaging for SMB (<50), mid-market (50–500), and enterprise (500+).
How They Solved It
Segmented CRM by employee count and industry using Global Database enrichment. Three campaign tracks.
The Result
The Problem
Corporate lender with 2,000 borrowers needs early warning on status changes, ownership transfers, financial deterioration.
How They Solved It
Connected Global Database monitoring to flag changes in status, directors, or filings.
The Result
Where Does Company Data Come From?
Government Business Registries — Companies House (UK), Handelsregister (Germany), KRS (Poland), SEC EDGAR (US), ACRA (Singapore). The gold standard. Global Database connects directly to 400+ registries across 200+ countries.
Official Financial Filings — Annual accounts, tax filings, regulatory disclosures. Factual and auditable.
Third-Party Providers — Some pull directly from registries. Others buy from intermediaries — adding delay and error.
Web Scraping & Estimation — Revenue from web traffic. Headcount from LinkedIn. Dangerous for compliance.
Self-Reported Data — Surveys, web forms, badge scans. Decays fast.
What the Data Actually Looks Like
Here's a simplified API response for a single company — firmographics, financials, ownership, and linkage in one call.
// Core Firmographic Data "company_name": "Acme Industries Ltd", "registration_number": "12345678", "vat_number": "GB123456789", "status": "Active", "legal_form": "Private Limited Company", "employees_estimate": 340, "revenue_estimate": { "value": 28500000, "currency": "GBP" }, // Directors "directors": [{ "name": "Jane Smith", "role": "Director" }], // Financials (latest filing) "financials": { "revenue": 28540000, "net_profit": 3200000, "source": "companies_house_filing" }, // Shareholders & UBO "shareholders": [{ "name": "Jane Smith", "percentage": 75.0, "is_ubo": true }], // Data provenance "data_source": "companies_house", "last_verified": "2026-02-24T09:14:00Z"
data_source and last_verified. Every data point is traceable to its registry source and timestamped. Most providers can't tell you whether a field is verified or estimated.What Makes Company Data Unreliable (And How to Fix It)
Stale Data
A company filed accounts 18 months ago. Since then, they've been acquired, changed address, and appointed new directors.
Fix: Providers that connect to registries in real time, not batch dumps.
Inconsistent Formats
"Ltd" in the UK, "GmbH" in Germany, "SARL" in France. If your system treats these as different entity types, segmentation breaks across borders.
Fix: Normalised legal forms, industry codes, and status fields. Global Database standardises data from 400+ registries into a consistent schema.
Estimated vs. Verified Data
An employee count from LinkedIn is an estimate. From a filed annual return, it's a fact.
Fix: Always check if a data point is registry-sourced or estimated. If the provider can't tell you, move on.
How to Choose a Company Data Provider
Depth beyond firmographics. Basic company attributes are table stakes. Ask for financials, directors, shareholders, UBO, and corporate linkage.
Source transparency. Can you distinguish registry-sourced fields from estimated ones?
Global coverage with local depth. US and UK is easy. Poland, Nigeria, Singapore with the same depth is hard.
Real-time access. APIs that check the registry when you ask — not six months ago.
Normalised fields. Legal forms, industry codes, and status on a common schema.
Resale rights. If you're building data into your product, you need redistribution rights.
7 Questions to Ask Your Current Data Provider
Most teams don't switch because they're happy. They switch because they discover what they're missing.
- "Is this data point registry-sourced or estimated?"If they can't tell you per-field, every data point is suspect.
- "When was this record last verified against the official registry?""Last updated 6 months ago" from a batch dump is not the same as verified at query time.
- "Can I see directors, shareholders, and UBO — or just name and address?"Many firmographic providers only deliver surface-level attributes.
- "How many government registries do you connect to directly?"Intermediaries add delay, error, and cost.
- "Do you cover my specific jurisdictions with the same data depth?""Coverage" that means name-and-address only isn't coverage.
- "Can I redistribute this data in my own product?"Legacy providers often restrict resale.
- "How do you handle cross-border normalisation?"If Ltd, GmbH, and SARL show up as three entity types, segmentation is broken.
Firmographic Data for Compliance and KYB
Regulations like the EU's AMLD 5 & 6, the UK's Economic Crime and Corporate Transparency Act, FATF recommendations, the US Corporate Transparency Act (BOI reporting), MiCA (crypto), and DORA (financial services ICT risk) all require businesses to verify the identity and ownership of companies they work with.
Firmographic data is the starting point — but on its own, it's not enough. A full KYB check requires:
- Legal name, registration number, VAT, EIN, LEI — confirmed against the official registry
- Registration status & legal form — is the entity active?
- Registered address — does it match what the company claims?
- Directors and officers — names, roles, addresses, nationality
- Shareholders and UBO — who ultimately controls the entity
- Financial filings — digitised balance sheets, P&L, cash flow, up to 20 years
- Corporate linkage — ultimate parent, subsidiaries, full ownership path
Self-reported data can't satisfy these requirements. Scraped data can't either. Only registry-sourced data — verified at the point of check — meets the regulatory standard.
Global Database was built for this. Every API call returns registry-verified data normalised across 200+ countries.