OpSmithOs

OpSmithOs. The brain behind the operation.

Your team asks it instead of asking you.

It makes the calls your team currently brings to you. The price they would have discounted. The booking they would have accepted. The enquiry they would have parked until you were free. Your team keeps moving, the answer is the one you would have given, and the guest hears back today instead of on Monday.

See it in actionSpeak to the founder
on shift now,22:14and it is still answering
60 doors, live every day·no ops manager·built inside a real operation, not a lab
The introduction of the bot has significantly reduced how much you guys come to me.

Joel Borokini

Founder of a 60 door property management company

Most AI answers your guests.

This one runs your team.

The guest inbox was never the thing keeping you up. It was your own team asking you what to do, because the document you wrote them does not cover the day they are having. OpSmithOs sits in the channel they already use and answers the way you would have, so the work carries on without you and the decision is still yours.

WHAT IT IS

An executive ops manager that lives in your Slack.

Not a chatbot and not another dashboard. It sits where your team already asks the questions and does the job the ops manager you have not hired would do. It answers, it makes the call, it holds the line where your team would have folded, it writes the message that has to go out, and it escalates the handful that are genuinely yours. It runs on your own procedures, your live calendar, your property database and the way you actually think, so what comes back is your answer and not a general one. Your VA stops guessing and stops waiting on somebody. The team closes the enquiries it used to park. The questions that used to become your evening never leave the channel. And the next twenty doors do not need another salary to carry them.

It turns ten messages into one reply your VA can send

An enquiry used to take a VA around ten back and forths. Now it is one pass. It reads the live calendars across the whole portfolio, works out what genuinely fits, and hands back a message with the availability, the rate and the link already in it, in about 40 seconds. Nobody opens a calendar and nobody waits on you. The guest hears back while they are still shopping, which is most of why one operator gets a direct booking and another gets ignored. And your VA spends that morning on the ten enquiries sitting behind this one instead of on this one.

It argues your price up, not down

A VA under pressure gives the price that was asked for, because the safe answer is always the cheap one and a discount never gets logged anywhere as a loss. This one knows what the unit genuinely sells for at that length of stay, so it counters instead of caving, and it will prove the direct price beats the platform rather than just claiming it. Judgement is not only faster than your team. It brings in more money on the same booking. That booking lands at the number you would have held out for, on every unit and every enquiry, whoever happens to be on shift that morning. What that buys you is a price you never have to hold yourself, so your time goes on winning the next booking instead of checking the last one, and you stop finding out at month end that a good month was quietly discounted away.

It writes the message that has to go out, not just the advice

The decision is half the job. On a live noise complaint it reached the same call as an experienced VA, collect the evidence, log it, issue a formal warning, and then produced the thing she had not, the warning itself, written and ready to send. The note to the landlord, the guest reply explaining a rate change, all of it comes back in your house structure. So the hard message goes out the same night. The refusal, the formal warning, the bad news a guest is not going to want, written in your tone and ready to send at half past ten, instead of sitting unwritten until somebody senior can find the words in the morning. The night is the whole point, because by the morning the neighbour has complained again and the guest can honestly say nobody ever told them. What that buys you is a team that can deliver bad news on their own, so your evening stays yours, and you stop being the only person in the company who can write the difficult one.

It checks every arrival for a missing deposit before anyone is awake

A run every morning lists who is checking in today, whether the deposit has actually landed and whether the check in details went out. The very first dry run of that check found 5 arrivals with no damage deposit recorded, before a single guest turned up. Nobody had to remember to look, so nobody starts their day opening bookings one at a time. You find out at breakfast instead of at the front door, and the front door is where a one star review gets written and where a booking you had already counted turns into a refund.

It hands the next shift a ranked list of what to fix first

It reads the outgoing handover and gives whoever clocks on next a prioritised list, most urgent first, each item carrying the property, the problem and the action it recommends. The shift opens on the thing that actually matters instead of a wall of messages, so nothing falls down the gap between two people and the same job gets done the same way whoever picked it up. A guest never has to ask twice, and asking twice is what people outside your company experience as an operation that is not on top of it.

It turns a line in Slack into a task with an owner and a reminder

You ask somebody to do something in a thread and the thread swallows it. Tag them and tag it instead, and the job is on the board under their name with the reminder already set. The task chases the person, so the work happens without a second person holding it in their head all week. You stop being the follow up system for your own company, and the pile of things only you are carrying stops growing every time you add a door.

It tells your team when the call is yours and not its

It knows the edge of its own competence. It labels a near miss as a near miss instead of passing one off as a match, and when something is genuinely a director's call it says so, names you and stops, rather than guessing confidently. That is what makes it trustworthy, and being trusted is the whole point, because a team that only half believes an answer checks it before acting on it, and an answer somebody has to check first has cost you exactly what having no answer would have cost you. Yours does not get checked. So the work moves at the speed of the answer, and what reaches you is a short list of decisions rather than a queue of questions.

It answers a cleaner's access question straight out of your own records

