Build vs Buy: Splitting the Decision Instead of Making It
A European SME lending platform (~€900M originated annually) had spent seven months deadlocked between engineering’s €4.8M / 24-month build proposal and the CFO’s vendor renewal. Envion decomposed "the platform" into 31 capabilities and asked one question of each: does a customer ever choose us, or refuse us, because of this? The recommendation: license the servicing core, build the four differentiating capabilities in-house, and own the boundary between them. 5-year TCO came in at €2.8M against €4.8M plus €6.2M of opportunity cost for the full build — and time to launch a new product dropped from 14 months to 6 weeks.
The challenge
The client's loan servicing ran on a licensed core platform they had outgrown. Every product change required a vendor change request: €40–80K, twelve to sixteen weeks. They had launched two products in three years and lost a partnership because they couldn't support a revenue-share structure the vendor's data model didn't accommodate.
Engineering wanted to build a replacement — 24 months and €4.8M. The CFO wanted to renew with a competing vendor. Both sides had been arguing for seven months without resolving anything, because neither had modelled the decision — they had positions.
The CEO engaged Envion for one deliverable: a defensible recommendation the board could act on.
Decision path
The engagement did not begin with cost. It began with decomposing "the platform" into capabilities and asking a single question of each: does a customer ever choose us, or refuse us, because of this?
Envion mapped 31 capabilities across four categories. Differentiating — the product configuration engine, pricing and fee logic, partner revenue-share modelling, and the origination decision flow — where every lost deal and every blocked launch traced back to: four capabilities, roughly 20% of the estimated build. Table stakes, high consequence — the ledger, payment scheduling, arrears handling, regulatory reporting: hard to build correctly, brutally unforgiving when wrong, and identical across every competitor — no customer has ever chosen a lender for its double-entry implementation. Table stakes, low consequence — document generation, notifications, reconciliation exports. Genuinely commodity — auth, storage, comms.
The client's build proposal treated all 31 as one indivisible programme. That was the actual error, and it was invisible until the capabilities were separated.
Envion contribution
Envion assembled the evidence. A real five-year TCO model in both directions — licence escalation against contracted volume growth, change-request spend at historical run rate, the fully loaded cost of the 9-engineer build team including 18–24 months of maintaining both systems in parallel, and the ongoing ~3.5-FTE maintenance floor that build proposals routinely omit.
Opportunity cost, stated explicitly: the build would consume the client's entire senior engineering capacity for two years. Envion listed, by name, the seven roadmap items that would not ship in that window and asked the commercial team to value them. That number — €6.2M in deferred revenue on their own estimates — exceeded the build cost itself and was the single figure that moved the board.
Vendor due diligence, done properly: technical evaluation of three candidate platforms against API surface, data extraction rights, contractual exit terms and — the one nobody had checked — whether each vendor's data model could represent a partner revenue-share structure. Two could not; the client had been about to renew with a competitor sharing the incumbent's exact limitation. And a reversibility test for each option: a build is very difficult to reverse; a licensed platform behind a well-designed abstraction layer is moderately reversible; a licensed platform integrated directly into application code is nearly as irreversible as a build — and worse, because you don't control the roadmap.
Delivery
The recommendation: buy the ledger and servicing core, build the differentiating layer, own the boundary between them. Specifically: license a servicing core selected against the revenue-share test rather than on price — €340K/year, not the cheapest option. Build the four differentiating capabilities in-house as a product layer sitting above the core, owning pricing, product configuration, partner economics and origination decisioning — nine months, four engineers, €1.1M. Mandate an anti-corruption layer between the two, so the core is replaceable without touching the product layer — Envion was explicit that skipping it would recreate the current trap with a different vendor. And negotiate exit terms up front — data extraction format, notice period, transition assistance — while the client still had leverage.
Envion also told them what to stop arguing about: the build-versus-buy debate had been framed as a values conflict between engineering and finance, and it wasn't. Both sides were right about different capabilities.
Outcome and evidence
Twenty-four months on: time to launch a new lending product fell from 14 months to 6 weeks. Cost per product change went from €40–80K plus vendor SLA to an internal sprint. Five products launched in 18 months, after two in three years. Partner revenue-share deals went from zero to three, worth €61M originated. Modelled 5-year TCO: €2.8M total, against €4.8M plus €6.2M opportunity cost for the full build. Engineering headcount required: 4 instead of 9. And the core platform was proven replaceable without a product rewrite — tested in a migration rehearsal.
Decompose before deciding: build the capabilities a customer would choose or refuse you for; buy everything else, even if you could build it better — "better" on a commodity capability is worth nothing. Price the opportunity cost, not just the build. Test the vendor against the specific thing you're stuck on. And ask what reversal costs — the best answer is often the one that's cheapest to undo.
| Metric | Before | After |
|---|---|---|
| Time to launch a new lending product | 14 months | 6 weeks |
| Cost per product change | €40–80K + vendor SLA | Internal sprint |
| Products launched | 2 in 3 years | 5 in 18 months |
| Partner revenue-share deals supported | 0 | 3 (€61M originated) |
| 5-year TCO vs. full build (modelled) | €4.8M + €6.2M opp. cost | €2.8M total |
| Engineering headcount required | 9 | 4 |
| Core platform replaceable without product rewrite | No | Yes (tested in a migration rehearsal) |
Client feedback
What the client says about this engagement
“Seven months of a build-versus-buy argument, and Envion's contribution was to point out we were arguing about the wrong unit. It was never one decision — it was thirty-one, and about four of them mattered. Once you split it that way the answer is nearly obvious, which is annoying, because we'd both been certain and neither of us had done the work.
The line that ended the debate was the opportunity cost slide. Not the build cost — the seven things we'd have to not ship. My CTO stopped defending the build the moment he saw his own team's roadmap on that list.”
Evidence gate. This page publishes only what Envion's project records and client disclosure permissions support. Outcomes are added once verified against a baseline, a measurement period, and an approved source.
FAQ
Questions about this case
Facing a similar challenge?
Stuck in a build-versus-buy argument? Envion decomposes the decision before pricing it — a few weeks of strategy against a multi-million programme is a rounding error.
Discuss a Similar ChallengeKeep exploring
Similar case studies
Executive Technology Leadership
Support for high-stakes product and AI decisions
Bring senior technology leadership into the business when the roadmap is unclear, delivery is at risk, an AI initiative needs stronger ownership, or the company needs an experienced technical voice before hiring a permanent CTO.
Discuss Interim CTO SupportCore responsibilities
- Align product and technology priorities with business goals and measurable outcomes.
- Review architecture, delivery risks, data foundations, security needs, and AI readiness.
- Lead internal teams and external partners through a practical execution plan.
- Clarify team structure, ownership, decision rights, and delivery cadence.
- Support investor, board, partner, and due-diligence conversations with credible technical judgment.
New experience
Prompt-to-Page — try it right here
Describe the landing page you want, in your own words. We turn it into a finished page and email you a private link in 5–10 minutes — no briefs, no calls, $0 to see the result.
- Describe what you want to create.
- We structure, write, and compose the page.
- You receive a private link when it is ready.
Start with a sentence — the interactive builder takes it from there.
Generate My PageSafe, respectful content only. No obligation.