Fixed date
no evaluation window
The vendor search will not start until the launch date is set.
By role
Compliance that grows with the company
Pass the sponsor bank review now. Run the full program on one customer record later; no long integration and no early hires.
What you switch on
Where a founding team starts
Enough for the partner review, ready for the regulator, all on one customer record.
Why this matters here
Before compliance is a team, it is a gate to launch
The date is determined by the sponsor bank or by the licence application. The programme must be capable of working today and have the ability to grow as each new customer is added. There isn't time for a lengthy vendor evaluation.
No compliance lead
and no budget yet
The duties come before the first compliance hire.
Engineering cost
weeks off the roadmap
Each week dedicated to integration is a week lost from the product roadmap.
15 min
From sandbox key to live response
Single
Endpoint in the signup flow
Zero
Compliance hires on day one
4 weeks
To partner approval
Week · Against the clock
Scroll to advance
Your first week on complead
-
Step 01
Test before the first meeting
A sandbox key, just one curl request, and you get a live screening result. No sales call needed.
-
Step 02
Screen inside signup
The check is included in the signup request; there is no additional service and no manual queue.
-
Step 03
Hand the sponsor its evidence
The decisions, along with their reasons and evidence, are all on a single record, and the sponsor bank pack has already been put together.
-
Step 04
Grow on the same record
As the program expands, there will be more volume and more modules but the level of integration will remain the same. All information on operations, team performance and risk trends can be seen in a single view.
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
The first questions come before the regulator
Early on, the banks that are sponsors, the payment schemes, and the investors review your controls, and the questions they raise are the same as the regulator's.
Read the compliance guides
Sponsor bank
A working program with evidence
Pre-launch
Payment scheme
Screening coverage and speed
On onboarding
Regulator
A named officer and a risk assessment
On licensing
Investor
Proof of financial crime controls
During due diligence
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 before launch?
No, but you will need a named officer by the time you apply for a license. Until then, the platform is built so one person can run the program, with screening, decisions and evidence on one record. The first compliance hire then inherits a working program, not a backlog.
How much engineering time does integration take?
One endpoint and roughly a day of engineering. The sandbox proves it before you commit, so the integration never has to compete with the product roadmap for a six-week slot.
Can we test before talking to sales?
Yes. A sandbox key and one curl request return a live screening result, usually within fifteen minutes of generating the key. No sales call is needed to see whether it fits your flow.
What does pricing look like at an early stage?
It scales with volume, so the cost tracks the business rather than leading it. An early-stage company is not priced as if it already had the volume it plans to reach.
What will our sponsor bank receive?
Decisions with their reasons and evidence on one record, and a sponsor bank pack that is already put together. Sponsor banks review your program before go-live and keep reviewing it afterwards, so the pack is generated each time rather than rebuilt.
Which modules do we need at launch?
AML screening and KYC/KYB first, ongoing monitoring once there is a back book, and case management when the first audit is scheduled. Each module switches on inside the same record, so the order follows your obligations, not a vendor's packaging.
Will we outgrow this as we scale?
No. Modules switch on as obligations arrive, and there is no second integration. The record your first customers were screened on is the one your auditor reads when you have a million.
Does screening add steps to our signup?
No. The check sits inside the signup request, with no additional service, no redirect and no manual queue. Every extra step at signup costs applicants you have already paid to acquire, so the control has to be invisible to them.
What will investors ask about our controls?
Whether financial crime controls exist and work, usually during due diligence. Investors, sponsor banks and payment schemes ask the regulator's questions earlier: a working programme, screening coverage and a named officer. The same record answers all of them.
Can we see operations in one view as we grow?
Yes. Operations, team performance and risk trends are visible in a single view. As the team grows from one person to several, you see where alerts pile up and how decisions are made without building a reporting layer.
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