Solutions · Banks & financial institutions

Your board has asked what tokenization means for you. A pilot is not the answer.

Most institutions are two years into tokenization and have a proof of concept, a white paper and no product. The gap is rarely technology. It is that nobody has resolved which asset, under which regime, held by whom, settled how.

Where you are

The situation, as we usually find it.

You have pilots, not products

A successful pilot proves a chain can move a token. It does not tell you which instrument your regulator will admit, who provides custody, or how the coupon gets paid on a bad Tuesday.

The business case is written backwards

Tokenization sold internally as back-office cost saving competes with every other efficiency project and loses. Sold as new revenue on new assets and new clients, it competes with nothing.

Your infrastructure stops at the chain boundary

Custody, settlement, collateral policy, risk weighting and the general ledger were designed for instruments held through a depository. None of them reaches an asset whose record lives elsewhere.

What blocks you

Three things stand in the way — and none is solved by technology alone.

Blocker 1

No admissible asset

You cannot tokenize your way to a product if no instrument on your shelf has a regulatory path in your jurisdiction. Asset selection is a regulatory question before it is a commercial one.

Blocker 2

Custody and settlement

Who holds the key, what happens on default, how delivery-versus-payment works when one leg is on-chain — these determine whether your risk function can sign, and they are usually left until last.

Blocker 3

Nobody owns the lifecycle

Corporate actions, redemptions, reporting, reconciliation and regulator notification need an operating owner. In most institutions this falls between innovation, operations and the product desk.

The journey

From where you are to a live, admitted product.

Highlighted steps are the ones we carry end to end. Durations are indicative for a first asset; each subsequent asset in the same class reuses most of the work.

01

Thesis and asset selection

Which asset, which client segment, which revenue line — chosen against what your regulator will actually admit.

2–4 wks
02

Regulatory path

The wrapper, the exemption or the filing, and the supervisory conversation that goes with it.

8–16 wks
03

Custody and settlement design

Key management, custodian arrangements, DvP model, collateral eligibility and the risk treatment.

4–8 wks
04

Build and integrate

Issuance and compliance contracts, core-banking and ledger integration, price and NAV feeds, audits.

8–14 wks
05

Controlled pilot

A live instrument with real clients under a bounded limit, with the operating manual written as you go.

6–10 wks
06

Scale to a shelf

The second instrument in the same class reuses the framework and costs a fraction of the first.

4–8 wks each
Division of labour

What we carry. What stays yours.

We carry
  • Asset and regulatory-path selection
  • Wrapper design and regulator engagement
  • Custody, settlement and collateral architecture
  • Issuance, compliance and lifecycle contracts
  • Independent assurance and audit coordination
  • The reusable template for instruments two through ten
You keep
  • The client relationship and the balance sheet
  • Credit, risk and investment decisions
  • Your licence and your brand
  • Distribution and pricing
  • The product owner
Why us, here

Relevant experience, not a capability list.

Market infrastructure, not just contracts

Our board built a national depository and its KYC registry, and the distributed-systems core of a national payments and CBDC programme — eligibility, custody and settlement at hundreds of millions of accounts.

Regulated products, distributed

Our founder built and ran a regulated insurance product business distributing bite-size supervised products through corporate partners and a ten-thousand-strong agent channel. The motion is the same.

Assurance your risk function can read

Risk assessment mapped to ISO 27005 and NIST, verification against deployed code, and a gate document written for an auditor.

The institutions that will have a tokenized shelf in two years are the ones that picked one admissible asset this year and built the framework underneath it.

Other routes