OpSmithOs

Built for short let and serviced accommodation operators

Everything a proper short let company runs on, built around you, with AI behind it.

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.

Not software you sign up to·Built on the tools you already run·You stay the operator

SITS ON WHAT YOU ALREADY RUN

It plugs into the stack 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.

  • Live in our own operation today
  • Connects through its API

Not listed? If it has an API, it gets built around.

See every system it connects to

Property management

  • Hostaway (Live in our own operation today)
  • Guesty (Connects through its API)
  • Lodgify (Connects through its API)
  • Hospitable (Connects through its API)
  • OwnerRez (Connects through its API)
  • Smoobu (Connects through its API)
  • Beds24 (Connects through its API)
  • Uplisting (Connects through its API)
  • Hostfully (Connects through its API)

Booking channels

  • Airbnb (Live in our own operation today)
  • Booking.com (Live in our own operation today)
  • Vrbo (Live in our own operation today)

Booking channels connect through your PMS.

Where your team and guests talk

  • Slack (Live in our own operation today)
  • WhatsApp (Live in our own operation today)
  • respond.io (Live in our own operation today)
  • Discord (Connects through its API)

Pricing

  • PriceLabs (Connects through its API)
  • Wheelhouse (Connects through its API)

Operations and tasks

  • monday.com (Live in our own operation today)
  • Miro (Live in our own operation today)
  • Breezeway (Connects through its API)

Payments and records

  • Stripe (Live in our own operation today)
  • Google Drive (Live in our own operation today)

WHAT WE BUILD

Which of these sounds like your operation?

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.

  1. 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
  2. Your team knows what to do. They just can't get round to all of it.

    We make the daily checks run on their own, and your team gets told what needs chasing.

    See a deposit caught
  3. It all runs, until something doesn't fit and lands on you.

    We add a check that reads the guest messages too, so a clash gets caught before anyone says yes.

    See a clash stopped
  4. Every question still comes to you, and you can't be on every shift.

    Your team asks OpSmithOs, an ops manager in their work chat, and gets the answer you'd give.

    See your team ask it

A business that runs the same way, regardless of who's on shift.

We 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.

Let's say your cleaner doesn't turn up, and the guest checks in at four.

An example, not a recording

Today, it's in your head

2hours on, and nobody's told the guest

Your VA13:40

Cleaner hasn't turned up. Guest checks in at four. What do I do?

You14:05

Try the backup cleaner.

Your VA14:50

She can't do it. Can I move the guest, and what am I allowed to offer?

You15:20

Leave it with me.

The guest15:40

Hi, we're about twenty minutes away. Is the flat ready?

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

  1. Is the backup cleaner free?Book her, and tell the guest the new time.
  2. Not free, but another home is?Offer the guest the move, and spend up to what you've agreed.That's today
  3. Neither?Send the guest a holding message, and one line to you.

Your VA, to the guest13:50

Really sorry, your flat won't be ready in time today. We can move you to another of our homes nearby instead. Does that work for you?

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.

Everything we write down for you (9)
  • Decision trees for what actually happens

    Lockouts, heating, refunds, double bookings, deposits, cancellations. Each mapped to the last message, with the reply to send at every end point.

  • Roles, and who to go to for what

    Every job has an owner and a backup, so a problem lands with whoever can fix it, not whoever's online.

  • A clear line between what the team decides and what comes to you

    What a VA approves, what goes to ops, and what only you sign off: anything that moves money or can't be undone.

  • A shift that starts and ends the same way every time

    Every inbox swept in the same order at clock in, and a handover at clock out that anyone can act on.

  • One place the truth lives

    A property database for access, beds, compliance dates and landlords, and a board for every kind of work.

  • A new VA you can trust inside a month

    Video first, weekly checkpoints judged on real messages, and a clear keep or release call at the end of the month.

  • New doors that go live without dropping anything

    From the landlord conversation to the first booking, every new door goes in the same way.

  • Landlords who get answers before they ask

    A record of what every owner wants, and a monthly statement that explains how the property did.

  • The numbers you run the business on

    Starting with how many times a week your team still needs you, and the checks that say the operation's healthy.

Next02 The systemsthe jobs a busy day skips

The jobs that lose out on a busy day now run on their own.

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.

Let's say three guests arrive today, and one of them hasn't paid their deposit.

An example, not a recording

Today, someone has to remember

17:00is when you find out

  1. 08:00Check today's arrivals for deposits. It's on your VA's list.
  2. 08:10Ten enquiries come in.
  3. 10:30A boiler breaks.
  4. 17:00The guest arrives, and nobody took the deposit.

Your VA17:02

Guest's at the door and there's no deposit on the booking. Do I let them in?

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.

  • Two bed flat, arriving at fiveNo deposit paid yet. Send the deposit link.
  • The other twoDeposit paid, check in details sent.

Your VA08:04

Deposit link sent.
  1. 16:00Checked again before arrival. The deposit's in.

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.

Everything we can run for you (8)
  • Enquiries answered against your live calendar

    Runsall day

    Every door checked against its live calendar, beds and head count, the ones that fit ranked, and a reply written.

  • Pre arrival checks that run themselves

    Runstwice a day

    Every arrival checked for deposit, check in message and access details, with what to do about anything missing.

  • Month end without the chasing

    Runsend of month

    Every landlord statement checked, the ready ones marked, and anything blocked sent back with the link that fixes it.

  • A brief before the first message of the day

    Runsevery morning

    Arrivals, departures, which deposits are in and the same day turnovers, in one post.

  • Handovers that don't lose anything

    Runsevery clock out

    Checked against the task boards, so the next shift gets what genuinely needs doing first.

  • No guest left waiting on an answer

    Runsevery few minutes

    Unanswered escalations get the person on shift tagged, checked against the PMS rather than someone's word.

  • Tasks that chase themselves

    Runsseveral times a day

    Stale tasks nudged to their owner, and small maintenance jobs kept on one list per property so none get lost.

  • Payments and records that stay clean

    Runsevery half hour

    Chargebacks flagged with their deadline and failed payments raised early. The property database gets checked for gaps every week.

