Before
What was getting in the way
- Every free sample was a hand-built order in the store.
- Sign-ups and progress lived in forms, spreadsheets and task lists.
- Nothing showed who was waiting on a kit or overdue on a mission.
Case study / Customer programmes
A content collaboration system that runs daily
A product testing program, rebuilt from manual orders and spreadsheets into one branded app.
157
Active testers
122
Completed missions
164
Submissions
Programme results from its first four months.
After
What changed
- Testing runs from one place instead of forms, spreadsheets and task lists.
- In the programme’s first four months: 157 active testers, 122 missions completed and 164 submissions.
Inside the work
From diagnosis
to delivery.
Open each step for the decisions, sequence and implementation details.
The programme needed more than a sign-up form. Each tester’s participation depended on receiving products, accepting a mission and completing a submission, with visibility for the team running it.
Understand
Traced how a tester joined, received a kit and submitted content, across every tool involved.
Prioritize
Sign-up and missions first, then kit ordering, then a daily check.
Implement
- A branded tester app: sign-up, missions with acceptance windows and limits, kit orders, submissions, automatic tier upgrades and an admin dashboard.
- A daily check that flags overdue missions, missing kit orders and inactive testers.
The useful lesson
What to take from this
In its first four months the programme recorded 157 active testers, 122 completed missions and 164 submissions. The daily check makes overdue missions, missing kit orders and inactive testers visible.
Explore our approach ↗A clearer way forward
Facing something similar?
Book a discovery call
30 minutes. A practical conversation.