Designer
Me
Role
Product Designer
Platform
B2C | SaaS
Team
1 PM, 2 Eng, 1 QA
Context
Paylo was designed for UK adults managing money across multiple disconnected tools. The average user juggles three or more apps to get a complete picture of their finances. Banking in one place, budgeting in another, savings somewhere else. The result is not just inconvenience. It is a genuine loss of financial control. People miss bills, underestimate spending, and save less than they intend to because the cognitive overhead of context-switching between apps erodes the habit entirely.
Reframed Challenge
Solution
01
This is the foundation of the entire system. Every downstream experience from package creation to pricing and bookings depends on how well this data is structured.
I designed a highly scannable interface that makes inventory easy to manage, with clear data hierarchy and quick add/edit interactions. The goal was to reduce complexity while ensuring accuracy and consistency.
02
This is the core innovation of the product where supply becomes monetizable. It bridges the gap between raw inventory and a bookable experience.
I introduced a multi-step flow (Rooms → Addons → Pricing) to guide users through complex inputs. Real-time calculations provide clarity on total cost and guest capacity, helping users make confident decisions without feeling overwhelmed.
03
This is the moment where users decide whether to book or not
I prioritised clarity and transparency. Filters enable quick narrowing of options, while the details page clearly communicates pricing, inclusions, and availability. The goal was to reduce uncertainty and build trust at the point of decision.
Structuring the Experience into a Single Flow
To eliminate fragmentation and ensure every action feeds into the next.
Standardising Hotel Inventory
Unstructured data would break pricing logic, packaging, and booking flows.
Using Multi-step Workflows
To reduce cognitive load and guide users through complex inputs.
Request-based Booking Model
High-value, customised bookings require validation and flexibility
Linking Retreats to Confirmed Bookings
To ensure data accuracy (pricing, availability, location).
Deposit-based Payment System
To lower commitment barriers for users.
Integrating Messaging into the Platform
To avoid reliance on external tools (email, WhatsApp).
Increase in booking conversion rate
Driven by clearer pricing, inclusions, and deposit flexibility
Reduction in manual coordination
Less reliance on emails and external tools
faster time-to-booking
From discovery → confirmed reservation
increase in booking completion (via deposit payments)
Enabled by deposit-based payment model
The biggest challenge wasn’t designing screens , it was designing a system where multiple users, data, and actions connect seamlessly without breaking the experience.
This will hide itself!