Onboarding is a regulated pipeline, not a signup form.
In financial services the funnel and the compliance record are the same object. We build the revenue system so that KYC, underwriting and partner distribution run as stages an examiner can read back.
The CRM says won. Compliance says pending.
Growth counts applications, risk counts approvals, finance counts funded accounts, and the verification decisions live in a vendor console nobody reports from. Four systems, four truths, and no way to explain a decline six months later.
An approved account is not a funded one.
FinTech — screenThe system a regulated revenue team can operate.
Onboarding as stages
Application, identity check, document collection, screening cleared and account opened, each a stage with entry criteria and a written reason for every exit.
KYC and KYB write-back
Verification, sanctions and PEP results pushed from the provider into properties on the contact and company, so screening outcomes are reportable instead of trapped in a vendor console.
Underwriting on its own board
A separate risk pipeline with its own stages, queues and SLAs, so credit and compliance review does not sit inside a sales rep deal board.
Partner and channel distribution
Brokers, ISOs and embedded partners modelled as their own objects, with referral attribution, tiering and payout data joined back to the accounts they originated.
Activation, not signups
Signed up, approved, first deposit, first transaction and sustained activity tracked as distinct milestones, so an approved account is never reported as revenue.
Audit trail on automation
Every workflow that moves, scores or declines a record writes actor, input and timestamp, so an examiner can reconstruct an automated decision without asking an engineer.
Trace one application end to end.
Diagnose
One real application traced end to end — first touch through screening, review and funding — marking every point where the record stops being evidence.
Define
Stages, decision reasons, required fields and retention rules written down and signed off by revenue, risk and compliance in the same room.
Instrument
Objects, workflows, provider integrations, consent and archiving rebuilt against that definition, with reporting on approval rates and time in review.
Hand over
Runbooks for the review queues, training for the operators, and a period sitting in the review queues with the operators who will own them.
Nobody budgets for the re-verification queue.
Documents expire, beneficial ownership changes, periodic reviews come due, and a manual remediation queue appears that no team owns. It is ordinary operational work, and it belongs in the pipeline with an owner, an SLA and a report — not in a spreadsheet beside it.