Everything works, but only because you're there.
We sit down with you and write down what your team does when something goes wrong.
See a no show handled
Built for short let and serviced accommodation operators
We write down how your operation runs, automate the jobs that keep slipping, and put an AI ops manager in your team's Slack. Done for you, and running in our own operation every day.
It starts with one call, and you'll hear what we'd build first and what can wait.
SITS ON WHAT YOU ALREADY RUN
Hostaway or any major PMS that opens its API, your booking channels, your team's Slack and your guests' WhatsApp. Nothing gets ripped out to make room for it.
Booking channels connect through your PMS.
WHAT WE BUILD
It's a build we do for you, not software you sign up to. Most operators recognise more than one of these, and we start with whichever hurts most.
We sit down with you and write down what your team does when something goes wrong.
See a no show handledWe make the daily checks run on their own, and your team gets told what needs chasing.
See a deposit caughtWe add a check that reads the guest messages too, so a clash gets caught before anyone says yes.
See a clash stoppedYour team asks OpSmithOs, an ops manager in their work chat, and gets the answer you'd give.
See your team ask itWe sit down with you and write down what your team does when something goes wrong, so whoever's on shift does what you'd have done.
Today, it's in your head
2hours on, and nobody's told the guest
Your VA13:40
You14:05
Your VA14:50
You15:20
The guest15:40
The guest's nearly there, nobody's told them, and it's all on you.
Once it's written down
0messages to you
The page your VA opens
The cleaner hasn't turned up
Your VA, to the guest13:50
Sent ten minutes after the cleaner didn't show
The guest knows by ten to two, and you read about it later, in the end of shift summary.
Whoever's on shift does what you'd have done, and you only hear about the ones that are genuinely yours.
Your team knows these jobs matter, and on a busy day they're the first to go. We make each one run on its own and tell your team what needs chasing.
Today, someone has to remember
17:00is when you find out
Your VA17:02
Your team knew. The check just lost out to a busy day.
Once it runs on its own
08:00is when your team knows
The arrivals check, in your team's Slack08:00
Three guests arrive today.
Your VA08:04
Sorted at eight in the morning, not at the door at five.
The checks get done every day, however busy it gets, and your team only hears about what needs chasing.
The first time this ran on our own operation, it found 5 arrivals with no deposit recorded.
The same goes for
Enquiries answered in about 40 seconds
Every calendar you manage gets checked and the reply written. By hand that's 45 minutes of searching, and the homes nobody got round to checking never get offered.
Watch an enquiry answered (1:08)Landlord statements checked in one go
At month end in ours, 31 were checked, 29 were ready to send, and the other 2 came back with what was holding them up.
A morning briefing for your team
Before the first guest message, one post says who's arriving, who's leaving, and which homes have one guest out and another in the same day.
A rule only checks what you told it to check. This also looks at what you'd have looked at yourself, and tells your team before anyone says yes.
The guest in your flat, on Monday
A new booking request, on Wednesday
With the calendar check on its own
2guests, one front door
Your VASunday, 15:10
YouSunday, 15:12
The calendar said free, so it went through. Now it's a refund, a bad review and your Sunday.
With the AI layer on that check
Answered in about12seconds
Your VAWednesday
What comes back
The dates are free and the price is right.
But don't accept it yet. The guest already in that flat asked on Monday to stay another week.
Offer the new guest the three bed nearby instead. It's available for the whole month.
The reply, written for the new guest
Your VA reads it and presses send
Both guests housed, both bookings kept, and you never get the phone call.
It checks what you'd have checked yourself, so the odd ones stop landing on you.
It's the same with
A free house with a broken shower
Your VA asks for an offer on a house that's free tonight. It sees the only shower's still waiting on a repair, and offers the home nearby instead.
A price per night, for the whole summer
A guest asks your nightly price for a stay that runs most of the summer. It quotes by the month instead, so the total doesn't look enormous and your rate holds.
OpSmithOs is an executive ops manager that lives in your team's Slack, paired with a front desk that reads your guest inbox. It's the three layers before this, joined up: your team asks it anything they'd have asked you, and it answers the way you would. And because it's the same judgement on both sides, what a guest said last night is already known when your VA asks this morning.

