Buddee · Product case · Sander Stricker
Onboarding a new HR and payroll customer
How I would approach redesigning Buddee's onboarding: the process I follow, the inputs I collect, and what they show. Real inputs come from Buddee's current flow and a call with customer success. Everything Buddee could not share is filled with fictional data, calibrated to that reality.
Real input
Fictional data
Mixed
Goal
01Goal description
From the briefProcess
- Start with one clear goal before collecting anything.
- Use Buddee's own words from the brief as the starting point.
Data
Brief: "new customers operational faster, with less work for them and for us, and working independently afterwards without much explanation."
To fill: the goal in one sentence, in my own words.
02KPIs
MixedProcess
- Translate the goal into one main metric.
- Add guardrails so the main metric does not improve at the cost of something else.
Data
To fill: main metric (e.g. time to first correct payslip) and guardrails (Buddee hours per onboarding, questions in the first 90 days), with baseline and target.
03Why this goal
MixedProcess
- Explain why this goal matters for Buddee now.
- Explain why not cutting support time, conversion or feature adoption on its own.
Data
To fill: the reasoning, linked to Buddee's growth plans and the cost of onboarding.
Inputs I collect
04The current flow, end to end
Real inputProcess
- Map every step from first contact to "operational": who, which tool, hand-offs, waiting time.
- Sources: call with Bas Jelle (customer success), the Valuecase portal, my own signup.
Data
2parallel tracks: HR and payroll
~39tasks in the onboarding portal
2meetings, 2 contacts afterwards
| # | Step | Who | Where |
|---|---|---|---|
| 1 | Demo account, sales call, contract signed | Prospect, sales | Buddee demo |
| 2 | Empty live account created, portal sent | Sales | Buddee, Valuecase |
| 3 | Contact details and company questions | Customer | Valuecase |
| 4 | Import template downloaded, filled, uploaded | Customer | Valuecase, Excel |
| 5 | Template checked, corrected and imported | Customer success | Buddee |
| 6 | Implementation meeting | Customer, CS | Call |
| 7 | Data check, leave, roles and permissions, workflows | Customer | Buddee |
| 8 | Employees invited (go-live) | Customer | Buddee |
| 9 | Payroll: data delivered, rebuilt in Nmbrs, CAO meeting, first run | Customer, payroll | Outside the portal |
05Lead time
Real range, fictional detailProcess
- Days from contract to go-live, and to the first correct payslip.
- Split by step to see where the waiting happens.
- Segment by data source: one existing system versus scattered data.
Data
Real: one week to 1.5 months for the customer, depending on how ready-to-use their data is.
Fictional data to generate: lead time distribution per customer, per step and per segment.
06Effort per onboarding
Real averages, fictional detailProcess
- Hours spent by Buddee (customer success, payroll) and by the customer.
- Where do the hours go: checking data, meetings, questions, payroll rebuild?
Data
4 hBuddee, HR track
4 hBuddee, payroll track
Fictional data to generate: hours per activity and per segment; customer hours.
07Time to contract
Fictional dataProcess
- Days from first contact or demo account to signing.
- What is already known at signing that could speed up onboarding?
Data
Fictional data to generate: days to contract, self-signup versus sales-led.
08Onboarding funnel
Real steps, fictional ratesProcess
- Share of customers reaching each step, and the time between steps.
- Find the biggest drop-offs and the longest waits.
- Ask Claude for indicators that correlate with reaching the goal.
Steps (from the Valuecase portal)
- Portal opened
- Contact details submitted
- Template downloaded
- Template uploaded
- Template approved and imported
- Implementation meeting held
- Phase 2 complete (ready to invite)
- Employees invited (go-live)
- First correct payslip
Fictional data to generate: conversion and median days per step, per segment. Chart goes here.
09Onboarding call transcripts
Fictional dataProcess
- Collect transcripts of implementation and payroll meetings.
- Let Claude cluster the questions and pain points, and count them.
Data
Fictional data to generate: a set of call excerpts and the resulting theme counts.
10Support emails during onboarding
Fictional dataProcess
- Questions from customers who are not yet fully onboarded, and in the first 90 days.
- Categorise by topic and by step in the flow.
Data
Fictional data to generate: question volume by category and by week after signing.
11Interviews with the people who onboard
Real inputProcess
- Short interviews with customer success and the payroll team.
- Done for this case: a call with Bas Jelle (customer success).
Key findings
- The real onboarding happens outside the product (portal, email, people).
- Biggest hurdles: employee data, then leave balances, then roles, permissions and workflows.
- Payroll is a separate track with its own specialist and a rebuild in Nmbrs.
- Customers choose Buddee for HR and payroll under one roof.
- His one wish: "fewer choices and more explanation in the system".
12My own walkthrough
Real inputProcess
- Go and look: create an account and experience the product as a new customer.
- Note friction as evidence, not as a list of fixes.
Observations
- Activation link does not log you in; it asks for a password that is only in the email.
- First screen is account settings, not a start screen.
- Welcome questions only cover leave, nothing on payroll.
- Features without guidance, e.g. a CSV import with no field list.
Analysis
13Claude analysis on the goal
MixedProcess
- Write a goal briefing for Claude.
- Give it all inputs from blocks 04 to 12.
- Ask for patterns, root causes and indicators linked to the goal.
Output
To fill: the briefing used, and the main findings from the (fictional) data.
14Common practices and examples
MixedProcess
- Claude compiles common onboarding practices in HR and payroll software.
- Examples of how others do it, first without Buddee's context.
Output
To fill: a short list of practices with examples, and which fit Buddee.
15Assumptions and what I test first
MixedProcess
- Make every assumption explicit.
- For each: how I would test it, and with which data.
Output
To fill: assumption · how to test · what the (fictional) data says.
Outcome
16The ideal onboarding
MixedProcess
- Principles, not a full design.
- A simple flow from signing to first payslip to working independently.
Output
To fill: principles and a simple flow diagram.
17Choices, and what I deliberately do not do
MixedProcess
- The trade-offs, with the reason for each.
- What I leave out, and why.
Output
To fill: choices and not-doing list.
18The first three months
MixedProcess
- Month 1: baseline and insight.
- Month 2: one or two experiments in the biggest segment.
- Month 3: measure against the baseline and decide.
- Small team, metrics and decision points.
Output
To fill: plan per month, team, metrics and targets.
19How I used AI
RealProcess
- The brief asks for this: say briefly what AI was used for.
Output
To fill: e.g. structuring, generating the fictional data, analysis, research on common practices, building this page.