--- title: "SAP — DAX 40 Agent Success Score | Hyperize" description: "SAP: AI Visibility 29.4/100, primary gap Interception. Hyperize DAX 40 Agent Success Index, measured under a public Task Selection Doctrine." canonical: https://www.hyperize.ai/en/dax40-index/brands/sap lang: en last-updated: 2026-07-21 --- # SAP. [Home](/en/) / [DAX 40 index](/en/dax40-index) / SAP Original research · Tech & Telecom Last measured · 21 Jul 2026 Wave · Q2-2026-W11-CENSUS Tier · proprietary Confidence · C Brand ![SAP](/logos/dax40/sap.svg) SAP SE Agent success ## SAP owns the S/4HANA story. Bottleneck Interception Intercepted before the brand is the answer. 3.1 /10 Agent Success Score AI Visibility 29 / 100 Found & recommended by AI agents AI Usability 26 / 100 Can an agent use the surface to get the job done Coverage · 2 of 6 lanes measured Commerce lane · Quote-only · Wave Q2-2026-W11-CENSUS Commerce 3.1 Talent usability measured After-sales — Procurement — Investor — Press — 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. The test ## 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 fleet phases ran in July 2026: every no-JS agent class is blocked at the network edge, the browser class passes and reaches the demo-request form. 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: Plain reader reads your raw page text, no browser Blocked Search assistant finds you through search Partial Coding agent a script hitting your site Blocked Computer-use agent clicks and types like a person Succeeded Autonomous operator runs the whole task unattended Not yet run Blocked somewhere on the path: Plain reader, Coding agent. A customer whose assistant runs on one of those breeds never finishes the task. Commerce lane ## Found, and able to transact? Two questions, measured separately. A brand can be recommended and still un-buyable, or perfectly buyable and never found. AI Visibility When someone asks an agent to choose a cloud ERP platform, does it route to SAP? 29 / 100 SAP comes up about a quarter of the time. The rest of the time, an agent recommends an alternative first. Discoverability · 18-datapoint audit AI Usability Once an agent is on SAP's site, can it request a demo or quote? 26 / 100 Computer-use agent reach a quote; the other agent classes do not. Browser-class agents reach a quote; text / code agents are blocked, no path past the quote was tested · breakdown above 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. Talent lane ## 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. AI Usability · Talent lane ### 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 58 AI Usability / 100 · derived, not hand-rated Plain reader fetches the posting page raw, no browser pass Plain curl (standard browser UA, single request, no retry needed) against the jobs.sap.com posting-detail URL returned HTTP 200, 107700 bytes. Full job title, "What you will bring" (requirements), "What you will do" and Coding agent parses the posting into structured fields pass No JobPosting JSON-LD ("application/ld+json") present on this page — zero such blocks in the response. Spec was instead extracted via schema.org Microdata (itemscope/itemprop attributes: itemtype "http://schema.org/JobPo Computer-use agent clicks through the career portal like a person untested 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's next ## What this means for SAP. Diagnosis 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 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. What proof looks like 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. Audit · €1,900 ### 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 audit](mailto:hello@hyperize.ai?subject=Audit%20%C2%B7%20SAP) Founding · €4,500 ### Found with us. Strategic partnership for brands building agent success as a long-term capability, not a one-off engagement. [Apply](mailto:hello@hyperize.ai?subject=Founding%20Program%20%C2%B7%20SAP) Snapshot ### Audit 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 Snapshot](mailto:hello@hyperize.ai?subject=Snapshot%20%C2%B7%20adjacent%20property%20for%20SAP) This 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. ✓ **Measured, not guessed.** Real agents against your real site, no questionnaire. ✓ **Publicly comparable.** Your score in the same grid as the measured DAX 40 brands. ✓ **Next wave closing.** Start now to be in the next index round. Channel position ## 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. 30% direct 70% via intermediary Intermediaries Accenture · Deloitte · Capgemini · PwC Frozen task slate ## 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 visibility measurement plus in-session usability phases (2026-07-21). 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 derived from the in-session fleet phases (text + code + browser) run 2026-07-21 against the frozen task; observed close state quote\_ready. Pending agent classes (browser/ACT where noted) are excluded from the derivation (usability-derivation/v1.2). Fairness Review pending the sector fairness grid. Methodology ## 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\]](#sources) AI Usability is derived from the access-profile above (usability-derivation/v1.2): 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\]](#sources) Formula 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. History ## Measurement timeline. Each wave appends; nothing overwrites. Frozen Wave Rule. 1. Entry · 01 28 May 2026 Wave · Protocol WAVE-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. 2. Entry · 02 21 Jul 2026 Wave · Protocol USAB-INSESSION-2026-07-21 ars-methodology/v1.1 In-session fleet phases (text, code, browser) run on the frozen S/4HANA Cloud task. Text + code: fully edge-blocked (Akamai 403 on every page for plain-HTTP clients, including robots.txt-allowed bot UAs; policy and enforcement inconsistent). Browser: passes, product surface renders, request-a-demo lead form reached with real fields, reCAPTCHA at submission. Note: the task-era URL /products/erp/s4hana-cloud.html now 404s (offering renamed SAP Cloud ERP; GROW = mid-market tier). Observed close: quote\_ready. Usability now derived from the measured profile (usability-derivation/v1.2). Sources ## Evidence and provenance. Public methodology references and internal evidence pointers behind every claim above. 1. \[S1\] AI Visibility audit · SAP Wave Q2 2026 (dispatched 2026-05-28) Accessed · 28 May 2026 Internal · Hyperize evidence - · AI Visibility score - · the close state reached (quote\_ready) 2. \[S2\] In-session fleet phases · sap text + code + browser (2026-07-21) Accessed · 21 Jul 2026 Internal · Hyperize evidence - · the per-class access profile - · the close state observed (quote\_ready) 3. \[S3\] [Task Selection Doctrine](https://hyperize.ai/en/methodology/task-selection) Accessed · 28 May 2026 Public · hyperize.ai - · fairness declaration - · Third-Party Interception framing Related ## Read the doctrine. Challenge the score. Extend the slate. [Methodology ### Task Selection. The fairness doctrine behind the slate above. Five failure modes, six criteria, public before each wave. Read](/en/methodology/task-selection) [Challenge ### Disagree with this score. Send evidence under public Fairness Review. Failed reviews are documented with the named failure mode. Challenge](mailto:hello@hyperize.ai?subject=DAX%2040%20Pilot%20%E2%80%94%20SAP%20Reference%20Page%20Challenge) [Extend ### Submit your own task. Open Surface Run · additive measurement. The Hyperize-selected slate stays frozen; your task gets the same methodology. Submit](mailto:hello@hyperize.ai?subject=Open%20Surface%20Run%20%E2%80%94%20SAP) Last updated · 21 Jul 2026 Next review · 30 Sept 2026 Wave · Q2-2026-W11-CENSUS Tier · proprietary Confidence · C Index score · 3.1/10 [Machine-readable record](https://www.hyperize.ai/en/dax40-index/brands/sap.json) Universe: DAX 40 composition as of 2026-07-01, reviewed after each Deutsche Boerse index review. Editorial 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](mailto:hello@hyperize.ai). Responses received are published in full alongside the findings. Full methodology and editorial-coverage notice: [coverage statement](/en/imprint#dax40-disclaimer). --- Canonical: https://www.hyperize.ai/en/dax40-index/brands/sap Machine-readable index: https://www.hyperize.ai/llms.txt