Rental Portal currently connects the recurring work of long-term RV parks and manufactured-home communities. The concepts further down this page are possible directions—not available features, release commitments, or plan promises.
These are product capabilities, not projected outcomes. Plan limits and technology fees remain defined on the Pricing page.
Model an organization, a supported property, and the long-term lots or sites inside it so later work starts from a known location.
Connect each resident to the correct place and active lease, including contact details, lease dates, rent terms, and tenancy information.
Keep what is due, what was paid, and how it was recorded in one history, with resident balance and payment access when enabled.
Keep notices, shared documents, and in-app messages attached to the tenancy context instead of scattering them across separate tools.
On Pro and Enterprise, receive requests with resident and location context, assign work, update status, and retain the service history.
Separate organization-wide, assigned-property, read-only, maintenance, tenant, and internal platform responsibilities.
The shared record model stays consistent while the product uses the place language that fits each community.
These concepts help make product direction discussable. They do not represent a roadmap, sequence, delivery date, or purchasing commitment.
Meter reads, allocations, resident utility charges, and exception review tied to each site.
Home ownership, title, serial, inspection, and site-history context for manufactured-home communities.
Reconciliation, ledger depth, tax context, exports, and clearer handoffs to an accounting system.
Reservations, availability, guest turnover, channel connections, and point-of-sale workflows for short stays.
Vendor access, estimates, approvals, mobile field updates, and service-level history around maintenance.
Cross-property operating signals, anomaly review, forecasting, and carefully controlled automation.
Future-looking pages are useful only when the path back to product truth is explicit.
Start with a repeatable operator need, not a feature list or competitor checkbox.
Confirm who performs the work, which records it touches, and what must remain out of scope.
Set permissions, tenant isolation, data authority, billing behavior, and failure states before presenting the idea as a solution.
A concept moves into the current foundation only after implementation and verification. This page does not imply dates or plan inclusion.
