For a new real estate platform request, define the domain model first:

Core entities:
- Property (id, address, type, price, status, owner_id, images[], features{})
- Owner/Landlord (id, contact_info, properties[])
- Tenant/Buyer (id, contact_info, leases[]/purchases[])
- Lease/Contract (id, property_id, tenant_id, start_date, end_date, rent, deposit, status)
- Transaction (id, type[rent|sale|deposit], amount, date, status)
- Agent (id, commission_rate, assigned_properties[])

Then scaffold stack (default recommendation unless client specifies otherwise):

• Frontend: React/Next.js (SSR for SEO on listings) + Tailwind
• Backend: Node.js/Express or NestJS (REST or GraphQL API)
• Database: PostgreSQL (relational data: leases, transactions) + S3/Cloudinary for images
• Auth: role-based (admin, agent, owner, tenant)
• Extras: Maps API (Google Maps/Mapbox), payment gateway (Stripe), PDF generation for contracts

Progress:

• Step 1: Requirements gathering — clarify business model (rental, sale, or both; residential/commercial)
• Step 2: Define data model & user roles (admin, agent, owner, tenant/buyer)
• Step 3: Design core flows (listing creation, search/filter, inquiry, contract, payment)
• Step 4: Build backend API with auth and CRUD for each entity
• Step 5: Build frontend (public listing site + private dashboard per role)
• Step 6: Integrate third-party services (maps, payments, e-signature, notifications)
• Step 7: Implement reporting (occupancy rate, revenue, overdue payments)
• Step 8: Deploy, set up monitoring and backups

Step details

1. Requirements gathering Ask/confirm: Is this for managing own properties, a multi-tenant SaaS for property managers, or a public marketplace? This determines whether multi-tenancy is needed.

2. Data model Always separate "listing" (public-facing) from "property" (internal record) if the same property can be listed multiple times or delisted.

3. Core flows to prioritize

1. Search & filter listings (price range, location, type, bedrooms)
2. Lead capture / inquiry form → CRM-like tracking
3. Lease/contract lifecycle (draft → signed → active → expired/renewed)
4. Payment tracking (rent due, late fees, receipts)
5. Maintenance requests (tenant → owner/manager)

4-5. Backend/Frontend Build API-first. Public listing pages need SSR/SSG for SEO. Dashboards can be CSR (SPA).

7. Reporting essentials Occupancy rate, monthly revenue vs. projected, overdue payments list, lease expiration calendar (renew 60-90 days ahead).