01 · case study
Onemineral
A property management system for short-term rentals.
(Now RentalWise.)
scope
Product design across PMS, calendar, bookings, CRM, and channels. Foundations library. Responsive desktop and mobile.
role
Lead product designer. Foundations to surfaces.
client
OneMineral. Property management software for vacation rental operators.
A product for property managers running dozens of short-term rentals across Airbnb, Booking.com, VRBO, and their own websites. The interface had to hold dense operational data, bookings, calendars, pricing, channels, and reviews, without feeling like enterprise software.
The brief was deceptively simple. Make complex feel manageable. The answer was not to start with screens. The answer was to start with the system underneath them.
02 · foundations
The system underneath
the product.
A foundations library of tokens, components, and patterns. Designed first, used everywhere. The library kept the product consistent as it grew across PMS, calendar, bookings, CRM, and channels.
03 · the multi-calendar
Sixty properties.
One calendar.
The hardest visualization problem in property management is showing many properties across many dates, with bookings, pricing, and restrictions overlapping on each cell. Most PMS products solve it with two screens. A list for properties. A separate calendar for dates. OneMineral solves it with one.
Properties down the left edge as rows. Dates across the top as columns. Bookings render as horizontal pills that span their actual duration. A guest's name, party size, and total value live inside the pill. Hover any cell for restrictions, pricing notes, or maintenance windows.
04 · property pages
Every property is
a small dashboard.
A property in OneMineral is not a record. It is a workspace. The detail page collects bookings, calendar, discounts, channels, reviews, and settings into a single tabbed surface. The right column carries everything secondary: accounts, notes, channel connections.
05 · bookings
From list
to receipt.
Bookings are where money moves. The list view shows what needs attention. Status pills for booking state. Colored due dates for payment urgency. Channel attribution per row.
The summary page breaks down a single booking into its parts. A donut for paid versus scheduled. A stacked bar for cost composition. Booking products as an editable line-item table. The right column collects everything secondary: guests, dates, payment status, source, notes, cancellation policy.
06 · reflection
System over surface.
Product design at this scale is not a screen problem. It is a system problem. The foundations library was built first. Every screen that followed was an instance of the system, not an invention.
That order matters. When a new feature needed shipping, it slotted into existing components, not new ones. When a new designer joined, the library taught them the product before any screen did. When the company rebranded from OneMineral to RentalWise, the foundations carried over almost unchanged. The system outlasted the name.
Now Rentalwise.