Kickstarting Voi's Hunter Ops platform
Voi's scooter fleet is only as good as the people rebalancing it — in-house specialists, supervisors, and 3PL partners collecting, charging, repairing and redeploying scooters city by city. That work ran on Excel sheets, a laminated street map taped to a wall, and WhatsApp. In a two-week sprint, I defined the IA and interaction spec for the platform that would formalize it: three account tiers, 41 screens, handed to engineering right after.
*This was a definition sprint. Build and rollout happened after these two weeks.
2 weeks
take rate in Sweden. Better than Volvia expected for a brand new product with zero existing demand.
50+ users
live on the same backbone. Insurance is regulated market by market, so the solution has to be flexible without a rebuild each time.
Turning shift logs into a system
Voi's fleet team has a long list of job titles: specialist, supervisor, city FM, 3PL manager, gig hunter. Underneath all of them, the work only splits two ways. You're in the field, collecting and dropping scooters. Or you're managing: overseeing performance, assigning tasks and shifts, keeping the fleet balanced. That split is what the platform needed to be built around, not the org chart. It's also where account and sub-account came from. A hunter's account holds their own shift, their own scooters, their own history. A supervisor's account holds a roster of hunters' accounts. Everything above that, 3PL managers, city FMs, is the same supervisor pattern one level up. A master account that can spin up and own multiple sub-accounts.
One table pattern, three access levels
Rather than invent new visual language, the account flows extend Voi's existing product — same coral mark, same card-based summary tiles already live on the Dashboard. Every tier reuses one row pattern (Name, Email, Zone, Status, Details, Delete), so a supervisor learns it once and reads it the same way at every level. Destructive actions get their own modal state, separated from routine edits, so deleting a hunter account never sits one careless click from editing one.
What each tier can do, and why it matters to the business
Individual performance tracking (by count and by time) — replaces the manual spreadsheet, makes hunter bonuses auditable instead of disputed
Zoning and shift planning — replaces the paper map, lets a supervisor react to same-day demand instead of relying on tenure
Repair tracking — applies the same time-based model to the warehouse side of the job, not just the street
Missing-scooter flagging — stops hunters burning hours re-chasing scooters already reported missing three times
Third-party hooks for navigation, GPS and comms — cuts the number of apps a hunter juggles mid-shift
Speed over polish
The new account flows were kept as clean, annotated wireframes on purpose — every edge case called out for engineering — so the two weeks went into getting roles and permissions right, not pixels. Visual polish was scoped to inherit directly from the already-styled Dashboard.
What’s next
3PLs repeatedly asked for direct access to edit scooter status and geofences themselves. Voi's team read that as a technical/API gap, not a UI one — so it's parked for a follow-up phase rather than folded into this spec.