Planning for Twenty Units: What Changes at Five

The first four units run on your attention. The fifth is where attention stops scaling, and everything after it is a system you build once.

Last updated: October 28, 2026

Four units is not a small business run badly. It's a small business run on memory, and memory is remarkably good at four. The fifth unit is where the model breaks — not because the work doubles, but because the dependencies start crossing. Two changeovers on one morning, one cleaner, one lock that jams. Recall can hold four units. It can't hold four units and a conflict.

Key Takeaways

• The ceiling isn't a number, it's a moment. It's the first time you learn something about a unit from a guest instead of from your own day.
• Five breaks because of crossings, not volume. One cleaner and two changeovers on the same morning is a scheduling problem, not a cleaning problem.
• Four things have to become processes. Turnover, arrival, supplies, and the rate check. Everything else can stay personal.
• Hire the hours, not the roles. The first hire removes the ten at night phone call. The second removes the seven in the morning key handover.
• At twenty, the calendar is the object. You don't hold it in your head. You read it, weekly, and you look for the crossings.

The four-unit ceiling

Ask a host with four units how they know Thursday is busy and they'll say they just know. That's not laziness. It's an accurate description of the operating system: four changeover days, two cleaners, a handful of access quirks, and a memory that's been trained on all of it for a year.

Then a fifth arrives, and the same memory starts producing errors that feel like bad luck. A cleaner sent to the wrong unit. A guest told the code that was changed last month. A night left open on one channel while it sold on another. None of those is a competence problem. Each one is a recall problem wearing a competence costume.

The signal to watch for isn't volume. It's the direction information travels. While you're running on memory, you find out about a unit because you were there, or because you thought about it. Once the model breaks, you find out because someone told you — a cleaner, a guest, a neighbour. The day you learn about your own property from a stranger is the day the ceiling arrived, and it arrived a few weeks before you noticed.

The number itself varies. Some hosts hold six because their units are in one building and the crossings are few. Some break at three, because the units are an hour apart. What doesn't vary is what happens next: the work has to move out of your head and onto a page, and the page has to be good enough that someone else can act on it.

What has to become a process

Four things, in this order. Not because the others don't matter, but because these four are where a single missed step becomes a guest-visible failure.

Turnover. Not a checklist yet — a schedule and a standard. Which unit, which day, who's doing it, and what "done" looks like when they leave. The written standard can be six lines. What matters is that two different people produce the same room from it.

Arrival. Access, the message that carries it, and the one thing a guest always asks. Written once per unit type rather than once per unit, then varied where the unit actually differs. Twenty units don't need twenty documents. They need three or four, plus a short list of exceptions.

Supplies. Linen, consumables, the spare key that lives somewhere. At four units you buy when you notice. At eight you buy when you count, because noticing stops working the week two units turn over on the same day.

The rate check. One pass a week across every unit and every channel: what's published, what's open, what's priced strangely. This is the one that quietly costs the most when it's skipped, because an empty night doesn't announce itself the way a dirty room does.

That pass only works on one screen. localsbnb.com connects Airbnb, Booking.com, Agoda and Trip.com in a single calendar and shows each channel's own rate and its status next to yours. So "what's published this week" becomes a view rather than a tour of four tabs.

A useful test for whether something is a process yet: could a competent person who has never done it follow the page, once, without calling you? If the answer is no, what you have is a habit with a document near it.

Then write the exception list. Twenty units have maybe nine real differences — the parking, the water pressure, the neighbour who complains, the stair that's steep. Nine lines, kept current, saves more time than another page of procedure.

The team shape at twenty

Twenty units is roughly one full working week of coordination before anyone cleans anything, which is why the first version of a team is always smaller than hosts expect and more specific than they plan.

The useful split isn't by job title. It's by decision. Keep the decisions that carry money or a relationship: what a night costs, what gets refunded, how an owner or a landlord is spoken to. Hand over the ones that carry a clock: cleaning, messaging after a certain hour, keys in the morning.

That produces a sequence rather than an org chart. The first person you bring in is the one who takes the ten at night phone call, because that's the hour that ruins the next day. The second takes the seven in the morning key handover, because that's the hour you can't move. Only after those two are covered does a third person start to make sense, and usually they arrive when one unit type has grown enough to need its own standard.

Hire after the process, not before it. A person handed an unwritten system inherits your chaos, learns it, and then leaves — taking the only copy with them. A person handed six lines and an exception list can improve the system, which is a different job and a much better one.

What you shouldn't do is solve twenty units by working twenty more hours. That works for a season and then it produces the error that costs a review, a booking, or a relationship with an owner you can't replace.

The calendar you can't hold in your head

At four units you look at the calendar to confirm what you already know. At twenty you look at it to find out. That's a different habit, and it needs a different weekly ritual — twenty minutes, same day, four questions.

What sold last week that I didn't expect. What's still open in the next fortnight that should have gone. Where is one unit pricing away from the others without a reason. Which channel has gone quiet, and is it the channel or the date.

Those four questions need the calendar and the numbers side by side. What matters isn't the individual row, it's what sits across it: a date open on one channel and sold on another, a price that never moved when the rest did. The dashboard keeps occupancy, ADR and RevPAR in view for the same period, which is what turns "the week felt quiet" into a number you can act on.

The crossings are what you're looking for. Two units turning over the same morning with one cleaner booked. A channel still publishing an old price for a week you repriced. A long stay that blocks the two nights that always sell. None of those appears on a unit-by-unit view; all of them appear when twenty units sit on one grid.

There's a second use for the same screen at this size: answering questions without opening it. Which units have guests arriving today, which are in-house, which are leaving. At four units that's a glance. At twenty it's the difference between a morning that starts with a plan and one that starts with a phone.

FAQ

Is five actually the number where it breaks?

For a lot of hosts, yes, and for reasons that have nothing to do with five. It's the point where the number of daily dependencies overtakes what a person can hold at once. If your units are spread across a city, it may be three. If they're in one building, it may be seven. Count the crossings in a normal week and you'll find your own number.

What should I standardise first?

Turnover, because it's the one a guest notices within a minute of walking in. Write six lines, have a second person follow them without your help, then fix whatever they had to ask about. The arrival message is next, and it's usually a single afternoon.

Do I need a team before twenty units?

No. You need a team before the hours you can't cover. For most hosts that's one person for evenings and one for mornings, and it happens somewhere between eight and fifteen units. Hiring earlier usually means paying someone to watch you work.

Twenty units isn't four units five times over. It's a different job with the same vocabulary, and the transition happens on a specific day, in a specific week, when you find out about your own property from someone else. The useful response is to write down what you already know how to do, and then to look at the week on one screen instead of twenty. localsbnb.com puts the bookings, the rates and the week's occupancy, ADR and RevPAR in the same place, which is what puts a crossing in front of you before it turns into a phone call.

---

This article is general guidance for hosts and isn't legal, tax or financial advice, and it isn't a staffing or employment standard. What a host may delegate, how a worker is engaged and what has to be declared differ by place. Confirm the current requirements with the competent authority and take local advice before you change how your units are run.