OPSMITHOS. WHAT IT ACTUALLY CHANGED.
Not a feature list. This is a 60 door operation, area by area, with the numbers that came out of it and the mistakes that got caught on the way. Names are out. Nothing else is dressed up.
COMPATIBILITY
BEFORE
Operators hear an ops bot in Slack and assume it means ripping out the PMS to fit it, or moving a team that has finally settled onto WhatsApp across to some new app just to get the benefit. Neither is true, and both are reasons a genuinely useful tool sits unused: the operator never gets past the assumption to find out.
NOW
It sits on top of whatever PMS is already running the business, Hostaway, Guesty or anything else, and reads the same live calendars and records that system already holds. It talks to the team inside whichever tool they already use for internal comms, Slack, WhatsApp or Discord. Nothing about how the team already works has to change for this to start working.
WHAT THIS BUYS YOU
What this buys you is not having to migrate anything to get the benefit. That means the platform you already pay for and the habits your team already has both stay exactly as they are, so adoption is not a second project sitting on top of running the business. The weeks a migration would have cost go straight back into actually using the thing, and you stop worrying that getting this means tearing up a system that already works and retraining a team that has already settled.
This is the ops side only, the layer that runs your team, not a guest facing product. It does not message guests and it is not the separate guest communication AI some operators already run alongside their PMS. Keeping the two apart matters: this is the executive ops manager for your team, not a chatbot for your guests.
IF YOU ARE THE FOUNDER
What this buys you is one less reason to put this off. You are not choosing between your PMS and this, and you are not asking your team to relearn where they talk to each other. That means the only real decision left is whether the operation gets easier to run, not whether the switch is worth the disruption, and you stop worrying that adopting this means a migration project you do not have time for on top of everything else.
IF YOU ARE ON THE TEAM
What this buys a VA is nothing new to learn about where to talk, because it shows up in Slack, WhatsApp or Discord, whichever one is already the team's habit. That means the only new thing is a better answer arriving in the same place they already look, not a new app to remember to open. For the team, adopting this costs nobody a habit they have to change.
MAINTENANCE
BEFORE
A guest reports a fault. The VA has no way to tell a five minute reset from a real callout, so the safe move is always to book a tradesperson, and the safe move is the expensive one. One job replaced a front lock at over £260 when the fault was actually the patio doors, and the spare keys were sitting in the property database the whole time. Nobody looked, because looking depended on somebody remembering to look, knowing where to look, and having the confidence to overrule a guest who has already said what they think is broken.
NOW
The fault goes into the channel and comes back as a diagnosis, not a ticket. It reads the description against that property’s own history, its actual hardware and what has gone wrong there before, then hands the VA the troubleshooting steps in order, most likely cause first, in language they can paste straight to the guest. It reads photographs, so a picture of a leak, a tripped breaker or an error code on a boiler display is diagnosed rather than described. Most jobs close right there, with the VA resolving it and the guest never knowing a contractor was ever a possibility.
WHAT IT ACTUALLY DOES FOR THE VA
It tells them which of the three things it usually is, and which to try first. It tells them whether this property has had this fault before and what fixed it that time. It knows the make and model, so the instruction is for the appliance that is actually in the flat rather than a generic one. It knows where the stopcock, the isolator and the fuse board are, which is the single most common reason a VA cannot help over the phone. And it knows when to stop: anything involving gas, water at the mains, or an electrical fault beyond a reset is escalated rather than talked through, with the reason stated. The VA is not being asked to become a tradesperson, they are being given the first twenty minutes of one.
When a callout is genuinely needed, the tradesperson arrives already knowing the fault, the model, the access arrangements and where the isolator is, so it is one visit instead of two. A standing cost cap lets small jobs proceed without waiting on a signature, so a £40 part does not sit in an inbox overnight while a guest has no hot water. When that cap was once raised above what the management contract’s pre authorisation clause allowed, the conflict was surfaced rather than quietly absorbed.
IF YOU ARE THE FOUNDER
What this buys you is not needing a callout to find out what a photo already told the bot. You stop paying for the wrong part and the second visit to fix the first one, money that used to leave the business before anyone had confirmed there was a real fault. That saving is what keeps the maintenance line flat as you add doors instead of climbing with them, and you stop worrying that a fault you never even see is quietly taxing every property you own.
IF YOU ARE ON THE TEAM
What this buys a VA is the diagnosis already worked out, for the exact make and model in that flat, in the order to try them. That means they fix it themselves in the time it used to take just to describe the fault to somebody else, instead of waiting on a callout that cannot be booked until tomorrow. For the team, a fault stops being a ticket sitting in a queue and becomes a job that closes on the spot, so nobody is chasing a tradesperson's diary for something a photo could have solved.
DEPOSITS
BEFORE
Chasing was reactive. One deposit took 13 separate touches across 23 days. The payment report itself got skipped five times in a single month.
NOW
An audit runs at 08:00 and 16:00 against every arrival in the next 48 hours and flags anything missing or unverifiable, checked against real payment data rather than a field that does not reliably reflect it.
THE DRY RUN
Before it was even fully live, the first pass found five real missing deposits on live upcoming arrivals, two of them checking in that same day. The company had already eaten that exact failure once: no deposit taken, company paid. This time it was caught before anyone walked in.
The check was wrong in both directions before it was right, and both were caught. First it reported no deposit on a booking that held £250. Then, two days later, the opposite. That forced the verdict to become time aware, hold fired against scheduled against lapsed, instead of a yes or no that is right by accident half the time.
IF YOU ARE THE FOUNDER
What this buys you is a check that runs twice a day whether you are thinking about it or not, instead of one that only runs when you remember to run it. That means the five deposits the first dry run caught, before those guests ever arrived, are the normal outcome now, not a lucky one. The attention that used to go on you personally re-running this check goes back into growing the business instead, and you stop worrying that the one thing you forgot is the one that costs you a deposit you can never recover.
IF YOU ARE ON THE TEAM
What this buys a VA is a flag on the specific booking at risk, not a list they have to build themselves by remembering which arrivals are the risky ones. That means they act on one clear task instead of holding the whole arrivals board in their head. For the team, the same catch runs whether the person on shift has done this a hundred times or it is their first week, so the standard stops depending on who is on.
ENQUIRY TO BOOKING
BEFORE
Every enquiry meant a person running a ten prompt ritual: scan the database, check the calendar for the exact dates, work out capacity, hand copy the right card into the reply. Slow, and unreliable with it. One enquiry got answered fully booked all August, then minutes later in the same thread, wide open from the 3rd.
NOW
One call takes the area, the dates and the guest count and returns every viable property with live availability, price ranges, near misses labelled as near misses, and a pass it on fallback when nothing fits.
THE ONE IT GOT WRONG
A VA asked for something sleeping seven singles. The bot said nothing was in stock. It was wrong: one property split to eight singles and was free for the exact window. The founder would not let it go, the cause was traced, and it was retested against that original enquiry before anyone called it fixed.
Properties checked per enquiry went from 8 to 45, which killed a long tail of 26 that were silently never offered even when they were the best fit. Bed matching is deterministic rather than a judgement call, and was tested against all 44 active properties. 44 of 44 correct.
IF YOU ARE THE FOUNDER
What this buys you is the search itself: every one of your 45 properties checked in about forty seconds, not the eight or so anybody could hold in their head. That means the 26 properties that were quietly never offered, even when they were the best fit, start actually earning instead of sitting empty while a worse match went out. The afternoon that search used to eat goes back into the enquiries queued up behind it, and you stop worrying that the single biggest time sink in the operation is also deciding, at random, which of your own doors gets a fair look.
IF YOU ARE ON THE TEAM
What this buys a VA is the same search across all 45 properties the founder would run himself, not the eight anybody could remember on a busy morning. That means they can quote in the moment the enquiry lands instead of promising to check and come back later, because there is nothing left to go and check by hand. For the team, quoting stops being a skill some people have and others do not: everyone is reading the same live calendars, so everyone quotes at the same standard.
MONTH END
BEFORE
Statements were reconciled from memory. Month end meant a morning of six blocked statements and no clear reason why any of them were stuck.
NOW
One sweep across every landlord, each statement either ready or blocked with the exact field that is missing, so the fix is a task rather than an investigation.
THE FEE FORMULA, CHECKED AGAINST REAL INVOICES
The fee maths was not trusted because it looked right. It was run against three landlords and 24 real bookings across every channel, and every single one landed on the exact contracted percentage. That is a formula matched to paid invoices, not a formula that seemed plausible.
The bot quotes only from the database price columns and never invents a number. One long stay instruction was found to be causing genuine under quotes, and the instruction itself was rewritten rather than that one quote being patched.
IF YOU ARE THE FOUNDER
What this buys you is a fee formula proven against three landlords and 24 real invoices, not one that merely seemed right. That means you are no longer the only person in the business who can tell whether a quote is defensible, so a negotiation does not have to wait for you to be in the room. The morning that used to go on reconciling from memory goes back into the landlord relationships that actually grow the portfolio, and you stop worrying that a defensible number only exists inside your own head.
IF YOU ARE ON THE TEAM
What this buys a VA is a number already matched against real paid invoices, not one that merely looks plausible. That means they can hold a line in a negotiation with a landlord instead of guessing how far they are allowed to move, because the fee behind that line has already landed on the exact contracted percentage against 24 real bookings. For the team, a quote stops depending on who happens to be senior enough to be trusted with it.
URGENCY
BEFORE
Everything landed in the same queue at the same speed, and how fast a dangerous message moved depended on who happened to read it and whether they understood what they were reading.
NOW
Danger is matched on meaning, not on keywords, and jumps every queue: it bypasses the normal path entirely and escalates immediately, at any hour, whether or not anyone is watching the channel.
THE CHAIN
A guest writes that they can smell gas, so it is recognised as an emergency in the same second rather than sitting behind eleven routine questions, which means the right person moves in minutes instead of the morning. That is the difference between an incident and a claim. One of those costs a callout; the other costs a property, a licence and a reputation you cannot rebuild by working harder.
This was tested before it went near a live channel, and the test caught a real hole: the matcher had been built from equipment words, so a smell of gas and water coming through a ceiling matched nothing at all. The two most dangerous phrasings would have received a calm, unhurried answer. Rebuilt to match intent, then retested 18 for 18 before shipping.
IF YOU ARE THE FOUNDER
What this buys you is speed on the one category where speed is the whole game: danger matched on meaning, not on keywords, moving in minutes instead of whenever someone next reads the channel. That means the difference between an incident and a claim, and a claim costs a property, a licence and a reputation you cannot rebuild by working harder. Your own attention stops being the safety net, so a dangerous message no longer needs you personally watching, and you stop worrying that the one mistake you cannot recover from is the one waiting on whoever happens to be awake tonight.
IF YOU ARE ON THE TEAM
What this buys a VA is the decision already made for them: a gas smell jumps every queue and escalates immediately, at any hour, without anyone needing to recognise it as urgent first. That means nobody on shift has to decide alone, at eleven at night, whether something counts as an emergency. For the team, the one call that is genuinely too risky to get wrong stops depending on who happens to be reading the channel at that moment.
IT COMPOUNDS
BEFORE
Whatever a VA worked out in a thread stayed in that thread. The same question got answered from scratch every time it was asked, by whoever happened to be on, at whatever standard they happened to have. Training was the founder answering the same thirty questions on a loop.
NOW
It teaches while it answers, and it learns while it teaches. Correct it once and that correction is permanent, from anyone, not just a founder. A nightly pass pulls durable rules out of the day's real conversations, so the operation's own standard is captured as it is set rather than reconstructed later.
THE CHAIN
A VA corrects it, so that answer is right for every person who asks it from then on, which means the standard only ever travels upward and nobody re-learns what the company already knows. Ask the same thing twice and it teaches the pattern harder the second time, so people stop needing to ask. Every month it needs less input and gives back more, and a team that is getting better on its own is the only kind you can grow without growing the payroll to match.
It was not always this way, and the gap was caught in a night. A VA taught it a real, durable fact that it used correctly that same day and would have forgotten by the next, because only founder corrections were persisting. Fixed the same evening. The same night turned up a second gap behind it: the founders' own direct messages, the single richest teaching signal in the system, were not being captured either.
IF YOU ARE THE FOUNDER
What this buys you is a nightly pass that pulls durable rules out of the day's real conversations, so a correction you gave once is permanent for everyone, not just remembered by you. That means you stop being the ceiling on how good the operation's judgement gets, because it gets sharper on the days you are not even in it. The thirty questions you used to answer on a loop go back into whatever only a founder can do, and you stop worrying that the standard your business runs on lives only in your head and leaves the day you do.
IF YOU ARE ON THE TEAM
What this buys a VA is the reasoning behind the answer, not just the answer itself, so a correction made once becomes something they actually know rather than something they ask for again next month. That means the same question stops coming back to whoever is on shift, freeing that time for the enquiries actually in front of them. For the team, the standard only ever travels upward: nobody re-learns what the company already worked out.
ESCALATIONS
BEFORE
The founders were the whole safety net. A booking taken at a fraction of the right rate, a two night stay five weeks out, a double accept that ended in a full refund: none were caught by a system, all three were caught because someone happened to be looking. A finished offer worth four figures a month sat unsent for 13 hours because nothing was pushing it.
NOW
Nothing arrives blank. Every escalation comes with the situation, what it has already checked, and the call it would make, so the founder is agreeing or disagreeing rather than starting from nothing.
THE CHAIN
An awkward call comes in, so it is escalated with a recommendation already attached, which turns a ten minute investigation into a five second yes. Twenty of those a week stop being twenty interruptions and become one short list. The founder's attention moves off the operation and onto the things only a founder can do, and an operation that no longer needs its founder in the daily loop is one that can take on more doors without taking more of the week.
The mandate is widened deliberately, one ratified piece at a time, with a worked example reasoned through properly rather than a blanket instruction. And a live prompt injection risk was closed before it was ever used: guest written text could previously reach write tools through the escalation path. It is read only now, found by asking what it could reach rather than by an incident.
IF YOU ARE THE FOUNDER
What this buys you is the ten minute investigation already done, so an awkward call becomes a five second yes or no instead of a stop everything and find out. That means twenty interruptions a week become one short list instead of twenty separate demands on your attention. The hours that used to go on being the only person allowed to say yes go back into the doors and decisions only you can make, and you stop worrying that growth means more of your evenings, because an operation that does not need you in the daily loop is one that can take on more doors without taking more of your week.
IF YOU ARE ON THE TEAM
What this buys a VA is a recommendation already attached to the escalation, not a blank question with no steer. That means raising something awkward stops meaning they wait, uncertain, for someone senior to work it out from scratch. For the team, twenty of those a week stop being twenty separate interruptions to somebody's day and become one short list somebody can clear in minutes.
CLAIMS AND DISPUTES
BEFORE
A guest claimed, and you argued back from memory under a deadline. Entry details could even go out before anyone had confirmed the deposit was secured, which happened on a live booking.
NOW
A release gate blocks door codes until the deposit is proven, and every interaction leaves a timestamped record: entry activity, staff messages at the time, mid stay check ins where the guest was asked and raised nothing.
THE CHAIN
A guest claims he could not get in, so the entry log and a cleaner's message from that hour are produced instead of a recollection, which means the platform decides on facts rather than on who complained hardest. That is a refund refused and a review removed. Do that consistently and disputes stop being a cost of doing business and start being something the operation reliably wins, which is margin you were previously donating.
Mid stay check ins are understood as evidence as much as service: a record that the guest was asked and had nothing to raise at the time. Guest facing sending is still shadow only, drafting but never sending, and stays that way until the ledger has been reviewed and the founder says otherwise.
IF YOU ARE THE FOUNDER
What this buys you is a timestamped record instead of your memory: the entry log, the staff messages, the mid stay check in where the guest raised nothing. That means a disputed claim gets decided on facts rather than on who complained hardest, a refund refused and a review removed instead of margin quietly given away. Do that consistently and disputes stop being a cost of doing business, and you stop worrying that a claim you cannot actually disprove is going to cost you the argument by default.
IF YOU ARE ON THE TEAM
What this buys a VA is a gate that checks the deposit before a door code goes out, so nobody on shift has to personally decide whether it is safe to release one. That means a guest cannot end up inside a property before the money that protects it is actually secured. For the team, a dispute stops being an argument they have to win from memory and becomes evidence somebody else already recorded.
YOU CAN SEE IT WORKING
BEFORE
Nobody could say whether things were improving. The founders were intervening more than 20 times across three days and the only evidence was how tired they felt.
NOW
Every intervention is classified by root cause and reported daily: what it answered, what it assisted with, what still needed a founder and why. The target is stated out loud and progress against it is visible rather than felt.
THE CHAIN
Every founder touch is logged with its cause, so the reasons cluster into a list rather than a feeling, which means the biggest one gets fixed and that whole category stops coming back. The number falls, and because the cause is attached you know exactly which part of the operation just got stronger. That is a business improving on evidence instead of on effort, and it is the only version of this you can repeat at eighty doors.
It is published honestly, which is the only reason it is worth anything. Solo handle rate as observed: 14 per cent, 56, 71, 83. The 14 was a genuinely hard mix that should not have gone to a bot at all, explained rather than excluded. The meter also caught itself over counting twice, and data from before that fix is flagged as inflated rather than quietly smoothed.
IF YOU ARE THE FOUNDER
What this buys you is every intervention classified by its actual cause, not a feeling that things are either fine or on fire. That means the biggest reason you are still being pulled in gets fixed once, properly, instead of managed week after week. The attention that used to go on wondering whether things are improving goes back into fixing what the evidence says is actually costing you, and you stop worrying whether the business is getting better, because you can watch the number that proves it, on the bad weeks as well as the good ones.
IF YOU ARE ON THE TEAM
What this buys a VA is one less question hanging over every task: did anyone tell the founder about this yet. That means they can close something out and move on, because the record of what needed the founder and what did not is kept automatically, not chased afterwards. For the team, the work speaks for itself instead of needing to be reported up before it counts as done.
THE OPERATION REMEMBERS
BEFORE
An SOP lived on a whiteboard, in the founder's head, or nowhere. Decisions were made in meetings and survived only in whoever attended. People left and took the operation's memory with them.
NOW
File a procedure and it wires itself in as a standing instruction with no code and no prompt edit. Recorded meetings, calls and boards are mined into that same corpus automatically, so what gets decided becomes what gets done.
THE CHAIN
A decision is made in a meeting, so it is captured and becomes a standing rule rather than a memory, which means it is applied to every relevant situation from that day on without anyone remembering to apply it. Onboarding stops being months of absorbing what is in the founder's head. A new VA is useful in days because the company's judgement is a thing they can query, not a thing they have to be told, and that is what makes the next ten doors cost less to run than the last ten.
It checks its own work. A two month retro mined 119 recorded meetings into hundreds of findings, and the first pass produced two fabricated claims: a recommendation the founders had explicitly ruled out, and a statistic that appeared in no transcript. Both were caught against the raw recordings and cut before the report was handed over. Where two sources genuinely contradicted each other, it flagged the conflict for a ruling rather than picking one.
IF YOU ARE THE FOUNDER
What this buys you is every procedure and every decision wired in as a standing instruction the moment it is made, not a memory that survives only in whoever attended. That means onboarding stops being a founder project measured in months, because the next ten doors cost less to run than the last ten did. The time you used to spend re-explaining what the business already decided goes back into deciding what comes next, and you stop worrying that the company is one head with a team attached, because it stops being that from the day this runs.
IF YOU ARE ON THE TEAM
What this buys a VA is the company's own judgement as something they can ask, not something they have to already know or track down whoever was in the room when it was decided. That means a new starter is useful in days, not months, because the reasoning behind a decision is there to query the first time it matters. For the team, nobody's tenure is the reason a rule gets remembered or forgotten.
BUILT TO BE TRUSTED
BEFORE
Most operations find out a tool was wrong when a guest tells them. There is no log, no cause, and no way to be sure it will not happen again next week.
NOW
It fails closed. When it is unsure it asks; when a check does not return cleanly it stays quiet rather than guessing. Every answer is traceable to the data it came from, and a high risk change goes through an adversarial review before it is deployed, not after.
THE CHAIN
A payment tool was reviewed before it could write anything, so a refund path with no idempotency key was caught in review rather than in production, which means the double refund it would have allowed never happened and never appeared on a statement. Do that before every risky release and the failure rate stops being luck. That is what lets you hand it more of the operation, and how much you can hand it is the whole ceiling on what this saves you.
Where it has been wrong, the cause was found and named. It once told a VA several properties were free when one was booked solid. She pushed back and she was right. The cause was not the data: it did not know the current date, so a subtly wrong question returned confident nonsense. The date is now injected on every single turn. That is the class of fault worth fearing, and it is why the reviews happen before the deploy.
IF YOU ARE THE FOUNDER
What this buys you is every answer traceable to the data it came from, and a high risk change reviewed before it ships rather than after a guest tells you it broke. That means you are not trusting a black box, you are trusting something that shows its working and stops the moment it is not sure. The reviewing you used to have to do yourself goes back into whatever only you can decide, and you stop worrying about how much of the operation you can safely hand over, because the failure rate stops being luck and becomes something checked before every release.
IF YOU ARE ON THE TEAM
What this buys a VA is permission to trust a quiet answer: when it is unsure it asks, and when a check does not come back clean it stays quiet rather than guessing. That means a VA is never handed confident nonsense dressed up as fact. For the team, that going quiet is not a fault to work around, it is the system doing exactly what it is meant to do.
THE POINT
Every number here came out of running 60 doors with a founder, a business partner and a small remote team. The failures are on the page for the same reason the wins are: an operation you cannot see the mistakes in is one nobody has looked at properly.