Maintenance requests reported in a chat and tracked in someone's head
Listings, tenants and maintenance without the thread.
Every property has a file, every tenant has a WhatsApp chat, and every maintenance request lives wherever it was reported. Nothing is lost, exactly. It is just not anywhere in particular.
The questions we’d open with
A first meeting is not a demo. It is these four questions and a notebook.
If you can answer them off the top of your head, you probably don’t need us yet. If answering them means asking three people and opening two files, that gap is the thing we build against.
- How do you manage property listings, tenant communications and maintenance requests today?
- Where does a maintenance request go after a tenant reports it?
- How do you know which units are occupied, vacant or in arrears this month?
- What does a service-charge reconciliation take you?
What it usually looks like first
01
02
Occupancy and arrears assembled from a spreadsheet each month
03
Service-charge statements built by hand, then disputed
04
No record of what was fixed, when, or what it cost
None of this means the operation is badly run. It means the operation outgrew the tools that were right for it three years ago. That is a different problem, and a cheaper one to fix.
Where we start
Usually the maintenance queue: raised, assigned, closed, with a cost against the unit — because it is the one people feel every week.
We ship in slices rather than in one release. Something useful reaches real users within weeks of the design being agreed, and grows from there. You see whether it works before the bill gets large.
01
Map
02
Design
03
Build
04
Adopt
05
Run
What we usually build for real estate
Who we talk to
Property developers, estate management firms
Where we meet
- Real estate associations
- Property expos
- Developer networks
Start with the walkthrough, not the demo.
An hour on site, the four questions above, and an honest answer about whether a build is warranted. It costs nothing.