Cost to Build an App Like Revolut in 2026 (Real Numbers)
Last updated: 16 May 2026Clone target: RevolutData source: MyAppTemplates.com analysis of 2026 public SOW benchmarks and shipped-app case studies
Executive Summary
Revolut is the rare category on this site where the software is not the dominant cost. Building the app — accounts, cards, transfers, FX, budgeting, push notifications — is a sizeable but bounded engineering project. Everything around it — the EMI or banking licence, regulatory capital, card scheme membership, SEPA/SWIFT access, PCI DSS, KYC/AML vendors, ongoing compliance staff — is where the real money goes. A serious launch sits in the $2M–$8M range before customer acquisition, and most of that is not engineering.
The table below ranks software-scope variants only. Mid-market fintech specialist agencies typically quote $250k–$900k for the engineering portion depending on rails, regions, and feature breadth. This is not a DIY category. The MyAppTemplates boilerplate at $199 can get you a working prototype, internal demo, or investor pitch app in days — but it does not, and cannot, replace BaFin/FCA authorisation, an issuer processor like Marqeta, a KYC provider like Onfido, or a CISO.
Read this page as a scoping document: what the software actually costs, what the regulated surrounds cost, and where the boilerplate is honestly useful (prototypes, ops tooling, internal admin) versus where it is not (production money movement).
Data
Revolut-style neobank — software scope variants
Software engineering cost only. Licensing, capital, KYC, card rails, and compliance are quoted separately below.
Every DIY build starts with the same flat boilerplate fee:$199 one-time — but this is a regulated category. Treat DIY as prototype-only, not production.
#
Scope variant
Type
Agency Quote (software only)
+ AI Spend (prototype)
Status
Build Time
1
Investor-pitch prototypeOnboarding, fake balance, mock card, mock transfer animations. No real money.
Prototype
$40k–$80k
$180–$280
Prototype only
1–2 weeks
2
Closed-beta wallet (single currency)Real KYC via Onfido, real ledger, BaaS-issued virtual card via Treasury Prime / Solaris, GBP only.
BaaS-backed
$250k–$420k
Not a DIY category
Regulated
4–6 months
3
Multi-currency wallet + FXGBP/EUR/USD accounts, interbank FX with markup, SEPA in/out, virtual + physical cards.
Crypto + stocks add-on layerCustodial crypto via Fireblocks/BitGo, fractional shares via DriveWealth/Alpaca, tax-lot reporting.
BaaS + brokerage
$350k–$550k (add-on)
Not a DIY category
Regulated
+4–6 months
6
Business / SMB accountsMulti-user company accounts, expense cards, accounting integrations (Xero/QuickBooks), approval flows.
BaaS-backed
$400k–$650k
Not a DIY category
Regulated
+5–7 months
7
Own EMI licence + direct railsOwn ledger, direct SEPA/Faster Payments participation, principal card issuer, in-house compliance stack.
Direct-rails
$1.2M–$2.4M (software only)
Not a DIY category
Regulated
18–30 months
1. Where the real money goes (non-software)
The software quotes above are the smallest line on a Revolut-style P&L. Here is the rest of the cost stack — these are not optional for production, and no boilerplate or AI workflow changes them.
Cost stack
Regulatory licensing & capital
UK FCA EMI licence application$150k–$350k legal + advisory9–18 months elapsed
Initial regulatory capital (EMI)€350k minimum, typically €1M–€5M heldLocked, not spent
Full credit institution licence (e.g. Lithuania, where Revolut holds one)€5M minimum capital + ~24 months
Annual compliance staff (MLRO, CISO, risk, ops)$600k–$1.2M/yearFrom year one
The boilerplate is not a path to a regulated neobank. It is genuinely useful in three narrower roles around a fintech build, and we'd rather you understand them clearly than pitch you something it can't do.
Honest fit
Investor pitch prototype
What you buildA flashy mobile app with onboarding, mock balance, mock transfers, faux card. Demonstrates UX, not money movement.
What the boilerplate gives youPhone OTP auth screens, paywall scaffold, tab navigation, theme system, Expo build for iOS and Android from one codebase.
Realistic spend$199 + $180–$280 Claude Code spend1–2 weeks with the @mobile-dev subagent
Honest fit
Internal ops & admin tooling
What you buildInternal dashboards for your compliance team, ops reviewers, support agents — not customer-facing money movement.
What the boilerplate gives youRate-limited Hono routes on Cloudflare Workers, Drizzle schema, JWT auth, modular feature architecture, CI/CD preconfigured.
Realistic spend$199 + $300–$600 Claude Code spend per ops module
Honest fit
Pre-licence waitlist & content app
What you buildWaitlist, referral mechanics, content/education layer, push-style email capture while your licence application is in flight.
What the boilerplate gives youAuth, RevenueCat-ready paywall (if you want paid early-access), Sentry error tracking, profile screens — production-grade shell.
Realistic spend$199 + $150–$300 Claude Code spend
3. Software architecture choices that move the agency quote
Two builds with the same feature list can quote 3x apart depending on these decisions. If you take one thing from this page into your agency RFP, it should be this list.
Decision
BaaS vs. own licence
BaaS pathFaster to market (6–12 months), software ~$400k–$900k, but you pay revenue share and inherit your partner's risk appetite and outages.
Own EMI licenceSlower (18–30 months), software ~$1.2M–$2.4M, plus capital and compliance staff — but unit economics and product control improve materially at scale.
Common patternLaunch on BaaS, migrate to own licence at ~250k–500k active users. Budget for a second, painful migration project.
Decision
Scope of FX & rails at launch
Single currency, single countryLowest quote band. Most failures happen here from trying to skip and launch multi-currency on day one.
Multi-currency + SEPAAdds $150k–$300k of software scope (ledger design, FX engine, reconciliation, statements per currency).
SWIFT + correspondent bankingAdds another tier of complexity. Most BaaS providers wrap this — if you go direct, double the timeline.
How to sequence a Revolut-style build honestly
If you're seriously planning this, here is the order most successful neobanks have actually followed in the last five years.
1
1. Validate with a prototype, not a pitch deck
Two weeks, $199 + Claude Code, with the boilerplate and the @mobile-dev subagent. Mock balances, mock transfers, real onboarding flow. Test it with 50–100 target users before raising or applying for anything.
2
2. Start the licence and BaaS conversations in parallel
Engage a fintech regulatory law firm and shortlist BaaS providers. Both have 3–9 month sales/diligence cycles. Doing them sequentially is the most common reason fintech launches slip by a year.
3
3. Hire MLRO and CISO before engineering hires three through ten
These two hires shape the product. Discovering at month nine that your compliance lead needs a different KYC flow is the most expensive rewrite in fintech.
4
4. Engineer the closed beta on BaaS in one country, one currency
Engage a fintech-specialist agency or build an in-house team. Budget $400k–$700k for software, 6–9 months. Use the boilerplate for the admin/ops surface even if the customer app is built bespoke.
5
5. Plan the second build now
Multi-currency, FX, second market, and eventually own-licence migration are not features — they are second projects. Budget for them in your Series A model, not your seed model.
Frequently Asked Questions
Can I really build a Revolut competitor with $199 and Claude Code?
No. You can build a credible-looking prototype, an internal demo, or a pre-licence waitlist app. You cannot legally move customer money without an EMI or banking licence, KYC/AML infrastructure, card scheme membership, and PCI DSS compliance — none of which are software problems.
What is the absolute minimum to launch something real?
Roughly $1.5M–$3M and 9–14 months: BaaS partner, single market, single currency, KYC vendor, app + admin software, MLRO and one compliance hire, and enough working capital. This gets you a closed beta in one country. Revolut-scale is a different planet.
Why are agency quotes for the software 'only' $400k–$900k when the total cost is millions?
Because licensing, capital, KYC per-transaction fees, card scheme fees, compliance hires, and audits are not engineering line items. A fintech-specialist agency quotes their delivery; you pay the rest separately to lawyers, regulators, BaaS partners, and your own staff.
Does the boilerplate include Stripe Connect or card issuing?
No. The boilerplate ships Stripe and RevenueCat adapters for subscription billing. The billing abstraction can accept a Connect or card-issuing integration as an additional adapter, but you (or your agency) write that integration. For a Revolut-style app you'd be integrating Marqeta, Enfuce, or a BaaS issuer — not Stripe Connect.
What about a 'Revolut for X' niche — same idea, narrower audience?
Same regulatory floor. A niche neobank for freelancers, expats, or a specific industry still needs an EMI licence or a BaaS partner, KYC, and the rest. The niche affects marketing CAC, not the compliance stack. The software scope is often smaller — $250k–$500k agency range — but the non-software stack barely moves.
Where does the boilerplate genuinely fit in a fintech build?
Three places: investor pitch prototypes (1–2 weeks), internal ops and admin tooling around your real banking stack, and pre-launch waitlist/content apps. In all three, the $199 buys you a production-grade React Native + Cloudflare Workers shell with auth, theming, CI, and AI-tooling so Claude Code is productive from day one.
Is fintech a saturated category in 2026?
Mature, not saturated. Wise, Revolut, Monzo, Nubank and Chime occupy the broad consumer slot. New entrants tend to win on vertical specialisation (a specific profession, a specific corridor, a specific demographic) or on bundled adjacent products (tax, accounting, investing). Pure broad-consumer neobank is hard.
Revolut is a regulatory project with an app attached.
The software is a real and significant build — $400k–$900k on BaaS, more on own rails — but it's the smaller half of the launch budget. If you're at the prototype, pitch, or internal-tooling stage, the boilerplate is the right tool. If you're at production money movement, hire a fintech agency and a regulatory law firm before you write a line of code.