ONE WEEK IN OUR OWN OPERATION, ABOUT 60 DOORS
From OpSmithOs's seven day report, July 2026.
How it used to go
1more question for a founder
Our VA
A founder, hours later
Our VA, to the guest, the next day
It waited for a founder, then it became a polite no.
Now, our VA asks OpSmithOs
About15seconds
Our VA
OpSmithOs
I've checked every home bed by bed. Only one has eight separate beds, and it's booked.
I won't send them something that doesn't fit. Pass this one to another operator and we earn commission.
For next time: eight separate beds means one property. Search by separate beds, not by how many it sleeps.
The reply, written for the guest
Our VA read it and pressed send
An enquiry we couldn't house paid us anyway, and the team does that every time now.
Four more it handled the same month
A guest made a low offer on a long stay.
It suggested a counter offer, and when our prices changed mid conversation it told the founder his own counter was now too low.
A guest's dates moved.
It answered what it was asked, then reminded our VA the clean had to move too, so nobody arrived to a dirty flat.
An enquiry came in for an area we don't cover.
No process existed, so it wrote one, asked for a yes, and uses it on its own now.
Our VA asked for something only a founder can approve.
It said so, and sent him the decision with what it would do, not a question to work out.
The front desk is your guest inbox. It reads every message that comes in, works out who needs to deal with it and drafts the reply. Here the cleaning team gets the job, and nothing reaches the guest until one of your team sends it.
A guest, at eight at night
The reply OpSmithOs drafted
Waiting for one of your team to press send
WATCH IT WORK
Filmed from jobs that run in our own operation, done by OpSmithOs, the full version. Every layer before it can be built on its own.
WHY IT EXISTS
We run about 60 doors in the UK with a small remote team. We had the SOPs, but nobody reads an SOP when a guest is waiting, so the calls still came to us, and the more doors we added, the more slipped through. We built the systems first, then the thing that makes the call the way we would. Now most of the team's questions never reach us, problems get caught before guests find them, and day to day it's a lot simpler.
Once we start scaling and the company starts growing, we only become more busy, and only more things slip through the cracks. We're only human, which is why we need to build out, so that if a human makes an error, the system catches it.
From OpSmithOs's daily reports, July 2026.
Moe, founder, AltoLuxo
Everything on this page runs in our operation before it gets built into yours.
QUESTIONS
It's a service that leaves you with your own systems. We write your processes and build the systems and the AI around how you already run, done for you. OpSmithOs is the full version, and you can stop before it. There's nothing to sign up to and set up yourself.
Four layers, in this order. The operation itself: written processes, decision trees, roles, and a clear line between what your team decides and what comes to you. Then the systems that run the recurring jobs on your live data, like enquiries, pre arrival checks and month end. Then an AI layer for the situations no process covers. And OpSmithOs, which joins all of it up in your team's own channel. You can stop at whichever layer your operation needs.
Yes, that's the first layer, and for a lot of operators it's the most valuable one. We go through how you run things today, including the habits nobody's written down, and build it out from there: decision trees for lockouts, heating, refunds, double bookings, deposits and cancellations with the message to send at every end point, roles with an owner and a backup, the shift routine, and a month long onboarding path for new VAs. It's written from your operation, not a template, and you own all of it.
Not for you, no. We manage our own portfolio of about 60 doors in the UK, but we don't take over yours. You stay the operator. What we build is everything behind it, the processes, the systems and the AI, taken from how we run ours.
Most of the jobs everyone agrees matter and nobody gets round to on a busy day: checking an enquiry against every live calendar, pre arrival checks for missing deposits and access details, month end statement readiness, the morning brief, handovers between shifts, chasing unanswered guests and stale tasks, and keeping payments and the property database clean. In our own operation the enquiry check takes about 40 seconds for the whole portfolio, where the searching by hand used to take 45 minutes.
Yes, wherever your PMS opens its API. Ours runs on Hostaway. On Guesty, Lodgify, Hospitable or another major PMS, it gets built on top of yours through that API and reads the same live calendars and reservations your team uses. A few only open their API on certain plans or by invitation, so that gets checked on the first call. Nothing gets ripped out to make room for it.
For your guests, yes. It reads your guests' WhatsApp alongside the Hostaway inbox and drafts the reply or the escalation for every message. Your team talks to it in Slack, which is where ours runs it. The team side isn't live in WhatsApp, so if your team lives in a WhatsApp group, say so on the call and you'll get a straight answer on what that would take.
Not until you've decided it should. OpSmithOs starts in shadow mode: it reads each message and proposes the reply or the escalation, your team carries on as normal, and nothing gets sent on its say so. Anything that moves money or can't be undone stays with you either way.
No, it makes them better at the job. Every answer comes with a line on why, so your VA learns the call, not just the answer. Put that next to a written onboarding path and a new VA can be trusted inside a month. What it takes away is the waiting: on a calendar, on somebody senior, on you.
It depends entirely on what gets built, which is why there's no price list. Some operators need the processes written and nothing else, some need two systems, some want the whole stack. One conversation scopes it, and you'll get a straight answer, including when the answer is that you don't need the AI part yet.
WORTH A CONVERSATION
Bring the job that keeps losing out on a busy day, or the call that still waits for you. You'll come away knowing what we'd build first and what can wait.
WHAT HAPPENS NEXT