Insights — Architecture
Custom or off-the-shelf? The right answer is never ideological.
Off-the-shelf software starts faster and carries less risk. Custom software fits your business exactly and belongs to you. Between the two, the real question is five-year total cost — and what you want to be able to change without depending on anyone.
01 — The problem
People compare a monthly subscription with a development quote. That comparison is what costs money.
A subscription at €40 per user for twenty people is nearly €10,000 a year, or €48,000 over five years, before add-on modules, integration and the initial data migration. A custom build quoted at €60,000 looks twice as expensive — until you count process adaptations, extra licences and the daily cost of working around the tool.
So the question is not “what is the price?”, but “what produces the lowest total cost, including the cost of what your teams do outside the tool?”.
01Five questions that genuinely decide
We always ask management the same questions before advising. They avoid opinion debates and bring the decision back to measurable facts.
- Is your process a competitive advantage, or a commodity everyone performs the same way?
- How many adaptations of the way you work does the off-the-shelf tool demand, and at what cost?
- What happens if you want to change supplier in three years: who holds your data, and in what format?
- What is the real cost of today's workarounds — spreadsheets, re-keying, double entry?
- How fast do you need to move, and what risk will you accept to get there?
02Off-the-shelf often wins, and we say so
For accounting, payroll, email or standard document management, off-the-shelf software is almost always the right choice: regulation imposes the same rules on everyone, and a specialised vendor maintains its product better than a small team could.
We state that plainly to our clients, even when it does not suit us commercially. Our value is not selling development: it is placing engineering effort where it makes a difference.
03Custom wins when the business is the value
A specialised ERP or CRM becomes relevant as soon as the way you work is an advantage: an unusual production logic, a complex billing model, planning where your margin is decided.
In that case the decisive argument is not aesthetic. Software aligned with the business removes re-keying, makes indicators reliable and cuts processing time — that is measurable, and it is what we commit to measuring.
04Whatever you choose: stay reversible
The worst outcome is neither custom nor off-the-shelf: it is lock-in. So we apply three rules to every project, whatever solution is chosen.
Your data stays recoverable in an open, documented format; the source code and access rights belong to you; and reversibility is designed from the start, not negotiated when you leave.
- Full, documented and tested data export
- Source code, repositories and access handed to the client
- Architecture documentation delivered at every stage
- A handover plan written into the contract
02 — An honest comparison
What changes in practice, not in the brochures
| Before | With Zorglon |
|---|---|
| A subscription whose price rises with every added module | A scope built once, with a known running cost |
| Teams adapting their work to the tool | A tool that follows the real process, including its exceptions |
| Data held by the vendor, exported at their convenience | Data held by you, in an open and documented format |
| An evolution to request, then to wait for | An evolution planned, costed and delivered in stages |
03 — Common questions
The objections we hear most
Is custom development not riskier?
The risk is real, but it falls under three conditions: a scope delivered in stages rather than one large project, reuse of the existing system measured before writing code, and regular decision points where you can stop. A project shipping one useful brick in six weeks is less risky than a poorly fitting five-year subscription.
What if you disappear?
That is why we deliver the source code, the repositories, the architecture documentation and the operating procedures. A third party must be able to take over the system without us. That requirement is written into the contract, not left to goodwill.
How long before the first useful brick?
Thirty to forty-five days for a pilot in limited production, when the scope is clear and the business rules are available. We deliver first what replaces a measurable pain, then we extend.
Still undecided between the two?
Thirty minutes are enough to frame the problem and tell you, honestly, whether off-the-shelf software does the job or whether custom development is justified.