Building a modular KYC platform without freezing product teams

KYC work has a gravitational pull toward monoliths: one form, one workflow, one team that becomes the gate for every launch.

We took the opposite bet — a modular KYC platform that multiple internal products could adopt without waiting on a central queue for every field change.

What “modular” meant in practice

• Stable verification primitives (document checks, face match, status machines) owned by the platform
• Composable UI and API surfaces so product teams could assemble flows for their context
• Clear ownership of configuration — products own their copy, branching, and launch criteria; the platform owns correctness of the rails

The outcome we cared about was time-to-onboard: weeks of reinvented verification work compressed into days of composing existing rails.

The hard part is the contract

Shared platforms die when the contract is vague. We invested in versioned status models and explicit extension points so a product could add a step without forking the core.

Full-stack ownership helped: the same team that shaped the API also shipped the client integration patterns, so “adopt the platform” was a documented path — not a scavenger hunt through Slack.