Small commercial and multi-unit residential.
20-200 units across single or multi-property portfolios. 2-10 employees plus contractors. Drowning in tenant texts, maintenance, rent inquiries, lease renewals.
Where it breaks.
- Tenant messages arrive on every channel at once and get triaged by whoever happens to see them.
- Maintenance requests lose their detail between the text that reported them and the vendor who has to fix them.
- Renewals and inspections are calendar work that only becomes urgent when it is late.
A site where a tenant request is a form that lands somewhere real, with the unit and the photos attached, rather than a phone number that rings a person who is already on another call. What a build includes
A portfolio's records usually live in two or three places — the accounting package, a spreadsheet of units, and somebody's inbox. An internal tool that makes one of them the record and syncs the rest is the application-shaped version of this problem. How we build applications
Start with Property Manager — triages tenant communication, classifies urgency, dispatches vendors with photos and unit details, tracks completion.
Add next: AR, for graceful, consistent late-rent follow-up with an audit trail. Compliance, for lease renewal calendars and mandatory inspections.
Start with the free audit if prospective tenants cannot find the listings; start with the bot if the problem is the volume of messages rather than the volume of leads.
Does it talk to tenants directly?
It triages and dispatches. Anything that changes money or a lease waits for a person.
What happens to the photos a tenant sends?
They travel with the request to the vendor — that is most of the value. They land in your tenant schema, not in somebody's phone.
We use a property management package already.
Then the question is whether the bot reads from it or an integration bridges it. That is a Discovery conversation, and it is a short one.