Apartment Leasing & Resident Portal Software Costs

Property management software’s per-unit pricing covers the owner-facing side of the platform — accounting, maintenance dispatch, owner reporting. The leasing and resident-facing layer on top of it — online applications, resident communication, maintenance requests, the resident portal itself — is billed separately in a lot of these platforms, and it has its own per-unit pricing quirks worth understanding on their own terms.

How leasing/resident-portal pricing tends to work

• Per-unit-per-month is the dominant mechanic, whether the resident portal is bundled into the core property management plan or licensed as a distinct module.
• Minimum monthly fees are common, and they change the effective per-unit rate meaningfully for smaller portfolios — a portfolio well under a platform’s target size can end up paying several times the advertised per-unit rate once the minimum is applied.
• Per-transaction fees layer on top — online rent payment processing frequently carries its own per-transaction charge, separate from the base subscription.
• Fully custom quotes at the enterprise end — larger platforms serving big portfolios often don’t publish per-unit rates at all for the resident-portal layer, quoting instead based on total portfolio size and module mix.

Where the minimum-fee math bites

The advertised per-unit rate is the headline number, but the minimum monthly fee is what actually determines cost for a portfolio below the platform’s target size. A landlord with a modest portfolio can end up paying an effective per-unit rate several times higher than the number in the pricing page, simply because the total unit count doesn’t clear the minimum — a structural quirk that rewards scale and penalizes exactly the portfolios that most need to watch cost per unit.

Leasing/resident side vs. owner-operations side

	Owner/PM operations software	Leasing & resident portal software
Primary user	Property managers, accounting staff	Prospective and current residents
Core function	Accounting, maintenance dispatch, owner reporting	Applications, resident communication, maintenance requests, payments
Pricing quirk	Per-unit fee scales with portfolio growth	Per-unit fee plus a minimum that penalizes smaller portfolios, plus per-transaction payment fees

Where a custom build fits

The resident-facing layer — applications, a maintenance request queue, resident messaging, payment status — is a well-scoped, buildable function on its own, separate from the accounting core a portfolio may prefer to keep on established, audited software. A custom-built resident portal replaces the per-unit-plus-minimum-fee structure with one flat monthly fee that doesn’t move with portfolio size, and doesn’t carry a separate per-transaction charge layered on top by the portal itself (payment processor fees are a separate, negotiated relationship either way). See the owner-side comparison at property management software per-unit costs, and the broader build-vs-license framework at reducing CRM and portal licensing costs.

Frequently asked questions

Can a custom resident portal integrate with our existing accounting/PM system?

Yes — a resident portal is typically scoped to read and write to whatever accounting or PM system stays in place, rather than replacing it, connecting through that system’s API.

Does dropping a bundled resident portal mean losing online rent payments?

No — payment processing is scoped as part of the custom build, connecting to your chosen payment processor rather than requiring the bundled platform’s built-in processor.

Is this worth evaluating below the platform’s minimum-fee threshold?

That’s exactly where the case is clearest — a portfolio paying a high effective per-unit rate because it’s under a vendor’s minimum is paying a penalty a flat monthly fee doesn’t have.