How to Hire an STR Property Manager: The 5-20 Door Checklist

TL;DR: The math has to work first: gross revenue needs to absorb a 15-25% management fee and still outperform your self-managed net. When the math works, four things determine whether the relationship succeeds: whether the PM has real presence in your specific sub-market, what the contract base actually calculates fees on, what performance benchmarks you lock in before signing, and how clean the exit is. Each is easy to skip under sales pressure. None of them are optional.

Most STR operators who hand over a portfolio at 5-20 doors do it too early, too fast, or for the wrong reason. Delegation is not a remedy for operational chaos, and a property manager does not build a broken operation. They run whatever you give them.

When handing over actually makes sense

Three conditions support the decision. Ideally all three are true before you start having PM conversations.

First: the gross revenue per door is high enough that a 15-25% management fee leaves you with more net income than you currently keep, after valuing your own time at an honest hourly rate. If the math does not close without heroic occupancy assumptions, the PM relationship will disappoint before it delivers.

Second: you have a constraint that a property manager resolves better than a virtual assistant. Local physical presence is the clearest case. A guest emergency at 2am in a market where you live six hours away is a PM problem, not a VA problem. If you have that constraint but are not certain a full PM is the answer, a local co-host arrangement paid per-turnover or hourly is worth testing first. It costs less and tells you whether the specific gap is actually being filled.

Third: you have documented SOPs and a working tech stack to hand over. Cleaners, check-in flows, guest communication templates, pricing logic. A PM who inherits no documentation starts from zero, and you pay management fees while they reconstruct what you should have already built.

The VA playbook for 10 to 30 door operators covers the automation and delegation layer that typically comes before a full PM engagement makes financial sense. If you have not gone through that layer, start there.

What to evaluate before any fee conversation

Five things worth verifying before terms come up.

Doors under management in your specific sub-market. Not the metro. Not the state. How many listings do they actively manage in your zip code or neighborhood tier, and how long have they been there. A PM with 300 doors regionally may have three in your market and no pricing intelligence for your demand patterns. That is not local expertise.

The PMS they use and the owner portal it provides. Most professional operators run Hostaway, Guesty, or equivalent. Ask to see the owner portal. You should be able to view real-time bookings, maintenance requests, and monthly revenue statements without asking for them. A monthly PDF email is not an owner portal.

Channel distribution and dynamic pricing setup. Which OTAs will your listing appear on, and is dynamic pricing active from day one? Some PMs default to Airbnb only and static pricing unless you push explicitly for more. Confirm in writing which channels launch at onboarding, which pricing tool they use, and who sets the minimum rate floor.

Guest response time and overnight coverage. Ask specifically how they handle a guest emergency at 11pm on a Saturday. A 24/7 staffed inbox, a tiered offshore response, a local co-host on call: any of these can work. Know which you are buying before you assume it.

References from current owners in your market with similar property types. Not testimonials on their website. Names, contact information, and permission to call. One conversation with a current owner in your sub-market tells you more than an entire discovery call.

Fee structure: what you are actually paying for

The calculation base matters more than the headline percentage. Two management contracts at 20% are not the same price if one calculates on gross booking revenue including cleaning fees and the other calculates on net of OTA service fees.

Four terms to get confirmed in writing:

1. The base. Gross revenue, net of platform service fees, or net of cleaning fees. The difference on a $60,000 per year gross property can run $4,000 to $8,000 in annual fees at the same percentage.

2. Cleaning fee treatment. Are cleaning fees charged to guests inside the base, meaning you pay the PM a percentage on cleaning revenue, or are they passed through at cost?

3. Maintenance markup. Most PMs mark up vendor invoices. Confirm the percentage and whether there is a cap per incident or per month. An uncapped markup on a significant repair adds up faster than the headline management rate.

4. One-time onboarding or setup costs. Photography, listing creation, system migration. Legitimate and common; know the number before signing, not after.

xychart-beta
  title "Annual PM Fee on $60,000 Gross Revenue by Rate"
  x-axis ["10% of gross", "15% of gross", "20% of gross", "25% of gross"]
  y-axis "Annual fee paid ($)" 0 --> 18000
  bar [6000, 9000, 12000, 15000]

Calculated on $60,000 gross booking revenue. Actual fees vary by calculation base (gross vs. net of OTA fees), cleaning fee inclusion, and maintenance markups. The base definition, not the headline rate, is the number to negotiate. Data as of August 2026 based on standard market structures; verify with each PM.

For the published rates we could verify directly from management company pricing pages, including TIDY at 3.9%, Evolve at 10-15%, and Weekender Management at 25%, see STR management fee benchmarks: what we could verify.

Contract red flags

Five terms that warrant a second read before you sign.

Auto-renewal with short or no notice period. A contract that renews for a full year unless you give 90-day written notice locks you in independent of performance. Standard termination notice runs 30 to 60 days. Anything that makes exit harder than entry is written to favor the PM.

Exclusivity without a performance floor. An exclusivity clause preventing you from switching managers is acceptable if it comes with defined performance benchmarks and stated consequences for missing them. Without that floor, you are locked in to whatever results arrive.

Undefined damage liability. The contract should say who files damage claims with OTAs, who documents the damage, and what happens when platform coverage does not pay. Leaving damage liability implicit surfaces as a problem at exactly the worst time.

