Start a pilot
Pilot AI in your SAP system in four weeks
5–10 named users, read-only, on the questions they already ask SAP every week. Measured against targets you agree up front. Go, extend or stop at week 4.
Fixed fee
$8,000
Credited in full against whichever licence you choose. If the pilot misses its targets, you stop at week 4 and the fee is the only cost.
Talk to us
Tell us what your team would ask SAP first
We start with a 30-minute live demo on those questions, then scope the pilot with you. The licence decision waits until the week 4 review.
- A real SAP ECC 6 system, not slides
- Your Basis and security questions answered
- With a CGR Senior Engineer
Prefer email? sales@cgrsoft.com
Week by week
CGR does the build. You provide access, users and half an hour a week.
Week 0
KickoffOne hour. Agree the users, their questions and the AI assistant. Name an IT contact and a Basis contact.
Week 1
Build on QACGR deploys the MCP server, registers it with your identity provider, maps each user to their SAP user and sets up a whitelist per role. Basis reviews.
Week 2
Go live, read-onlySwitch to production. Users get a 30-minute walkthrough and start asking.
Week 3
Daily use and tuningA 30-minute weekly check-in. CGR adjusts whitelists and adds the reports users ask for.
Week 4
Review and decisionMeasure against the targets and agree the next step: production, a longer pilot, or stop.
Not yet running CGR SAP Connector? Your Basis team installs it on QA during week 0. It is one SAINT package, installed in hours.
Scope
What’s in, and what’s deliberately not
| Area | In the pilot | Not in the pilot |
|---|---|---|
| Users | 5–10 named users, each signing in with their own company account | Company-wide rollout |
| Access | Read-only: tables and the ALV reports already in use, with saved variants | Creating or changing SAP documents |
| Data | Only objects on each role’s whitelist, inside the user’s own SAP authorizations | Wildcard or administrator access |
| SAP system | Built and tested on QA, then production read-only | Any change to SAP roles or configuration |
| AI assistant | One assistant you already license | Buying or licensing AI tools |
How success is measured
Five targets, checked from SAP’s own log
Exact numbers are agreed at kickoff. At the review, each user also says how long the same answers took before the pilot.
Adoption
70%+
of pilot users ask SAP questions in weeks 2 and 3
Calls per user in the audit log
Accuracy
95%+
of 20 sampled answers match SAP
Each answer checked in SAP GUI
Speed
< 20 s
for most answers
Response times in the audit log
Security
Zero
calls succeed outside a user’s whitelist or SAP authorizations
Deliberate test calls plus Basis review
Traceability
100%
of calls tied to a named user
Basis review of the audit log
Who provides what
A clear split, so nobody waits
CGR
MCP server, deployment, identity and SAP setup, whitelists, training, weekly check-ins, final review
Your IT team
Cloud resources (or CGR’s hosted service), identity provider app approval, network access to SAP
Your Basis team
Connector install if needed, whitelist and audit log review, SAP user mapping
Pilot users
Their questions at kickoff, real use in weeks 2 and 3, feedback at the review
Not included: AI assistant licences and cloud usage in your own tenant. After the pilot, roll out to more users, then add processes that create and change SAP documents one at a time, each with a confirmation step before anything is posted.