Custom Platform or Off-the-Shelf Software: A Decision Framework
Whether to build or buy depends on how much of your process is really different, what you can maintain and what the full cost looks like over five years.

Sooner or later, every growing organisation reaches the same fork. The current tools no longer fit, and the choice is between buying a standard product and adapting to it, or building something designed around the way the business works. Both paths can succeed. Both have produced expensive failures. The difference usually comes down to whether the decision was made on evidence or on enthusiasm.
Start with what is really different about you
Most of what a company does is not unique. Accounting, payroll, purchasing, stock control and basic customer relationship management (CRM) work much the same way across thousands of businesses, and mature products handle them well. Building these yourself rarely makes sense, because you would be paying to reinvent something that already exists and is maintained by someone else.
The case for custom software rests on the parts of your operation that are both different and important. A logistics operator in Aqaba that schedules port collections, customs clearance and trucking in a specific sequence may find that no standard product models that sequence well. A training provider running accredited programmes with unusual attendance and certification rules may hit the same wall. If that difference is part of why customers choose you, software that supports it properly can be worth building.
So the first exercise is to list your core processes and mark each one honestly: standard, or truly distinctive. Most organisations find the distinctive list is shorter than they expected.
It also helps to separate distinctive processes from distinctive habits. An unusual way of approving discounts may simply be a habit that a standard product’s approval rules can handle once it is written down. An unusual way of scheduling technicians across sites, based on certifications and travel time, may be a genuine difference worth supporting properly.
The main options, in practice
Off-the-shelf, configured
You choose a product, such as an ERP (enterprise resource planning) system, a CRM or a sector-specific system, and set it up using its built-in options: fields, workflows, approval rules, reports. You adapt some of your processes to the product. This is usually the fastest and lowest-risk path for standard processes.
Off-the-shelf, extended
You buy a product and add custom modules, integrations or reports for the parts it does not cover. Platforms like Odoo, Microsoft Dynamics and many CRMs are designed for this. The risk is going too far: heavy customisation makes upgrades painful and can leave you with the costs of both buying and building.
Custom platform
You design and build software around your own processes, usually on a modern framework and cloud hosting, often integrated with a standard accounting or ERP system for the common functions. You get exactly what you need, and you take on full responsibility for maintaining, securing and improving it.
A decision framework you can score
Score each option from 1 to 5 against the criteria below, weighted for what matters most to you. The scoring forces a structured conversation; the numbers themselves matter less than the discussion they create.
| Criterion | Question to ask | Tends to favour |
|---|---|---|
| Process fit | How much of our real process does the product support without workarounds? | Buy, if fit is high |
| Differentiation | Is this process part of how we compete? | Build, if yes |
| Time to value | How soon do we need it working? | Buy |
| Five-year cost | Licences, hosting, support, changes and staff time over five years | Depends; calculate both |
| Ability to maintain | Do we have, or can we reliably contract, people to support custom code? | Buy, if no |
| Control and flexibility | How often will this process change, and how fast must the system follow? | Build, if change is frequent |
| Vendor risk | What happens if the vendor or local partner disappears or raises prices? | Depends on vendor and contract |
The costs people forget
Comparisons often set a custom build quote against a licence price and stop there. A fair comparison over five years should include:
- For off-the-shelf: licences or subscriptions for all users, implementation partner fees, customisation, integration, data migration, training, annual support, and the cost of upgrades when customisations need reworking.
- For custom: design and development, hosting, security updates, bug fixing, new features as the business changes, documentation, and the risk cost of depending on a small number of developers who know the code.
- For both: your own staff’s time during the project, the disruption of go-live and the effort of keeping data clean afterwards.
Custom software is not finished when it launches. Budget for ongoing development every year, or the system will slowly stop fitting the business it was built for.
Questions to settle before you decide
- Have we documented our real processes, including exceptions, so we can test products against them?
- Have we seen at least two standard products demonstrated with our own scenarios, not the vendor’s script?
- Who will own the system internally after go-live?
- If we build, who owns the source code, and is it written into the contract?
- If we buy, how many users, modules and integrations will we need in three years, and what will that cost?
- What is the exit path if the choice turns out to be wrong?
The fourth question deserves extra attention. Organisations sometimes commission custom systems without securing ownership of the code or proper documentation, then find themselves unable to change developers. Make ownership, documentation and handover explicit in any development agreement, and have your legal adviser review it.
Making the call with clear eyes
The custom vs off-the-shelf software decision is rarely all or nothing. Many organisations end up with a standard core for finance and operations, plus a focused custom platform for the one or two processes that set them apart, connected by well-designed integrations. That mix keeps costs controlled where processes are common and gives freedom where it counts.
Our Enterprise Systems service supports this decision from requirements analysis and option assessment through to system design, platform development and integration, so the choice rests on documented processes and a five-year cost view rather than on a vendor demonstration.



