August 31, 2026 · 5 min read

The hidden costs of add-ons: how to compare property management software pricing

A step-by-step method to turn any property management software quote into a total cost per unit, including add-ons, tiers and per-transaction fees.

The headline price of property management software is rarely what you pay. Base prices are often quoted per unit per month, but the total can include minimums, tiers, onboarding fees, per-transaction fees, and separately priced modules for things you may consider essential, such as screening, a website, texting or AI. None of this is hidden in a dishonest sense; it is usually on the order form. It is hidden in the sense that it is hard to compare two quotes that are structured differently.

The fix is to convert every quote into one number: your expected total annual cost, divided by your units, divided by twelve. That is your all-in cost per unit per month. The method below shows how to build it.

Step 1: List what you actually need

Before you look at any pricing page, write down the features you use today and the ones you plan to use within a year. Group them by area: leasing, accounting, maintenance, resident and owner portals, reporting, and AI. This list is what every quote must be priced against. If a vendor's base plan does not include an item on your list, the cost of adding it belongs in your total.

Step 2: Find every pricing component

Ask each vendor for a written quote that covers all of these, and ask directly when an item is not mentioned:

  • Base subscription: per unit, per property, per user, or a flat fee, and whether different unit types (residential, commercial, single-family) are priced differently.
  • Monthly or annual minimums, and what happens if your unit count falls below them.
  • Tiers: which features sit in which plan, and whether one needed feature forces an upgrade for your whole portfolio.
  • Add-on modules: screening, websites, texting, call tracking, renter's insurance tracking, inspections, utility billing, advanced reporting, and AI features.
  • Per-transaction fees: card and bank payments, screening reports, e-signatures, outgoing texts or calls, and owner or vendor payouts.
  • One-time fees: implementation, data migration, training and account setup.
  • Contract terms: length, auto-renewal, annual price increases, and the cost of leaving, including data export.

Step 3: Decide who pays each transaction fee

Per-transaction fees are the hardest to compare because they depend on volume and on who bears them. Some fees can be passed to residents or applicants, some must be paid by you or the owner, and passing fees on may be limited by local law or by the rules of the payment networks. For each fee, note the amount, the expected monthly volume, and who pays. Include in your total only the fees your company or your owners will bear, and keep a separate note of what residents will pay, since that affects their experience too.

Step 4: Build the total

Put each component on one row of a spreadsheet, with a column per vendor. Convert everything to an annual amount. Spread one-time fees over the number of years you expect to keep the system; three years is a reasonable default if you have no better estimate.

Imagine you manage 400 units and receive this quote: a base price of $1.50 per unit per month, an AI leasing module at $0.75 per unit per month, a texting module at $100 per month, a $2,400 implementation fee, and a $2 fee your company pays on each bank payment. You expect about 300 bank payments a month.

  • Base: 400 x $1.50 x 12 = $7,200 per year.
  • AI module: 400 x $0.75 x 12 = $3,600 per year.
  • Texting: $100 x 12 = $1,200 per year.
  • Implementation spread over three years: $2,400 / 3 = $800 per year.
  • Bank payment fees: 300 x $2 x 12 = $7,200 per year.
  • Total: $20,000 per year, or $20,000 / 400 / 12 = about $4.17 per unit per month.

In this example the headline price was $1.50 per unit, and the all-in cost was close to three times that. The largest single addition was a per-transaction fee, which is easy to overlook because it never appears on the monthly invoice as a subscription line.

Step 5: Test the total against change

A good comparison holds up when your portfolio changes. Recalculate each quote for three scenarios: your current size, the size you expect in two years, and a smaller portfolio if you lose a large owner. Watch for minimums that bite when you shrink, tier thresholds that force an upgrade when you grow, and per-transaction fees that grow faster than your revenue.

Step 6: Count the cost of the gaps

Software you do not buy still has a cost. If a quote leaves out something on your list, you will pay for it elsewhere, either in another tool or in staff time. Estimate both, and add them to the vendor's column. Include the time spent moving data between systems, since that is often the cost teams notice last.

Questions to ask before you sign

  • Is this quote the complete price for every feature on our list, at our current size?
  • Which fees do we pay per transaction, and which can be passed on?
  • How much can the price rise at renewal, and is that in writing?
  • Are new features, including new AI features, included in our plan, or sold separately when released?
  • What does it cost to export all our data if we leave?

A note on StrivBridge

StrivBridge is priced as a single line: $5 per unit per month with a $65 monthly minimum, with every feature, including AI, included and no add-ons or tiers. Put it through the same spreadsheet as any other quote, and try it free for 30 days.

Try StrivBridge on a sample company