About Analytics Legends.
As of 2026-08-23
Last updated: 23 August 2026
This page exists so you never have to guess who wrote a page, how it was produced, or whether a machine had a hand in it. If our crawler turned up in your server logs and you followed the link in its user-agent, you are in the right place — the crawler section below is for you.
Who writes this
Analytics Legends is edited by one named person, Cédric-Olivier Mâry, who is also its publication director. Twenty-seven years in the SAP ecosystem, working in French, English and German, on the stack this site covers and nothing else: SAP Datasphere, SAP Business Data Cloud, SAP Analytics Cloud, BW/4HANA and Databricks, plus the programme leadership around them.
There is no content team, no freelance pool and no syndication network. One editor is accountable for everything published here. That is a deliberate limit: it caps how much we can write, and it is why the written pages are narrow and deep rather than broad and thin.
The publisher is CM CONSULTING, a French EURL. Company registration, host, payment processor and governing law are in the legal notice.
Analytics Legends is not affiliated with, sponsored by, or endorsed by SAP SE. We are not an SAP partner, and we do not resell SAP software or services.
Why it exists
One purpose: help people who work on SAP analytics decide something. Which technology to bet a programme on, what a day rate should be, which firm does this work in a given country, which certification is worth the time, what actually changed in the product this month. Every page is meant to answer a question someone arrived with.
We sell subscriptions to part of it. That pays for the work; it does not decide the editorial line. Nothing here is a paid placement, and no company can buy a listing, a rank or a better description.
How each page is made
Three registers, and they are not equivalent. We say which is which, because a reader deserves to know whether they are reading an argument or a compilation.
- Written by hand — studies, concept cards, academy modules and guides. An argument, with its sources. Somebody is responsible for every sentence.
- Curated — the news feed. Items are selected, classified and summarised, and every item links to the publisher who broke it. Headlines are quoted from the source, never rewritten, and each carries the language it was written in.
- Compiled automatically — the company directory and the opportunity radar, built from public sources on a schedule. Facts and links, kept fresh. No prose we did not write. A field we do not know is shown as unknown.
The automation fetches public pages, extracts structured facts — a company name, a country, a role, a date, a link — classifies them, re-checks that the links still resolve, and drops rows whose source has gone. It runs nightly, unattended.
What it never does:
- It never republishes someone else's prose. A third-party description is a source we point at, never a payload we serve. Job-ad titles appear as quotations of the advertiser's own wording.
- It never invents a missing value. An unmeasured day rate, position or field is published as unmeasured. An absence is never rendered as a zero.
- It never writes an opinion. Rankings, verdicts and recommendations are editorial, and they are written by hand.
- It never publishes personal data. Individuals are not listed, and contact details encountered while crawling are redacted before storage.
Where AI is used, and where it is not
Plainly, because you would be right to ask. AI assists the editor: drafting, translating between our two languages, classifying items into the right family, and reviewing the platform's own code and data for defects. It is a tool in the workshop.
It is not a substitute for the editor. No page is published because a model produced it: everything carrying an argument is read, corrected and signed off by the person named above, and he answers for it. Where a page is a compilation rather than an argument, the list above says so.
In the other direction: our content may be retrieved and cited by AI answer engines, with attribution, and may not be used to train models. That policy, and the list of agents it names, is machine-readable at /llms.txt and enforced in /robots.txt.
Our crawler
We operate a crawler called AnalyticsLegendsBot. If you run a site we reference, you may see it. It identifies itself in every request and links back to this page.
- It obeys robots.txt. A disallow is honoured; there is no fallback path around it.
- It is paced. One request at a time, with a pause between each. It is not a load test.
- It reads public pages only. No logins, no paywalls, no forms, no personal data.
- It takes facts, not text. What we keep is a name, a country, a role, a date, and a link back to you.
If you would rather we did not crawl you, or you want a page about your organisation corrected or removed, write to contact@analyticslegends.ai. A removal request is honoured; you do not need to justify it.
Corrections
If something here is wrong, tell us and we will fix it. Factual errors are corrected at the source, so the correction survives the next refresh rather than being patched on the page where it happened to show. Write to contact@analyticslegends.ai.
Contact
contact@analyticslegends.ai — editorial, corrections, removals, crawler questions and press.