Where the waste goes, how the cleaner gets in, which appliance does what. It comes back with the route and the walkthrough video attached, in a form your coordinator can forward as it stands. No searching, no ringing a colleague, and no waiting on the one person who happens to know. The clean happens on time, the colleague who would have been interrupted stays on their own work, and the same answer comes back next week when somebody new asks it.

It clears month end across every landlord, so nobody spends a day chasing

You used to find the gaps by opening statements one at a time until something did not add up. It runs the whole set instead. One sweep, 31 landlord statements, 29 ready and 2 blocked, each blocked one carrying a link to the exact thing missing. There is nothing left to hunt for, so the two get cleared and every landlord is paid on the date they expect. The person who used to work through them one at a time is back on enquiries, which is the side of the business that earns. And the twentieth landlord costs you no more month end than the second, which is how you take on doors without month end growing with them.

It does a dozen more jobs than this page has room for.

It sweeps the whole portfolio for units that have gone quiet and flags the urgent ones. It scrubs your property database every week and posts the gaps so somebody chases them. It reads a photo pasted into a thread and tells your team what to do about it. It posts tomorrow's cleans so nobody opens a calendar. It takes a voice note when typing is not realistic. It works as a private message, so a new starter can ask the question they think is stupid without an audience. It holds your marketing strategy as well as your data, which is how it works out which of two listings is the real unit. And when it hits a hole in your process it writes the play, gets your yes, and answers with it from then on. A feature list is finished the day it ships. This one is not. Every month it takes on more of the work your team is still doing by hand, and you never hire anybody to cover the extra. What that buys you is capacity that arrives without a salary attached, so the money stays in the doors you are adding next, and you stop planning your growth around who you can find and afford. None of it is a separate clever trick, either. It is one ability, judgement, used over and over on whatever turns up. Here is that one ability, on a single enquiry.

ONE AWKWARD ENQUIRY, START TO FINISH

One enquiry. Every calendar you own. One reply, ready to send.

This is the enquiry that eats an afternoon. A VA opening calendars one at a time, checking the five units anybody can remember to check, ringing a founder about the awkward part, then going back to the guest tomorrow with a maybe. It is slow, it is inaccurate, and it still ends with the wrong home going out. That is not a slow process. That is a broken one, and what it costs you is the booking. Here it is running instead. Three steps, about 40 seconds.

THE ASK

One message from a guest, with six separate conditions buried in it.

GUEST ENQUIRYDirect, Friday morning

Hi, there are six of us and we are after somewhere for a fortnight in August, the 8th to the 22nd. We would all like our own bed, so six singles rather than doubling up. We will have two cars and would rather not leave them on the road. My mother is coming and she cannot do stairs, so we need a bedroom on the ground floor. We also have a small dog. And we would like to stay put for the whole two weeks, not move halfway through. Is there anything that works?

THE SIX CONDITIONS

  • Fourteen nights, 8 to 22 August
  • Six single beds, nobody sharing
  • Parking for two cars, off the road
  • A bedroom on the ground floor
  • A dog in the house
  • One place for the fortnight, no moving

Read straight out of the message. Nobody typed them into a form.

THE SEARCH

It tests all six against every door you own, on the live calendars.

WHAT IT READS

Your live calendars

every door, not the five anybody can remember to check

Your own house rules

beds, parking, access and pets, door by door

Holds and owner blocks

anything provisional counts as gone

YOUR PORTFOLIO

60doors checked, one pass

Every square is one door. The bars inside it are the fortnight the family asked for, and a dark bar is a night already gone. The lit squares are the three it kept.

Those 60 doors are 45 separate properties, and this family wants one address, so the set it searched is properties. It read all 45. A person opens five, because five is what anybody can remember to check on a busy morning, not because they gave up early. The rest never get opened at all. Three came back worth looking at, and every other one failed on something it can name. Nobody told it what a near miss looks like. And the ones that fit but were never put forward, never offered, never even searched for, are the bookings nobody counts, because nothing logs the enquiry you answered with the second best home you could remember.

THE RESULT

Three doors kept, one picked, and the message written.

1ON THE BENCH

Four bed townhouse in the centre

CLEARS 4 of 6010203040506

The fortnight is free and the dog is fine. Every bedroom is a flight of stairs up, and the parking is a street permit.

2NEAR MISS

Three bed apartment, all on one level

CLEARS 3 of 6010203040506

Step free with two spaces of its own. It sleeps six on a sofa bed, and it runs out three nights early.

3BEST FIT

Five bed house with a self contained annexe

CLEARS 6 of 6010203040506

Six proper singles, two cars off the road, a ground floor bedroom and bathroom, the dog welcome, and the whole fortnight open.

THE CALL

Option 3, and it is not close.

It is the only one that answers all six. Its single compromise, two of the beds sitting in the annexe, is something the guest can see in the photographs before they book rather than find out about on arrival. It is also the only one of the three that holds its rate across a fortnight in August. Option 1 stays on the bench in case they will accept the stairs. Option 2 never goes out, because a move on night twelve of a family holiday is a refund and a review you cannot answer.

