Know how SAP S/4HANA transformations are solutioned, accelerated and supported
For CIOs, programme sponsors and service-line heads deciding how to run an S/4HANA move and what to expect in operational support afterwards.
- Engagement type
- Team Pod
- Experts
- 2 delivery · 1 advisor
- Hours
- ~70
- Duration
- 4 weeks
What the client needed
A firm needed two things on SAP: how providers currently solution S/4HANA transformations — approaches, accelerators and what differentiates them — and how operational support differs between the private and public cloud editions: deployment and infrastructure responsibilities, the effort behind licence management and audit support, the advisory layer in cloud-standard operations, and how average effort per ticket varies by vertical for similar maintenance deals.
The brief
The questions on the table
As the client wrote them, lightly shortened. Client and respondents are not named.
- Q1
Which solutioning approaches are prevalent for S/4HANA transformations, and what do accelerators change?
- Q2
How do providers differentiate, and what are the common use cases?
- Q3
What differs between private and public cloud editions in deployment, infrastructure and licence-management effort?
- Q4
How does average effort per ticket vary across verticals for similar S/4HANA maintenance deals?
The hours
What the work involved
- 01
Transformation approaches
Greenfield, brownfield and selective transition as providers actually propose them, with the accelerators that move effort and the ones that are mostly marketing.
- 02
Provider differentiation
How the big SAP practices position, price and staff, from the delivery partner who ran one.
- 03
Cloud editions
Private versus public cloud: responsibilities, licence administration and audit support effort, and the advisory layer cloud-standard operations need.
- 04
Support benchmarks
Average effort per ticket by vertical from comparable maintenance deals, with the factors behind the spread.
- 05
Working session
With the client’s SAP programme office; the senior advisor reviewed the benchmarks and the approach recommendation.
Deliverables
What the client received
- Approach and accelerator noteWhat changes effort.
- Differentiation mapBy provider type.
- Cloud-edition comparisonDeployment, licence, advisory.
- Support benchmarksEffort per ticket by vertical.
- One working sessionWith notes.
The terms
What an engagement like this costs
You buy hours in blocks and can change the expert at the end of any block, at no extra cost. Longer projects run in stages: pause after a block, pick up the next stage when you are ready.
- Rate band
- $65–$250 /hr
- Senior specialists can be up to $500
- Hour blocks
- 1 · 2 · 5 · 10 · 20 · 50 · custom
- This engagement
- Team Pod · ~70 hours · 4 weeks
More in IT services
Planning an S/4HANA move?
Describe what you needFor example: “We are choosing between RISE private cloud and public cloud and need the support and licence effort compared.”
We aim to come back with matched experts within 24 to 72 hours.