Roadmap
What's on our build queue, in priority order. We update this monthly.
Currently shipping (this quarter)
Direct email sending
Today, your PMs draft owner digests, notices, and case packs in PMFriend, then copy-paste into their own email tool to send. Direct sending via AWS SES (Sydney region, DKIM-signed for deliverability) is in flight — once it lands, the workflow shrinks to one click.
ETA: Next 2–4 weeks.
Tenant SMS notifications
When a maintenance request status changes ("plumber booked", "work complete"), tenants will get an SMS. Currently they're left guessing.
ETA: Next 4–6 weeks.
Photo upload across the inspection flow
Inspection reports today are text-only. Photo upload + AI captioning ("east-facing wall, light scuff at skirting") is in development. The foundation is already live for tenant-side maintenance reports: tenants can attach up to 3 photos when filing a report and the AI reads them during triage. The remaining work is the inspection-side form + a condition-report-specific prompt.
ETA: Next 4–6 weeks.
Next up (Tier 1 features for time savings)
Owner-churn early warning
The AI watches owner email sentiment + digest open rate + complaint frequency, and flags owners trending toward churn before they leave.
Why this matters: Losing a 20-property owner ≈ $20k/year. The AI reads patterns a busy PM misses.
Bond claim builder
End-of-tenancy bond claims, itemised + tribunal-defensible. Reads ingoing + outgoing condition reports + photos and produces a line-by-line claim with reasoning.
Multilingual tenant comms — partly shipped
Shipped: tenants write in any language on WhatsApp or email; the acknowledgement, every status update and the did it get fixed? prompt go back in their language (Arabic, Hindi, Urdu, Malayalam, Tamil, Bengali, Sinhala, Tagalog, Ukrainian, Russian, English); voice notes are transcribed; contractors get the job in theirs. Still to come: the AI translating a tenant's message for the PM inside the inbox and drafting a free-form reply in the tenant's language.
Bigger bets (Tier 2 / 3)
Lease-renewal rent advisor
"Should I renew this tenant at $640/wk or push to $680?" Currently a gut call. The AI reads payment history + maintenance cost + scraped suburb comparables and recommends a number with justification.
Contractor quote comparator
3 PDF quotes for a $15k roof job. AI extracts line items, builds a side-by-side comparison, flags anomalies ("quote B omits waste disposal").
After-hours tenant emergency triage
Tenant texts at 11pm about a burst pipe. AI chatbot asks 3 diagnostic questions, either auto-dispatches an emergency plumber (if under cost ceiling) or pages the PM with a summary. PM's sleep is preserved.
AI portfolio health score
Weekly per-PM summary of what's hot in their portfolio: "Sarah's portfolio has 3x normal arrears this month — 2 tenants at the same property just lost jobs."
For larger operators — available on request
Beyond the standard plans, each of these is delivered under a separate agreement, scoped and priced for your organisation. None of them is switched on by default.
- Dedicated deployment — your own PMFriend stack in AWS Bahrain or UAE, or inside your own AWS account — on request, separate agreement.
- SAML 2.0 single sign-on and a Microsoft Entra directory per customer (Google and Entra sign-in already work); SCIM user sync is planned to follow — on request, separate agreement.
- A direct connector to one specific ERP or CAFM (Yardi, Maximo, SAP, Dynamics…) — reading and writing jobs in your system itself. This is an integration project, not part of the standard plans — on request, separate agreement. Without a project, every new job can already arrive in your helpdesk or CAFM by e-mail, or by a signed webhook with status back (Microsoft Dynamics 365 through Power Automate): see Jobs into your helpdesk or CAFM.
- A test environment with your own data for that integration project — on request, separate agreement.
- The AI model of your choice — a different model, or your own model endpoint, configured for your account; the product keeps working the same way — on request, separate agreement.
- Support SLA with defined response times — on request, separate agreement. (Pilot onboarding has a fixed price: see pricing.)
On the wish list (no committed timeline)
- Mobile tenant app (today: web form only)
- 2-factor authentication
- Predictive maintenance: when the same asset fails again, suggest a preventive work order instead of only flagging it
- Acknowledgements in Arabic or Hindi for messages typed in Latin letters (Arabizi, Hinglish)
- Access by building or portfolio — a building manager sees only their buildings, a director sees the portfolio, plus a read-only role (today: agency-wide visibility)
- Operator rules in settings — a photo required before a job closes, no dispatch to a contractor with expired insurance, an owner named for every certificate — with breaches landing in the Attention Inbox
- Cost-approval tiers: who approves which amount, with the decision recorded
- Custom fields on properties and jobs (cost centre, vendor ID, contract number)
- SAML 2.0 single sign-on, a Microsoft Entra directory per customer, and SCIM user sync (Google and Entra sign-in already work)
- Live chat support
What we won't build
To be transparent — three things you might wish for, that we won't:
- Autonomous email/SMS sending without human review. Hard rule. Every owner / tenant / contractor message gets PM review first.
- AI-driven tenant screening. Discrimination-law minefield. Requires regulatory moat we don't have.
- AI-written tribunal representations. Legal-advice adjacency. Not our lane.
How priorities are set
Three inputs:
- Time saved per week per PM. A feature that saves 6 hours/week beats a feature that saves 30 minutes/week.
- AU regulatory moat. A feature that's hard for global SaaS competitors to replicate (state-specific notices, AU compliance defaults) wins over generic features.
- Customer requests. Multiple agencies asking for the same thing moves something up the list.
If there's something you wish was higher on the list, email
support@pmfriend.com and tell us why. Customer requests do move the
list.