Build-vs-buy comes up on almost every first call. The answer turns on a handful of numbers most product leads and CTOs have not actually priced out. This is the model we walk through on those calls. Copy it, argue with it, swap in your own figures. Every euro here is an illustrative assumption, not a quote.

The scenario is a licensed fintech, an EMI, neobank or wallet platform, standing up a programmable-finance surface under its own authorisation: accounts and wallets, money movement across providers and rails, settlement and reconciliation, policy and automation, and the risk and compliance workflows around all of it. Crypto sits in there as one rail, AA wallets, on and off-ramps, stablecoin settlement, alongside the fiat rails and providers that actually clear the money. Target is 100k end-users at year-end, 200k in year two, EU first and then MENA.

Three ways to get there.

Option A: build in-house

You hire a specialist team, wire the underlying providers together yourself, and own the control plane end to end, the accounts layer, the routing, the settlement and reconciliation logic, the policy engine.

Year-one costs (illustrative)

  • Engineering team (loaded cost, EU senior rates):
    • 2 senior backend engineers (payments plus on-chain): €140k/yr each. €280k.
    • 1 senior frontend engineer: €130k. €130k.
    • 1 DevOps / platform engineer: €130k. €130k.
    • 1 engineering manager (part-time, 50%): €170k × 0.5. €85k.
    • Total eng: €625k.
  • Compliance team:
    • 1 compliance engineer with MiCA plus EU TFR experience: €120k. €120k.
    • 1 compliance lead (part-time, 50%): €150k × 0.5. €75k.
    • External EU fintech counsel retainer plus opinions: €60k.
    • Total compliance: €255k.
  • Provider integrations (direct contracts, licensed-fintech tiers, illustrative annual costs):
    • An AA wallet infra vendor (enterprise tier): ~€60k/yr.
    • A ramp aggregator: ~€36k/yr minimum.
    • A Travel Rule provider: ~€40k/yr.
    • An AML screening vendor: ~€90k/yr.
    • EMI / SEPA rails partner (setup plus minimum): ~€30k/yr.
    • A custody provider (only on a custodial path): ~€120k/yr; skip it on a non-custodial design.
    • Total providers: ~€256k (or ~€376k with custody).
  • Infrastructure (cloud, observability, security tooling): €60k.
  • Smart-contract audits (tier-1 firm, one round plus remediation): €80k.
  • Security certifications (SOC 2 Type I program start): €40k.
  • Opportunity cost of eng team not working on the partner's core product: we leave this off the cash model but it's where most internal build decisions actually fail. It belongs on your scorecard.

Year-one total (in-house, non-custodial path, illustrative)

~€1.32M cash, plus ~€625k opportunity cost = effective ~€1.95M.

A custodial path adds roughly €120k. With realistic EU senior-rate variance, the illustrative band lands at ~€1.8M to €2.5M in the first year.

Months to first production feature

Team hired: months 1 to 3. Foundation code (auth, base SDK internals, chain clients, key management): months 3 to 5. First end-to-end flow (an account plus one ramp plus Travel Rule plus the first AML hook): months 5 to 8. Compliance pre-audit and production readiness: months 9 to 12. First real user in production: usually month 10 to 14.

Option B: several specialist vendors, no bundled orchestration

You skip the full build. You integrate the specialist vendors directly but write no custom wallet or routing code. This is the common "we'll glue it together ourselves" pattern, and the orchestration, the policy, settlement and reconciliation that ties the providers into one record, still lands on your team.

Year-one costs (illustrative)

  • Engineering team (smaller, because vendors do the heavy lifting):
    • 1 senior backend engineer (integration lead): €140k.
    • 1 mid backend engineer: €95k.
    • 1 frontend engineer: €100k.
    • Partial DevOps + EM: €60k.
    • Total eng: €395k.
  • Compliance:
    • 1 compliance engineer: €120k.
    • Counsel retainer: €40k (lighter because fewer original opinions needed).
    • Total compliance: €160k.
  • Provider contracts (same list as Option A): ~€256k.
  • Integration overhead (sub-processor paperwork, DPAs, joint security reviews across four or five vendors, annual re-certifications): ~€40k (soft cost, but real).
  • Infrastructure plus observability: ~€45k.
  • Smart-contract audits (for your own wallet contracts, if you deploy any): usually skipped at this tier. €0.

Year-one total (illustrative)

~€896k cash, plus ~€395k opportunity cost = effective ~€1.29M.

With realistic EU senior-rate variance and vendor-tier choices, the illustrative band runs from ~€420k to €780k cash on lower-end tiers up to ~€1.0M to €1.3M with enterprise tiers and a heavier integration team.

Months to first production feature

Integration is shorter than a full build, but the compounding is real. Every vendor brings its own DPA, sub-processor list, sandbox quirks, webhook format and paperwork cycle, and you carry the cross-vendor liability where they meet. Partners on this path usually ship 6 to 9 months after kickoff.

Option C: one control plane

You integrate OVAAL. One contract, one SDK, one compliance pack covering the providers downstream. The accounts layer, routing, settlement, reconciliation and policy come as one orchestration layer; the providers and rails, crypto among them, plug in beneath it.