READY TO SENDBack in the channel, as it stood. No reshaping.
Before45 minutes of somebody opening calendars
Now40 secondsstart to finish

Thanks for setting it out so clearly, it makes this easy. I have checked our live calendars this morning and we have one home that covers all six of your points for the full fortnight, the 8th to the 22nd of August.

It is a five bedroom house with a self contained annexe. Six proper single beds so nobody shares, off street parking for two cars, and a bedroom and bathroom on the ground floor with no steps up from the drive. Dogs are very welcome, there is an enclosed garden and hard floors downstairs.

Two of the six beds are in the annexe, which is attached to the house and has its own bathroom, so I will send photographs of it. I can hold the dates while you have a look.

Written by OpSmithOs. Sent by the VA exactly as it stood. About 40 seconds from the question landing in the channel.

Run that chain out. It said which one was the near miss and why, so nobody had to go back over the shortlist before sending, so the reply went out this morning instead of after somebody senior had been round it. The guest heard back while they were still shopping, so a fourteen night August booking did not sit in an inbox until Monday and go cold. The near miss never went out, so there is no move on night twelve, no refund and no review you cannot answer. The option that would have needed money knocked off it was never offered, so the rate held. And your VA never opened a calendar, so her morning went on the ten enquiries sitting behind this one, every one of which goes out today as well. Now do that on every enquiry like this, and the enquiries like this are the big ones. It is not an hour saved. It is bookings that were never going to exist, on doors you already own and are already paying for. And not one line of that came off a procedure, because no procedure you have ever written covers an enquiry like that one.

More doors, and not one more evening of yours.

WHAT IT IS COSTING YOU RIGHT NOW

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

Open your own SOPs and read them like a stranger. A rate card you have edited since. A unit you have handed back. A rule written for one guest who complained once and never came back. Every line was true the day you typed it. Not one of them knows what changed on Tuesday. You are not short of documentation. You are short of documentation that is still correct.

Now watch what your team does when the page does not fit the situation. They do one of three things. They find the nearest rule and apply it anyway, which is how a long stay gets quoted like a short one. They give the safe answer, and the safe answer is always the cheap one. Or they message you and stop, and the enquiry goes cold while you are driving. Nobody ever logs that as a loss. It is one of the biggest ones you have.

The gap was never information. It is judgement. You know what the business is protecting, what that unit is genuinely worth, what the guest was already promised, and where your line sits and why it sits there. None of that made it into the manual, because none of it was ever a rule. It was you. OpSmithOs carries it, applies it to the thing actually in front of your team, and it is there at eleven at night when you are not.

And judgement is not only faster. It is more accurate, and accuracy is the half that actually pays you, because an answer your team does not have to go back over is the only kind that saves anybody any time at all. It also brings in more money. The same enquiry, answered by something applying your standard instead of guessing at it, holds the rate rather than discounting it, offers the home that actually fits rather than the nearest one somebody could remember, and says no to the booking that was going to cost you a refund. A faster answer gives you an hour back. This gives you the hour and the booking as well, so what you gain turns up in your year end and not just in somebody's morning.

01

Your judgement sits beside a new starter on their first morning

You handed over the procedure on every hire you have ever made, and the procedure was always the easy half. The judgement underneath it never got handed over, because it was never written down anywhere. It was just you, and it took your best people months of live situations to pick it up. Now it is beside them from day one, and every answer carries the reason it is the answer, so the second time they have it themselves. One of our operators put it plainly on a recorded call. He asks it rather than the team because he does not want anybody thinking he is asking a newbie question, and either way the question gets answered. So the ramp that used to be measured in months is measured in days, and you can hire on attitude instead of paying for the years somebody else spent learning your job.

02

Your process closes its own gaps without you writing anything

We had no play at all for enquiries in an area where we hold no units, so a VA would simply say there is nothing available. The gap went in and it came back with the procedure written, the board built to hold it and the answer wired into its own replies, all in one pass. It does the same off the back of a live thread. Once the dates are locked, check the turnover clean is booked against the real checkout date and not the old one. Nobody asked for that rule. Every SOP you have ever written started dying the day you saved it. This one goes the other way, so the standard your team works to is higher this month than it was last month, and nobody sat down to write it.

03

You find out about the clash today, not on arrival day

The expensive ones never arrive looking expensive. A VA asked whether the money worked on a month long request. It answered on the money, then said the dates clashed with the guest already living in that property, who had put in writing that he wanted to stay on. About 12 seconds, the money check included. Nobody asked it to read that thread. Without it you meet that one on the doorstep, two guests and one front door. That costs a refund, the second booking, and a review that reads like a warning to everybody who finds you next. And it costs it on a Sunday, to you, because there is nobody else it could possibly land on.

04

The losses nobody ever writes down stop happening

A guest asked for a price per night on a stay running most of the summer. Priced nightly it looks enormous and gets talked down from there. It refused to quote nightly, swept the portfolio for the one unit that genuinely fitted, quoted monthly and converted it back so the guest could see the value. Same stay, better number. That call happens somewhere in your operation every week and it usually goes the other way. Nobody ever finds that money afterwards, because a discount is not recorded anywhere as a loss. It shows up as a slightly worse year rather than as a decision anybody made.

