Skip to content
Flexible livingHeadless WordPress

Sentral

The same apartment is sold three ways depending on how long you want it, and the site has to make that a choice rather than a confusion.

Sentral: the live site
Our role
Frontend team on the booking experience
Timeline
5 months
Team
Lead engineer, two frontend engineers

3

Stay lengths

nightly, monthly, long-term

Multi

Cities

location-led search

Headless

WordPress backend

property content per building

01

The problem

One building, three different customers

Sentral operates apartment buildings that serve travellers wanting a few nights, professionals wanting a few months, and residents signing a lease. Same units, three completely different purchase decisions.

There is also a fourth audience: real estate partners and investors, who need the operator's credentials rather than a booking flow.

Fitting all of that into one homepage without it becoming a menu of menus is the actual design problem.

02

What we did

Lead with location, branch by intent

The homepage leads with a single location selector, because whichever customer you are, the first question is which city. Stay length branches after that rather than before it, which keeps the entry point simple.

Property content is managed in WordPress and consumed headlessly, so each building's description, amenities and imagery are maintained by the operations team in an admin they already know. Opening a new location is a content task rather than a release.

Real estate sits in the main navigation as its own destination rather than being buried in a footer, because that audience arrives deliberately and should not have to hunt.

A rewards programme threads through the experience for the repeat-stay segment, which is where the margin is in flexible living.

  • Location-first search as the single entry point
  • Stay length as a branch after location, not before
  • Headless WordPress for per-building content and amenities
  • Separate real estate track for partners and investors
  • Rewards programme for repeat stays
03

The outcome

Three products, one coherent front door

Travellers, monthly stayers and residents all start in the same place and end up in the right flow, while the operations team manages the property content itself.

What it is built on

Frontend

  • React
  • JavaScript
  • Responsive UI

Content

  • Headless WordPress
  • WP REST or GraphQL
  • Per-property content model

Tooling

  • Sentry
  • GA4
  • Accessibility overlay

What we learned

  • 01

    When one inventory serves several intents, branch after the question everyone shares rather than making people self-classify first.

  • 02

    A content layer is what makes opening a new location a content task instead of a release.

Next step

Tell us what you are trying to build.

Thirty minutes with the engineer who would lead the project. You will leave with an opinion on what to build, what to skip, and roughly what it costs, whether or not you hire us.

2 build slots open · Next start: early next month

What happens next

  1. 1You send a few lines about the product and the deadline
  2. 2We reply within one working day with times
  3. 3A 30-minute call, no deck, no sales script
  4. 4A written summary and a ballpark range within 48 hours