Nine days to two

The situation

Kestrel onboarded merchants through a form built by the compliance team in 2019. It asked for everything up front, in the order the regulator listed it, and told applicants nothing about where they stood. A third of them never finished. Support absorbed the rest.

What we did

1. 01

   We watched people fail before we drew anything

   Eleven onboarding sessions with real applicants, recorded end to end. Seven of the eleven stalled at the same two points: proof of business address, and a document upload that silently rejected anything over 4 MB.

2. 02

   We split the form by who can answer it

   Not by regulation, by reality. Questions a founder can answer alone came first and unlocked a sandbox account immediately. Anything needing an accountant or a lawyer moved to a second stage that runs in parallel with the sandbox instead of blocking it.

3. 03

   We made status the primary interface

   The applicant now sees what is done, what is being reviewed, and what is waiting on them — with the specific reason attached. Most support tickets had been asking exactly that question.

4. 04

   We shipped it as a system, not a screen

   Every state — pending, needs-input, in-review, rejected with reason, approved — became a component with its own copy contract, so risk and support could change wording without a design ticket.

Where it landed

Merchants reach their first live payment in two days instead of nine. The compliance content did not shrink; the sequence changed. Kestrel has since applied the same staging model to two other regulated flows.