Judgement was the half of the job you could never hand over. Now you can.

THE THING YOU ACTUALLY HAVE

Your operation runs on one person's head. Yours.

Revenue grows in a line. Exceptions grow in a curve.

Volume you can hire for, because volume is the same job done more times. Exceptions you cannot, because the answer to an exception only exists in your head. And every answer that only exists in your head is a queue.

So three things happen, and they happen to every operation that gets past the size one person can hold. Execution drifts, because the same job gets done differently depending who picked it up. You become the ceiling, because growth is now capped by attention you have already spent. And knowledge evaporates, because when somebody good leaves, quality resets to whatever the next person can work out for themselves.

Hiring your way out is the obvious move and it is the one that fails. An ops manager is a salary you feel every month and a person who can still only be in one place. A VA is affordable and makes it worse first, because every one of those questions now comes through you before it can be answered, which is why people give up at week three and decide VAs do not work. The VA was never the problem. They were missing the half of the job that has never existed on paper.

We counted a full week in our own operation. 612 questions came off the team that needed a real decision, not a fact off a page. Every one of them used to stop until a founder picked up.

The message at eleven at night. The question your VA has asked before, because your answer was slightly different last time. The SOP nobody opens, because it is long and the situation in front of them is not in it. The month end that will not close because a couple of statements are missing something and nobody knows which ones.

You did not build a company. You built a lookup service, and you are the database.

And it does not level off. Every door you add adds decisions, not just cleans. That is why growth stops feeling like growth.

None of that gets fixed by writing more of it down.

SEVEN DAYS, ONE OPERATION

One week of the questions that stop at you.

Not one of these was written for a website. This is the shape of thing that lands on an operator every day, and a document cannot answer any of it, because the day your team is having is not in it. Scroll at your own pace and watch how long you last.

Where does the cleaner get in, and where does the waste go?Platform says free, calendar says blocked. Which one is right?No damage deposit on this arrival. Do I chase it or let it run?Is this one I should be deciding, or you?There is no procedure for this one. What now?Are the landlord statements ready to send this month?
612in seven days. 88 percent closed with no ops lead, no ops manager on shift and no founder jumping in.

Six of them, as they arrived.

That is one operation of around 60 doors, counted off its own daily reports, not off a survey and not off a projection. Every one of those questions used to sit there until a founder picked up. Every one of them is somebody on your team stopped, doing nothing, waiting on you. Hand the answer back in the moment and that same team takes more enquiries, more turnovers and more doors with nobody added to it, and you get back the week you were spending as a switchboard.

01

Your team stops waiting on you

The answer lands in the channel they already had open, in seconds, with the reason attached, so the second time they have it themselves. Nobody queues behind your phone and no enquiry goes cold while you are driving. The enquiry answered while the guest is still looking is the one that converts, and that is the whole difference between a team that processes enquiries and a team that closes them.

02

Your evenings stop being the buffer

On the busiest single day of that week it answered 105 and needed a founder twice. Twice. The rest never reached anybody, and not one of them was left undone. An evening you are not spending as the answer desk is an evening you can spend on the next twenty doors, and that is what you are actually buying here.

03

More doors stops meaning more of this

That busiest day carried more than twice the volume of the day before it and needed half as many founder touches. Volume up, founder touches down. You took on more work and you did not take on another salary to do it, so the next twenty doors cost you cleans and turnovers rather than another hire. A business that can take on more work without taking on more people is one you can keep growing, and one somebody would want to buy.

You were never going to write your way out of that. Nobody types 612 answers a week.

WHAT IT DOES TO THE BUSINESS

Add doors without adding admin, late evenings, headcount or more stress.

Operations do not break because you added a door. They break because every door you add lands on the same few people, and those people are already at capacity. So the admin grows in a curve while the team grows in a line, and the gap between the two is your evenings.

What changes first is consistency. The same situation gets the same answer whoever is on shift, on a Tuesday and at eleven at night. So your team stops going back over an answer before they use it, and that is the largest single thing anybody gets back here, because an answer somebody has to check first has cost you exactly what having no answer would have cost you.

What that buys is execution. More of it, because nobody is queuing behind you for a decision. More accurate execution, because the decision they get is the one you would have made. And more reach, because every enquiry is tested against every property rather than the handful somebody can remember to check on the day. More accurate execution across more of your portfolio is revenue: prices argued up instead of down, enquiries answered while the guest is still looking, homes offered that would never have been put forward, landlords paid on the same date every month.

None of those is the point on its own. The point is that each one makes the next one bigger, so here it is a rung at a time. The answer comes back in seconds, so your team acts on it instead of waiting on you. The answer is the one you would have given, so what they do is right the first time. Right the first time, every time, is why they stop checking it before they use it, and not checking it hands every person on your team hours back in the week. Those hours go on enquiries, and more enquiries answered on the day they land is more bookings. Every gap it runs into gets written up as a new rule and wired in, so next month your team is working to a higher standard than it was this month, and you wrote none of it. Do that for a year and the growth is built into the system instead of into how hard you personally worked. The next twenty doors do not need an ops manager, they do not need six months of onboarding, and they do not need another evening of yours. You are taking on more work without taking on more payroll, and a business that does that is one you can keep growing past the size of yourself, or one somebody else will want to buy.

