Analytics Legends The knowledge platform for SAP Analytics
Guide

List of SAP customers: 19,090 tracked, 168 with strong proof

As of 2026-08-14

A list of SAP customers is easy to produce and hard to make true. Ours holds 19,090 organisations across 140 country buckets, published in three levels rather than one: 19,090 tracked, 829 documented with at least one source, 168 verified by strong proof. If you came for a downloadable roster, the useful answer is that the roster is the least reliable part of any such list — what makes a name worth acting on is the evidence attached to it.

Why most published SAP customer lists are not evidence

The common way to build one is to scrape logo walls, press coverage and job advertisements, then present the union as a customer base. That produces three failure modes, each surviving casual review because the output looks like a clean list.

Wrong entity: an index page listing companies in a country becomes a list of customers, so names arrive that were never customers of anything. Wrong time: an organisation named in a decade-old release may have migrated away twice since, and a list with no date cannot tell you. Wrong product: a company running SAP payroll looks identical, once scraped, to one running a full BW-to-Datasphere estate.

A list that does not separate what it knows from what it merely found inherits all three, and the reader cannot tell which is which.

The three levels we publish, and what each one means

Tracked (19,090) — the organisation is in the directory with an SAP association recorded. A research population, not an assertion that it is a current SAP customer.

Documented (829) — at least one source URL supports the association. Enough to justify research time, not enough for a proposal unread.

Verified by strong proof (168) — the association rests on a named class of evidence: an SAP reference story, a press release, a partner case study, an annual report, or an official career or project page. The tier that can be cited.

The distance between 19,090 and 168 is not a defect being hidden; it is the shape of publicly verifiable information about who runs SAP. A list presenting tens of thousands of names at one confidence level makes a claim it cannot support, and the number that matters for your work is usually the smallest one.

Running SAP is not the same as running SAP analytics

For an analytics consultant or practice, the SAP customer list is the wrong population to start from. 983 of the 19,090 tracked organisations carry strong evidence of SAP analytics use specifically — Datasphere, Business Data Cloud, SAP Analytics Cloud, BW/4HANA or BusinessObjects named in a source, or a substantial recorded analytics project or team.

That is the population an analytics proposition addresses. The others may well run analytics on SAP data; there is no published evidence either way, and treating absence of evidence as evidence of absence is as wrong as the reverse.

So 19,090 names is a research population, while the 983 are organisations whose analytics estate is at least partly on public record — the group where a first conversation starts from something specific.

Three checks that make any such list usable

Check the evidence class, not the name: a reference story published by SAP and a name harvested from a job advertisement are not the same fact, and only the first survives a procurement conversation. Check the date, because SAP estates change on multi-year cycles. Check the product, because 'runs SAP' covers a dozen landscapes with nothing commercially in common.

The durable use of such a list is the reverse of the question people search for: not 'who are SAP's customers' but 'which organisations here have publicly documented an SAP analytics estate, recently enough for the source to still describe reality'. Names satisfying that are far fewer than 19,090, and each is worth more than a thousand unsourced entries — the more so while the move off classic BW remains an open decision, since that decision turns a customer name into an engagement.

What we cannot assert

We cannot tell you whether an organisation is a current SAP customer unless a source says so and carries a date — 18,261 of the 19,090 tracked rows have no source URL attached, which makes them research leads rather than facts. We cannot tell you what any organisation spends with SAP, which modules it runs, or when its contract renews: none of that is public. And we do not publish a downloadable roster, because a name separated from its evidence and its date is exactly the artefact that makes SAP customer lists unreliable.

Frequently asked

Is there a complete public list of SAP customers?

No. Completeness would mean access to something SAP does not publish. Public lists are compiled from reference stories, press coverage, filings and job advertisements — a partial, unevenly dated view. We track 19,090 on that basis: 829 carry a source, 168 strong proof.

What counts as strong proof that an organisation uses SAP?

An SAP reference story, a press release, a partner case study, an annual report, or an official career or project page naming the system. 168 of the 19,090 reach that bar.

How many SAP customers actually use SAP analytics?

983 of the 19,090 carry strong evidence of it — an analytics product named in a source, or a recorded analytics project or team. The rest may use it; there is no public evidence either way.

What this page is built on

Read next