Choose your country or region

How it works

We run the project. You run the bank.

Our team takes your bank from first call to launch: connections, design, testing and a careful pilot. The aim is live customers this year.

The programme

Seven steps. None of them a leap of faith.

  1. We learn your products, your customers, your core and every tool around it. Together we agree what launches first.
  2. Modern API or decades-old files. Identity checks, screening and payments too. Our team builds every connection.
  3. Your colours, words, screens and flows – down to components made for your bank alone.
  4. Every connection and flow runs against your test systems. Your team sets the risk policy, limits and approvals.
  5. A small group of real customers first. Your team decides every case.
  6. Open the doors when your team says so. We’re with you through it.
  7. Every product update reaches your app. Need something new? We build it in on request.
Day one

Your first meeting is a demo of your bank.

We set it up with your name and colours before we talk scope. Your team sees the finished thing first.

Who does what

Our team builds. Yours decides.

Our team

  • Maps your core and tools in discovery
  • Builds and tests every connection
  • Designs and builds your app, web and mobile
  • Builds custom components where you need them
  • Runs the sandbox tests and sets up the pilot
  • Ships updates after launch

Your team

  • Tells us how your bank works today
  • Opens access to your test systems
  • Signs off your design and your words
  • Sets your risk policy, limits and approvals
  • Picks the pilot customers and decides every case
  • Says when it’s time to launch
What you bring

Less than you’d fear. Mostly access and decisions.

Access to your core’s test system

A sandbox, an API or a file drop. Whatever your core offers.

Your providers’ details

Identity checks, screening, payments. We connect the contracts you already have.

Your brand and your rules

Logo, colours, tone of voice, and the risk policy you want enforced.

A few people who decide

Someone each from operations, compliance and IT, and a sponsor.
Who does the work

Three phases. Our team on each.

Discovery. Every system, mapped.

Your core, your providers and your rules, listed – then a plan with real dates.

Connection. Built by us.

Your core and providers connected, then tested on your sandbox before anything else.

Launch. Small group first.

A few real customers, decided by your team. Everyone else when you say so.

Timing

Real dates come after discovery. Not from a guess on a website.

Every core and every bank is different. The aim is live customers this year; your plan sets the dates.

A dated plan

Once we know your core and tools, you get a plan with dates.

No core project first

Nothing waits on replacing your core. We connect the one you have.

Launch on your word

Real customers see it when your team decides they should.
For your IT team

Nothing reaches production without sign-off.

Your bank gets its own database and encryption keys. Staff sign in through your SSO. Everything is tested on your sandbox first.

Questions

Questions buyers ask first.

How long does an implementation take?
We aim for live customers this year. You get a dated plan after discovery, once we know your core and your tools.
Our core has no modern API. Can you still connect it?
Yes. We connect through files too – ISO 20022 statements and payment files exchanged over SFTP or S3.
Can we try it before real customers do?
Yes. Everything runs on your sandbox first, then a pilot with a small group of real customers your team picks.
Who looks after the app once we’re live?
We do. Every bank runs on the same product, so updates reach your app without a new project.
Pilot programme

Start with a call, not a contract.

A first conversation, a demo set up as your bank, and a straight answer on what it takes to go live.

  • Your name and colours in the demo
  • Straight answers for risk, compliance and IT
  • No commitment