CONCEPT DEMONSTRATION — NOT A CLIENT CASE STUDY
Boutique hospitality
Solara House: one fictional hotel, the whole approach.
A fictional 28-room boutique hotel on a coastal town square, invented by BSTS to show — concretely — what keep, connect, automate, build, and secure look like in hospitality.
Before
The stack Solara House starts with
Nothing here is broken, exactly. Everything is simply alone.
The systems
- Property management systemSolid, staff knows it cold — kept
- Point of sale (restaurant & bar)Reliable, but an island — kept, connected
- Booking engine + two OTA channelsRates updated by hand in three places
- Spreadsheet guest-preference logMaintained by one veteran front-desk lead
- Shared inboxWhere special requests go to be forgotten
The daily frictions
- A reservation is touched by hand up to four times before check-in
- Guest preferences survive only if the right person is on shift
- The nightly report takes 40 minutes of copy-paste after close
- No one can say which packages actually sell without an afternoon of digging
The engagement
Five moves, in the order the method demands.
Keep first — always. What survives the keep decision defines what connect, automate, build, and secure have to work with.
- 01 · Keep
The PMS and POS stay
Both systems work and the staff is fluent in them. Replacing either would burn a year of muscle memory for zero guest-visible gain. They are documented, secured, and kept.
- 02 · Connect
One guest record, everywhere
The PMS, POS, and booking engine are joined through their existing APIs. A dietary note captured at booking now appears on the restaurant's seating sheet automatically.
- 03 · Automate
The repetitive middle of the guest journey
Confirmation, pre-arrival, and post-stay messages compose themselves from the unified record and go out on schedule. The nightly report assembles itself at close. Staff review, they no longer re-key.
- 04 · Build
A small AI concierge assistant — drafts only
An assistant drafts replies to routine guest emails from house knowledge: hours, parking, late checkout policy. Every draft waits for a human send. It never invents policy and never touches payment data.
- 05 · Secure
A baseline informed by NIST CSF 2.0
Access review, least privilege on guest data, encrypted backups, and a one-page incident plan the whole team has read. Security sized to a 28-room operation, not a compliance theater production.
After
What changes for the team
The guest never sees the plumbing. The team feels it every shift.
- A reservation is entered once and flows to every system that needs it
- Guest preferences belong to the house, not to whoever is on shift
- The nightly report is waiting at close instead of costing 40 minutes
- Routine email is drafted by software and approved by people
- The owner can see package performance without an afternoon of digging
A note on honesty
Because Solara House is a demonstration, we attach no invented numbers to it — no fictional revenue lift, no imaginary satisfaction score. It shows the shape of the work, and the shape is real.
Go deeper
Solara House lives inside BSTS OS, too.
The demonstration data in our operating system — prospect record, assessment, roadmap, projects, risks, and decisions — is this same fictional hotel. Explore it interactively, or start the assessment for your own property.