Should You Hire an Admin or Automate? The Maths for a 40-Room Operator

There is a point, usually somewhere between thirty and fifty rooms, where the admin stops fitting into the edges of the week. Rent reminders, tour confirmations, move-in documents, the enquiry that came in on Saturday night. None of it is hard. All of it is constant.

At that point most operators reach for the same two options. Hire someone. Or buy something that promises to handle it.

The comparison gets made badly, because it gets made as a price comparison. A salary against a subscription. That framing produces the wrong answer roughly half the time, and the wrong answer is expensive in both directions: a hire who spends their week on work that never needed a person, or an automation build that runs into the first real exception and gets quietly abandoned.

Here is a better way to run the numbers.

The Real Question Is Which Hours

A person and an automation are not competing for the same work. They only look like they are because both of them are answers to "I am spending too many hours on admin."

Automation is very good at work that repeats on a schedule and never varies: the reminder that goes out on the same day every month, the confirmation that follows every tour booking, the document request that fires the moment someone signs. It does this at 2am on a Sunday without being asked, and it does not forget when you are on holiday.

A person is very good at everything with judgment in it. The resident who is late on rent for a reason that matters. The prospect who is clearly a poor fit for the house and needs to hear it kindly. The maintenance issue that is actually a conflict between two people. A viewing where someone needs to be shown the room.

So the first thing to work out is not what either costs. It is what fraction of your admin week is judgment and what fraction is repetition. Until you know that number, you are guessing.

A Hire Costs More Than the Salary, and Less Than You Fear

Check local rates rather than trusting a figure from an article, but for a full-time operations admin in most US markets you should model somewhere around $42,000 a year once you include payroll taxes, benefits and the software seat they will need. Part-time at twenty-five hours lands nearer $22,000.

The costs people leave out are the ones that matter. There is a hiring process, four to eight weeks of it. There is training, which comes out of your week, not theirs. There is the fact that a single admin is a single point of failure: when they are ill or on leave, the reminders stop going out, because the reminders were them.

And there is the ceiling. A person who is fully occupied at forty rooms is not going to absorb sixty. You will have this conversation again.

What you get in exchange is real and often undervalued. Someone who notices things. A person who can tell you that three residents in the same house have all gone quiet, which is not a data point any system was watching for.

Automation Is Cheap Until It Meets an Exception

A well-scoped automation build for a portfolio this size is a four-figure project, not a five-figure one, and it does not recur at anything like salary scale. On pure arithmetic against a $42,000 hire, it is not close.

That arithmetic is also the reason this comparison gets made badly. The build is only cheap if it is scoped to work that genuinely repeats.

The failure mode is well documented and it always looks the same. Someone automates a process that has an exception in it roughly one time in eight. The automation handles seven cases correctly and the eighth badly. The operator loses confidence in all eight, turns it off, and concludes that automation does not work in this sector. What actually happened is that a judgment step got handed to something that cannot exercise judgment.

The fix is not better software. It is drawing the line in the right place before you build, then making sure the exception routes to a human quickly and visibly rather than sitting in a queue nobody watches.

Sort Your Week Into Three Piles Before You Spend Anything

This takes an afternoon and it is the highest-return afternoon in the decision.

Log every admin task for two weeks. Not categories, actual tasks, with rough minutes against each. Then sort them into three piles.

The first pile is work that repeats identically. Rent reminders. Tour confirmations and the reminder before the tour. Document requests at move-in. The first reply to an enquiry. Renewal outreach opened ninety days ahead. This pile automates well and it is usually far larger than operators expect.

The second pile is work that needs judgment every time. Difficult conversations, pricing decisions, conflict, anything where the right answer depends on knowing the person. This pile needs a human and always will.

The third pile is work that repeats but has exceptions. This is the pile that decides your answer, and it is where most of the money is. It automates only if the exception has somewhere obvious to go.

Now total the minutes. If the first pile is most of your week, automate first and hire later, smaller, if at all. If the second pile is most of your week, hire the person and stop reading articles about automation, because it will disappoint you.

When the Hire Is Genuinely the Right Answer

There are situations where a person is straightforwardly correct and it is worth saying so plainly.

If your properties need someone physically present, that is a person. If you are running under twenty rooms, your admin load probably does not justify either spend yet, and the honest answer is to wait. If your processes change every month because you are still working out what the business is, automating them means rebuilding them repeatedly. Stabilise first.

And if the work you want to hand off is mostly relationship work, a person will do it better than any system, permanently.

Do the Audit First. It Costs You Nothing Either Way.

The reason this decision goes wrong is almost never that someone picked the wrong option. It is that they picked before they knew the split between their three piles.

An operator who knows that sixty percent of their admin week is identical repetition will make a good decision in either direction. They might automate that sixty percent and hire part-time for the rest. They might hire full-time and automate later. Both are defensible. What is not defensible is spending $42,000 a year, or four figures on a build, on a guess.

Do the two-week log. Sort the piles. Then decide.

If you would rather not do the sorting yourself, that is what our free operations audit is: we map your actual workflows, identify which pile each task belongs in, and give you the Operating Map at the end. You keep it whether or not you ever work with us, and it is just as useful for writing the job description as it is for scoping a build.

Either way, get the number before you spend the money.