Four steps. Fixed-fee. One accountable owner.

The same engagement structure across every project — MiCA Register Exposure Snapshot, Operational Readiness Diagnostic, Build, Embedded Run. Each step ends in a deliverable you keep, whether or not you take the next step.

The four steps

Every project follows the same ladder. Fixed fees at each step, scoped up front — no hourly billing, no scope creep. Prices are confirmed after Snapshot / Diagnostic, based on findings.

Step 1 · 1 week
Snapshot
Board-ready exposure summary — fixed fee, one week

For CASPs: MiCA Register Exposure — each counterparty resolved against ESMA's weekly interim register, exposure quantified in euros, addressed to the CCO or board. For other regulated firms: a comparable board-ready diagnostic scoped to your obligation.

Step 3 · by scope
Build
Systems in production, measurable outcome per module — fixed fee, by scope

We build the specific pipelines and systems for the gaps found. Every module ships to production with a measurable outcome agreed up front — not a prototype that stops at the demo. Examples: "records accepted at NCA validation", "Travel Rule holds on mismatch, automated", "AI control per-request audit trail live".

Step 4 · ongoing
Embedded Run
2–3 KPIs in SOW, monthly — the SaaS structurally can't do this

Compliance is a process, not a milestone: the register updates weekly, regulation shifts, and AI systems need continuous governance. We operate what we built, with 2–3 measurable KPIs in the SOW — e.g. 100% of records pass validation; compliance-gap closure inside an agreed number of days.

How we price

Four principles, applied to every engagement.

Fixed-fee, not hourly

Every step is scoped up front. The number is agreed before we start; the outcome is agreed before we start.

Snapshot / Diagnostic first

Build pricing is confirmed after Step 1 or Step 2 — because until we've seen the actual gaps, a build quote is fiction.

Weeks, not Big-Four months

Snapshot in a week; production modules in weeks — not a multi-month procurement-and-slides cycle. Speed to proof.

One accountable senior architect

The same person owns Snapshot, Diagnostic, Build and Embedded Run — from first call to years of operation. No rotating cast of freelancers; no handoff to a delivery team who wasn't in the room.

Snapshot & Diagnostic

The architect resolves counterparties, writes the exposure summary, and scopes the diagnostic personally.

Build

The architect owns technical decisions and the production guarantee — with AI engineers, a BA, a certified PM and QA behind them.

Embedded Run

The same architect runs against the KPIs in your SOW — every month, for as long as the engagement runs.

Start with Snapshot.

30-minute call to scope the Snapshot to your obligation. If you're a CASP, we'll walk through what the Register Exposure Snapshot produces before you commit to it.

Book a Snapshot call