Skip to main content

Professionals

Hitting the twenty-property wall: why two people can't go much further

The point where a two-person team stops coping, the signs to spot it in time, and the real options for getting past it without breaking the company.

Matéo Baraness
Matéo Baraness

23 June 2026 · 4 min read

When I launched Nomad's Co, we were two. Me and someone on support. We had no trouble handling around twenty properties with that setup. Everyone starts out that way: when you launch a property management business, you're convinced you can stay as a pair for a long time. And it's true — up to a point.

That point sits around twenty properties. I saw it in our own numbers, and I've seen it at plenty of property managers we coach in our academy. It's almost always the same threshold.

The wall, and how you spot it

You don't see it coming at first. You keep signing new properties, revenue grows, you tell yourself things are running. Then the signals show up, in this order:

Response times to guests get slower. You used to reply in ten minutes, now it's two hours. Sometimes more when one of the two of you is out on site. Guests start complaining in reviews.

You start forgetting things. A check-out that didn't get confirmed, a complaint that slips through, a guest who didn't receive their arrival instructions. Nothing serious individually, but it multiplies.

Review scores drop. Gently at first. You go from 4.9 to 4.8. Then 4.7. You tell yourself it's natural variability, but in reality it's structural.

Your team is exhausted. On Sunday evenings nobody wants to answer messages. Weekends become an ordeal. Holidays are unthinkable.

You stop prospecting. You don't have the time. You turn down owners who reach out because you know that accepting one more property means digging deeper into the hole.

That's when you've hit the wall. Twenty properties with two people is the mathematical limit.

Why it's twenty and not thirty

The maths is straightforward. A typical short-term rental property runs around a hundred nights booked per year, spread across roughly forty reservations. Each reservation involves between five and fifteen interactions (messages before, during, after the stay).

For twenty properties, that's between four thousand and twelve thousand interactions per year. Roughly ten to thirty a day on average, but with spikes up to fifty on a summer Saturday.

On top of that you've got the operational work: scheduling cleanings, managing suppliers, dealing with incidents, invoicing owners, handling complaints. Two full-time people can absorb that — but only just.

Options for getting past it

I've seen three possible paths.

Option 1: hire

The obvious one. You bring on a third person, then a fourth. You structure the roles (guest support, operations, sales).

The problem is that the economics are tight. One extra employee, with all-in costs, runs three to four thousand euros a month. To cover that cost, you need to add ten to fifteen properties. Finding them, signing them, onboarding them takes six months minimum. And during those six months, you're paying a salary without the revenue to match.

It's the classic path, but it's risky. Plenty of property managers fall apart at exactly this moment because they hired too early or didn't plan cash flow well enough.

Option 2: cap the business at twenty properties

It's a real option, and some people pick it deliberately. They put a ceiling on their growth and keep a small, calm operation.

The upside is you control everything. The downside is you're leaving money on the table, and more importantly, you're fragile. If one owner takes their property back in-house, you immediately lose five percent of your revenue. And you're still working just as hard.

Option 3: automate what can be automated, hire for the rest

This is the strategy that worked best for us, and it's what we recommend when we coach other property managers.

The principle: look at your operational load and identify what's repetitive with no added value. Answering routine guest questions is typical. Sending check-in instructions is typical. Chasing for reviews is typical.

You put in place a system that absorbs that layer. A well-configured conversational agent can handle seventy to eighty-five percent of guest interactions with no human involvement. Across twenty properties, that frees up fifteen to twenty-five hours a week.

You reinvest those hours in what actually matters. Prospecting. The real emergencies when they happen. On-site operational quality. The relationship with owners.

And when you reach forty properties, that's when you hire. But not because you're drowning: to structure healthy growth.

What we did at Nomad's Co

We went from twenty to over a hundred properties in under two years with a team that stayed small. The thing that changed everything was putting in place — from twenty-five properties onward — a system that handled the entire conversational layer. Today more than eighty-five percent of guest interactions are absorbed without any human intervention, and only the important requests make it up to us.

It wasn't magic at the start. We had to enter very precise information for each property, define the rules clearly, calibrate the call-transfer rules for when there's a genuine problem. But once the system hit its rhythm, we could sign new owners one after another without adding weight to the team.

What I'd recommend

If you're between ten and twenty properties, take an honest look at your mental load. If you're already tired, don't hire straight away. First, automate the layer that's saturating you. You'll gain time, stabilise quality, and know better when you actually need another member of staff.

If you're at twenty properties or more, and your team is on the edge: it's urgent. Every week that passes with under-served guests is another wave of falling reviews and owners starting to doubt. The supporting system you put in place can be operational in two to three weeks, and you recover fast.

Scaling up is the most dangerous moment in a property management business. Most of the structures that close down do it at this point, not at launch. Take it seriously.