Command center
Good morning. AI handled the routine work. You have three decisions.
This is the property manager's daily home: what needs a person, what the agent already handled, and one place to ask Property Brain to do the next thing.
I handled 14 routine actions. I need you for 3 decisions.
Resident questions, reminders, vendor follow-up, inspection prep, inbox triage, and system synchronization moved without interrupting you. I stopped where spend, liability, or judgment requires a person.
What Property Brain is watching now
The portfolio is moving. Three human decisions are holding the only consequential work.
Resident AI is containing routine service; payment-plan reminders and inspection prep are running inside policy; vendor follow-up is current. Decide the carpet, leak spend, and cabinet classification and the rest can keep moving.
Every property carries its memory.
Lease terms, owner preferences, appliances, warranties, inspections, repairs, vendors, documents, and decisions become one continuous record.
| Property | Owner | Lifecycle | Open work | Next event | Risk |
|---|
From vacancy to move-in with fewer handoffs.
Marketing, leads, applications, screening, approval, e-signature, and move-in are one workflow. Specialist services stay with partner APIs; Property Brain keeps context and process moving.
Pipeline is moving.
I watch readiness, lead response, screening, signatures, and move-in dependencies. I can prepare the next action and stop where a leasing or legal decision belongs to a person.
The resident starts with AI. The PM starts with a complete handoff.
The mobile experience answers questions, guides safe troubleshooting, handles policy-based payment-plan requests, schedules routine condition updates, and escalates only where a property-management person is actually needed.
See the financial picture. Then see exactly what needs action.
The CFO-level signal stays available, but the operator sees invoices, distributions, delinquency, payment-plan status, and exceptions before digging into a statement.
Operating statement · executive / CFO drill-down
One conversation layer across residents, owners, vendors, and applicants.
AI summarizes the thread, drafts from property/workflow context, tracks unresolved conversations, and prepares group communication for human review.
Know what the thread means before replying.
The assistant can summarize, retrieve property context, identify workflow dependency, draft the next message, and preserve the record.
Capture evidence once. Use it everywhere.
Mobile-first inspections compare current condition with prior evidence, organize the record, draft the turn scope, and flag what requires human judgment.
Possible new damage near the lower cabinet face. Condition appears materially different from move-in evidence. Confidence: 82%. Review both images before classifying resident responsibility.
Select a checkpoint to compare what changed and what was already known.
The turn keeps moving until a decision is required.
Inspection evidence becomes scope, scope becomes estimates, estimates become structured approvals, approvals release work, and completion triggers the quality walk.
Resolve the easy things. Route the right things.
The resident starts with a property-aware AI that knows the lease, equipment, warranties, prior issues, owner rules, and approved vendors before a property manager ever touches the request.
Context-rich approvals without the email chain.
Every request carries cost, evidence, property history, threshold rules, and a manager recommendation. The approval becomes a structured event the workflow can act on.
Show the owner what matters without inviting them to manage the manager.
This preview is built around distributions, property health, approvals, important activity, and concise reporting. Detail level and communication frequency follow owner preferences.
“What do I actually need to know about 123 Main this month?”
Property Brain answers with the owner-selected level of detail: financial outcome, meaningful property events, approvals, and recommendations—not the PM's entire operating queue.
Find the right trade in seconds. Let vendors do the onboarding work.
Search and filter by trade, then route using service area, compliance, owner preference, availability, response time, and performance. Existing vendor lists can be bulk imported during implementation.
Showing all approved vendors
The SOP becomes an active system.
Recurring work does not depend on memory. Rules watch dates and conditions, prepare context, communicate, create tasks, and stop at human checkpoints.
Documents stop being folders. They become context.
Leases, amendments, inspections, warranties, invoices, estimates, photos, and owner instructions remain in their systems while becoming searchable and usable by workflows.
See the product from every side.
Play through owner, resident, vendor, and property-manager moments. Each simulation uses the same property context and records its communication event.
Turn owner preferences into executable policy.
Thresholds, channels, vendor preferences, repair philosophy, and agent guardrails should live in the system instead of in a manager's memory.
Agent can advance approved categories without interrupting the owner.
Even when the estimate falls below the standing threshold.
Allow urgent property-protection work while immediately notifying the owner.
Example behavior: send routine reminders automatically, offer an eligible resident a plan inside these rules, record the agreement, schedule reminders, and bring the PM only exceptions or failed arrangements.
Resident communication preferences can influence warmth, directness, detail, step-by-step guidance, channel, and timing. They do not influence screening, maintenance priority, charges, enforcement, or legal rights.
Configure the operating system around how the company actually works.
The setup captures portfolio scope, integrations, owner authority, approved vendors, automation defaults, and human decision boundaries before agents begin acting.
Select representative properties and workflows.
Buildium, Property Meld, OneDrive.
Authority, channels, preferences.
Trade, service area, compliance, routing.
Turn passive SOPs into triggers and actions.
Define human checkpoints and exceptions.
Time saved, touches, cycle time, misses, CX.
Property Operations Agent
DIAGNOSE · ASSEMBLE CONTEXT · ADVANCE WORK · ESCALATE DECISIONS
Property management is not one workflow. It is an interconnected system.
The product does not try to become the accounting ledger, maintenance vendor network, or document repository on day one. It becomes the intelligence and workflow layer above them: assembling context, executing repeatable steps, and stopping when a human judgment is required.
Property knowledge is scattered
Lease terms, owner preferences, appliance history, warranties, photos, and prior decisions live in different places.
Recurring work depends on people remembering
Inspections, reminders, follow-ups, estimates, approvals, and quality walks get manually recreated.
Move-outs become communication chaos
Contractors, estimates, photos, owner approvals, resident responsibility, and timing fragment across channels.
Ready unit + listing.
Respond and prequalify.
Partner result.
Human leasing decision.
E-sign + move-in.
24/7 help + handoff.
Ledger exceptions.
Triage + vendors.
Offer or notice.
Human consequence checks.
Evidence to ready.
History improves next cycle.
The pain points this product is designed to remove.
Scattered property context
A new hire cannot easily know owner preferences, lease details, appliance history, warranties, or prior decisions without asking someone.
Inspections require too much manual assembly
Scheduling, reminders, room-by-room evidence, photo organization, prior-condition comparison, and post-inspection follow-up are disconnected.
Move-outs explode into dozens of touches
Damage, normal wear, estimates, owner approvals, contractors, resident communication, scope changes, and readiness tracking create friction.
Maintenance starts with avoidable manager work
Residents report simple issues that could be safely troubleshot before a person is interrupted.
Owner approvals live in messages
The owner lacks a clean recommendation, evidence, historical context, and a durable decision record.
Onboarding depends on tribal knowledge
A new employee has to learn what each property and owner “usually wants” from scattered human memory.
SOPs are passive documents
They describe what should happen but do not schedule, watch, remind, route, or escalate.
Managers become the integration layer
Humans manually move facts between Buildium, Property Meld, OneDrive, email, text, and vendor conversations.
Growth adds administrative drag
More doors often mean more coordination rather than proportional leverage.
Do not replace the systems that already work. Connect them.
Systems of record
Buildium — property, resident, lease, accounting data.
Property Meld — maintenance execution.
OneDrive — documents, photos, warranties, SOP assets.
Property Intelligence OS
Unified property context, workflow state, agent actions, inspection evidence, decisions, communication events, and role-based experience.
Human experiences
Manager: exception queue + approvals.
Resident: guided AI support.
Owner: structured decisions.
Vendor: clean scopes and status.
| Capability | Existing system remains source | OS adds | Why |
|---|---|---|---|
| Accounting / ledger | Buildium | Read context + deep links | Avoid rebuilding financial infrastructure early. |
| Maintenance execution | Property Meld | Triage, property context, routing intelligence | Reduce manager touches before and around the work order. |
| Documents | OneDrive | Index, retrieve, attach to workflows | Documents become useful without migration. |
| Inspections / turns | Mixed today | Native workflow + evidence model | Highest-value operational gap and strongest MVP. |
The agent moves work. Humans make consequential judgments.
Workflow wakes automatically from lease / event state.
Lease, prior inspection, owner rules, vendors, history.
Rooms, photo checklist, dictation, evidence comparison.
AI presents evidence. Manager makes chargeability judgment.
Normalize vendor responses and compare options.
Structured yes / no / ask with complete context.
Approved scope, dates, access notes, communication.
Follow up on delays and collect proof of completion.
Final checklist automatically appears after completion.
Manager confirms readiness for lease-up.
Decisions, work history, invoices, dates, evidence indexed.
Vendor performance and process timings inform future recommendations.
Assist aggressively. Adjudicate carefully.
| Decision | AI can do | AI should not do alone | Checkpoint |
|---|---|---|---|
| Resident damage | Compare evidence, surface changes, summarize lease context | Automatically impose a resident charge from image inference | Manager reviews evidence + applicable rules |
| Owner spend | Recommend vendor, normalize estimates, apply stored threshold | Spend above threshold without approval | Owner or authorized manager approval |
| Emergency maintenance | Recognize emergency language, show safety steps, escalate immediately | Delay emergency routing with prolonged troubleshooting | Emergency protocol + human/vendor escalation |
| Lease / legal language | Draft amendment or disposition explanation from known inputs | Represent uncertain legal interpretation as definitive | Manager / counsel review where required |
| Vendor routing | Rank approved vendors by trade, history, availability, location | Ignore licensing, insurance, owner preference, or spend rules | Policy constraints before dispatch |
The product should feel powerful because it removes coordination, not because it pretends human judgment is unnecessary.
First change the property manager's day. Then remove the resident interruptions that create it.
PM Command Center + Agent
Morning brief, what AI handled, human decisions, agent actions, sync health, communications, delinquency, maintenance exceptions, and audit trail.
24/7 Resident AI
Property-aware help, safe troubleshooting, payment-plan guidance, condition updates, questions, and complete PM handoffs.
Inspection → Turn → Owner
Longitudinal evidence, scope, estimates, approvals, vendor work, and quality walk.
Financial + payment-plan agent
Action-first financials, policy-driven reminders, arrangements, invoice authority, and distributions.
Vendor + Owner experiences
Vendor import/onboarding and a minimal owner experience with tailored reporting and approvals.
Reusable client adapters
Normalize each client's PMS, maintenance, documents, payments, messaging, screening, and e-sign systems behind common workflows.