Product Roadmap

Product Roadmap

Phased delivery plan

Each phase expands scope only after measurable go/no-go gates are met — client value, legal readiness, operational and financial-crime controls, resilience, and a supportable commercial model.

New to the wording on this page? 5 terms explainedShow

Go/no-go gate

A checkpoint between phases where named people decide whether the product may continue. Not a status update — a decision with genuine power to stop the work.

For example: Before phase two, legal must confirm settlement finality in that specific country. If they cannot, the phase does not start — regardless of how much has already been spent.

NPANew Product Approval

A bank's formal internal sign-off before launching anything genuinely new. Risk, legal, compliance, operations and technology all have to agree — not just the commercial team.

For example: Before the first client can use a tokenised deposit service, each function signs off in turn. Any one of them can block it. This is usually why bank products take far longer to launch than startup products.

Legal finalitySettlement finality

The point at which the law says a transfer is permanent and cannot be unwound — including if one party later goes bankrupt. It is a legal question, decided country by country, and is not the same as software saying 'complete'.

For example: Your system shows a payment as settled at 10:00. At 11:00 the receiving company collapses and a court decides the 10:00 transfer can be clawed back into the bankruptcy pool. Technically it settled; legally it was not final.

MVPMinimum Viable Product

The smallest version of a product that still delivers real value to a real customer — built to learn whether the idea works before spending heavily.

For example: Rather than building settlement for twelve currencies across forty countries, you launch Hong Kong dollars between two entities of one willing client, and learn from that.

Walking skeleton

A thin end-to-end version of the whole system — every stage connected and working, even if each does very little. It proves the pieces join up before you make any of them sophisticated.

For example: One payment, one currency, one client, moving all the way from instruction through screening to settlement and reconciliation. Nothing is clever, but every join is proven real.

See every term used across this site

What's a “go/no-go gate”?

A checklist of conditions that must all be true before a phase is allowed to expand — a green tick doesn't mean “we'd like to,” it means someone accountable has actually confirmed it. If a gate isn't met, the phase doesn't move forward, no matter how good the technology looks.

Client-value validation

A real client has confirmed this actually solves their problem — not just an internal assumption.

Legal and regulatory readiness

Lawyers and regulators have confirmed this is allowed to operate in that market.

Financial-crime controls tested

Sanctions and money-laundering checks have been tested and proven to work, not just designed.

Operational readiness

The team can actually run this day to day — support, monitoring, fixing problems — not just build it.

Resilience / incident testing completed

The system has been tested for what happens when something breaks, and it recovers safely.

Commercial economics approved

Finance has confirmed the numbers make business sense at scale, not just in a pilot.

Client-support readiness

There's a real support model in place — someone a client can actually reach when something goes wrong.