Why fintech startup Ledgerly swapped a single dense form for progressive disclosure and cut support tickets 41%

Design · 5 min read

Ledgerly launched in late 2025 with a traditional, single-page onboarding form that collected business details, tax documents, and bank verification all at once. New users routinely abandoned the process midway or submitted wrong documents, triggering a surge in verification support tickets. The product team prioritized speed-to-market initially, but the support backlog and low activation forced a product-design rethink.

The team ran a lightweight discovery phase: 18 moderated usability sessions and analysis of form analytics via FullStory and Amplitude. Designers found cognitive overload and unclear expectations were the main failure modes. They shifted to progressive disclosure: identity verification first, then bank linking, then tax documents — each stage explicitly framed with time estimates and examples of acceptable documents.

After an A/B test with 7,200 eligible signups over six weeks, the progressive flow reduced verification-related support tickets by 41% and increased completed onboarding by 18%. Importantly, average time-to-first-transaction dropped from 6.2 days to 2.9 days. The case underscores that startup speed-to-market shouldn't omit microcopy and task framing; small changes in flow architecture can produce outsized operational wins.