Rental Property Management SaaS

Landlords juggle spreadsheets, chats and receipts. One owner-scoped workspace covers properties, tenants, leases, billing, payments and reports — with a tenant portal and AI access over MCP.

A multi-role SaaS for landlords in the UAE and the Gulf, with three portals: landlord, tenant and admin. It models the full rent cycle — property and unit, lease, bill (including meter readings), payment, receipt — and the costs around it.

An owner can ask an AI assistant about their own portfolio, either inside the app or from an MCP-compatible AI client. Both paths are read-only and scoped to that owner’s data.

The problem

Small landlords track rent in spreadsheets and chat threads. Overdue rent, expiring leases and utility readings slip, and there is no single view of what each property actually earns.

The approach

A workspace per owner that ties every invoice to a lease and every payment to an invoice, so the dashboard, reminders and reports all come from the same records — and an assistant can answer questions from them.

What it includes

• Properties, units, tenants & leasesLease lifecycle with renewals, terminations and rent history.
• Rent billingBatch invoice generation with proration; utility bills refuse to run without current and previous meter readings.
• Payments & reconciliationManual payments, receipts, reconciliation and financial periods; invoice and receipt PDFs.
• ExpensesOne-off and recurring expenses with pause, resume and end.
• Financial reportsSummary, monthly trend, outstanding ageing, occupancy and more, with CSV export.
• Configurable remindersPer-owner rules (rent due soon, overdue, lease expiring, meter reading due) with day offsets, processed hourly.
• Tenant portalInvoices, lease, maintenance requests with photos, documents and notifications.
• Maintenance & documentsRequests, vendors, staff, appointments and costs; versioned documents; audit log.
• Property AI assistantRead-only, owner-scoped answers that name their data source.
• MCP tools for AI clients10 read-only tools — see the MCP integration project.
• Online rent paymentsPlannedRazorpay and Stripe adapters are written; no provider is configured or tested live yet.
• WhatsApp Business messagingPlannedToday reminders open a wa.me link; there is no WhatsApp API integration.

Role

• Defined the product, domain model and an 18-step build plan, from data model to release checklist.
• Built it on the Hatchable platform, largely through its AI builder, reviewing and correcting each step.
• Specified the owner-isolation rules, the billing rules and the MCP integration, and documented known limitations honestly in the README.

How it is put together

Serverless API functions on Hatchable over managed PostgreSQL. Every query is scoped to the signed-in owner at the application layer.

1. PortalsLandlord, tenant & admin — HTML/JS
2. AuthEmail OTP / passkeys; role resolved per request
3. API functions/api/v1 — owner-scoped helpers
4. Billing & reportsNUMERIC maths, proration, ageing
5. PostgreSQL156 migrations; cron for reminders

• Owner resolved from the session, never from the request body
• Tenants and suspended owners blocked from owner APIs
• Payment webhooks HMAC-verified

Simplified. Isolation is enforced in application code (owner_id filters), not database row-level security.