Pricing

Priced by what you have to supervise, not by seats

A microfinance bank and a Tier-1 group get the same evidence chain and a very different amount of work around it. This page sets out what an engagement at each size involves and what moves the number, so the first commercial conversation starts from scope rather than from a rate card neither side believes.

Microfinance

Microfinance banks, bureaux de change and SCUML-registered DNFBPs running compliance with a small team — often one MLRO wearing several hats.

Contact for pricing

Proportionate controls: the same evidence chain, configured to the risk a smaller book actually carries.
A single institution, a single set of books, and a compliance function measured in people rather than departments.
Emphasis on getting CDD, screening and STR filing defensible before anything is tuned.

Get a figure for this scope

Most enquiries

Tier-2 and fintech

Tier-2 commercial banks, payment service providers and fintechs with high machine-intake volume and a compliance team that has to keep up with it.

Contact for pricing

Monitoring tuned against real activity, with the rationale for every threshold retained as a reviewable change.
Integrations with the core banking system, the switch and identity verification carrying most of the implementation weight.
Queue throughput and investigation quality measured together, because either one alone is gameable.

Get a figure for this scope

Tier-1 and enterprise

Tier-1 commercial banks, insurers, capital markets firms and groups operating several licensed entities under one compliance function.

Contact for pricing

Several entities, several regulators, and board-level reporting that has to reconcile across all of them.
Deployment, tenancy and data residency answered before anything else — bring the CISO to the first conversation.
Independent audit as a first-class user, not a report someone exports on request.

Get a figure for this scope

Placeholder — no approved price, currency figure or commercial band exists for any tier; the cells below are an empty shell, not a redacted rate card. Replace with sourced, approved content before this page is made public.

Placeholder for indicative commercial figures by tier. No figures are published.
Commercial shape	Microfinance	Tier-2 and fintech	Tier-1 and enterprise
Annual licence	Not published	Not published	Not published
Implementation	Not published	Not published	Not published
Minimum term	Not published	Not published	Not published

Capability by tier

The same platform at every size

The compliance capability does not change between a microfinance bank and a Tier-1 group. What changes is how much integration, migration and parallel running sits around it — which is why those rows say scoped rather than included.

Placeholder — the tier packaging is not decided — the capability rows are real, but which tier includes what has not been agreed commercially. Replace with sourced, approved content before this page is made public.

Platform capabilities by institution tier. Rows link to the capability page; cells are provisional packaging.
Capability	Microfinance	Tier-2 and fintech	Tier-1 and enterprise
Customer profiles, ownership and CDD	Included	Included	Included
Transaction monitoring and rule tuning	Included	Included	Included
Sanctions, PEP and adverse media screening	Included	Included	Included
Investigation and case workspace	Included	Included	Included
STR, CTR and goAML filing	Included	Included	Included
Audit trail, retention and legal hold	Included	Included	Included
Core banking, switch and identity integrations	Scoped	Scoped	Scoped
Deployment model, tenancy and data residency	Scoped	Scoped	Scoped
Implementation, migration and UAT	Scoped	Scoped	Scoped
Training and certification for the team	Scoped	Scoped	Scoped

Before a number exists

What a specialist asks about

Six questions decide the figure. Having the answers ready is the difference between a quote in the first conversation and a quote in the third.

Entities in scope

One licensed institution, or a group with several licences and one compliance function reporting across them.

Volume of monitored activity

How much customer and transaction data is screened and monitored, and how far back the history goes.

Deployment and residency

Where the data must physically sit, and what the tenancy boundary has to look like for your CISO to sign it off.

Integration landscape

Which core banking system, which switch, which identity and list providers — and whether each is an existing contract or a new one.

Environments

Production alone, or production with the separate UAT and training environments an examiner expects to see used.

Migration scope

Whether historical cases, filings and evidence come across, and in what state they arrive.

Pricing FAQ

The questions we are asked first

These open and close without JavaScript, and a browser search finds the text inside a closed one.

Why is there no price on this page?

Because there is no single number that would be true. What an institution pays depends on the entities in scope, the volume monitored, the deployment model and the integration work — and a published figure that turns out not to apply to you is worse than no figure at all. Tell us the scope and you get a number for that scope.

What actually changes the price?

The six drivers listed above this section, in roughly that order of impact. Nothing about the compliance capability itself changes between institution sizes; what changes is how much of it has to be integrated, migrated and run in parallel.

Can we license only part of the platform?

Ask. The capabilities are built as one evidence chain — a screening hit becomes a case becomes a filed report, carrying its provenance the whole way — so splitting it has consequences worth talking through rather than answering on a web page.

Is there a free trial?

There is a guided product tour that needs no account and no signup, and it walks a real adjudication workflow on synthetic data. Beyond that, an evaluation runs as a scoped engagement against your own configuration rather than as a self-serve trial, because the thing being evaluated is how the platform fits your obligations.

How do we get this into an RFP or a tender?

Use the contact page and choose the RFP option — it routes to the desk that answers tenders and security questionnaires rather than into the demo queue. Say what the deadline is.

Does the price include sanctions and PEP list data?

That depends on whether you already license list data and from whom. It is one of the scoping questions above, and it is answered in the commercial conversation rather than assumed here.

Start the conversation

Tell us the scope and get a figure for it

Institution type, entities in scope, and what your integration landscape looks like. That is enough to start.

Book a demo Send an RFP instead