This is where the fallacy of the out-of-the-box solution begins.
Vendors often showcase reference clients or quote that their platform supports “industry best practice”. What they seldom mention is that many of those organisations still had to spend millions on customisation, change requests, and consultants to make that “standardised solution” behave like their existing process.
The software isn’t the problem — the fit is.
Transformation succeeds when technology enables the process, not when the process is forced to conform to the technology.
To help organisations evaluate this objectively, we use a straightforward framework: a decision matrix based on two variables — the complexity of the process and whether the process is standardised or bespoke.
Case Study
A large European bank under pressure to comply with regulation, specifically BCBS 239, initiates a change project to implement a new system. Unfortunately, the project was spearheaded by people with mostly a finance background. Surprisingly, it didn’t occur to anyone in the room to bring in people who have a strong understanding of applications and how they work.
They have a custom and complex loan process and they decide to go with an out of the box solution. In general, it is never a good idea to try to layer a complex bespoke process on top of a complex standardised application.
For many financial services organisations, the phrase “out-of-the-box solution” has become synonymous with “quick win”, “minimal cost”, and “industry best practice”. Software vendors reinforce this belief by promoting their products as plug-and-play platforms that can solve complex transformation challenges with minimal effort.
It sounds ideal: buy a system that already works, switch it on, and watch your business transform.
Unfortunately, that’s rarely how it works out.
Across banks, insurers, asset managers, and fintechs, we continue to see transformation programmes stall, run over budget, and even fail — not because the software is bad, but because the solution fundamentally doesn’t fit how the organisation operates. The assumption that standardised = better causes teams to shoehorn deeply bespoke, complex processes into rigid systems that were never designed for that level of variation.
The reality is simple:
“If your process is bespoke and complex, an out-of-the-box system won’t liberate you — it will constrain you.”
The Transformation Myth: “Out-of-the-Box Works for Everyone”
Financial services organisations don’t fail in transformation because of a lack of effort or investment. They fail because they make one of the most common assumptions in digital transformation: “Everyone in our industry uses this system… therefore it must work for us.” financial institutions are rarely identical. They have:
- Unique products and pricing models
- Legacy operating structures
- Regulatory requirements across multiple jurisdictions
- Risk and compliance workflows specific to their governance framework
- Even two banks offering similar products can have entirely different internal processes due to local compliance obligations, risk appetite, or historical technology decisions.

1. Standardised + Simple
Solution: Standardised (Simple) — Use off-the-shelf
Example (Financial Services):
Employee travel-expense reimbursement.
- Every company processes expenses.
- The workflow is standard and already optimised in most expense management tools.
- There is no competitive advantage in doing it differently.
Typical tools: Concur, SAP SuccessFactors, Workday Expenses.
Why standardised works:
The organisation adopts the system’s default process with minimal configuration. No custom development required.
2. Standardised + Complex
Solution: Standardised (Advanced) — Use configurable out-of-the-box system
Example (Financial Services):
Regulatory reporting for global frameworks (e.g., BCBS 239, IFRS 9, Basel III liquidity risk reporting).
- Highly complex data models.
- Hundreds of calculations and reporting rules.
- However, the required outputs are defined by regulators, not by the bank individually — meaning the workflow is standardised across the industry.
Typical tools: AxiomSL, Moody’s RiskAuthority, Wolters Kluwer OneSumX.
Why standardised works:
Vendors build solutions specifically for regulatory reporting complexity. Banks should configure, not customise.
3. Bespoke + Simple
Solution: Custom (Lightweight) — Build a small tailored solution
Example (Financial Services):
A niche investment firm’s onboarding workflow for high-net-worth referral partners.
- The process is unique to this firm’s business model.
- The workflow is linear and straightforward.
- Off-the-shelf CRMs can’t model the specific referral logic without heavy workaround or extra licensing.
Possible custom solution: A simple internal web form + workflow approval + database.
Why custom works:
The process is unique but not difficult. A light custom application is cheaper and easier than bending a CRM to fit.
4. Bespoke + Complex
Solution: Custom (Full Custom) — Build to fit the business
Example (Financial Services):
- Commercial lending approval and pricing workflow for structured or syndicated loans.
- Each loan step is different from identification, origination and monitoring.
- Decisions require risk modelling, legal review, covenants, and multiple approval layers.
- Approvers need integration with credit systems, risk systems, and document repositories.
- “Standardised loan origination” software can’t handle the variance and ends up requiring extensive workarounds and change requests.
Typical failed attempt:
Trying to force this into Allvue, Salesforce, Dynamics, or Workday.
Why custom works:
This is the organisation’s competitive advantage — how they price risk and structure deals. Custom enables speed and differentiation.
Summary
| Matrix Category | Financial Services Example | Why It Fits |
| Standardised + Simple | Expense reimbursement | No competitive advantage — adopt default workflow. |
| Standardised + Complex | Basel III / BCBS 239 regulatory reporting | Complex but dictated externally — configure, don’t customise. |
| Bespoke + Simple | High-net-worth referral onboarding workflow | Unique process, but linear — build lightweight custom. |
| Bespoke + Complex | Commercial lending / structured credit origination | Core to competitive advantage — custom is essential. |
Remember, vendors will typically try to push their out of the box standardised solution. The closer you adhere to their out of the box solution the higher will be their profit margins and the quicker they will get paid. Please always ensure you have a resource on the team, ideally a full stack developer, who understands how applications work. Don’t repeat the mistakes of others.