From custom software that truly fit, through standard packages and best-of-breed, back to purpose-built software. Anyone who has seen the whole story recognises the pattern — and understands why the rules are changing now.
Anyone entering the IT sector around 2007 heard on day one that the AS/400 urgently needed replacing. Yet entire companies ran reliably on those systems. That was no accident: the technical constraints of the time forced teams to think ten times before building anything, and everything was written for one specific organisation. Old? Certainly. But stable, considered and fit for purpose.
Old systems had to go, and standard software took their place. The first generation of standard packages offered fairly basic functionality, so substantial customisation was still added to make them fit. It rarely became the best of both worlds.
ERP systems grew into suites containing every conceivable function. But software designed to serve everyone rarely fits anyone properly. Organisations conformed to the standard and quietly compromised on how well their own processes were supported.
The response was predictable: specialist applications appeared alongside the ERP for warehousing, product data, planning and more. A logical idea. But those satellite applications followed the same path: they began focused and grew into cumbersome suites full of functionality that customers only partly use. The result today is an expensive ERP acting as a transaction engine, surrounded by expensive satellite applications with exactly the problem we set out to solve in ERP.
Our conclusion after twenty years: use your ERP for what it does well — as a transaction engine and financial core. Connect the surrounding processes through deliberately simple integrations, including file exchange where that is sufficient. Do not fill those satellite processes with another standard suite; build something lean that supports exactly what your process needs. These excursions can look like a universe of complexity, but a closer look usually reveals something manageable. Take ownership of that software and avoid licence and management costs that do not match a relatively simple process step. In that way, we return to what worked before — considered and tailored — using technology that removes the old overhead.
Those who understand this shift will lead tomorrow.
Calycis comes from the Latin calyx, the heart of a flower: a strong core that carries everything, surrounded by petals, each with its own form.
The ERP is the transaction engine and financial core: proven, stable and authoritative for master data.
Specific processes live in compact satellite applications, custom-built for your organisation.
Interfaces are deliberately simple: file exchange where sufficient, not a fragile integration circus.
Ownership stays with you: no licence fees or management contracts for a relatively simple process step.
The classic arguments against self-managed software are familiar. They were once valid. With the right practices, they no longer have to be.
That is true of undocumented spaghetti code. Our applications follow consistent delivery patterns, a governed data-model approach and fixed security standards. Every application is structured like the previous one and is therefore equally transferable.
That is why we also deliver for self-management: you receive the code, IP and documentation. Our applications are deliberately kept straightforward, so a capable development team can take over without months of onboarding.
Integration is not an afterthought for us; it is a design principle. We use consistent patterns, file-based integration where sufficient, and the ERP always remains authoritative for master data.
That is exactly why we build compactly: one process per application, with a deliberate decoupling point to the core. The temptation to add everything is the trap. Our philosophy is the antidote.
Building your own software without the overhead of the past requires a mature way of working. That is why we captured twenty years of experience in Primordia, our codified delivery method. The same steps and deliverables we would use without AI, now executed at today’s speed.
More about Primordia →Show us a process that is currently holding you back, and we will demonstrate how compact the solution can be.
