SaaS Product Design
Boost On Time
Performance tracking and scheduling SaaS built for eCommerce teams who live inside their listings all day.
- Role
- UI/UX Designer
- Client
- Pippa Technologies Inc.
- Year
- 2025
- Scope
- UX ResearchDashboardDesign SystemWeb App
Overview
Boost On Time helps eCommerce teams schedule listing boosts and track how each campaign performs across marketplaces. The core problem was density: operators needed to see dozens of scheduled boosts, their status, and their results without drowning in tables.
I owned the end-to-end experience, from research and user flows through to high-fidelity UI and an interactive prototype in Figma.
Understanding the operator
I ran interviews and usability sessions with the people who actually run boost campaigns. The recurring theme was context-switching: they were juggling a spreadsheet, a calendar, and the marketplace dashboard just to answer one question: what is running right now, and is it working?
That reframed the product from a scheduling tool into a monitoring tool that happens to schedule.
Designing for density without noise
The dashboard leads with a single status band (live, queued, and finished) before it shows any table. Scheduling moved into a focused side panel so operators never lose their place in the list.
Every metric card follows one rule: one number, one comparison, one action. Anything that failed that rule got moved into a detail view.
A system, not a set of screens
I built a component library covering tables, filters, status chips, empty states and the scheduling panel, so new modules could be assembled rather than redrawn. Tokens for spacing, type and status colour keep the product visually consistent as it grows.
Outcome
What shipped.
End-to-end flows, wireframes and high-fidelity UI delivered in Figma
Reusable component library adopted across the wider product
Scheduling and monitoring unified into a single operator workspace
Related reading
- Internal tools fail differently from consumer apps
A consumer app is judged on the first visit. A CRM is judged on the hundredth. Almost every design instinct you have was formed on the wrong one.
- Naming things: the quiet half of a design system
Components are the easy part. The names decide whether anyone can find them a year later, and whether the system survives its first handover.
Next
Working on something shaped like this?
Send the product, the problem and the deadline. I'll tell you what I'd actually do and whether I'm the right person for it.
Start a conversation