Decisions grow in a curve, and the curve stops landing on you

The newest doors always feel heavier than the first ones, and it is not the cleans. Cleans scale in a line. Decisions do not, and every decision with no page behind it lands on you. Take those out of your week and the doors you add next cost you beds and turnarounds, not nights. That is the difference between a business that grows and a business that just gets busier.

The doors you never offer stop being invisible

Every portfolio has properties that quietly never get put forward. Not because they are worse, but because a shortlist is whatever one person can remember on the morning the enquiry lands, and it is the same handful every morning. Ask any operator which of their own doors gets offered least and they cannot tell you, because nothing anywhere counts the enquiry you answered with the second best home you happened to think of. Test every enquiry against every property and the quiet ones start appearing, so a unit that was sitting empty because nobody thought of it starts earning. That is not efficiency. That is revenue that was always there, on doors you are already paying for.

Nobody checks its work before it goes out

What accuracy buys you is the checking pass that you do not have to do. It calls a near miss a near miss instead of dressing one up as a match, so nobody reads the answer twice before they use it. Your VA sends the reply in the moment, the guest is answered while they are still shopping, and the rest of that morning goes on the ten enquiries sitting behind this one instead of on double checking this one. Your own time stops going on being the last set of eyes, and that is the part you feel first. You can be out for the day and be confident your operation is still running to your standard.

Cheaper hires give senior output

You have been paying for years of experience because years of experience is where judgement lived. It does not live there any more. Hire on attitude, put the judgement beside them from the first morning, and the person you could afford answers like the person you could not. Your wage bill stops being the ceiling on how fast you can take on doors.

A new starter is useful in their first week

A cleaning coordinator days into the job, with no knowledge of a single property, was asked where the waste goes and how a cleaner gets in. She got the answer, the access route and the walkthrough video back in one message and forwarded it as it stood. Nobody senior was interrupted and nothing was searched for. Onboarding stops being a founder project and the ramp gets measured in days.

The edge cases stop reaching you

The odd ones came to you because nobody else was allowed to call them. A guest needed relocating, which used to be a phone call to a founder. Instead the VA put it in the channel and got the commercial position, the numbered actions and the drafted message back. The founder read the thread later, already closed. You hear about the odd ones because it told you, not because it asked you.

You never hire an ops manager

The role you keep almost advertising for is answering questions, holding the line on price, chasing the gaps and writing things down. That is this, covered at three in the morning, on a Sunday, in August, at every door count. It does not resign, it does not go on holiday in your peak week, and it does not walk out of the building carrying everything it learned about your operation.

Your team stops accepting bookings you cannot honour

A request came in on a unit the platform was showing as open. The live calendar had every night blocked, and the property was quietly being handed back to its landlord. It said do not accept, gave both reasons, and drafted the guest a warm reply with a home that was genuinely free. Accepting that one costs a refund, a scramble, a landlord conversation and a review you cannot answer. These things are common in a busy operation, which is exactly why they get overlooked, and the person who normally catches them is you. Now nobody has to catch them, because they stop happening.

Dead leads start paying you

An enquiry landed that nothing in the portfolio could honestly fill. It searched every property, refused to send near misses, built the play to keep the guest and protect the review, found another operator, passed the booking over for commission and wrote the whole move up as a procedure. About 15 seconds. By hand that is tonnes of messages, tonnes of explaining and constant monitoring, so in a busy week it is simply a no. Now a no has revenue in it.

Month end stops eating a week

The month end sweep you read about above is the mechanism. This is what it buys. Your landlords get paid on the same date every month without a founder clearing an evening for it, and the two that are blocked are blocked with a reason attached rather than sitting silently until somebody notices. Predictable statements are how you keep the landlords you have, and they are most of how you win the next ones, because the first question a new landlord asks the old one is whether the money turns up when it should.

The systems you already pay for finally get used

Your PMS, your boards and your procedures were never the problem. Under pressure nobody goes looking for them, so the process quietly stops happening. Asking in the channel is easier than searching, and the answer comes back inside your process every time. Nothing else changed in our operation the month this went live. The systems had been sitting there all along. They only started getting used when asking beat looking. So you stop paying for software nobody opens, and the process you designed is the process that actually runs.

Your knowledge stops walking out of the door

Right now the answers live in your head and in whichever team member has been there longest. Both of those can leave. Every call it makes becomes something the business owns and the next person inherits on their first day, so you stop rehiring the same knowledge every time somebody moves on.

Guests never see it. They just see nothing getting missed

Nobody books a home because of your operations. They notice that the answer came back the same evening, that nothing was waiting on a founder, and that the thing they asked about actually happened. That is what a five star review usually describes, and it is what a returning direct booking is made of. The operational win and the revenue win are the same win.

