Every ERP vendor shows a demo that fits. In a demo, everything fits. It only goes wrong once your own workflow deviates from what the package expects, and it does deviate, because that very way of working is what sets you apart. From that point you have two choices: adapt your business to the software, or build custom work on top of a package that wasn't made for it.
It's not the vendor, it's the architecture
It's tempting to think you simply picked the wrong party. But the problem is rarely the vendor; it's in the setup. A standard package is built around assumptions about how a business works. If your process deviates from those, you're asking the system to be something it isn't. Every custom layer you add fights against those assumptions instead of moving with them.
More than a quarter
of organizations exceed their project budget on an ERP implementation, according to the annual ERP report by Panorama Consulting (2026). A good part of that overrun sits precisely in papering over the gap between the standard package and your own way of working.
The setup that does work
There is one arrangement that does hold up in practice. Keep your financial administration, general ledger, VAT and payments, in a proven accounting package, because that's what such a package is good at. And build the rest, your own operation, custom around it, on a foundation made for custom work. That way each part does what it's good at, without you bending your process or fighting a standard package.
Custom work without the classic downsides
Custom work has a bad name: expensive, slow, and dependent on a developer for every change. That's because it's usually built on top of a standard package. On a foundation designed for custom work from the ground up, those downsides largely disappear: business rules, phases and labels you set yourself, and the system grows with your process instead of blocking it.
That's exactly the thinking behind Ralect One: you keep the finances in a proven package, and the operation around it, from request and quote to project, service and planning, runs in one system built around your way of working. Pipeline phases, project phases, presets and business rules you manage yourself, without a developer needed for every change.
So the question isn't which standard package comes closest to your process. The question is whether you want to adapt your process to software, or software that adapts to your process. For a business that distinguishes itself precisely through its way of working, that isn't a detail, it's the whole point.
