Product · In development
Sentro HQ
One inbox and one calendar for boutique accommodation operators in Southeast Asia, so no enquiry slips past and no month is a mystery.
The problem
I run the website for a small surf B&B, so I’ve watched this happen from the inside. A guesthouse of that size is spoken to from everywhere at once: Facebook messages, Instagram replies, Booking.com, Agoda, Expedia, Airbnb, and its own website, and answered from none of them reliably. Enquiries go quiet in a channel nobody checked that day, some of them worth a whole wedding or a corporate block. And because every booking site keeps its own records, no one can see the season whole.
The operators losing these bookings aren’t careless. They’re running a property with their hands full, across seven inboxes that don’t speak to each other.
What it does
The unified inbox
Facebook and Instagram messages gathered into one list of what hasn’t been answered: who wrote, what they asked, how long they’ve been waiting, with high-value enquiries (events, whole-resort takeovers, corporate stays) flagged so they’re never the ones that wait.
The booking calendar
Confirmations from the booking sites are read automatically as they arrive by email, and calendar feeds from Airbnb and the property’s own website are pulled alongside them: one occupancy timeline, colour-coded by channel, in place of six separate ledgers.
How it’s built
Next.js and Supabase, with n8n running the data pipeline and Claude doing the reading: parsing booking emails and understanding what a guest is actually asking for. Built for its first property but multi-tenant from the first table: nothing in it assumes there will only ever be one guesthouse.
Where it stands
Version 0.1 is live for its first property, watching seven channels. Replies from inside the dashboard, AI-drafted responses, and onboarding for further properties are on the roadmap, in that order. [Update as it progresses.]