Booksy: redefining digital tipping

Booksy Business's wallet buried its most-used actions behind bad information architecture and gave support agents no way to explain payout problems to frustrated providers. This case study covers a solo, three-day vibe-coded prototype built to validate a full redesign before committing engineering resources to it.
Role
Senior Product Designer
Year
2026
Product
Booksy / Finance domain
Industry
Marketplace / SAAS

Booksy Business's wallet had eight distinct UX problems identified through audit, from buried financial stats to a fast payout flow with no destination choice, and a support queue where the highest-severity ticket category (Payout Blocked/Held, 97.6% severity rate) was an architecture and visibility problem the interface did nothing to soften. Rather than route this through a standard design-to-dev cycle, the redesign was vibe-coded solo in Cursor: a fully interactive prototype, complete with haptics, micro-sound, and motion feedback, built in three days to validate the direction before committing engineering time to it.
This is a concept-stage project. No usability testing or production data exists yet; every claim below is either a design decision already shipped in the prototype or a business hypothesis flagged as such.


Timeline
3 days total: 1 day sketching the core screen and visual direction, 2 days vibe-coding the full flow, including interaction design (haptics, micro-sound, motion)
Scope
8 of 8 UX audit findings addressed in the prototype (payout destination choice, unified transaction/payout list, in-wallet stats, transaction search, consolidated filters, and more)
Role & stack
Solo: concept, interaction design, and a working prototype built with AI-assisted (vibe-coded) development in Cursor, structured so the resulting code could be handed to engineering as a reference implementation

Fewer support tickets in the "no visibility / unclear status" bucket, driven by payout-level detail, in-app KYC error explanations, and a built-in support contact path.
Higher engagement with the wallet section, driven by surfacing revenue/tip stats directly in Overview instead of requiring a separate navigation step.
Higher Fast Payout usage (and associated commission), driven by promoting it as a standalone action and adding destination choice at the point of use.

The best flow gets out of the way. It’s not about adding surface delight, but systematically removing friction between the user and their intent.
About meSay hello

Drop a message mariusz.karluk@gmail.com or visit my Linkedin
© 2026 Mariusz Karłuk. All rights reserved.