Adhilokha

A booking platform for a luxury villa collection

Eighty properties across Bali, Lombok, and the Nusa Islands, bookable in four currencies from one platform.

Worked with: Adhilokha
Type: Web Platform
Role: Product design, full-stack build, property CMS
Duration: 16 weeks
Year: 2026

The challenge

Adhilokha had spent over a decade building something a website is genuinely bad at carrying: a collection of eighty villas, each handpicked, each with its own character. The portfolio had outgrown the way it was being shown. Guests arriving from four continents were quoted in one currency, browsed listings that read like inventory rather than places, and reached the end of a property page with nowhere to go but a phone number. A collection sold on discernment was being presented as a list.

Our approach

We started from how guests actually search, which is almost never by name. They arrive knowing a region and a shape of trip, say Uluwatu, seven bedrooms, a villa rather than a resort. So city and property type lead the interface and everything else follows from what those two choices leave. Pricing switches between USD, IDR, EUR, and CNY without leaving the page, because a rate a guest has to convert in their head is a rate they read as an obstacle. And the listings are built around the photography rather than around a data table: a villa in Sanur and a villa in Uluwatu are not two rows differing by a field, and the page should not pretend otherwise.

Search the way guests arrive
Nobody opens a villa site knowing which villa they want. They know a region, a rough size, and whether they are after a villa or a resort. Those are the two controls that lead, and the collection narrows from there rather than asking for a name it does not have. Sort and the remaining filters sit behind that first decision, where they are useful rather than in the way.
City and property type lead; the collection narrows from there.
Four currencies, one page
The collection sells to guests arriving from four continents, and a rate someone has to convert in their head reads as friction whatever the number is. USD, IDR, EUR, and CNY switch in place, with no reload, no separate regional site, and no arithmetic asked of anyone. It is a small piece of engineering that removes a large piece of hesitation.
Properties that read as places
A luxury villa is not a row in a table. Each property leads with its photography and carries what a guest actually decides on: bedrooms, bathrooms, capacity, and the handful of features that make it that villa rather than the one before it. The nightly rate is stated plainly rather than buried behind an enquiry, because a collection confident in its properties has no reason to hide what they cost.
Enquiry where the guest already is
In this market the conversation happens on WhatsApp, and pretending otherwise costs bookings. So the enquiry route is WhatsApp from any property page, arriving with the property already attached. The guest does not restate what they were looking at, and the team does not open a thread by asking.
The half nobody sees
A collection of eighty properties is only as current as the person editing it, so the admin behind this platform was designed with the same care as the front of it. The team adds a villa, orders its photography, sets rates per currency, and publishes, without a developer and without a ticket. That is the difference between a site that is launched and one that stays true a year later.
The CMS the team runs the collection from, built to the same standard as the public site.

The outcome

Adhilokha now runs discovery, property management, and enquiries from one platform. Guests browse the full collection in their own currency and reach the team over WhatsApp from any property page, with the context of what they were looking at already carried across.