Choosing Software by the Unit You Actually Operate

The system that fits three units is often the wrong one at twelve, and the one built for twelve is usually too much at three. The unit count you run now decides the shortlist.

Last updated: October 12, 2026

Software that fits three units is often the wrong pick at twelve, and the tool built for twelve is usually too much at three. You don't need to guess where you'll be in five years. You need the unit count you run today, because that number decides which features pay for themselves now and which ones just add a monthly line.

Key Takeaways

• Your unit count picks the shortlist, not your wish list. Three units and twelve units need different tools, and the gap between them is real.
• The features that matter later rarely matter now. Group calendars and owner statements can wait until you actually run enough rooms.
• A low monthly fee can still cost the most. The cheap tier turns expensive when you keep doing by hand what the tool won't do.
• Per-unit pricing makes the math honest. A flat fee hides your cost; a per-unit fee shows it at every size.
• Keep the shortlist and revisit it each season. What fits at three units can stop fitting the moment you add the fourth.

What changes between three units and twelve

At three units, you can still hold most of the operation in your head. You know which guest checks in on Thursday, which flat needs a cleaner, and which night is still open on the calendar. Software at this size is support, not spine.

At twelve, the same mental model breaks. Twelve calendars stop fitting in one picture. Two guests arrive the same afternoon in two different units, and a turnover slips because it lived on a note you forgot to move. The work doesn't just get bigger; it changes shape.

The clearest difference is the number of decisions per day. Three units ask a handful of questions. Twelve ask the same handful every few hours, across more people. Once you add a cleaner, a co-host or a helper, the questions also stop arriving to one person.

Unit count also changes how you buy supplies and how you schedule people. Three units mean one cleaner on one day. Twelve mean a rota, a stock count and a backup for the day someone's car won't start. None of that counts as a software feature, yet all of it decides what the software has to hold.

So the first question isn't which software is best. It's how many units you'll actually run this season, and how many hands will touch them. Those two numbers do more to narrow the field than any feature checklist built by someone else.

The features that only matter later

Some features earn their place at three units. Others are built for the moment you pass ten, and buying them early means paying for capacity you won't use yet.

A shared calendar is early. Even at three units, one view of what's booked and what's open saves you from checking two apps. Direct connections to the channels you sell on are early too, because they cut the manual re-typing that causes most double bookings. LOCALSBNB connects directly to four OTAs: Airbnb, Booking.com, Agoda and Trip.com.

Owner statements, staff permissions and multi-property reporting belong in the later group. They matter when you answer to someone else, or when one person can't see every unit anymore. At three units they're often just clutter.

Importing beats typing, and it's useful from day one. If you already run on Airbnb, you can pull your listing data across, titles, photos, base capacity and calendar structure, instead of rebuilding each unit by hand. That's a one-time saving, but it's the kind that decides whether setup takes an evening or a weekend.

A useful test is to ask when you'd feel the absence of a feature. If the honest answer is "when I'm at eight units", it belongs in the later pile. The features worth paying for today are the ones whose absence you'd feel this week, not next year.

Where a low monthly price becomes expensive

A low monthly figure isn't the same as a low cost. The cheap tier turns into the expensive one when it stops doing a job you then pay a person to do instead.

Picture the split. A tool at the lowest tier might keep the calendar in sync but leave every message to be answered by hand. At three units, that's an hour a week and easy to absorb. At twelve, it's closer to an hour a day, and you're either answering messages at midnight or paying someone to.

The same logic runs through rates. If a tool can't hold a rate plan, you rebuild each price whenever a season turns, and those hours add up quietly. The monthly fee is visible; the lost evenings aren't.

This is where per-unit pricing helps rather than hurts. A per-unit fee turns the cost into something you can divide by the nights you sell, so you can see when the tool has paid for itself and when it hasn't.

There's a mirror image of this problem. Paying for a heavy tier at three units feels like progress, but the extra features sit unused while the fee runs every month. Over-buying and under-buying cost you in the same currency: money you can't get back and time you didn't save.

A shortlist you can revisit each season

The method is simple. Write down the number of units you run now, add one or two for the season ahead, and list the three jobs you most want off your plate. Then check each candidate against those, not against a feature list built for someone else.

Ask one question per candidate: does it remove a job you'd otherwise do by hand at your current size? If the answer is no, it belongs in the later pile, whatever it costs. If the answer is yes, check the per-unit price at your real unit count.

Then price it honestly. LOCALSBNB runs on two tiers: a lightweight plan at $4.5 per unit per month when you pay yearly, or $7 per unit per month monthly. At three units the gap is small; at twelve it's worth a minute of arithmetic. You can see the tiers and start on your own listing at localsbnb.com.

Revisit the shortlist every season. A tool that fit six units may strain at ten, and one that felt light at three may hold longer than you expect. Choosing once and never looking again is how hosts end up paying for a heavy system they no longer enjoy.

Write the season on the list as a date. When the date comes round, open the list, check the unit count, and ask the same question again. A shortlist without a review date quietly becomes a decision you never made.

One more habit keeps the list useful. Keep it short. A shortlist of two or three tools you've tested against your real jobs beats a spreadsheet of ten you've only compared on price. The point isn't to survey the whole market; it's to leave with one tool that fits the size you run.

FAQ

How many units before I need software at all?

There's no fixed number, but three is usually where a shared calendar starts saving real time. Below that, one well-kept calendar can carry you, as long as you're the only person who touches it.

Is the cheapest tier always the wrong choice?

No. It's the right choice while it still removes the jobs you do by hand. It turns expensive only when you keep doing those jobs anyway and pay for help on top.

What should I check before I pick a tier?

Check it at your real unit count, not the number you hope to reach. Then check whether it imports what you already have, so setup doesn't eat a weekend you'd rather spend elsewhere.

The number of units you run isn't a small detail. It's the filter that does most of the work. Match the tool to that number, keep the later features in a later pile, and price everything per unit so the arithmetic stays honest. When you're ready to compare tiers against your own listing, localsbnb.com is a sensible first stop.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current requirements of your local authority and the terms each platform applies today.