Zati for property-management teams
The request is logged. What happens next?
A resident asks for an update. A vendor has replied somewhere. Your team needs to know what is confirmed, what is missing and who should follow up. Zati AI workers help with the coordination around your property software: organizing the latest information, preparing the next step and bringing decisions back to your team. Start with one useful workflow, and see a relevant demo before deciding on a workshop. 30 minutes. No tenant records needed. We check your existing tools first.
Your team needs the next step, not another place to check.
-
01
When a resident asks again
Find the latest recorded update and prepare an accurate response for review. A scheduled visit stays “scheduled” until there is evidence it happened.
-
02
When the vendor reply is missing
Make the missing information visible. Prepare a follow-up question without inventing a promised arrival time or assuming nobody has acted.
-
03
When someone covers the desk
Prepare a handover showing the source, last update and proposed next step, so the next person can check the record before acting.
-
04
When an owner wants an update
Bring the recorded facts into a draft summary. Keep unresolved questions visible instead of turning incomplete information into certainty.
Sample workflow: a maintenance follow-up list your team can check
-
01
Kitchen tap leaking
Latest recorded update: vendor offered Thursday morning. Missing: resident access not confirmed. Proposed next step: ask staff to confirm access before agreeing the visit.
-
02
Repair visit scheduled
Latest recorded update: the appointment appears in the supplied record. Missing: no completion note in these records. Proposed next step: check with the responsible person; do not mark it complete.
-
03
Owner requested progress
Latest recorded update: two messages contain different dates. Missing: which date is current. Proposed next step: resolve the conflict before drafting the owner update.
-
04
Illustrative only
These are fictional records, not a live customer account. Each item points back to its source, and your staff reviews the draft and decides what to do. A first demo can use fictional information; an export-based exercise does not mean Zati has a live connection to your systems.
Give each worker a clear job.
-
01
Maintenance follow-up
Organize supplied request and vendor updates into a staff-reviewed follow-up list. Flag missing details and conflicting dates. Repair decisions, emergency handling and spending stay with the authorized people.
-
02
Leasing follow-up
Explore a queue of inquiries needing attention and draft replies from approved information. Staff confirms current availability, terms and any proposed appointment before sending.
-
03
Owner updates
Explore draft progress summaries from agreed records, with sources and open questions. Financial figures are verified against the system of record.
-
04
Team handovers
Explore an end-of-day brief of recorded changes, open questions and suggested next steps. Start with one role and a few sample cases, and expand only after your team can check the work confidently.
One useful workflow. A clear way to test it.
-
01
Show us the handoff
On a free discovery call, walk through a recent example. Which people and tools were involved? What was hard to find? What would a useful result look like?
-
02
Check what you already have
Your existing report, reminder or template may solve it, so we look there first. If there is a useful gap, we agree a small workflow worth demonstrating.
-
03
See a relevant demo
If there is a fit, David prepares a personalized example before you choose whether to book a workshop. It can use fictional data or agreed exports, and supported access and open questions are made clear.
-
04
Build and practise together
In a Sanifu workshop, configure or build the agreed slice, test sample cases and practise checking its output. External actions need the permissions and approvals agreed for that workflow.
Keep the system of record. People stay in control.
-
01
Your existing tools
Tell us which property software and email system you use. We look at the exact task, available exports or APIs, account permissions and setup effort before proposing a connection. Yardi, AppFolio, Buildium, Entrata, RealPage or another system: the name is a starting question, not a promise of compatibility.
-
02
Your team supplies the judgment
Give a worker a defined task and only the access that task needs. Agree which outputs are drafts, what a person checks and which actions need approval. Your staff remains responsible for the property work and decisions.
Sanifu workshops: learn it on a workflow your team recognizes
-
01
Two live hours — $600
A tightly scoped starting exercise with prepared inputs and agreed checks, for when the learning goal and setup are already clear.
-
02
Four live hours — $1,200
More time for setup, testing and team practice, as one four-hour workshop or two two-hour sessions.
-
03
What is included
Private work with David Ndungu, preparation included, priced per workshop. Up to three people in person; unlimited by video. Before payment we agree the learning goal, inputs, access, sample cases, checks and scope. Software subscriptions or usage fees are separate and agreed in advance. A workshop is a bounded learning engagement; production rollout needs its own scope.
Questions
Is Zati another property-management system?
No. Zati is a platform for organizing AI workers. Here we explore coordination tasks around your existing process and tools. Your property software remains the source of record.
Can you show me something relevant before I pay?
Yes. Start with the free 30-minute discovery call. If there is a fit, David prepares a personalized demo before you choose whether to book a workshop.
Will it work with our software?
We check the exact product, available access and proposed task first. A product name alone does not establish an integration. The first example may use fictional data or an agreed export.
Does this send messages or book vendors automatically?
The starting exercise prepares drafts for staff review. Any later sending, scheduling or other external action must be separately supported and explicitly authorized.
Do we have to upload tenant information?
No tenant records are needed for discovery. The demo can use fictional data. Any later use of business records needs separately agreed access and handling.
Is this for replacing our staff?
The starting point is supporting the people doing the work: preparing information, drafts and handovers they can check. Your team makes the property decisions.
What if our existing software already does this?
We start there. The useful outcome may be using an existing report, reminder or template better. We only propose a workshop after establishing a relevant learning goal.
Will the workshop leave us with a production-ready system?
The outcome is one bounded learning slice, tested against sample cases, plus written next steps. That alone does not establish readiness for unattended production use.
Can you guarantee time savings or better reviews?
No. We can define a useful test and help your team evaluate the result. Measure time, corrections and follow-through on your actual workflow before making any savings claim.
Bring one task your team keeps having to chase.
We’ll look at the current process, check what your existing tools can do and explore a small, inspectable next step. Free 30-minute discovery; a relevant demo if there is a fit; the workshop choice comes afterward. Please leave out tenant details, passwords and sensitive records when booking.