It gets better every month it runs, not worse

Every answer carries one line for next time, so your team asks once instead of every month. One of our VAs gave feedback on it, the change was made that week, and she noticed on the next call without anybody prompting her. Every gap it hits gets written up as a play and wired back in with your approval. Software normally decays from the day it ships. This one goes the other way.

One number tells you if it is working. How often your team still needs you

Founder touch count. In one week it handled 612 questions for the team and closed 88 percent of them with no human needed. On the busiest single day it answered 105 and needed a founder twice. The volume went up and the number of times anyone had to come to us went down, which is the only direction that number is allowed to move. Two days after this went live one of our operators hit something he was not sure about and rang a founder. Nobody picked up, so he asked it instead and got exactly what he needed. That one thread is the whole business.

THE SAME ENQUIRY, TWICE

Ten messages and a morning. Or one message and forty seconds.

One guest enquiry, run both ways. On the left, how it used to go. On the right, the same enquiry today. Nothing about the guest changed.

An indicative demo of the shape of it, not a screen recording.

The old way

10messages, and counting
3 hours 22 minutesand the guest still has nothing

Your VA 08:12

enquiry in. family wants a fortnight in august

You 08:26

which unit are they asking about

Your VA 08:41

the two bed. is it free that whole run

You 09:04

check the live calendar, not the platform

Your VA 09:19

looking now

09:47

platform says open. middle week is blocked

You 10:12

anything else that fits a family that long

Your VA 10:33

checking the rest of the portfolio

11:08

two look close. what do i send him

You 11:34

leave it with me, i will look tonight
still coming

Ten messages in, and the plan is a founder looking at it tonight. The guest has still had nothing.

With OpSmithOs

1message, and it is done
40 secondsand the reply is written

Your VA 00:02

enquiry in. family wants a fortnight in august. what do i send

Reading the live calendars, every door

60 doors read, one house takes the whole fortnight

WHAT IT CAME BACK WITH

  • The two bed they asked for is gone. The middle week is taken, whatever the platform says.
  • The three bed by the park is open the whole fortnight and keeps the family in one house.
  • Dates held until Friday, so the guest has a reason to answer today.

For next time: never split a family across two addresses to save a booking. Offer the one house that takes all of them, or you lose the whole stay.

AND THE REPLY IT HANDS BACK

an example of the shape, not a real guest thread

The two bed is not free for the whole fortnight, and I did not want to move you halfway through the holiday.

The three bed by the park is open for all two weeks. Two doubles and a twin, a garden and parking on the drive. I have held it until Friday, so just say the word.

Paste it into the guest thread.

Nobody opened a calendar. Nobody waited on a founder.

That is one enquiry. Now count the ones your team took this week. Every one of them ended with somebody waiting on you, and an enquiry that waits is a booking somebody else took. Answer them while the guest is still looking and that is revenue you were quietly losing, at every door you own. And the morning that used to go on one enquiry now goes on the ten behind it, which is more bookings out of the same team, on the same payroll.

BUILT INSIDE A LIVE OPERATION

It has run a real operation of 60 doors every day since it went live.

AltoLuxo manages around 60 short let doors across 3 cities with a founder, a business partner and a small VA team. There is no ops manager. OpSmithOs is the reason there does not need to be.

It was built where it hurts, by the person it was hurting. Every capability exists because a real operation was bleeding somewhere and needed it to stop.

The enquiry that took ten messages now takes one

A guest enquiry used to take a VA around ten back and forths. It is one pass now. It checks the live calendars across the whole portfolio, not the five somebody can remember to check, and comes back with a ready to send reply in about 40 seconds. The five were never the problem. The ones that would have qualified and were never opened were.

The first dry run caught 5 arrivals with no deposit

The very first dry run of the pre arrival audit found 5 upcoming arrivals with no damage deposit recorded. Before the guests arrived. Nobody had asked it to look, and nobody would have thought to.

31 landlord statements swept, 29 ready, 2 blocked with the fix attached

One sweep across 31 landlord statements. 29 ready. 2 blocked, each with a link to the exact thing that was missing. Nobody spent a day chasing.

The number we actually watch is founder touch count. How many times in a week the team still needs a founder. It is supposed to go down forever. When it does, you can be away for a week and the work still gets done to the same standard, so you can keep adding doors without adding yourself to every one of them, and if you ever want to sell, you are selling a business that runs rather than a job with your name on it.

SEVEN DAYS IN A LIVE OPERATION

612 questions in one week. It closed 88 percent with no ops lead, no ops manager and no founder.

The page above counts that week as the problem. This is the same week as the report. The volume went up, the founder touches went down, and the whole thing was already written by the time the laptop opened.

OpSmithOs, seven day report

Live every day since 29 June 2026

612

questions handled in seven days

Closed with no ops lead, no ops manager and no founder

88 percent

105

answered on the busiest single day

2

times that day it needed a founder

60

doors it carried while it did it

