01 / The objective
The starting point
At PayFit the issue was not a lack of ideas but a bottleneck. The marketing team wanted to launch tools on the site regularly. The dev team was working on higher-priority pages. As a result, the tools stayed in the backlog and marketing was frustrated at not being able to move.
Project priorities
- Launch tools without pulling the dev team into every project
- Respect the frameworks and best practices the developers already use
- Give marketing the means to publish this kind of tool on its own
02 / What we did
The decisions that made a difference
- 01
A volume approach
launch 3 tools at once, on the basis that at least one would work and serve as a base to iterate on.
- 02
Processes and playbooks
to build tools with the developers' frameworks and best practices.
- 03
The 3 tools, from design to production
- Employee cost simulator: total employer cost, net pay, breakdown of contributions
- PayFit gains calculator: time and money saved with the solution
- Working-hours calculator: hours, breaks and premiums per day
- 04
Handover of the playbooks
to the teams, so they launch the next tools themselves.
03 / Results
The key results
All 3 tools are in production, and the working-hours calculator reached 12,000 monthly visits within 3 months. Beyond traffic, the real result is organisational: marketing now has a process and playbooks to publish its own tools without blocking the dev team.
visits / monthWorking-hours calculator, reached in 3 months.
calculators in productionEmployee cost, PayFit gains and working hours.
reusable playbookHanded over to marketing to launch the next tools.
The takeaway
The project delivered both a tool that attracts visitors and a team equipped to launch the next ones. Lead generation is not quantified in this case.
Historical project results. The scope and period are stated for each metric.
