Readiness model
How we judge whether a neobank can prove regulatory readiness — not just claim it in a slide deck.
1. Freeze the claim set
We list what your bank says it is ready for: licence stage, product lines, customer segments, and the supervisory questions you expect next. Readiness only makes sense against a fixed claim set.
2. Align policy to operating reality
Policies, playbooks, and system configurations are compared to how teams actually open accounts, move funds, escalate incidents, and close complaints. Drift between paper and practice is the most common readiness failure.
3. Stress the evidence
For each material control we ask: can you produce the right artefact in a realistic timeframe? Samples include customer due diligence files, transaction monitoring cases, board packs, and incident timelines.
4. Map ownership and handoffs
Readiness collapses at boundaries — product to compliance, compliance to operations, vendor to bank. We walk those handoffs with the people who move work day to day.
5. Sequence what to fix first
Findings are ranked by regulatory exposure and delivery cost. You receive a sequenced plan: stabilisers that unblock an upcoming review, then structural work that protects the next product wave.