The busiest day carried more than twice a quiet one and still only needed a founder twice. No ops lead reading the queue, no ops manager chasing it, no founder pulled away from something else. So the answer is the same one every time it is asked, the call gets made in seconds instead of at the end of somebody's shift, and more of them close on the day they land. Which is how the same team ends up carrying more doors than it did last quarter without anybody noticing the extra work arrive.

WHAT IT DID WHILE NOBODY WAS WATCHING

A sample of the calls OpSmithOs made this week

  • Stopped a booking we could not honour

    no founder

    The platform showed the dates open. The live calendar showed a guest already in there. 12 seconds, and no refund to make.

  • Turned a dead enquiry into commission

    no founder

    Nothing in the portfolio honestly fitted, so it found another operator and passed the booking on. 15 seconds, and a no had income in it.

  • Refused to quote per night

    no founder

    A nightly figure on a summer stay is where the haggle starts. It quoted the month instead, and the rate held.

  • Argued the rate up, not down

    no founder

    The rate card changed mid thread. It read the change and told the founder his own counter was too low.

  • Wrote the play we never had

    no founder

    No procedure existed for that area. It wrote one, built the board and wired it into its own replies. It answers that one alone now.

  • Checked a clean nobody asked about

    no founder

    The dates moved, so it made sure the turnover was booked against the real checkout and not the old one. Nobody arrives to a dirty flat.

  • Answered the cleaner in full

    no founder

    The access route and the walkthrough video attached, in a form the coordinator could forward as it stood. Nobody senior was interrupted.

  • Said the call was ours, not its

    founder called

    It named a founder, gave the position, and stopped. What reached him was a decision, not a question.

Eight real calls out of one operation. Nothing in the rail was written for a website.

Nobody cleared an evening for any of this.

REAL THREADS, START TO FINISH

Five real threads where a quick question turned into money kept or money made.

Nothing below was written for a website. Each one is a thread out of a live operation. One line from a team member, everything it checked between the question and the answer, how long that took, who it would otherwise have been escalated to, and what would have happened in a busy week if nobody had looked.

0102030405
01

It cleared the money, then found the guest already living there

A month long request lands in your channel and your VA asks whether the money works. It cleared the number against what that unit genuinely sells for, read the calendar, found the guest already in the property, pulled his messages and saw he had asked in writing to stay on, then offered the new guest live alternatives in the same reply. About 12 seconds, money check included. Unpicking that by hand is a jump across systems, a pile of messages and somebody senior comparing dates, and in a busy week it simply gets missed.

Both bookings kept, nobody rang a founder about it, and the review that makes you look like a bad company never got written.

02

It could not fill the enquiry, so it earned commission on it instead

An enquiry lands off a mismatch between the platform and your channel manager. It ran a deep search across every property and found nothing that honestly fitted, so it refused to send near misses. Then it built the play, keep the guest happy and protect the review, located another operator, passed the booking on for commission, and wrote the move up as a new procedure. All inside about 15 seconds. Handled by hand that is tonnes of messages, tonnes of explaining, constant monitoring and room for mistakes, and it ends in a decision nobody below you is allowed to make, so it either lands on a founder or it quietly becomes a polite no.

An enquiry you could not house paid you anyway, the guest was kept, and your team now runs that play as standard without being taught it.

03

It refused to quote per night, because per night is where the haggle starts

A guest wants a two bed for most of the summer and asks your team for a price per night. It would not hand one over. A nightly figure makes a stay that long look enormous and invites the haggle. So it swept the portfolio for the one unit that genuinely fitted, quoted monthly, converted it back so the guest could see the value, and handed over a message ready to send. By hand that is the sweep, the monthly maths and somebody senior reshaping the quote before it goes out. Quoted nightly, that stay gets talked down, and the discount never gets logged as a loss.

The haggle never started, so the margin never moved, and nobody had to be senior enough to hold the line.

04

It told the founder his own counter was too low

A guest lowballs a long direct stay and your VA asks, can we do it? It checked every night was open, called the offer what it was, and countered. Then the founder edited the rate card mid thread. It read the change on its own, recalculated, and told him his counter was now too low and he was leaving money on the table. It argued the price up, then still proved that booking direct beat the platform. Nobody on your team argues your price up. Nobody recalculates a live negotiation because a spreadsheet changed. It did.

It found money the founder himself was about to leave behind.

05

It said do not accept, and the reason was not caught by SOPs

Your VA does the right thing and double checks. No clash on our calendar, right? The platform showed the dates open. The live calendar showed every night blocked, and the property was quietly being handed back to its landlord. It said do not accept, gave both reasons, swept the portfolio and drafted the guest a warm reply with a home that was genuinely free. By hand those checks are screenshots, messages and somebody senior comparing the platform to the calendar night by night, so in a busy week the booking just gets accepted. Unwinding it costs a refund, a scramble and a landlord conversation.

No refund, no scramble, and the guest was offered a home you could honestly give them.