Next03 The AI layerthe thing nobody wrote a rule for

Your systems handle what's expected. This handles what isn't.

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.

Let's say a guest asks to stay another week, and then someone books that same flat for a month.

An example, not a recording

The guest in your flat, on Monday

Any chance we could stay on another week? Happy to pay the same.

A new booking request, on Wednesday

One month in that same flat, starting Sunday. The calendar shows the dates as free.

With the calendar check on its own

2guests, one front door

  1. The dates are free.
  2. The price is right.
  3. The booking's accepted. Nobody read Monday's message.
  4. SundayTwo guests are standing at one front door.

Your VASunday, 15:10

The new guest's arrived and the other one hasn't left. He says he asked to stay. What do I do?

YouSunday, 15:12

I'm on my way over.

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

Can we take this month long booking?

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

Thanks for your interest in those dates, we'd love to host you. We're finalising dates with a current guest for part of that window, so can I offer you a three bed home with a garden and parking, available for your full stay?

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.

An SOP is your judgement, written down once and already out of date. This is your judgement, on shift.

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

questions our team asked it instead of asking us
612
sorted with no ops lead, no ops manager and no founder
88percent

From OpSmithOs's seven day report, July 2026.

A group of eight wanted one house, with a bed each. We didn't have one.

What it did here is real, names taken out

How it used to go

1more question for a founder

Our VA

Group of eight want one house with a bed each. Nothing fits. Do I just say no?

A founder, hours later

Leave it with me.

Our VA, to the guest, the next day

Sorry, we've nothing available that fits.

It waited for a founder, then it became a polite no.

Now, our VA asks OpSmithOs

About15seconds

Our VA

A group of eight want one house, with a bed each. What have we got?

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

For eight separate beds in one property we don't have the right fit, so I won't send you something that doesn't match. We can source it through our operator network and handle it end to end.

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.

On your front desk, it drafts every guest reply, and a person presses send.

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.

An example

A guest, at eight at night

Hi, grateful if the sofa bed could be made up. Many thanks.

The reply OpSmithOs drafted

Of course. We've passed this to our cleaning team, so it's made up before you arrive.

Waiting for one of your team to press send

You know the call made when nobody was watching is the one you'd have made.

WATCH IT WORK

Watch three jobs your team does every day get done properly.

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.

  1. Answering an enquiry

    One enquiry from start to finish: every calendar checked, the reply written, and nothing that fits left out.

    Read the script

    A booking provider emails. Their client starts Monday for eight weeks, and they want options.

    By hand, your VA checks the calendars one property at a time. Forty five minutes later, they've done five.

    The rest never get opened, so they never get put forward. That's gaps in your occupancy, money lost, and a morning gone.

    So instead, they ask OpSmithOs.

    It checks all forty five properties, works out the distance from where they're working, works out the rates, pulls in the photos, and writes the guest ready message.

    About forty seconds later, it's ready to send. Seven homes, nearest first, plus three that free up a few days later.

    That's forty five minutes your VA gets back, to get to the next enquiry quicker, look after the guest who's waiting, or sort the maintenance job before it turns into a complaint.

    And because every property gets checked, nothing's missed, and they all get put forward. You're first to reply, ahead of every other operator, and that's what closes enquiries and brings in the money.

  2. The thing nobody asked about

    An open repair caught before the guest arrives, and the booking still lands.

  3. Your front desk, after hours

    A guest messages at night. The job goes to the right team and the reply's drafted, ready to send.

    Read the script

    It's eight at night, and a guest messages.

    Before OpSmithOs replies, it decides who should own the message.

    Sofa bed made up? OpSmithOs picks that up. It drafts the reply, then passes the job to your cleaning team.

    An Airbnb alteration? That's a team call, so it escalates it with the next steps. The new dates are free, they're in demand, so push for a higher rate.

    And it isn't reading from a script. Whatever your team agreed in Slack, with the founders or your ops manager, or what your maintenance contact said on WhatsApp, OpSmithOs is aware of it.

    So tonight's reply is up to date with what's actually going on.

    In shadow mode it drafts every reply, and a person presses send.

    So nothing goes to a guest that your team wouldn't have said.

WHY IT EXISTS

We built it because our operation ran on two people's heads.

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.
Moe, in a team meeting, 30 June 2026Lightly edited for clarity, nothing added.
Times a day the team needed a founder, four days running in July. It fell from four to one.
4 · 4 · 2 · 1

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

What short let operators ask before they start.

Is this software, or a service?

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.

What systems does a short let business actually need?

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.

Can you write the SOPs and decision trees for my serviced accommodation business?

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.

Are you an Airbnb management company?

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.

Which parts of a short let business can run automatically?

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.

Does it work with Hostaway, Guesty or my PMS?

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.

Does it work in WhatsApp as well as Slack?

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.

Will an AI start messaging my guests?

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.

Will this replace my VAs?

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.

How much does it cost?

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

Tell us what's costing you, and you'll hear what we'd build.

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

  1. A call about where it actually hurts.
  2. Your operation mapped as it really runs, habits included.
  3. Built alongside your team, with the AI in shadow mode first.
  4. It keeps getting better, and your team needs you less.

OR START HERE

Straight to the founder's inbox. Tell him what you would want built and he will tell you what that actually looks like on your door count. If you would rather just book a slot, the button above does that instead.

How many doors

This lands in the founder's inbox. Nothing is stored on this site and nothing is tracked.