Year-one costs at a mid scale (around 80k users), illustrative

OVAAL uses a modular commercial model, platform access, the modules you switch on, and a usage / transaction share, and we publish indicative ranges for each part. The figures below sit inside those ranges; they are indicative, not a quote, and final terms are sized per partner.

  • Setup (modules and onboarding): indicative €15k to €45k one-time; mid-scale lands toward the middle of that band.
  • Platform access: indicative €2.5k to €10k per month, tiered by scale.
  • Usage / transaction share: indicative 10% to 25% of OVAAL's take, lower as the access tier rises. You keep the majority.
  • Your integration team (integration is typically a focused engineering burst, not a standing team):
    • 1 senior backend engineer, ~2 months: ~€23k.
    • 1 frontend engineer, ~2 months: ~€17k.
    • Total integration eng: ~€40k.
  • Your compliance review (reading the compliance pack, signing the DPA): ~€15k, roughly two weeks of compliance-lead time.
  • Counsel (reviewing the DPA, not drafting fresh opinions): ~€10k.
  • Infrastructure plus observability (smaller footprint): ~€20k.

Year-one total (illustrative)

Putting indicative platform terms together with your own integration and review effort, year one lands in the low hundreds of thousands of euros rather than the seven figures of a full build, an illustrative ~€200k to €280k cash at this scale, including the integration burst. After integration the marginal cost is platform access plus usage share; there is no standing full-time team dedicated to the orchestration layer. See the indicative ranges for how the parts size up and down by tier.

Months to first production feature

Rollout depends on scope, regulatory responsibilities and provider onboarding, but the design target is weeks rather than quarters from signed paperwork to a first production cohort, with a first small group of real users in month two or three and wider availability in month three or four. We publish honest case retros post-launch rather than promise a fixed number here.

Side-by-side

All figures illustrative. OVAAL's column reflects indicative platform ranges plus your own integration and review effort, not a quote.

                        In-house     Specialists    Control plane
                        (Option A)   (Option B)     (Option C)

Year-1 cash             ~€1.32M      ~€896k         ~€200-280k
+ opportunity cost      ~€625k       ~€395k         ~€40k
= effective cost        ~€1.95M      ~€1.29M        ~€240-320k

Months to first prod    10-14        6-9            weeks (target)
Provider contracts      4-6          4-5            1
Compliance packs        1 (yours)    1 (yours)      1 (ours to yours)
API surfaces to learn   5+           5+             1
Ongoing FT team needed  4-6          2-3            ~0.25 (support)

Where the math changes

Option A wins if:

  • You need capabilities outside any provider's scope: licensed custody, non-EU jurisdictions, unusual chains, or bespoke compliance logic a regulator requires for your specific licence.
  • The money-movement layer itself is your core differentiator and you need to own every line of it.
  • You already have the senior payments-and-on-chain team on payroll and marginal capacity is cheap.

Option B wins if:

  • You need best-in-class depth in one or two slices, an AA wallet vendor's maturity, a ramp aggregator's coverage, a Travel Rule provider's history, more than you need to cut integration count.
  • You already run one or two of these vendors and the marginal integration cost is small.
  • You have the engineering capacity to carry multi-vendor maintenance, and the cross-vendor liability, on an ongoing basis.

Option C wins if:

  • Time to production matters more than maximal depth in any single slice.
  • Your differentiation is in identity, brand and market fit, not in rebuilding accounts, routing, settlement and reconciliation that a control plane already provides.
  • You want one compliance pack to clear, one relationship to maintain, and indicative ranges you can budget against.
  • A non-custodial, provider-neutral design fits your regulatory model under MiCA in the EU or VARA / CBB in MENA.

Assumptions you should stress-test

These are the inputs that move the model most. All of them are illustrative; swap in your own.

  • EU senior eng loaded cost: we used €140k for a senior backend engineer. Real numbers run €110k to €180k across London, Berlin, Amsterdam, Warsaw and Vilnius. Use yours.
  • Provider tier pricing: we used licensed-fintech-tier figures. Startup tiers are cheaper; enterprise tiers above 500k users are materially higher, especially for AML screening and AA wallet infra.
  • Opportunity cost: we counted the full eng-team cost as opportunity. Some teams treat it as zero (spare capacity), others at two or three times salary (real roadmap loss). Your call.
  • Regulatory scope: the Option A and B figures assume EU-only. Adding MENA brings regional counsel (roughly €30k to €60k), regional compliance tooling and extra rail relationships.
  • Year two onward: Options A and B keep carrying the team cost. The control-plane marginal cost drops sharply once integration is done, so the crossover advantage compounds.

The real question

The question isn't really "which option is cheapest." It's "where do you want your engineering team's attention?" If the answer is your own product and market, not rebuilding accounts, routing, settlement and policy that a control plane already runs, Option C tends to pay for itself.

To run the model against your own user count, jurisdictional scope and existing stack, get the integration brief or book an architecture review and we'll size it together on the first call.

For the underlying pieces: the indicative commercial ranges, the six control-plane modules, and the architecture walkthrough behind the integration timeline.