intelligentfood
Three months to go-live: Sales & Service Cloud V2 integrated with S/4HANA Public Cloud.
Read the story →ERP + CX
One transformation, not five projects
One target architecture for ERP, sales, service and commerce. Our team delivers S/4HANA Public Cloud as the core and connects the customer processes through SAP Integration Suite. We plan data preparation, migration and any legacy archive as separate stages, with an owner and acceptance criteria for each.
Request a readiness check →Two generations at their limit
- Business Suite 7: mainstream maintenance to 2027 for the last three enhancement packages; optional extended maintenance to 2030 under SAP’s conditions.
- First-generation cloud CRM that no longer fits the way your team works.
- Service and logistics still managed partly in Excel.
- Duplicate customer and product data across systems.
One move, not five building sites
One shared target architecture aligns ERP, customer processes and integrations. We deliver in phases, each creating value. There is no big bang: existing and new systems run in parallel until the agreed cutover.
The target architecture
Build your transformation
Select your systems and the work you want to improve. Your results update immediately.
Answer both questions to prioritise your selected work packages.
Possible next steps
Select a system to build your brief.
SAP ECC
SAP S/4HANA Public Cloud
Assess a new ERP core. An ECC archive on AWS is optional, subject to retention, access and licence checks.
Questions for the assessment: Which processes, customisations and historical records must the new ERP support?
Legacy CRM
SAP Sales & Service Cloud V2
Assess customer processes and connect sales and service with the ERP through SAP Integration Suite.
Questions for the assessment: Which customer processes and integrations must work at go-live?
Spreadsheets
Governed ERP / CX data
Clean and map the data. Agree who approves each migration rule before loading records.
Questions for the assessment: Who owns data quality, and which spreadsheets hold business-critical records?
Webshop
Existing shop ↔ SAP ERP
Assess retaining and integrating the shop first. Compare SAP Commerce Cloud if replacement is justified.
Questions for the assessment: Can the existing shop support the required pricing, stock and order integrations?
Newsletter tool
SAP Engagement Cloud
Connect consent, audiences and customer events. Start with one measurable campaign before expanding automation.
Questions for the assessment: Where is consent recorded, and which event should trigger the first campaign?
Quotes & product configuration
SAP CPQ
Check configuration rules, prices and approvals. Connect approved quotes to CRM and ERP orders.
Questions for the assessment: Which product rules and discount approvals slow down your quotes?
Field technicians & scheduling
SAP Field Service Management
Connect service orders, skills, availability and spare parts. Equip technicians with mobile job information.
Questions for the assessment: Which dispatch constraints and offline tasks must technicians handle?
Before each implementation: confirm data ownership, interfaces and acceptance criteria. Existing systems can stay in place while dependencies are checked.
Discussion draft, not a validated architecture or quote. The assessment checks fit, scope, licences and data.
A new core, kept clean
SAP S/4HANA Public Cloud starts greenfield with agreed standard processes. Clean Core uses supported configuration, released extensions and SAP BTP.
Start clean, keep the history
We assess an ECC archive, potentially on AWS, separately: access, retention, licensing and operating costs must be agreed before retirement. Clean operational data moves to the new core.
Every channel, one integration hub
Sales and Service Cloud V2, Commerce, CPQ and FSM sit on top of the core. SAP Integration Suite connects them through a shared hub.
Independent subsidiaries, connected group
A Two-Tier ERP satellite pattern lets group subsidiaries operate independently on S/4HANA Public Cloud while staying connected to the group’s central systems.
Think big, start small
Start with Phase 0: data quality, ownership and migration priorities. AI can suggest corrections; the data owner approves them. Or choose a fixed-price readiness check to define architecture, phases and a cost range before committing to implementation.
Request a readiness check →How you stay in control
- You see our Jira, not just our invoices.
- A budget traffic light warns you before things get tight, not afterwards.
- The people in the proposal are the people on the project: no rotation, no juniors in the engine room.
- If something within the agreed scope does not work, we fix it at our expense.
Built and running
Meier Tobler
Integration Suite connects shop, logistics and S/4HANA at Meier Tobler: over one million messages per month.
Read the story →Your questions, answered
What does it cost to start?
Start with Phase 0 data cleansing or a fixed-price readiness check. The readiness check defines phases and a cost range before you commit to the transformation.
Greenfield or brownfield?
SAP S/4HANA Public Cloud starts greenfield with agreed standard processes. Clean Core uses supported configuration, released extensions and SAP BTP.
What happens to the legacy data?
We assess an ECC archive, potentially on AWS, separately: access, retention, licensing and operating costs must be agreed before retirement. Clean operational data moves to the new core.
How long does it take?
Timing depends on scope and the readiness findings. We deliver in phases with parallel operation until cutover. intelligentfood’s Sales & Service platform went live in three months; that is a reference, not a promise for every transformation.
Make the first step concrete
Bring your current landscape. Together we define the entry point, scope and next decision.
Request a readiness check →