Ledgerly: a calmer way to run payroll

A ground-up redesign of a payroll product for small teams, from first run to the monthly close.

Three colleagues reviewing work together on a laptop

01Brief

Payroll that feels finished before payday

Ledgerly's customers run payroll once a month and dread it every time. We rebuilt the core flow so a first-time admin can finish a run without opening the help centre.

Challenge
Monthly runs took 14 steps across four screens, and most support tickets arrived on payday.
Role
Product design lead, working with two engineers and a researcher.
Scope
Research, flows, interface design, design system and launch support.
Client
Ledgerly
Timeline
14 weeks

02Discovery

We watched twelve real payroll runs

Before drawing anything we sat with twelve admins on payday. Nobody followed the order the product expected. People checked totals first, then fixed individual payslips, then went looking for the button that would let them send it.

What we heard

  • "I never know if I'm done." The old flow had no clear end state.
  • Corrections meant starting again from step one.
  • Totals were hidden until the very last screen.
The redesigned pay run overview with one total, three items to review and an approve button
Fig. 3The new run overview: totals first, exceptions second, one clear action.

03The run

An overtime entry being corrected inline inside the pay run
Fig. 4Inline corrections keep the admin in the run.

One screen, in the order people think

The run overview now opens on the number everyone checks first: what leaves the account. Exceptions sit directly underneath, each one fixable in place.

  1. Review the total
  2. Resolve what's flagged
  3. Approve and send

05Results

Ninety days after launch

Measured across every account that ran payroll at least twice in the period.

  • 62%Less time to complete a monthly runMedian, 11 min to 4 min
  • -41%Payday support ticketsQuarter on quarter
  • 4.7Average satisfaction after a runOut of 5

For the first time I closed payroll and didn't double-check it on paper. It just told me I was done, and I believed it.

Portrait of a smiling woman in glasses and a striped shirtMarta LindqvistOffice manager, Brightfield Studio

06Process

How the work ran

  1. Shadow

    Twelve observed payroll runs and a review of six months of support tickets.

  2. Shape

    Three flow concepts tested as clickable prototypes with eight admins.

  3. Build

    Paired with engineering in two-week cycles, shipping to a beta group from week six.

  4. Tune

    Copy, empty states and error recovery refined against live beta feedback.

THIS PAGE WAS MADE WITH CASE STUDY BUILDER

Your next project could look like this by tonight.

Your next project could look like this by tonight.

Your next project could look like this by tonight.

Case Study Builder

Case Study Builder - CMS Layouts is a plugin for Framer. Every case study on this site was made with it.

Create a free website with Framer, the website builder loved by startups, designers and agencies.