Now run the totals. Bookings kept, commission made, reviews protected, margin argued up, and new rules written without anybody sitting down to write them. Every one of those started as one person asking one question. So that person answers it themselves next time, which means the team closes the enquiries it used to park, which means you stop being the last step in somebody else's job, which means the next twenty doors land on a system rather than on a person. That is the difference between a business that grows and a business that just gets busier.

THE TEAM, IN THEIR OWN WORDS

The people who used to ring us now ask it first.

“So far, I have been using it for like, what, two days? So it's a game changer for me.”

Dave Lajom

Operations lead

Two days after it went live

“When I've seen your system, it would be easier for me to understand the 65 units, compared to the US company where I manually check them one by one on monitors. That's why I've been amazed at your system.”

AJ Felipe

Operations VA

Also runs a portfolio for another operator

“It's been very, very helpful in terms of me recommending options to the guests. I don't want to give unnecessary options to the guests that they will not consider.”

Avy Vergara

Operations VA

On choosing what to offer a guest

“It's so much easier. Mo developed the check in and check out, so I don't need to ask every time.”

Shannen Hermo

Cleaning operations

Two weeks into the job

“When the bot came in, I thought, this is much, much better.”

Nathan Valenzuela

Operations VA

On the change in his own workload

“That's why earlier I rang you, Mo. And good thing you didn't pick up, because I was forced to just ask it. And then, oh, okay, I was able to get it. So I would say that gave me more confidence.”

Dave Lajom

Operations lead

On the team being equipped to catch what used to get missed

SEE IT MOVING

Four short films, if you would rather watch than read.

The same threads and the same argument, told on screen.

What it actually is

An executive ops manager in your Slack, in six slides.

Why it exists

60 doors, a small team, and no ops manager.

What it does to the business

Scale is where operations break.

The booking clash

It answered the question it was asked, then found the one nobody asked.

WHAT WE BUILD

Systems for short let operators, with the AI infrastructure underneath.

Nobody buys the same thing here. Some operations need the enquiry side fixed, some need month end to stop eating a week, some need the whole thing joined up. You talk through what is actually costing you, and what gets built is scoped to that. OpSmithOs is the full version of it, and plenty of operators start further down.

The systems

The plumbing most operations never get round to. Enquiries that answer themselves against your live calendar, pre arrival checks that run without anyone remembering, month end that assembles itself, the reporting your landlords keep asking for. Built around your stack and your way of working, not a template you have to bend into.

The AI layer on top

Automation does the same thing every time, which is fine until the situation is not the same. The layer above it holds what your operation is actually trying to do, so it handles the ones no procedure covers and tells your team why, rather than stopping and waiting for you.

OpSmithOs, the full version

Everything joined up and sat in the channel your team already works in, making the calls that currently stop at you. It is the ceiling rather than the starting point, and it is the same build either way, so nothing has to be thrown away to get there.

01

One conversation about where your operation actually hurts

You talk about how your operation really runs, including the parts that only exist as habit in your own head. That conversation is the only thing asked of you. You do not write any of it up, prepare anything, or hand a project to your team. Nothing is added to your week and nothing is taken off theirs.

02

The build happens on our side, while your team carries on

Your team works exactly as they are while it gets fitted around them. Before anybody relies on it, it is put against the questions your operation has already had and corrected until it answers them the way you would have. Nothing goes live on a guess, which is why your team trusts the first answer they get instead of checking it, and an answer somebody has to check first has saved you nothing.

03

From the first week, the questions stop reaching you

Things your team would have brought to you get handled without you. Anything it gets wrong early is our job to fix, not a ticket for you to chase. More gets handled every week after that, because it keeps writing down what it learns. You measure it by how rarely your team still needs you.

WORTH A CONVERSATION

The demo is a live operation, not a deck.

You book a slot, you get the founder. He runs around 60 doors on this every day, so the demo is his actual Slack, the actual threads, the same catches you have just read, happening live. Bring the scenario that hurts most in your operation and watch what comes back.

See it working live inside a real operation, nothing staged and nothing pre recorded.

Talk through where your own week still leans on you, the questions, the escalations, the evenings.

Leave knowing which decisions would stop reaching you first, and what that is worth on your door count.

Book a call with the founder

No deck, no pressure and nothing to prepare. If it is not right for your operation, you will hear that on the call too.

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.

If your operation cannot run a Tuesday without you, that is the thing to fix.

Not another hire, not another dashboard, and not a longer manual nobody opens. The judgement that currently only exists in your head, on shift whether you are there or not, answering your team in the channel they already use, catching what nobody asked it to look at, and writing down what it learns so the business keeps it. None of that is one big change. It is a lot of small ones that feed each other, month after month, and this is what they add up to. Your best person hands in their notice and the work does not get any worse, because what they knew is written down and the next person has it on their first morning. You take a Tuesday off and the operation runs the same Tuesday it would have run with you in it. That is what makes it a business you can keep adding doors to, and a business somebody would want to buy, rather than a job with your name on it. It runs an operation of around 60 doors across 3 cities today, and it was built by the person it was costing. If that is the year you are having, it is worth a conversation.

Book a call with the founder

OpSmithOs. The brain behind the operation.

contact@opsmithos.com