Own your business logic
AI makes made-to-measure affordable. Why should you fit the vendor, when the system could fit you? Freedom is built in two stages, and you can stop after the first.
Who this is for
You are buying freedom and optionality, not a cheaper project. This path suits companies that:
- run processes that differ from the vendor's standard in ways that matter competitively, and are tired of paying to bend them back;
- want to stop scheduling a forced upgrade every two years;
- want systems that learn from how the business runs and suggest better ways of working. S/4HANA is a transactional system; it does not do that;
- want their business rules written down, owned and portable, instead of living in custom code, tables, spreadsheets and people's heads.
We never decompile, reverse-engineer or copy any vendor's software. Freedom rebuilds your rules from your data, configuration, documents, observed process behavior and interviews with your people.
Two stages
Freedom: core
Keep S/4HANA as the ledger and system of record, for regulatory and audit reasons. Move everything around it into agents and services you own, connected through APIs: order-to-cash workflows, collections, approvals, reporting and planning. This is where most customization and effort live.
Illustration, not a client result: a collections team of 30 clerks working through dunning, disputes and promise-to-pay follow-ups could shrink to two people supervising agents that do the chasing, drafting and reconciliation. Those two handle the exceptions and the relationships. The other 28 move to work that needs them.
Freedom: full
Own the whole system, built from your rules, data, documents and observed process behavior. It is your IP. There are no forced upgrades, and no one else's release calendar. The system can learn: it notices where cases stall, where exceptions cluster, and proposes changes for your people to approve.
The ledger moves last, only after the periphery has run in parallel long enough to earn trust.
What agents do, and what people do
Agent shares are model assumptions, by hours of work. assumption
| Workstream | Agents | People | Agent share of hours |
|---|---|---|---|
| Rule capture | Extract rules and mappings from configuration, code, documents, transaction history and logs | Process owners confirm, correct and rank; senior SAP experts judge what is intent and what is accident | high |
| Build | Generate services, workflows and APIs from the rule model, with tests | Agentic engineers design architecture and review | 90% (code) |
| Data migration | Mapping, loading, reconciliation | Finance signs off balances | 80% |
| Testing and parallel run | Generate scenarios; compare old and new outputs daily | Resolve differences; approve cutover per slice | 85% |
| Change management | Role guides, support | Lead; train; redesign jobs | 55% |
| Cutover | Runbooks, monitoring | Run each slice; decide go/no-go | 45% |
How it runs
Assessment (8 weeks for a large estate)
Build the semantic model of how the business runs. Pick the first slice and show a working prototype against your own data.
First slice, built beside SAP
For example, collections or approvals. Agents and services run in parallel with the existing process; outputs are compared every day.
Cut over slice by slice
A slice goes live only when the parallel run holds. Each step can be reversed, and the old path stays available until you retire it.
Stop, or continue to full
After core you have a complete working system around SAP. You can stay there. If you continue, planning, reporting and finance processes follow, and the ledger moves last.
Hypercare and learning loop
Agents monitor outcomes and propose improvements; people approve them.
What it looks like at scale
Example: a company with $5–20B in revenue, moderate customization. Planning estimates, not quotes. assumption
| Delivery model | Core: cost | Core: calendar | Full: cost | Full: calendar |
|---|---|---|---|---|
| Traditional SI, hourly | $48M | 35 mo | $72M | 42 mo |
| Our small team, without agents | $44.3M | 42 mo | $66.5M | 49 mo |
| Our small team, with agents | $23.6M | 17 mo | $35.5M | 20 mo |
| Team size with agents | 20 | 26 | ||
Without agents, the same team would take 42 mo for core and 49 mo for full, longer than the traditional SI. Agents are what make this path possible with a small team.
What you pay, and when it pays back
Freedom: core
Freedom: full
Be clear about the economics. One-time, Freedom costs more than the current path. The case rests on the 5-year view, which counts the SAP run cost you stop paying. We assume today's run cost is about $10M a year (an assumption), falling to $6.4M after core and $3.5M after full. If your run cost is lower, the payback is slower; the estimator lets you change it. Beyond the numbers, you are buying optionality.
Cutting run cost during the transition. Since 10 July 2026, SAP's on-premise maintenance commitments let customers split a landscape into separate commercial installations and choose a different support model or provider for each.1 That helps on the parts you keep: put what is retiring first on lower-cost support. Third-party support is one route; one provider claims up to 50% off SAP annual support fees, and Gartner's market page says savings of about 50% are typical.2 Both are vendor or analyst claims, and they are not in our model. Check what applies to your contract.
The board's questions
Boards are right to be cautious about replacing a ledger. The structure of this path is the answer.
Staged
Slices, not a big bang. Core is a complete stopping point.
Parallel run
Old and new run side by side; differences are compared daily and must close.
Ledger last
The system of record is the final thing to move, if it moves at all.
Reversible
Each step can be rolled back until you retire the old path.
Risks on this path, and how we handle them
| Risk | What we do |
|---|---|
| Rules captured wrongly, including accidental behavior mistaken for intent | Evidence links on every rule; process owners confirm; parallel run exposes differences before cutover. |
| Audit and regulatory concerns | Core keeps SAP as the ledger. Controls are mapped explicitly and reviewed by finance and audit. |
| You depend on us for what you now own | Rules, code and documentation are yours. We hand over runbooks and train your engineers. |
| Systems that learn may drift | Suggestions are proposals; people approve changes. Model and prompt versions are frozen around period-end. |
| Higher cost and a longer program than the current path | Shown above. Fixed fee at cost after assessment; success fee only on acceptance; start with core and stop if the case does not hold. |
| Estimates are wrong | All figures are planning estimates. The assessment replaces them with a quote. |
Sources
- SAP Support Portal. On-premise maintenance and support (commitments effective 10 July 2026, EU case AT.40823).
- Rimini Street. Support for SAP ECC 6 and S/4HANA through 2040 (vendor claim); Gartner. Independent third-party software support.