End-to-end product design for Bizimply's workforce management platform — introduced a day-by-day timecard view across web and mobile, enabling hospitality managers to review, correct, and approve attendance daily from anywhere. Unblocked stalled sales deals, retained at-risk customers, and removed a key competitor advantage.
View liveBizimply's timecard system only supported weekly views on web — forcing hospitality managers to batch-review attendance at end-of-week from a workstation, by which point details were stale. Deals were being lost, prospects were stalling, and existing customers were churning because competitors already offered daily timecards on mobile.
Stalled prospects committed
Deals converted
At-risk customers retained
Churn reduced
No longer a disqualifier
Sales objection removed
4–6 months to deployment
Timeline

Product Designer. Validated through CRM lost-deal analysis, 5–7 customer interviews, 50+ cross-lifecycle quotes, churn exit data, and competitor analysis. Built a mobile first solution for managers and a dedicated daily timecards page with bidirectional sync to the weekly view instead of extending the rigid existing architecture. Led internal alignment with Sales and CS stakeholders, resolved pushback, and delivered complete design specifications covering every screen, flow, and edge case before handoff to development.
Design
Other
CRM lost-deal analysis, customer interviews, 50+ quote collection across the sales lifecycle, churn exit review, and competitor analysis
Evaluated extending the weekly view vs. building a dedicated daily page — chose dedicated with bidirectional sync to weekly
Pressure-tested the design with Sales and CS managers, iterated on feedback, achieved full stakeholder alignment
Designed complete web and mobile experiences — inline editing, filtering, swipe-to-approve, bulk actions, cross-platform sync
Validated with original research participants, left all set for building stage
“Covering every screen and edge case in the design phase is worth the upfront investment — it pays dividends in delivery speed. A component library would have prevented the copy, colour, and spacing inconsistencies fixed during beta. The most telling success signal was the feedback that shifted to payroll integration requests, meaning the core problem was well targeted and the bottleneck would move downstream.”