All work
Client workLive

Stay With Kaelo

Two staff can never confirm the same nights.

Visit staywithkaelo.com
What
Real estate website: serviced apartments and property management
Year
2026
Status
Live
Runs on
Website + an admin that installs on a phone (PWA)
Home, demo data
The live site, 12 Nov 2026. No guest data.
The goal

One place for the whole stay, from the first enquiry to the morning someone leaves, and for the owners whose homes Kaelo manages.

We built the website and team admin for Stay With Kaelo, a Lagos brand of serviced apartments and private villas that also manages homes for their owners. Guests browse every stay, check dates and get a quote for their exact nights; owners can list their property; the team runs every enquiry, booking, arrival, stay, photo, price and the main pages from one admin.

The problem

The bad days it removes

  1. 01

    Two staff confirm the same Friday for two guests

    If two people confirm the same nights at once, one goes through; the other is told no.

  2. 02

    The price on Instagram isn’t the price on WhatsApp

    The price is worked out once, and the enquiry keeps the number the guest saw.

  3. 03

    A stranger turns up at the gate

    Guests see the neighbourhood, not the gate. The address goes out only after confirmation.

  4. 04

    Three phones, no inbox

    Every channel lands in one list, each with a status.

  5. 05

    The arrival-morning scramble

    The day opens on who’s arriving and who’s leaving, each message already written.

The solution

What we built

For guests and owners

  • Search by free dates, a quote for the exact nights
  • Video tours that keep playing while a new one uploads
  • One shortlist link instead of ten photos
  • A page for property owners to list their home

For the team

  • Front desk and managers see different jobs
  • Booking decisions leave a history nobody can edit
  • Booked nights show as taken, never why
  • New staff practise on sample bookings, cleared in one action
Why a PWA

The admin installs on the team’s phones, and the guest site holds up on a weak network.

  • The admin installs as an app, with alerts per device
  • A guest’s number never shows on a lock screen
  • When the network drops, the guest site still opens; prices and calendars always load fresh

Why we build web apps that install: one link to share, no app-store wait, updates the moment they ship, and one codebase for the phone and the desk.

Proof
Automated checks
Run 9 Nov
Browser steps
Driven in real Chrome
Built with
Next.js 16React 19SupabasePush alertsVideo toursMaps