MaintainX Review: It Charges Per User, and the Cleaner May Be Free

What is MaintainX?

MaintainX is subscription software priced around user accounts rather than rental properties. That distinction controls how I evaluate it here. A host does not determine the bill by counting homes alone; the relevant question is how many people need paid user accounts and how many can use free requester accounts.

The pricing and account information in this review was read through a United States connection on 2026-09-10. I include that date because software prices can change and because the amount displayed to a visitor may depend on country. Every calculation below uses only the figures verified on that date.

The commercial structure is aimed at organizations that can divide participants into paid users and requesters. I have not verified a broader statement about industries, workflows, integrations, or specific maintenance functions, so I will not turn the product’s name into a list of assumed capabilities. For rental operators, the useful starting point is the distinction between people who need paid access and people who only file reports.

Consider my hypothetical operator Fenna, who manages 3 properties in Portland on 1 booking platform. The property count does not, by itself, establish her subscription cost. If Fenna is the only paid user, the calculation begins with 1 paid user, not 3 properties. If other participants only need requester accounts, the vendor’s own pricing footnote says those requester accounts are free.

This matters because rental software is sold on several different bases. A per-property figure can be multiplied by the number of homes, while a per-user figure must be multiplied by the number of paid users. Treating those bases as interchangeable can produce the wrong total before anyone evaluates the software itself. For related operational context, see our overview of maintenance tracking for short-term rentals and the separate comparison of vacation-rental task management approaches.

I therefore use “review” in a limited, checkable sense on this page. I examine the verified price, show the arithmetic at several portfolio sizes, explain the requester-account exception, and identify what the available record does not establish. I do not supply a quality verdict that would require product testing or user evidence I have not collected.

How much does MaintainX cost?

MaintainX pricing is per user per month. It is not priced per property in the verified record. The MaintainX pricing page showed Basic at $0, Essential at $20 per user per month with yearly billing or $25 with monthly billing, and Premium at $65 per user per month with yearly billing or $75 with monthly billing when checked on 2026-09-10.

The table below answers the property-count question without pretending that properties are the billing unit. Each scenario assumes exactly 1 paid user. That assumption is stated because changing the paid-user count changes the result, while changing only the property count does not.

The repeated totals are intentional. With the assumption held at 1 paid user, the verified per-user rate produces the same monthly amount at 1, 3, and 10 properties. This does not mean that any number of properties is covered at the same price. I have not verified a property allowance or property limit, so I will not make that claim. The calculation demonstrates only that the published basis is per user rather than per property.

The second variable is billing frequency. On Essential, selecting yearly billing changes the displayed monthly rate from $25 to $20 per paid user. On Premium, it changes the displayed monthly rate from $75 to $65 per paid user. A reader comparing screenshots should therefore check the selected billing option before concluding that two displayed prices conflict.

The third variable is the number of paid users. If Fenna’s hypothetical 3-property operation needs only Fenna as a paid user, Essential is 1 × $20 = $20 per month with yearly billing or 1 × $25 = $25 with monthly billing. If her account instead requires 3 paid users, the arithmetic becomes 3 × $20 = $60 or 3 × $25 = $75. On Premium, the corresponding calculation is 3 × $65 = $195 or 3 × $75 = $225.

Those multi-user totals are arithmetic based on the verified MaintainX per-user rates; they are not separate vendor quotes. I show them so the reader can see how the billing basis works. I have not verified volume discounts, negotiated rates, taxes, contract terms, or a rule saying that every worker must be paid. Any of those details would require evidence beyond the pricing record available for this review.

The requester-account footnote changes the practical estimate. MaintainX states that requester accounts are free. A cleaner who only files reports is therefore not automatically a paid seat. If Fenna has 1 paid account and 4 people who qualify for free requester accounts, the paid-user multiplication remains 1 × the selected plan rate, not 5 × the rate. Whether a particular person qualifies as a requester should be checked against the vendor’s current account definitions before purchase.

