SAP.
SAP owns the S/4HANA story.
Found & recommended by AI agents
Search-class agents touched the close in some runs; the full agent-fleet access profile lands in a later wave.
This page measures two lanes. Commerce: can an agent find SAP, and once it arrives, transact. Talent: can a candidate's agent find an open engineering role on SAP's own career surface and prepare the application. After-sales, procurement, investor and press lanes run on different surfaces and are not yet measured.
Your brand isn't measured yet
What does an AI agent do with your website?
The same measurement as SAP, free for your domain. Five agent classes, one real task, your score in 48 hours.
SAP's site holds up. System integrators own the deal end to end.
We asked AI assistants to pick a cloud ERP for a mid-market manufacturer: 18 measurements across three AI providers, in German, zero errors. The full agent test is still ahead; a follow-up measurement is scheduled.
The sap.com site holds up. AI can read the S/4HANA Cloud story, the edition split, and the industry solutions. The deal happens elsewhere: Accenture, Deloitte, Capgemini, PwC and the SAP partner ecosystem run the demo, scope the project, and own the multi-year contract.
The second risk is SAP's own portfolio. S/4HANA is the ERP; SuccessFactors is HR, Ariba is procurement, Concur is expenses, BTP is the platform. An ERP question must not end at SuccessFactors, and a mid-market question not at Business One.
One label, many breeds. From a plain reader to an autonomous operator, the kinds behind ChatGPT, Perplexity, and Claude Code:
Found, and able to transact?
Two questions, measured separately. A brand can be recommended and still un-buyable, or perfectly buyable and never found.
When someone asks an agent to choose a cloud ERP platform, does it route to SAP?
SAP comes up about a quarter of the time. The rest of the time, an agent recommends an alternative first.
Discoverability · 18-datapoint auditOnce an agent is on SAP's site, can it request a demo or quote?
Search-class agents surface a quote in some runs; the full agent-fleet access profile lands in a later wave.
Evidence · 65 / 100 A measure of how provable and consistent the result is, grounded in cross-method ground-truth agreement (the methods that ran returned the same price), not a separate measured run. A confidence layer on the two scores above, not a third sales axis.
The talent lane.
A candidate's agent, sent to find an open software-engineering role at SAP and prepare the application. Same brand, second surface: the career portal.
Readable posting, unresolved apply step.
Both non-browser agent classes read the full posting server-side as plain HTML prose with schema.org Microdata (no JobPosting JSON-LD, no JS rendering needed for the JD itself); the linked application entry sits on a robots-disallowed path that redirects to the domain root under a raw request, so whether a SuccessFactors login wall or a direct form follows cannot be resolved without browser-side JavaScript execution.
Furthest close-state reached: spec match · frozen task locked 2026-07-02
The score above is provisional where a class shows untested: untested classes are excluded from the calculation, so the pending check can only confirm or raise the value, never silently lower it.
AI Visibility · in measurement — the audit run for this lane has not landed yet. No Talent-lane composite is shown until both axes are measured.
What this does not yet cover
This measurement did not submit an application, upload any file, create an account, or log in. Only the GET-reachable posting-detail page and a raw GET on the linked apply-entry URL were inspected; the apply URL's 301 redirect to the domain root was observed at the HTTP layer only — no browser/JS execution was used to follow the client-side/SuccessFactors route further. Whether login is required, what artefacts (CV/cover letter) are needed, and the real form length remain unconfirmed and are deferred to the Phase C browser pass.
Fairness note
This measurement read one live, regular SAP engineering posting on jobs.sap.com, SAP's own careers domain, and tested how reliably machines can find and extract it. No application was submitted, no account was created, and no personal data was used. SAP's posting is fully machine-readable server-side, which few large career sites achieve; the application entry point could not be conclusively assessed without executing browser JavaScript, so it is recorded as unresolved rather than as a defect, and any login requirement in SAP's application process is documented as a fact, not counted against the score.
What this means for SAP.
On product discovery, SAP is not lacking findability. The brand is Europe's largest software company, named in every mid-market ERP question alongside Oracle and Microsoft. The gap is the partner-intermediated deal mode: the ERP decision does not close on sap.com, it runs through system integrators (Accenture, Deloitte, Capgemini, PwC) who scope, implement, and own the contract. The agent reaches SAP, reads the S/4HANA Cloud story, then the deal routes through an integrator. SAP owns the S/4HANA story, the integrator owns the deal. A second layer is product disambiguation: the agent must resolve an ERP query to S/4HANA, not to SuccessFactors or Ariba, and a mid-market query to S/4HANA Cloud, not to Business One.
What changes the outcome works on both layers. The brand-own page surfaces the S/4HANA story cleanly. The remaining levers: route the agent from the platform story to the right implementation partner for a scoped demo, and make the product boundary unambiguous so an ERP query never resolves to an HR or procurement module. Named Hyperize offerings here: Answer Pages on "Welches SAP-Produkt ist das ERP fuer den Mittelstand und welcher Partner implementiert es?" that bind the ERP query to S/4HANA Cloud and route to the partner-demo channel, and Reference Pages that make the named instruments (the S/4HANA vs SuccessFactors vs Ariba product map, the public-vs-private edition split, the partner-locator by industry) agent-readable. If your product is sold through a partner channel and the buy is a project, this is the AI test that decides whether agents reach you before the integrator shortlist hardens.
The proof isn't more content. It's a repeatable lift in whether agents find, verify, cite, recommend, and complete the brand journey directly — re-measured each wave.
Commission an audit.
Where the BrandScore opens the question, an audit closes it. An interpretive engagement on your full surface, scored under the same methodology.
Get the auditFound with us.
Strategic partnership for brands building agent success as a long-term capability, not a one-off engagement.
ApplyAudit an adjacent property.
The BrandScore covers the primary domain. Get the same methodology applied to an adjacent property: a country site, a sub-brand, a category beyond the DAX-40 slate.
Get a SnapshotThis is SAP. What about your brand?
You just saw how an AI agent treats a DAX 40 brand.
The same measurement runs free against your domain: five agent classes, one real buying task, your Agent Success Score in 48 hours, in the exact format of this page.
System integrators and implementation partners capture 70% of enterprise software demand before SAP.
Third-Party Interception derived from AI Visibility response analysis: the partner-intermediated deal mode applies, and at the strongest level of this wave. Enterprise ERP deals route through system integrators (Accenture, Deloitte, Capgemini, PwC) and the SAP partner ecosystem, which run the demo, scope the implementation, and own the contract. The agent surfaces the integrator layer alongside SAP's direct S/4HANA Cloud product story; the buyer never transacts with SAP directly.
Intermediaries Accenture · Deloitte · Capgemini · PwC
Hyperize-selected tasks.
One task from the public sector grid. Task list is frozen before each wave runs.
SAP S/4HANA Cloud ERP for a mid-market manufacturer (~500M EUR revenue, international sites)
- Close state
- a quote
- Bottleneck
- Brand surface carries the S/4HANA Cloud story and the demo request; system-integrator intermediation (Accenture / Deloitte / Capgemini / PwC) captures the demo-scope-contract close, and the multi-product portfolio risks an ERP query resolving to SuccessFactors or Ariba.
Fairness note
Wave 11 Q2 2026 partial measurement. Single task (SAP S/4HANA Cloud ERP for a mid-market manufacturer, ~500M EUR revenue with international sites, quote_ready close). AI Visibility from the audit pass (Q2-2026, openai/perplexity/anthropic, DE language, 18/18 valid datapoints). AI Usability axis pending the agent-fleet run (scheduled for a later wave) — current Usability score reflects structural defaults for the quote_ready close, not a measured per-class access profile. Fairness Review pending the sector fairness grid.
How the score was produced.
Discoverability is audit-pipeline-derived. 3-provider sample (openai, perplexity, anthropic), 3 query variants per task, 2 runs per variant · 18 valid datapoints scored against a five-state handoff cascade. [S1]
AI Usability is derived from the access-profile above (usability-derivation/v1): how far the best agent reached (close state) modulated by how many agent classes succeeded. The per-class profile is the truth; the score is a reproducible summary of it, not a separate rating. Fleet phases (HTTP / Coding / Browser / ACT) produce the profile. [S2]
Agent Success Score = (AI Visibility × 0.20) + (AI Usability × 0.70) + (Evidence × 0.10)
On a 0–100 scale, displayed 0–10. AI Usability bundles the agent's reach + completion; AI Visibility is audit-derived discoverability. Weighting is public; the per-prompt derivation is not.
Measurement scope
Confidence C · one measured task on a 3-provider track (openai, perplexity, anthropic). Confidence promotes to B with a second task plus a fourth provider on the next wave.
Measurement timeline.
Each wave appends; nothing overwrites. Frozen Wave Rule.
- Entry · 01
28 May 2026
Wave · ProtocolWAVE-Q2-2026-W11-CENSUS
ars-methodology/v1.1
Wave 11 partial measurement landed. AI Visibility pass complete (18/18 valid, 0 errors). The agent-fleet run is scheduled for a later wave — Usability axis on this wave reflects structural defaults for the quote_ready close. Producer-page survival of the S/4HANA story confirmed by the AI Visibility response analysis; system-integrator channel position derived from the AI Visibility response texts (Accenture / Deloitte / Capgemini / PwC dominate the deal layer). Product-disambiguation risk (S/4HANA vs SuccessFactors / Ariba; S/4HANA Cloud vs Business One) flagged for the diagnosis.
Evidence and provenance.
Public methodology references and internal evidence pointers behind every claim above.
- [S1]Accessed · 28 May 2026
AI Visibility audit · SAP Wave Q2 2026 (dispatched 2026-05-28)
Internal · Hyperize evidence
- · AI Visibility score
- · the close state reached (quote_ready)
- [S2]Accessed · 28 May 2026
Agent-fleet run · SAP phase 1-4 (queued)
Internal · Hyperize evidence
- · the per-class access profile (a later wave)
- Accessed · 28 May 2026
Public · hyperize.ai
- · fairness declaration
- · Third-Party Interception framing
Read the doctrine. Challenge the score. Extend the slate.
Task Selection.
The fairness doctrine behind the slate above. Five failure modes, six criteria, public before each wave.
Read ChallengeDisagree with this score.
Send evidence under public Fairness Review. Failed reviews are documented with the named failure mode.
Challenge ExtendSubmit your own task.
Open Surface Run · additive measurement. The Hyperize-selected slate stays frozen; your task gets the same methodology.
SubmitEditorial coverage
The DAX 40 Agent Success Index is a point-in-time snapshot of the agent-success of public digital touchpoints. Results are not statements about product quality, company performance, service quality, or the legal obligations of the brands named. Brand names and logos remain the property of their respective owners and are used solely for identification and reporting purposes in the context of editorial coverage (§ 23 MarkenG, Art. 5 GG).
Brands wishing to respond, engage, or correct a factual error may contact hello@hyperize.ai. Responses received are published in full alongside the findings. Full methodology and editorial-coverage notice: coverage statement.
