The request arrives with its history
Photos, priority and the unit past: the two previous leaks, the warranty status, who fixed it last time. You are not opening a ticket, you are opening a file.
For managers
The day arrives assembled.
Most mornings start by reconstructing yesterday out of texts, calls, a spreadsheet and memory. That reconstruction is the job nobody hired you to do, and it is the one this removes: every request shows up already carrying the unit, its history and the person who owns the next step.
The loop
What the morning looks like instead.
Six things that arrive attached rather than assembled by hand. Every one of them is running on a database today.
Dispatch carries the job packet
Scope, access notes and what to record on completion go to the vendor before they arrive, so the first call is not about how to get in.
The window lands on a calendar
Property appointments sync with Google Calendar, in the timezone of the property itself rather than whichever one a phone picked up.
Closed means photographed
Completion evidence files against the unit. When the owner asks in March what the February invoice bought, the answer is attached to it.
Applications defend themselves
The criteria were a version before the application arrived, the submission is a version, and the decision carries evidence it was delivered.
Owner approvals carry the estimate
You send a recommendation with the number attached to it, instead of re-explaining the same repair across three messages.
Your team
Authority is granted, never inherited.
This is the part most software gets wrong quietly. A role is treated as a bundle of powers, so adding somebody to the team hands them everything the role could ever do — including signing a lease on the landlord behalf and adjusting a financial entry.
A job title grants nothing
Half the capabilities in the model require an explicit grant before anyone holds them — 131 of 264. Being on the team says who may receive authority, never who already has it.
Held is not revoked
A grant can be suspended and come back. Putting a team member on hold while something is reviewed does not destroy the grant or its lineage, so restoring it is not a rebuild from memory.
Narrowing and widening are different acts
You can reduce your own authority profile on a property by yourself. Restoring it requires the owner. The person who starts an act and the person who confirms it stay apart.
Access ends without erasing
When a team member leaves, their grants end and their work stays attributed to them. Losing access and losing history are not the same event.
Why this matters to you specifically: when authority is inherited from a title, every dispute about what somebody was allowed to do becomes a dispute about your judgement. When it is granted explicitly, the answer is a record — and the record is what protects the person who runs the team.
The guardrails
Rules that protect you from a fast afternoon.
These read like limits on your team. They are actually limits on how badly a busy day can go wrong, and every one of them removes a dispute you would otherwise be standing in the middle of.
A chat message is never service
In-app alerts, SMS, push and ordinary e-mail can only help someone notice. If your team believes a message counted as an official notice, the product disagrees before a court does.
Saying it is done does not close it
Text written in a conversation never changes the source workflow. A repair closes when the work order closes, with evidence, not when somebody writes that it is handled.
A late fee needs the signed rule
Only the exact late-payment rule the signed lease carries supports an automatic charge. Where it is ambiguous the assessment waits for a person instead of guessing against the tenant.
Nothing silently pauses a deadline
Not a provider failure, a logout, a restarted worker, a reassignment or an unread message. You find out a clock is running while there is still time to act on it.
Today
What is already running.
The honest split for a manager — what holds your data on a database now, and what is built and moving there.
- Work orders, service awards and completion evidenceLive
- Appointments with Google Calendar syncLive
- Applications, criteria versions and review actionsLive
- Screening charged through StripeLive
- Tenant, owner and vendor invitationsLive
- Move-in inspectionsLive
- Team grants, holds and revocationIn build
- Conversations and notification preferencesIn build
- Official notices and delivery evidenceIn build
- Owner statements and accounting syncIn build
The roadmap has the whole picture, and pricing is per property, never per seat — your team, your vendors and your tenants do not add to the bill.
Early access
Stop rebuilding yesterday every morning.
Bring one property in and watch a single request carry its own context from report to closed.