STR Global Unlocked with Simon Lehmann: Unfiltered knowledge for the short term rental industry

Why Scaling Your STR Breaks Without This System

• Powered by AJL Atelier

Share episode

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 11:50

Book a strategic consultation with me now: https://bit.ly/simon-consultation

Scaling a short-term rental business shouldn’t mean hiring endlessly, adding more tools, or working longer hours. Yet for many STR operators, growth creates more complexity, tighter margins, and a business that still depends heavily on the founder.

In this video, I break down what actually makes a short-term rental business scalable. Drawing on decades of experience building and leading companies in the hospitality industry and working with operators managing anywhere from 50 to 10,000+ units, he explains why most STR businesses build the wrong kind of systems.

You’ll discover the three pillars every scalable STR operating system needs, why SOPs and technology alone aren’t enough, and what separates a documented process from a system that actually works without you.

Resources

Stay connected:

SPEAKER_00

Have you spent years scaling your short-term rental business, hiring more people, adding more tools, working longer hours, only to find that growth feels harder than ever. Your margins keep slipping, and the business doesn't function without you. I've led companies that grew from a few hundred to several thousand units. I was co-founder and chairman of Ocasa Europe, chairman of MadeConf in Australia, and today I work with operators managing anywhere between 50 and 10,000 units and more. And I see the same problem at every single one of those levels. It comes down to whether your systems carry the business when you're unreachable for two weeks, or whether everything falls apart after three days. In this video, I'll show you what exactly makes a system work in our industry. Why most STR operators have built the wrong kind of system without realizing it, and what you need to change to scale faster and finally step out of the day-to-day business and operation. There's actually one specific component that decides whether a system generally scales or whether it just sits in a notion dock nobody opens. It's not your tech stack, it's not your SOPs, it's not how many people you've hired. I'll show you what it really is in a moment. And if your business currently feels like it can't run without you for a single day, there is a link below this video where you can book a consultation with me directly. Let's get on to it. The three pillar model. Before we get into the details, a generally scalable system in an STR business stands on three pillars. If one of them is missing or weak, the whole system collapses under pressure. Let me walk you through each of them and pay close attention when we get to the third pillar, because that's exactly the component I mentioned at the start. The one that almost every operator either leaves out completely or underestimates. Pillar number one, the operating model. The first pillar is your operating model. The standardized way work gets done across onboarding, pricing, housekeeping, maintenance, guest communication, and owner reporting. And I want to be very clear, this is not a binder of SOPs. It's a tiered playbook, standard, premium exception, where roughly 80% of your properties run on autopilot and only the 20% that generally require it get controlled variation. This pillar is critical because without it, every new unit you sign adds operational drag instead of leverage. You scale headcount linearly with units your margins compress and your service quality actually drifts as you grow. What most operators in our industry get wrong is that they customize per owner. Every property becomes a snowflake. The playbook exists in someone's head, usually the founders. And then they confuse a notion workspace full of SOPs with an actual operating model. Those are not the same thing. How do you do it right? Three tiers maximum. You force fit every unit into a tier. Your owner contracts enforce the tier upfront. You don't negotiate operations downstream. Every process has one owner, one KPI, and one escalation path. And the playbook gets reviewed quarterly, nothing changes outside that window. When this pillar is missing, you become the system. Two days off and the business wobbles. Two weeks and it falls apart. That's the first pillar. But even if you build that one correctly, without the second pillar, you still don't have a foundation. And without the third, which I'll show you in a moment, everything collapses the second your volume goes up. Pillar number two the data and tech spine. The second pillar is your data and tech spine. An integrated stack, the PMS, the channel manager, revenue management, guest comms, ops, accounting, all writing into one data model for every unit. Guest owner and PL. The principle is simple. Tools serve the data. The data does not serve the tools. This pillar is critical because without a single source of truth, every decision becomes a debate. Your team wastes hours reconciling spreadsheets instead of running the business. You can't see margin per unit, per owner, per channel. So you optimize the blind. What most operators get wrong is that they bolt on tools as they grow. Each new tool has its own logic for what a unit is or what a booking is. Data ends up in five places, none of them agree with each other, and the founder becomes the human integration layer between systems that should be talking to each other directly. How do you do it right? Pick your master system, usually the PMS, or start building an integration layer on AI and force every other tool to conform to its data model. Reconciliation runs daily and automatically, not manually at month end. You build one dashboard per role. GM, ops, revenue manager, owner success, not 14 tabs in a spreadsheet. And you audit the stack annually. Kill anything that doesn't write into the spinal. When this pillar is missing, you have data but no information. Decisions get made on instinct or on volume, not on economics. And that brings us to the pillar that decides almost everything. The component I told you about at the start, the one that isn't in your tech stack, isn't in your SOPs, and that you cannot replace with more headcount. Pillar number three, the decision loop. Closing the open loop. The third pillar is the decision loop, the management operating system that turns data into decisions and decisions into accountable action on a fixed cadence. KPIs, review decision, owner, deadline, follow-up, repeat weekly, monthly, quarterly. This pillar is the connective tissue between the first two. It stays invisible because you cannot see it in a tech stack diagram or an org chart. It lives in calendars, in how meetings are structured, and in how disagreements get resolved. That's exactly why operators leave it out. There is nothing to buy or install. But this is the real lever. Because pillars one and two produce signals. Without a loop, those signals never translate into action. You can have the cleanest dashboard in the industry and still drift because nobody owns the metric or has the authority to act on it. What most operators get wrong here, there is no fixed cadence. Meetings happen only when problems blow up. KPIs exist without specific owners. Marketing cares about occupancy. Nobody specifically owns it. The founder is the escalation path for every non-routine decision. And the so-called reviews become status updates instead of decisions. How do you do it on the data side? Five to seven KPIs that actually move the business, not 50. Each KPI has a target, an owner, a cadence, and a defined escalate when trigger. Reviews end with the decisions and deadlines, not vague action items. How do you do it right now on the people side? Decisions rights are documented at every level. The GM doesn't ask you whether to refund 200 euros or dollars. You promote the operators who close loops, not the ones who create them. And the founder shows up to the quarterly review, not to the weekly. A great example of this in action is what Konstantin Schroeder has built at RBO. They've scaled to around 1500 units in property management. But here is the part most operators miss. They didn't scale their headcount at the same rate. The unit count went up materially without the org chart following the same curve. Now think about what that actually requires. The moment you decouple unit growth from headcount growth, every weakness in your operation loop becomes visible. Fuzzy standards, vague KPIs, unclear accountability, no one of it survives that kind of scaling. Your loop has to be airtight before the operation collapses under its own weight. So what they have effectively done is productize the decision loop. Standards are codified across portfolio. Performance is measured per unit, per market, per process. Accountability sits with named owners at every layer. And the data feeds back into where attention is focused next. That's the loop running in production every single day without the founder having to manually orchestrate it. And that's the real lesson here. Most STR operators couldn't add 500 units without doubling their team because their internal loop isn't tight enough. The standards aren't codified. The data isn't trusted. The accountability is fuzzy. They'd been drowning within months. So if you want to test how strong your decision loop really is, ask yourself a simple question. Could you double your unit count over the next 12 months without doubling your team? If that answer is no, you don't have a decision loop. You have a hierarchy that depends on you being in the room. So if you want to test how strong your decision loop really is, ask yourself a simple question. What happens to a business that builds this pillar correctly? The business runs without you. You go from operator to owner. You can take two weeks off, sign new units, raise capital, even prepare an exit. Because the loop is closing whether you are in the room or not. Those are the three pillars every genuinely scalable STR system stands on. And no matter where you currently are, one thing always stays in the same. The operators who scale sustainably are the ones who treat their systems as they actually product their building. And no matter where you are currently, one thing always stays the same. The operators who scale sustainably are the ones who treat their systems as the actual product they are building, not as documents they put together once and forget about it. If you want to see what it looks like when an operator builds this on 1500 units without adding more headcount, watch my interview with Konstantin Schroeder of RBO next. I'll see you there.