Licence route, the provider approvals on the critical path, what is reusable and what is not, and a realistic date. You leave with the sequence either way.
Book the 30-minute call
The decision in 60 seconds
Both routes need the same product underneath. What changes is who holds the licence, and when the regulatory work lands on you.
Route A
As the agent of a licensed firm, or through a BaaS provider. The fastest way to real customers when the partner’s approval process is already moving.
What you build
What the partner carries
Route B
From the CBUAE or SAMA in the Gulf, or the FCA in the UK. More control and no sponsor fees, and from day one a safeguarding, reporting and compliance function that must exist before your first customer does.
What you build
What you carry as well
The code you own is almost the same on both routes. The question is when you want regulatory ownership, and what you can carry before then.
Read the full article (13 min)Who you will be talking to
Finamp is a UK software company, registered in England and Wales. We are not a regulated firm: we never hold funds or provide payment services. You remain the licensed entity, or your partner does.
Co-founder and CEO of Finamp since 2022, based in London. Fifteen years before that as CTO and head of mobile on products for UK companies. He runs the launch route call and stays on the build.
LinkedIn profileCo-founder of Finamp since 2021, based in London, with two earlier technology companies founded and run before it. Leads delivery and the Gulf work, and joins the call when your route runs through the UAE or Saudi Arabia.
LinkedIn profileWhat you will see on the call
Three screens from the back office we build. Real, not mock-ups. The last few minutes of the call are spent in them.
Status, fees, FX and failure reasons, visible to the customer in the app and to your team in the back office, from the same data at the same time. It is the first thing a licensed partner asks to see.
Compliance, operations, support and finance each get their own access level, with every action attributed to a named user. A partner requires it; your own licence requires it more.
Operations reporting and an audit trail that your compliance function, your partner and your auditors can all read from the same record.
The working demo, built around what you are launching, is the second call.
How a build runs here
Each step ends with something you can show your board, and a decision point where you can stop.
Thirty minutes. Your licence route, the provider approvals on the critical path, what is reusable, a realistic date. No charge; you leave with the sequence either way.
Your product, built around what you are launching, running on test data. Its fee is credited in full against the build if you go ahead. If you do not, you keep the designs.
We test the provider APIs end to end and fix the integration design. The build price and date are confirmed only after this, so neither side is guessing.
Fixed scope, dated milestones, fortnightly releases to a test environment your team can use. Compliance and operations are in from the first sprint, not the last.
Planned as their own track. We say where each approval sits on the calendar and what the build can do before it lands.
App-store submission, controlled rollout, on-call support through the first weeks, then a monthly plan. The option to buy the code outright stays open throughout.
Straight answers
You operate on your own licence or under a licensed partner. We build for whichever route you take, and we help you choose it.
A launch date that ignores the provider’s critical path is a guess. You get a date once the approvals are on the calendar.
Real screens on the first call. The working demo is built around your product, not a generic one.
You pay for the build once. A small annual licence fee after launch, nothing per user, nothing per transaction, and no share of your volume.
The price to own the source outright is in the contract from the start, and the source is held in escrow, so you are never negotiating from dependence.
Before you book
Yes. Choosing the route is what the call is for. Bring your launch date, your funding position and the providers you have spoken to; we map the rest.
We map what is reusable and whether the delay is a provider problem or a build problem. Sometimes the answer is to stay and fix the product layer; sometimes it is to switch. You get the sequence either way.
The code. You pay for the build once, with a small annual licence fee and nothing per user or per transaction. The price to buy the source outright is in the contract before you sign, and the source is held in escrow from the start.
Yes. Real back-office screens on the first call, and a working demo built around your product on the second. You never commit to a build before you have seen your own product working.
The UK and the Gulf. The licence routes differ (the FCA; the CBUAE and SAMA), the product underneath does not, and we have built for both.
Book the call
Four quick questions on the form, so the 30 minutes start on your product, not on introductions.