S/4HANA migrations, module development, BPR and PMO. We work as a subcontractor alongside an existing consulting team, or we take full responsibility for the project. specialized partner network for enterprise pace.
Business context
Typical situations where it's worth talking to us. If more than one rings a bell, we can probably help.
Operations now strain the spreadsheet templates. Manual data sync eats several hours weekly, and every transfer is a potential error. A structured ERP module or SAP integration removes this.
Multiple parallel systems: SAP, webshop, CRM, warehouse. Each thinks in a different data format. REST, OData or message-bus integration connects them so a data point is created in one place.
A large rollout where scope slips along with the weeks. We work in short sprints with measurable partial deliverables: every phase has a demo and a documented handover.
One person knows how the customizing works — and when they leave, the knowledge leaves with them. Every shipment includes functional and technical docs, code comments and a handover protocol.
Deliverables
Concrete deliverables, not abstract capabilities. Documentation and handover included with every shipment.
S/4HANA on-premise and cloud projects, FI/CO/MM/SD modules through to industry-specific customizing. OData, REST and SOAP interfaces. Phased migration from ECC to S/4HANA.
Custom ABAP reports, BAdI, BAPI, user exits, RFC modules. Review and modernization of existing customizing code base. Testable code with coverage reports.
Business Process Reengineering: assess, propose, prototype, measure. As PMO: project ownership, deadline tracking, stakeholder communication, risk register.
Functional spec for the client, technical spec for developers, ops manual for IT. Confluence or Notion. Release notes per release. Readable six months later.
Key user training, end user manual, video walkthrough. Handover protocol with checklist. 30-day hyper-care after go-live with documented incident handling.
Output
Go-live is not the end, it's a handover. You receive every artifact below, and your team can work with all of them.
Process-level description for every customizing item, with screenshots and a use case matrix. The business side understands what they're getting.
Data model, interface descriptions, security review, performance calculations. Your IT team can take over support afterwards.
Git-based version control (Bitbucket or GitLab), code review history, commented code. Full source handed over at the end.
ABAP Unit tests, integration tests, UAT case descriptions. Regression tests can be re-run any time.
Key user manual, end user workflow guide, video walkthrough for the most common operations. Onboard new joiners in a day.
Step-by-step cutover plan, rollback procedure, monitoring and incident handling protocol. Go-live is not improvised.
Architecture diagrams, ADRs, known-issues list, escalation paths. The partner team can pick it up six months later.
Process
Six steps from discovery to support. The domain-specific content is tailored per project type.
Business process audit (BPR), system integration assessment, stakeholder interviews, current systems mapping.
Functional specification, technical documentation, interface design, data model, security review.
ABAP / Java / Spring Boot, interface development (REST / OData / SOAP), code review, documentation.
Unit test, integration test, UAT (User Acceptance Test), load test, security audit.
User training, parallel testing, gradual go-live, fallback plan, cutover documentation.
Incident management, performance monitoring, documentation upkeep, 3rd line developer support.
Architecture
Typical integration architecture: the ERP is the master, data connections run on documented interfaces. No direct DB access from downstream systems.
External systems
Integration layer
Core
Data
The center of the solution is SAP S/4HANA, where business data is created and process control lives. Every external system (webshop, customer portal, mobile app, 3rd-party SaaS) talks to it via the integration layer.
The integration layer exposes REST, OData or message-bus connections. Downstream systems remain independent of internal ERP changes, and can be replaced without touching SAP customizing.
Stack
Proven, documented tools. When the project justifies it we deviate — but we always explain why.
Integrations
Typical, documented integration partners. For a new integration, we start from the interface specification.
Timeline
A medium-sized integration project runs 12–16 weeks. Larger S/4HANA implementations are months or longer, in which case discovery alone takes 4–6 weeks.
Process audit, interface mapping, scope finalization.
Functional and technical spec, security review, sign-off.
ABAP development, integration work, bi-weekly reviews.
ABAP Unit, integration tests, key user UAT, bug fixing.
Cutover execution, 30-day hyper-care, documented support handover.
Limits
It's more honest to clarify upfront. Some kinds of work we intentionally don't take on — either it's not our profile, or we can't ship it at the quality we'd put our name on.
We do implementation and integration. License procurement and commercial negotiation belong to direct SAP or SAP Partner channels.
On-prem or SAP-cloud hosting isn't our profile. We can recommend trusted partners, but we don't run the infrastructure.
For 'SAP Best Practices' standard scope, large SAP Partners are cheaper. We're strong in customizing and integration complexity.
We don't work on SAP IS-U (utility) or SAP IS-Banking modules. They require dedicated expertise we won't pretend to have.
First week
The goal of the first week: concrete scope, stakeholder map, and a roadmap that isn't an empty promise.
Monday
60–90 minutes, stakeholder intros, high-level scope. Onboarding pack handed over.
Tuesday
Business side, IT, key users identified. First version of the risk register.
Wednesday
SAP system versions, customizing inventory, interface catalogue recorded.
Thursday
Typical solution direction sketched, alternatives mapped, rough cost estimate.
Friday
A concrete 12–16 week outline, decision points, scope refinement, next steps.
Pricing
Three engagement models. Each one comes with a precise scope after discovery — concrete numbers follow once we've seen the project.
After discovery we set a precise scope, fixed price and fixed deadline. Change management is formalized (CR process). Transparent for the business, but reacts less elastically to scope shifts.
Ideal when
Well-known scope, audits, ABAP development with clear deliverables.
Sprint-based billing (bi-weekly) with daily or hourly capacity. Flexible: new requirements drop into the next sprint. More project management overhead on the client side.
Ideal when
Longer engagements, ongoing development, customizing evolution where scope can't be frozen.
Monthly fixed capacity (e.g. 40 or 80 hours), priority-based ticket handling, guaranteed response time. Predictable support for existing systems.
Ideal when
Application maintenance, support, post-go-live refinement.
Case studies
Anonymized cases that fit this pillar. Detailed write-ups are prepared from our project logs.
FAQ
Next step
Concrete scope, transparent pricing, documented delivery. The first 30-minute call is free, and after NDA we share concrete numbers.