Inside a 734,565-company Polish business database: sources and method

What a vendor should be able to say about its own data

Most B2B lead generation vendors describe their company data with an adjective: comprehensive, extensive, best-in-class. Almost none say which register it came from, how often it is refreshed, or what a buyer cannot filter on. This page takes the opposite approach for one specific database: Poland, 734,565 companies, with the sourcing and the gaps stated plainly.

The database in question is the one behind Ripe Leads' Polish outbound campaigns, and the same figures are visible on the public drill-down section of the Ripe Leads homepage, not held back as an internal number only quoted in sales conversations. A buyer can therefore put the two side by side. A number that lives only inside a proposal gives a buyer nothing to test; a number on a live page can be checked before the call and again after it.

What follows is the method, not the pitch: what the total counts, where the companies sit regionally, which sectors are best represented, and, importantly, what data is not available at all.

The four headings below double as a procurement checklist for any Polish data vendor: which register, how many records per voivodeship, which fields are populated, and when the last pull ran. Few competitors in the Polish market currently publish that structure themselves, which is worth noting when weighing one quote against another.

What "734,565 active Polish companies" actually counts

The database holds 734,565 company records tagged to Poland, and every one of them currently carries an active status in the underlying source, a full match between the total count and the active count. That reflects a database built from records that pass an activity filter at source rather than one that accumulates closed entities over time and relies on a separate cleanup step.

Of the 734,565 records, 663,745 carry a known sector classification, just over 90 per cent. That is a substantially higher classified share than in smaller markets, consistent with Poland's scale as one of the larger economies this database covers. A buyer filtering by industry can expect strong coverage across the large majority of the dataset.

The total is a snapshot taken at the last refresh, not a live counter. Poland registers and closes companies every working day, so a buyer who pulls a fresh export a month later should expect a total in the same range, and should treat an identical figure as a sign the vendor has not refreshed at all.

Four voivodeships, and one that does not appear

The database publishes a regional breakdown for its four largest Polish voivodeships. Mazowieckie, home to Warsaw, leads by a wide margin, more than three times the size of the second-largest region in this dataset.

Within Warsaw, the largest single city by company count, the top five sectors run Professional Services at 34,024, Wholesale and Distribution at 19,681, Real Estate at 19,404, IT and Software at 13,922, and Construction and Trades at 13,492. A fifth region, Dolnośląskie, holds 61,671 companies in the underlying data but is not surfaced on the public site, which caps its regional drill-down at the top four.

That concentration in Mazowieckie matters for a buyer planning a country-wide campaign versus one focused on Warsaw specifically. A campaign aimed only at the capital region reaches 244,632 companies, more than Wielkopolskie, Śląskie and Małopolskie hold between them at 202,488. A campaign needing coverage across those three should confirm each region carries enough classified, targetable records for the sector in question.

Which industries the classified records cover

Across the classified share of the database, the largest sector is Professional Services, followed by three sectors tied to physical infrastructure and industry: manufacturing, real estate and construction. The overall mix is broader and less concentrated in any single sector than in smaller national datasets, consistent with the size and diversity of the Polish economy.

• Professional Services. 112,348 companies, the largest named sector.
• Manufacturing and Industry. 80,894 companies.
• Real Estate. 73,941 companies.
• Construction and Trades. 69,839 companies.
• Wholesale and Distribution. 68,365 companies, followed by Transport and Logistics at 39,156, IT and Software at 38,549, Retail and E-commerce at 31,192, Food and Hospitality at 26,931, and Marketing and Media at 22,385.

The spread across these ten sectors is even, with the largest, Professional Services, holding 112,348 of the 663,745 classified records. That means the database supports targeted outbound across a wide range of industries rather than concentrating strength in one or two, as some smaller national datasets do.

That breadth is a direct consequence of the Polish economy's own size and diversity rather than a feature of the database design. A buyer targeting a narrow sub-sector should still confirm classified coverage for that specific segment, since a healthy top-ten spread does not guarantee depth in every niche below it.

What is missing: no headcount field, and partial revenue coverage

The single most important limitation of this dataset: it carries no employee headcount field for Poland at all. Every one of the 734,565 records shows a null value where a headcount figure would sit. This is a genuine gap in the source data, not a filtering choice, and no headcount figure for Polish companies should be cited from this database under any circumstance. A buyer needing to segment by company size in Poland will need to rely on revenue bands or sector proxies instead, or source headcount separately.

Revenue coverage is present but partial: 395,436 records carry no revenue value, 138,114 sit under EUR 100,000, 119,847 between EUR 100,000 and EUR 1 million, 67,537 between EUR 1 million and EUR 10 million, and 13,631 above EUR 10 million. That leaves just over half the database with a usable revenue figure, a smaller share than the sector-classification coverage, so revenue-based filtering should be treated as a partial view rather than a full population count.

A buyer who has been quoted a headcount-segmented figure for the Polish market by any vendor should ask directly where that figure came from, since it did not come from this dataset, and a vendor unable to name its own source for a Polish headcount claim is worth treating with some caution.

Where "active" comes from, and how often KRS and CEIDG are pulled

"Active" in this database reflects the status field carried by the underlying source registers, KRS for registered companies and CEIDG for sole traders, at the point of the most recent refresh, not a judgement made by the vendor about whether a company still trades. A company that has wound up but not yet filed the change with KRS keeps its active flag until the register catches up. Every database built on a public register inherits that lag.

So 734,565 describes the formally registered and active population on the day of the pull. It does not promise that every record trades this week. Ask a vendor how it handles that lag, and note whether the question is one it has already thought about.

Public registers in Poland update on an ongoing basis rather than on a fixed schedule, so a database drawing from KRS and CEIDG is only as current as its last synchronisation. A buyer should ask any vendor, this one included, how recently its Polish data was last refreshed before relying on it for a time-sensitive campaign.

Using this page to test another vendor

This page hands a buyer two things a marketing claim withholds. The regional and sector totals above sit on the Ripe Leads homepage as well, so they can be compared without asking anyone, and the gaps are named instead of left for the buyer to discover after signing. Over 90 per cent of this database carries a sector tag, revenue coverage sits just above half, and headcount is not available for Poland at all, a limitation worth confirming with any vendor claiming to segment the Polish market by company size.

None of that makes 734,565 companies a small database; it is one of the larger national datasets this analysis covers. It does mean a buyer should ask any vendor, this one included, exactly which fields are populated before assuming a headline number tells the whole story.

Point the same standard back at Ripe Leads. Ask for a dated export, run the voivodeship totals against the ones printed here, and treat any gap the operator cannot explain the way you would treat it from any other vendor.