Payroll Signup Redesign
Payroll onboardings went from 43 to 492 a month between October 2023 and January 2024, after I replaced a 90-field signup with a guided first run

In short
Payroll onboardings a month
492
January 2024
from 43 in October 2023Before vs after
Employee updates done a month
7.76k
January 2024
from 2.30k in October 2023Before vs after
Companies exporting payroll data
608
a month, January 2024
from 508 in October 2023Before vs after
Before vs after: same product, same sales approach and same payroll software, but no control group. Source: Factorial BI charts, October 2023 to January 2024.
- The old signup asked for over ninety fields before the first payslip. Most companies never finished.
- I replaced it with a setup guide that asks only for what the first payroll run needs. Everything else waits.
- Onboardings grew every month after launch, with the same product, sales approach and payroll software.
The problem
Factorial's payroll tool had stalled. With the Payroll and Sales teams I looked at lost sales, reasons people left and revenue impact. We gave ourselves six weeks to ship something measurable before the quarter closed.
Companies couldn't see the value of payroll until they ran a full month. And the confusing bulk salary screen sat in the middle of signup, so everyone setting up for real hit it on day one.
The first run
We benchmarked Personio, Gusto, Remote and Payfit. Then I sketched a setup guide that asks for three things: payroll rules, the changes to track and the connection to the payroll software. I tested it with happy and unhappy customers. Version 1 tested badly, version 3 well.
What comes next
After setup, a first steps checklist sits on top of the payroll run: a mini tour, financial insights and employee updates. Help from payroll specialists opens from the same page.
ShippedThe checklist sits above the payroll run, so the next action is always in view.
ShippedRequest help: payroll specialists for policies, integrations and compensations.
Settings you can find
The settings page had become an endless list nobody could search, so we grouped it into a page you can navigate. Bulk salary entry got a simpler version: one salary for many employees at once.
Impact
DataEmployee updates done each month, same period.
DataCompanies exporting payroll data each month, same period.
Honest read
No control group
Product, sales approach and payroll software stayed the same, but a before and after can't rule out every other cause.
Team and role
- Design and product
- Me. The Payroll team had no designer, so I owned what to build, weekly planning, user testing and quality checks through to launch.
- Payroll team
- Analysed lost sales, churn and revenue impact with me.
- Sales and activation
- Regular meetings through to launch.
What I learned
- Progress beats effort. The data is the same on day one or in week three. What changes is whether the product gives something back first.
- Postpone first. The setup guide got smaller every week, and companies started finishing their first payroll run the week they signed up.
- Planning is design work. With no designer on the team, I also ran weekly planning, so the effort went to the screens that moved onboardings.
