Onboarding is a confession

Somewhere in your inbox is a calendar invite called Onboarding: session one of four. You bought the software to get your evenings back, and its first move was to take four of them. Nobody in this industry finds that strange any more. We never stopped finding it strange. Buying software that then requires you to learn software is like ordering dinner and being handed a recipe.

The industry has a tell

Look at the apparatus that has grown up around business software. Implementation fees. Onboarding specialists. Customer success teams. Certification academies, where you can become an accredited operator of somebody else's product. Help centres the size of small universities. Tooltip tours that open with the words Welcome to your new workspace.

Every piece of that machinery exists for one reason: the product, on its own, does not fit the person it was sold to. An industry that believed its software was usable would not employ an entire profession to teach people to use it. The training programme is the confession. Somebody measured the gap between their product and your reality, and decided you should be the one to close it.

The learning curve is a bill

Vendors talk about the learning curve the way they talk about the weather, as if it arrives naturally with every product and must simply be endured. It is not weather. It is a bill. At some point in that company's history, a design decision was made easier by making the product harder, and the cost of that decision did not vanish. It was posted to you, payable in evenings and webinars.

No other tool in your life gets away with this. The kettle did not come with an implementation partner. The drill has no certification track. When a door needs a printed sign telling you whether to push or pull, designers call that a failure of the door, not a failure of the people walking into it. Software is the only industry that took the same failure and rebranded it as your homework. We hate this. Not as a marketing position, but as operators who have sat through the webinars ourselves.

You run properties, not software

This lands harder in our corner of the world than most. Nobody gets into short lets or rentals because they want to administer systems. Yet the standard advice for a growing portfolio is to buy a stack of them: a channel manager, a pricing tool, a messaging tool, a task app and a spreadsheet with opinions. Five products, five learning curves, and you as the unpaid integration layer in the middle. We wrote about that trap in our guide to running a portfolio without hiring, and the punchline bears repeating: every hour you spend learning a tool, feeding a tool or refereeing two tools that disagree is an hour your actual business did not get.

The tools were supposed to be staff. Somewhere along the way, you became theirs.

Turn it around

You should not have to learn to use software. Software should learn to use you.

We mean that sentence exactly as written. A good assistant learns how their principal works: when to interrupt, what to escalate, what counts as obvious, which decisions are theirs to take and which ones wait. That is what your software should spend its first week doing. Studying you. Not the other way round, with you two modules deep in its academy, earning a badge for finding the dashboard.

And software arriving in 2026 should already know the job before it meets you. Short lets and rentals are not a mystery domain. Prices go stale, guests message at midnight, cleans follow checkouts, owners want to know where the money went. A system built for this work should walk in the door knowing all of that, the way a good hire would, and then learn the specifics of your operation: your properties, your floors, your rules about who approves what.

What that looks like in practice

Inside Upgraded OS, the test for every feature is whether it works this way round. The Smart Pricing Engine reprices every listing overnight against live market data, inside floors you set. Setting a floor is a decision you were always going to make. It is not a revenue management course. The unified inbox pulls every guest conversation from every channel into the one place you always believed they belonged. Cleans and inspections fall out of the booking calendar as tasks on their own, and owner statements assemble themselves from the money that actually moved, ready to share without a spreadsheet weekend. If you want the sober version of what genuinely runs itself and what still needs a human, we wrote that down too.

Is there anything to tell the system at the start? Of course. Your properties, your floor prices, your rules. But that is a conversation, not a curriculum. You are handing over decisions you already own, not memorising menus somebody else designed. After that, the adapting is the software's job. Yours is approving what matters.

Our own confession

Our homepage says the first cohort is a handful of operators we onboard personally, and we do. That is what an early product owes its first operators, and we would rather be in the room than pretend otherwise. But notice the direction of those sessions. They are not training. Nobody is walked through modules. They are the conversations where the software learns each operator: the properties, the floors, the rules, the way each of them likes to run things. The first cohort is not learning Upgraded OS. Upgraded OS is learning them, and every operator it learns makes the next operator's first day shorter.

The standard, in one line

If a feature needs a tutorial, it is not finished. That is the rule we hold ourselves to, and you are welcome to hold us to it as well. If we ever invite you to a training webinar for our own product, something has gone badly wrong in our building. The only first day we are prepared to ship is the one a great assistant gives you: a few sharp questions, and then the work quietly starts happening.

Software that costs you a course before it saves you an hour has started its life in debt, and most of it never works the debt off. Yours should arrive solvent.