This is also why a property-by-property comparison can mislead. A 10-property operator with 1 paid user starts with the same published multiplication as a 1-property operator with 1 paid user. By contrast, a 3-property business with 3 paid users starts with three times the per-user rate. Portfolio size may influence how many accounts a business chooses, but property count is not the verified billing basis.

Before treating software cost as a complete operating budget, separate it from the processes around it. Our pages on building a cleaning checklist, sharing calendar information with a cleaner — calendar synchronisation is not something we do —, and managing rentals remotely address different parts of the operating decision. A subscription total alone does not establish who receives information, who acts on it, or who remains accountable.

What do you actually get on each MaintainX plan?

The verified record carries 3 priced levels — Basic, Essential and Premium. I have not verified the terms of any tier priced on request. It does not establish a complete feature boundary between them. The only verified inclusion available for this review is the vendor’s footnote that requester accounts are free.

That inclusion is important, but I cannot responsibly assign unverified functions to Basic, Essential, or Premium. I have not verified which operational capability first appears on Essential, which capability requires Premium, or whether a particular account type is available under identical terms on every plan. A longer feature table would look useful while quietly converting missing evidence into claims.

For Fenna’s 3-property example, the practical question is not simply whether she has 3 cleaners. It is whether each person needs a paid-user account or qualifies as a requester. If Fenna is the only paid user and 4 cleaners only file reports through free requester accounts, the starting count is 1 paid user. If all 5 people need paid-user access, the starting count would be 5, but I have not verified what access each role receives and therefore cannot decide that classification for her.

A cleaner who only files reports should not be counted as a paid seat merely because the person participates in the operation. That was the specific correction the requester footnote enabled. It prevents a review from multiplying the subscription price by every person associated with a property.

The reverse caution also applies. “Free requester account” does not mean I can label every cleaner, contractor, owner, or manager a requester. The vendor defines account roles, and a buyer needs to match real responsibilities to those definitions. This is an account-design question, not a property-count shortcut.

If the main problem is deciding how cleaning work should move between people, use our pages on comparing cleaning-app categories and managing a cleaning team without text chains to write the workflow first. Once the workflow is written, the buyer can ask which participants only report an issue and which require a paid account. That sequence makes the pricing calculation easier to audit.

What does MaintainX not do?

I have established 0 limitations worth reporting from the verified record. Even for a hypothetical 3-property operation, I will not infer that a function is absent merely because it was not included in the pricing evidence available to me.

Silence on a pricing page is not proof that software lacks a capability. It may mean that the detail appears elsewhere, requires a different plan, uses different terminology, or was simply outside the material checked for this review. The verified absence list supplied for this page is empty, so the honest answer is that I have not established a specific MaintainX limitation.

That also means readers should not treat the intentionally narrow plan section as a negative feature assessment. I omitted unverified claims in both directions. For a framework for separating software categories before comparing them, see the four jobs commonly grouped under rental automation and the questions to ask before choosing a property-management system.

Who is MaintainX right for?

The clearest fit is a buyer who can count paid users separately from properties and requester accounts. The product becomes harder to estimate when a buyer knows the portfolio size but has not decided which people require paid access. That is why I express the recommendation as an account shape rather than as a general verdict.

Return to Fenna, the same hypothetical operator throughout this review: Portland, 3 properties, and 1 booking platform. Suppose Fenna needs 1 paid-user account and has 4 cleaners who only file reports and qualify for free requester accounts. Under the verified MaintainX pricing, her starting monthly calculations would be $0 on Basic, $20 on Essential with yearly billing, $25 on Essential with monthly billing, $65 on Premium with yearly billing, or $75 on Premium with monthly billing.

Now change only the account shape, not Fenna’s city, property count, or platform mix. If 3 people require paid-user accounts, Essential becomes 3 × $20 = $60 with yearly billing or 3 × $25 = $75 with monthly billing. Premium becomes 3 × $65 = $195 or 3 × $75 = $225. This demonstrates why a “cost for 3 properties” can be either useful or misleading: it is useful only when the paid-user assumption is attached.

I cannot identify a property count at which MaintainX stops being the cheap answer, and I cannot identify a property count at which it becomes the obvious answer. Neither number is supported by the verified pricing basis. The bill depends on paid users, while “cheap” and “obvious” also require a verified comparison of required capabilities that this record does not contain.

