A deadline
not a project
The requirement arrives with a date and no evaluation window.
By role
Compliance that fits the roadmap
You need enough programme to satisfy a sponsor bank, without a six-week integration or a headcount you cannot justify yet.
What you switch on
What a founding team switches on first
The minimum that a partner accepts and a regulator recognises.
Why this matters here
Compliance is a launch blocker before it is a function.
The requirement arrives from a sponsor bank or a licence application with a date attached. You need something defensible now and scalable later, chosen without the six weeks a proper evaluation would take.
No MLRO yet
and no budget for one
The obligations exist before the headcount does.
Roadmap tax
six weeks of engineering
Integration work taken straight from the product plan.
15 min
To first live call
1
Endpoint to integrate
0
Compliance hires to start
4 weeks
To partner sign-off
Week · Against the clock
Scroll to advance
A week in the job
-
Step 01
Prove it works today
Sandbox key in the browser, a curl command, and a real screening response before any call.
-
Step 02
One endpoint in the flow
Screening inside the signup request. No queue, no second screen, no new service to run.
-
Step 03
Satisfy the partner
Decision trail and evidence pack ready for the sponsor bank rather than assembled for the meeting.
-
Step 04
Scale without a migration
Volume changes the plan, not the integration. Modules switch on when the obligation arrives.
complead / sandbox
- Time to keyinstant
- First call15 min
- Contract requiredno
complead / screening / search
- Integration1 endpoint
- Engineer-days
- Median148 ms
complead / audit
- Evidence packgenerated
- Prep time0 days
- Review meetings1
complead / account
- Rate limitscales
- New modulesno re-integration
- Migrationnone
Prove
Integrate
Satisfy
Scale
What you answer to
Who asks first, and what they want
A regulator is rarely the first reader. A sponsor bank, a payment scheme or an investor gets there earlier, with the same questions.
Read the compliance guides
Sponsor bank
Programme evidence before launch
Pre-launch
Payment scheme
Screening coverage and response times
On onboarding
Regulator
Named officer and risk assessment
On licensing
Investor
Diligence on financial crime controls
At raise
Case study · Fintech
Read the case study
From sandbox key to sponsor-bank sign-off in a month
The integration took an afternoon. The remaining four weeks went on the evidence pack rather than the plumbing, and the bank review was a single meeting.
1 day
To first live call
4 weeks
To sign-off
0
Compliance hires
Cross-family links
Where teams like yours go next
FAQ
Before you ask us
Do we need a compliance hire first?
No, but you will need a named officer at licensing. The platform is built so one person can run the programme until then.
How long is the integration really?
One endpoint, roughly a day of engineering. The sandbox proves it before you commit.
What does pricing look like early on?
It scales with volume, so the cost tracks the business rather than leading it.
Will we outgrow this?
Modules switch on as obligations arrive; there is no second integration when you do.
Get a sandbox key before you get a meeting
Fifteen minutes to a live screening call. If it fits, the rest of the conversation is easy.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data