A standardised core · in months, not years
We introduce cloud ERP as a pre-configured standard solution, built on SAP Cloud ERP and cut to the processes Swiss mid-sized companies actually need. Not a customising project with an open end, but a solution that runs from day one and is developed further every quarter.
And more than that: in the age of AI the ERP core is the company's anchor of facts. Without it no company-owned language model can answer reliably.
The grown system costs more than replacing it
The typical system landscape of a Swiss mid-sized company grew over twenty years: an ERP core from another era, three to five point solutions beside it, and in between spreadsheets nobody can switch off any more.
Maintenance instead of progress
Every modification made back then has to be retested with every update. The effort of preserving what exists eats the budget for improving it, until nothing moves at all.
Figures nobody trusts
The monthly close takes weeks because figures from several systems are merged by hand. Decisions rest on reports that are already old when they appear.
Knowledge in a few heads
Why a posting works the way it does is known to a handful of people. If they are unavailable, the business stops. The grown system has become a personnel risk.
Standard does not mean compromise
A standardised solution is not a stripped-down system. It is a system whose processes already run in thousands of comparable companies and which therefore stays faster, cheaper and permanently updatable.
| Aspect | Classic ERP project | Standardised cloud solution |
|---|---|---|
| Project start | Months of concept work before anyone sees a system | Pre-configured system with your master data within the first weeks |
| Method | Collect requirements, then bend the system to fit | Show the standard process, allow deviations only with a reason |
| Modifications | Deep in the system core, every update becomes a project | Kept apart from the core, updates run without a regression project |
| Currency | Release changes every few years as a major undertaking | Quarterly innovations without operational standstill |
| Operations | Own servers, own maintenance, own outage risk | Operated by the provider, data region in Europe selectable |
| Rolling out further sites | Every site is a new project | Copy the template, add local specifics, in roughly half the time |
| Data quality | Grown, inconsistent, historically justified | One consistent data model: the precondition for analytics and AI |
What actually changes
An ERP change is not justified by technology but by what runs differently in daily business. We see the following effects regularly in mid-market projects.
| Area | Effect in daily business |
|---|---|
| Sales | Quotations are produced from costed templates instead of spreadsheets. Availability and delivery dates can be committed to during the call. Not «let me check and come back to you». |
| Project delivery | Effort, material and subcontracted work post to the same project. Contribution margin is visible during the project, not only at final invoicing. |
| Manufacturing | Even one-off and engineer-to-order producers work end to end: bill of materials, routing, confirmations and post-costing hang together. |
| Procurement | Demand arises from the order rather than from experience. Stock levels fall without hurting delivery capability. |
| Service | Asset history, warranty and job confirmations in the same system. The service case becomes billable instead of disappearing into goodwill. |
| Finance | Close in days rather than weeks. Postings arise from the process, not from re-entry. VAT, payments and QR-bill according to Swiss requirements. |
| Management | Key figures current, from one source. The discussion turns to the measure rather than to whose figure is right. |
| International units | Further sites adopt the template. Multi-currency, multi-language and local accounting rules are standard, not an extension. |
| IT operations | No server procurement, no weekend maintenance windows, no worry about an operating system reaching end of support. |
| Succession and absence | Processes live in the system instead of in heads. The business stays able to act when a key person is out. |
The ERP core is the anchor of facts for any company-owned language model
A language model can phrase, summarise and infer. But it does not know the contribution margin of order 4711. Only your business system knows that. This gives the ERP core a significance in the AI era that reaches well beyond transaction processing.
What a modern cloud ERP brings to this
The major ERP vendors have built exactly this bridge over the past two years. At SAP the components are called Knowledge Graph: a machine-readable map of business objects and their relationships, Business Data Cloud for bringing in further data sources, and the assistance and agent layer above them that makes both usable inside the process.
For you this means: choose a current, close-to-standard ERP core today and you get AI readiness as part of the platform, instead of having to retrofit it expensively later. Stay on a heavily modified legacy system and you have to build that layer yourself, again for every extension.
This is where the circle closes with our knowledge approach: the ERP core supplies the structured side, the knowledge layer the unstructured one. Both belong in the same architecture.
Solution 01, Corporate knowledge management →Why the standard counts twice here
- One consistent data model
- A model can only interpret what is named. Standard fields have a defined meaning, home-built extra fields do not.
- Permissions take effect
- The assistant answers within the rights of the person asking. That requires a clean role concept in the core.
- Currency without effort
- New AI capabilities arrive with the quarterly updates. No migration project.
- Traceability
- Every answer can be traced back to the document it came from. Without that, AI cannot be used in accounting.
What belongs to it here
An international standard solution only becomes operable through local requirements. These are known and well practised. They are not a project risk if planned in from the start.
Payments
QR-bill and the international payment standard in both directions, bank connectivity, dunning according to local practice.
Value added tax
Swiss rates, acquisition tax and net tax rates properly represented, returns produced from the system.
Payroll and HR
Connection to a locally certified payroll solution instead of rebuilding it, including clean posting into accounting.
Multi-language
Operation and documents in German, French, Italian and English, without extra development.
Data handling
Operation in European data centres with a contractually agreed region: a topic that comes up in every steering committee.
Industry practice
Engineer-to-order, plant construction, trade, mountain railways, energy: the standard is applied to the industry's processes, not the other way round.
You see the system before you decide
We do not sell selection projects. After the first conversation and the on-site assessment we show a concrete solution, with your processes and a quotation.
On-site assessment
We walk through your core processes and record where the standard fits and where there are justified specifics. The result: the scope and a reliable frame for effort and timing.
Running prototype
A pre-configured system with your master data and your document types. Your own people work with it: change requests arise against a running system, not against a concept paper.
Implementation and operation
Data migration, training, go-live and a supported first closing period. Afterwards support in regular operation, including the quarterly innovations.
International roll-outs to further sites then build on the established template, in our experience in roughly half the time of the initial implementation.
Will your core carry the next ten years?
In a first conversation we look at your landscape and say honestly whether a change pays off or whether there are cheaper levers.
Get in touch → All solutions