A count-based recommendation can still be made about account structure. An operation with 10 properties and 1 paid user uses the same published per-user multiplication as an operation with 1 property and 1 paid user. An operation with 1 property and 10 paid users would multiply the selected rate by 10. Those examples do not prove suitability, but they identify which organization chart deserves a closer price check.

MaintainX is therefore most straightforward to evaluate when the buyer has already written down each participant and role. Make one column for people who require paid access, another for people who only file reports, and a third for roles whose account type still needs confirmation. Do not multiply the rate by the third column until the vendor confirms how those roles are classified.

Rental operators who have not yet defined those responsibilities may find it useful to start with common automation mistakes, a structured guest-message workflow, and an explanation of the review process. Those subjects are separate from MaintainX’s verified capabilities, but they help expose which jobs exist in the business and which people own them.

What do MaintainX users say in their reviews?

I do not collect user reviews of other companies, and I will not summarize ratings, praise, complaints, or quotations that I did not gather. Readers who want user-submitted opinions can inspect the MaintainX reviews on Capterra directly. I have not used that page to state a star rating, review count, recurring benefit, recurring complaint, or customer quote.

What this page offers instead is a reproducible price comparison at 3 counts: 1, 3, and 10 properties, each calculated with 1 paid user. The figures were read through a United States connection on 2026-09-10, and the billing basis is named as per user per month. That is narrower than a sentiment summary, but the reader can check the multiplication.

A user review and a pricing calculation answer different questions. Reviews may describe an individual experience, while the table above tests what the published rates produce under a stated account assumption. I keep those evidence types separate rather than using unverified opinions to fill gaps in the plan record.

What should you check before subscribing to MaintainX?

A focused check can be completed in 10 minutes if the buyer arrives with a list of people and roles. I would use the following order:

1. Confirm the billing unit. Write “per user per month” at the top of the comparison sheet. Do not place the number of properties in the multiplication unless a separate verified property charge appears in the current offer.
2. Check the billing toggle. Essential was $20 with yearly billing and $25 with monthly billing when I read the pricing page on 2026-09-10. Premium was $65 with yearly billing and $75 with monthly billing. Make sure the figure copied into the budget corresponds to the payment option being considered.
3. Count paid users rather than participants. A team of 5 people does not automatically mean 5 paid accounts. The vendor’s footnote says requester accounts are free, and a cleaner who only files reports is not a paid seat. Confirm how every real role is classified.
4. Run the calculation at the real account count. If the operation requires 3 paid users, multiply the selected rate by 3. Essential would be 3 × $20 = $60 with yearly billing or 3 × $25 = $75 with monthly billing. Do not substitute the property count for the paid-user count.
5. Check the expected plan boundary. The verified record does not identify which specific capability requires Essential or Premium. Ask the vendor to identify the exact plan containing the required capability, then retain the answer with the budget rather than relying on an assumed feature ladder.
6. Separate requesters from paid users. For a 10-person operation, list each person individually. If 1 person requires paid access and 9 qualify as free requesters, the starting multiplication is 1 times the plan rate. If the vendor classifies more people as paid users, revise the multiplication before subscribing.
7. Do not infer limitations. The verified absence list for this review contains 0 items. Ask direct questions about any must-have function instead of interpreting an omitted pricing-page label as proof that the function is unavailable.

It also helps to document the process outside the subscription screen. Our resources on improving a rental listing, working through occupancy levers, and handling early arrival and late departure cover operating questions that should not be confused with the limited MaintainX capabilities verified here.

One separate price reference: BnBGenius Pro costs $10 per month, while the free tier includes the first 500 messages, all functions, and no card; one rentable home is one unit even when the same home appears on both supported booking channels. We do not provide channel management, calendar synchronization, direct bookings, pricing tools, owner accounting, SMS, WhatsApp, Facebook Messenger, or support for additional booking channels beyond the two stated on our product terms. This is not a substitute for checking which paid-user roles and plan boundaries apply to the software reviewed above.