How Cenoa cut business onboarding from 2 weeks to 2 days
Cenoa is a digital bank built for businesses. Like every regulated financial institution, it has a hard rule: no account moves its first dollar until the business behind it clears Know-Your-Business (KYB) review. Documents have to be collected, identities verified, ownership structures untangled, sanctions and risk screens run, and a compliance officer has to sign off. None of that is optional, and none of it is going away.
The problem was never whether to review. It was how long the review took. Every application sat in a manual queue where an analyst pulled documents from a portal, keyed data into three systems, cross-checked registries by hand, and escalated anything ambiguous over email. On a good day that was a few hours. On a bad day — a foreign entity, a complex ownership chain, a missing certificate — it was the better part of two weeks.
Where the two weeks actually went
When we mapped the flow with Cenoa's operations team, the pattern was familiar. The bottleneck wasn't the compliance decision — that final judgment took minutes once an analyst had the full picture. The bottleneck was everything upstream of the decision: assembling the file.
An analyst spent the overwhelming majority of each application shuffling between systems. Extract the registration certificate. Read the ownership declaration. Look up the ultimate beneficial owners. Run each name against sanctions and PEP lists. Score the risk. Only then could a human actually decide. Assembly, not judgment, was eating the calendar.
That distinction matters, because it tells you exactly what to automate and what to leave alone. You do not want an agent making the final KYB call on a borderline entity — a regulator wants a named human on that decision, on the record. You do want an agent doing the twelve steps of assembly that put that human in a position to decide in three minutes instead of an hour.
The flow we built
We deployed a four-stage flow that runs on every application the moment it lands. The agent moves optimistically through all four stages; a compliance reviewer confirms the last call in one click.
Click a step. The agent runs all of them; a human confirms the last call.
The agent pulls registration certificates, ownership declarations, and IDs out of whatever format they arrive in — PDF, photo, scan — and normalizes them into structured fields. No manual keying.
Nothing here removes the compliance officer. It removes the two weeks of assembly that stood between the officer and the decision. When a reviewer opens a case, the file is already built: documents extracted, identities checked, risk scored, exceptions flagged in plain language. The routine cases clear in minutes. The genuinely hard ones — the entities that should take longer — still get the full human attention they need, just without the queue of easy cases stacked in front of them.
What changed
The results were not incremental. Compressing assembly from hours to minutes changed the shape of the whole funnel.
| Metric | Before | After |
|---|---|---|
| Onboarding time | 2 days | |
| KYB review per application | 3 minutes | |
| Days to first revenue | Day 1 |
Estimated revenue uplift: +$200K/yr — from faster activation and fewer drop-offs during onboarding.
The KYB review itself went from an hour of manual assembly to three minutes of human confirmation — a 20× compression on the step that had been the constraint. End to end, onboarding dropped from two weeks to two days. And the metric that actually pays for the project, days to first revenue, collapsed from roughly twelve days to day one. A business that signed up could transact the same day instead of nearly two weeks later.
The part that's easy to miss: control never left the building
It would be easy to read "2 weeks to 2 days" as we removed the humans. The opposite is true. A compliance reviewer is on every single approval. What changed is that the reviewer spends their time on judgment instead of data entry.
This is the distinction that makes the difference in a regulated environment. A fully autonomous onboarding agent would have been a non-starter — no compliance team is going to let a model approve a borderline account with no human on the record, and no regulator would accept "the system did it" as an answer during an exam. Every decision in Cenoa's flow is logged with its inputs, the model's output, the reviewer's call, and the rationale behind it. When an examiner asks why an account was approved, the answer is a clean, attributable trail, not a shrug.
That is the whole point of a human-in-the-loop design: the agent does the volume, the human owns the last call, and the record holds up.
What carries over to your onboarding
Cenoa is a bank, but nothing about this flow is bank-specific. Any high-volume review where a human must stay on the final decision — vendor onboarding, merchant approval, seller verification, credit review — has the same shape. The work that eats the calendar is assembly, not judgment. Automate the assembly, keep the human on the call, and log everything.
If your onboarding queue looks like Cenoa's did — a compliance step that's fast once the file is built, sitting behind hours of manual file-building — the playbook transfers directly. Our fintech solutions page walks through KYC/KYB, dispute handling, and the audit-trail model in more depth.
The fastest way to know if it fits is to put one real onboarding flow in front of us. Thirty minutes, your funnel, a mapped flow and an honest go / no-go at the end.