Uncapped maintenance markup. A percentage markup on vendor work with no per-incident ceiling. This is the fee line most operators do not notice until a significant repair appears on a monthly statement.

Guaranteed revenue language without a written indemnity. Any PM promising a revenue floor is either genuinely underwriting the property, which is rare and worth scrutinizing, or using marketing language without contractual backing. Ask for the indemnity clause in writing. It usually does not exist.

For a detailed view of how the underlying management agreement should be structured, including fee models and liability split, see the co-hosting and management agreement guide.

Performance benchmarks to lock in before signing

The time to align on metrics is before the contract starts, not when revenue disappoints. Three benchmarks with real teeth:

Occupancy floor, set by season or month. Use verified market data for your specific sub-market, from AirDNA, Transparent, or Key Data, to establish what median occupancy looks like month by month. Set the floor at median. Agree on the measurement source before signing so there is no dispute about which data governs a missed month.

ADR versus a defined comparable listing set. Agree on what comparable means, bedroom count, amenity tier, neighborhood tier, and pick a specific data source. A PM consistently pricing 15% below the comparable set is losing you revenue. Whether that is conservative management or inadequate dynamic pricing matters, and a benchmark makes the conversation factual rather than adversarial.

Review score minimum. A trailing 90-day score below 4.7 on Airbnb triggers algorithmic suppression that reduces visibility faster than any pricing error. Set the floor, define the measurement window, and put a response protocol in the contract for when a negative review sits unaddressed beyond a defined period.

graph TD
    A[Considering a PM at 5-20 doors] --> B{Math: gross revenue absorbs 15-25% fee?}
    B -- No --> C[Stay self-managed or hire a VA instead]
    B -- Yes --> D{Constraint that a VA cannot solve?}
    D -- No --> E[Test a co-host arrangement first]
    D -- Yes --> F{SOPs and tech stack documented and ready to hand over?}
    F -- No --> G[Build those first, then revisit]
    F -- Yes --> H[Evaluate PM candidates]
    H --> I{Real market presence in your sub-market?}
    I -- No --> J[Look for a different PM]
    I -- Yes --> K{Contract passes red flag review?}
    K -- No --> L[Negotiate terms or walk]
    K -- Yes --> M[Sign with benchmarks in the contract]

Triggers to switch back to self-management

A PM relationship that has stopped working should end on a defined timeline, not drag six months past the point where metrics were consistently missed.

Four triggers that warrant action:

Two consecutive months below agreed benchmarks. A single bad month happens in every property’s history. Two consecutive months on occupancy, ADR, or review score is a pattern, not variance, and it should trigger a formal conversation with a defined response window and a consequence if the window closes without improvement.

A recurring guest complaint the PM does not resolve. One complaint handled badly is a training issue. Three complaints on the same problem, slow response time, a maintenance item not fixed between turnovers, check-in instructions consistently wrong, is a system failure that a conversation alone will not fix.

An unexplained revenue drop of more than 20% versus the prior comparable period. Market-wide softness explains market-wide declines. A property-specific drop that the PM cannot attribute to a specific cause requires a specific answer, not a general market narrative.

Any material breach of contract terms. Maintenance work approved above a stated threshold without notification. Undisclosed pricing changes. Channel additions or removals without your sign-off.

The exit process on Airbnb follows the co-host permission model. Your property manager should have been added as a co-host with scoped access, not given your account credentials. Removing them is a permissions change on the co-host settings page, not an account recovery operation. Airbnb’s co-host permissions documentation covers the access levels and how to adjust them; the process is clean when access was set up correctly at the start. The same principle applies to any PMS they were given access to: revoke access on the day the relationship ends, not after.

Common pitfalls

Handing over without documented SOPs. Your cleaners, check-in process, guest communication templates, and maintenance escalation paths are implicit in your head and invisible to a PM who has never seen your property. Every undocumented process becomes a point of failure at the first edge case.

Giving account credentials instead of co-host access. On Airbnb, the co-host role provides scoped access to calendar, messaging, pricing, and reservations without exposing your account to unauthorized changes. Sharing your login removes the audit trail and exposes you to actions you cannot reverse without a support escalation. On your PMS, confirm the PM uses a scoped staff account with the appropriate permission level, not an owner login.

Staying past the benchmarks. The most common failure mode in PM relationships is not the wrong choice at signing. It is staying six to twelve months past the point where metrics were consistently missed, citing “we were hoping it would improve.” It usually does not without a structural change in how the PM is operating your properties.

Not keeping read access to your own data. Ask for read-only access to the PMS the PM uses so you can view bookings, pricing history, and maintenance logs independently of their monthly reporting. A PM who refuses owner read access to your own property data is a reason to reconsider before signing, not after.

Tooling and handover

When you move from self-management to a PM, the tech stack transition carries the most friction. If you were running your own PMS, confirm in writing whether your historical data, booking records, guest communications, maintenance logs, transfers to the PM’s system or is archived separately and accessible to you.

For the full picture on which tools belong at different scales in a growing portfolio, the STR tech stack guide for 10-30 doors covers which combinations of PMS, channel management, dynamic pricing, and operations tooling fit specific operator profiles and budgets.

For the scaling decisions that typically precede a PM conversation, the operations scaling guide for 10 to 30 doors covers the operational breakpoints, system requirements, and team structure that make managed delegation sustainable rather than costly.