Build a property management app for landlords

You are a full-stack developer who builds property software.
I work in Real Estate: a real-estate brokerage. This work matters to home buyers, sellers and property investors.

## Goal
Build a web app where landlords manage properties, tenants, rent and maintenance in one place.

## What matters in Real Estate
- People involved: agents and brokers; buyers; sellers; investors; developers; home-loan lenders; legal and documentation staff.
- Rules and standards that usually apply: fair-housing and anti-discrimination rules; RERA in India (registered projects, honest advertising); seller disclosure laws; stamp duty and registration; AML checks on high-value deals and agent licensing.
- Numbers that matter: days on market; closed deals; lead-to-site-visit rate; visit-to-offer rate; commission per deal; sale-to-list price ratio.
- Common risks to plan for: delayed possession; title disputes; misleading listings; leads lost to slow follow-up; market slowdowns.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Number of properties and units: [NUMBER]
- Country and currency: [COUNTRY, CURRENCY]
- Online rent payments wanted: [YES OR NO, GATEWAY]
- Preferred stack: [STACK]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Summarise what you understood about the product, its users and the launch scope. Point out anything unclear or contradictory and ask before you guess.
2. Model properties, units, leases, tenants, rent schedules and payments.
3. Build lease management with start and end dates, deposits and renewals.
4. Generate rent invoices automatically with reminders and late fees.
5. Build a tenant portal: pay rent, see receipts, raise maintenance requests with photos.
6. Build maintenance tracking with vendors, status and costs.
7. Build reports: rent roll, arrears, occupancy, income and expenses by property.
8. Add document storage for leases and IDs with secure access.
9. Give a launch checklist covering security, performance, SEO, accessibility, backups and monitoring.
10. List what is deliberately out of scope for version 1 and what to build next.

## What to deliver
- Data model
- Feature list by user type
- Phase-by-phase build
- Payment and reminder logic
- Reports specification

## Expert rules
- Build mobile first and make every screen work from 360px wide upwards, with labels, keyboard support and 4.5:1 contrast.
- Validate every input on the server, use prepared statements, hash passwords, protect forms with CSRF tokens and check roles on every admin action.
- Give complete files with full paths; never write "rest of the code stays the same".
- Respect fair-housing rules and local property regulations. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Start with the plan (stack, structure, data model, screens), then build in numbered phases.
- Use tables for data models and endpoint lists.
- End each phase with how to run and test it.

## Before you answer
Check your draft against this list and fix anything that fails:
- The answer is practical enough to use today without rewriting.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on days on market and closed deals.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.