Building the operating system for a short-term-rental portfolio.
The live command center · app.solneststays.com
Ryan runs four short-term rentals, two in Prince George, two up the mountain in Sun Peaks. Two markets, two seasons, four sets of keys, and a phone that buzzed at 1 a.m. when a guest couldn't find the lockbox code.
Every part of the operation lived in a different tab. Hospitable held the bookings, PriceLabs set the rates, Notion held the manuals, GoHighLevel passed for a CRM. None of them talked to each other, and none could answer the only two questions that mattered on a Sunday night: are we pacing ahead of last year, and is anything on fire right now?
This is the system that replaced the tabs. Seven agents and twenty-nine workflows quietly pull, price, answer and alert around the clock.
A deterministic Python pricing engine (fifteen modules, a hundred and sixty-four tests) reads comps, pace and orphan nights each night and files nearly two thousand pricing decisions. The model never sets a price; the numbers do.
Guest messages arrive HMAC-signed, get classified and answered against each property's knowledge base, then wait for a human tap. 273 messages handled, a 37-minute average response, 69% positive sentiment.
Turnovers, arrivals and red flags synthesised into a daily brief; seventeen signal detectors that file written insights, then grade their own calls a week later.
A CORTEX cycle runs the whole fleet on demand, but most days the agents fire on their own cron schedules. The portfolio runs unattended, and version-controlled as code.
Each tool writes into its own staging path, gets normalised, and lands in one canonical schema, so everything reads from a single, trustworthy source.
Pulls, normalises, schedules
Every record, reconciled
Real-time, always current
A guest message from the internet is never trusted on face value. The chain that carries it is HMAC-signed end to end, verified inside a five-minute replay window, deduped against a nonce, and rate-limited, verified before it was ever trusted with a real guest.
The most important product decision was that the agent does not send. "Most of the time" is exactly wrong for the message that tells a guest the wrong check-in date. The owner's reputation never rides on the model being right unsupervised.
A rollup once wrote a thousand rows dated into next year. Nothing crashed; the numbers simply stopped meaning anything. A number that is wrong but confident is more dangerous than no number. The activity log made the bad rows findable.
“It is the operating system for a short-term-rental portfolio, not a dashboard bolted onto six other tools.”