Owner, resident and guest portals under your own name. The conversations that run through them. The leasing, maintenance and money work behind them. And an engine that handles the parts nobody should have to remember.
A lease signed in one area is the record a work order attaches to in another, and the record the engine watches for a renewal window. It reads as six areas because that is how a management company is staffed. Underneath, it is one database.
Three surfaces, three different jobs. Owners see statements, payouts and the state of the properties they own. Residents pay rent, raise maintenance and sign documents. Guests get arrival details and a trip pass. Each one is a real product surface rather than a login page, and all of them carry your company name.
Email, SMS and voice notes land in one thread, attached to the person and to the property rather than to whoever happened to answer. A coordinator who leaves does not take the history out with them, and nothing that matters lives in an individual inbox.
Online applications and tour scheduling at the front, screening with adverse-action handling in the middle, unlimited e-signature at the end. Renewals and key dates are tracked as a lease lifecycle, not as a set of reminders somebody remembered to put in a calendar.
Screening — Operate and above
A request can arrive through a portal, a text message, an email or a phone call and still land in the same queue. Triage sets the urgency, routing decides who owns the work, and dispatch sends it to the right vendor with the unit context attached. The whole trail stays on the unit afterwards.
Automatic dispatch — Operate and above
Rent collected by ACH, monthly owner statements that generate rather than get assembled, owner payouts, reserves, and an approval step before money is spent on somebody else’s building. The ledger those numbers belong to stays in your accounting system.
Payouts, reserves and approvals — Operate and above
Workflows are templates that fire on real events — a payment going late, a lease entering its renewal window, a lead nobody has answered. Not a nightly job, and not a rule that lives in one person’s head. You can see which template ran, against which record, and when.
Some templates — Operate and above
Everything above is on every plan except the lines marked otherwise. What changes as you move up a tier is how much of the work is still yours — the pricing page lays out the ladder.
On Operate, an agent works the leasing, resident and owner threads alongside your staff — inside the same system, against the same records, leaving the same trail behind it.
We are not going to tell you how many hours it saves. We do not have your portfolio, your markets or your standards, and a number invented on a marketing page would be worth nothing to you. What we can describe precisely is what it does, and what happens when it gets something wrong.
The agent reads and replies inside the same leasing, resident and owner conversations your staff use. There is no second console to keep an eye on and no separate history to reconcile later.
Answering a leasing inquiry, following up on a late payment, confirming a maintenance window. Whether it sends or hands a draft to a person is set per workflow — one decision per kind of work, not one decision for everything.
The agent is a distinct actor in the record — it never borrows a member of staff’s name. What it did, on which lease or unit, under which template, at what time: it reads the same way an audit would read it.
It can be paused for the whole organization, or corrected message by message where it got something wrong. Nothing it touches is a one-way door, which is the only basis on which we would let it touch anything.
AppFolio, Buildium, Rentvine, Rent Manager — whichever one you keep, keep it. The accounting system is the hardest thing in this industry to move, and the least rewarding thing to move twice.
This is a decision, not a gap. Software that also wanted to be your ledger would spend its first year asking you to move and its second year explaining the variance.
There is no chart of accounts to move and no prior year to re-close. You start on the surfaces your owners and residents actually touch, and the books stay exactly where they are.
Money is collected here, statements are produced here, payouts are made here. What that means for your general ledger stays your accounting system’s job, and your accountant’s process does not change.
A full export is available on request, at any time, on every plan. A product that keeps its customers by making the exit expensive is not the product we are trying to build.
Every company on this platform is an organization with its own fence around it. That fence is not a convention the application agrees to follow — it is enforced one level below the application, where forgetting is not an option.
Every organization-scoped table is governed by row-level security in Postgres. A query for another company’s records does not come back filtered — it comes back empty, because the database refused it. The fence is not a condition in application code that somebody can forget to write.
Portals, statements and outbound messages resolve your organization’s own branding when they render. Your owners and residents see your company, which is the whole difference between running a platform and reselling somebody else’s storefront.
A full export on request, at any time, on any plan. No retention window to wait out, no fee attached to leaving, and no conversation about it first.
The full account — how the fence is built, what it is tested against, and what we do when something is wrong — is on the security page.
Start an organization and set it up with your own properties, or book a walkthrough and we will take it through your door count, your markets and the accounting system you already keep.
Unlimited users on every plan. Your accounting never moves.