Real Estate Management Platform
Budget: $250 – $750 USD
Overview
We’re building a web-based real-estate management system used by companies to run properties, branches, owners, agents and tenants from one dashboard. The MVP must support three user roles (Admin, Agent, Tenant) with secure logins, role-based permissions and tailored interfaces. The feasibility study (provided) contains full page and flow details — bidders should read it.
#Tech stack (required)
Frontend: React (Vite)
Backend: NestJS
Database: PostgreSQL
Maps: Google Maps (or other approved provider; explain choice)
Auth: JWT + refresh tokens, secure password hashing (bcrypt)
DB modelling: TypeORM.
CI/CD: candidate’s choice (must support staging and production deploy)
# Key MVP features
Multi-company registration (multi-tenant data separation)
Branch management per company
Employee management & role/permission system per company
Owners management + property-owner linking
Property management: apartments, photos, parking
Tenant management + lease contracts + file uploads
Maintenance requests & invoice attachments
Revenue reporting (filters: period, occupied/vacant, type)
Detailed permission model for employees & owners
Property display on maps with info cards
Responsive UI (desktop first, mobile friendly)
Admin panel to control entire app (add/edit/delete/disable)
#Non-functional requirements
Secure auth and role-based access control
Reasonable performance with pagination and indexes for lists
Clean, maintainable TypeScript code (frontend & backend)
DB migrations and seed scripts
What I expect from bidders (must include in proposal)
Experience proof: links to 2–3 similar projects (React + NestJS + Postgres). Public repos / screenshots / live demos preferred.
Milestones & timeline: itemized milestones (see suggested below). Do not bid if you can’t deliver fast.
Testing & QA plan: how you ensure quality.
Deliverables: source code (Git), deployment scripts, docs, Postgres schema.
Availability & timezone: working hours and weekly capacity.
Price: fixed-price or hourly rate + estimate of total hours. (No ballpark guesses — give a real bid).
References: at least two client references or GitHub/LinkedIn profiles.
Do NOT apply if you are learning, junior, or have minimal experience with this stack.
We’re building a web-based real-estate management system used by companies to run properties, branches, owners, agents and tenants from one dashboard. The MVP must support three user roles (Admin, Agent, Tenant) with secure logins, role-based permissions and tailored interfaces. The feasibility study (provided) contains full page and flow details — bidders should read it.
#Tech stack (required)
Frontend: React (Vite)
Backend: NestJS
Database: PostgreSQL
Maps: Google Maps (or other approved provider; explain choice)
Auth: JWT + refresh tokens, secure password hashing (bcrypt)
DB modelling: TypeORM.
CI/CD: candidate’s choice (must support staging and production deploy)
# Key MVP features
Multi-company registration (multi-tenant data separation)
Branch management per company
Employee management & role/permission system per company
Owners management + property-owner linking
Property management: apartments, photos, parking
Tenant management + lease contracts + file uploads
Maintenance requests & invoice attachments
Revenue reporting (filters: period, occupied/vacant, type)
Detailed permission model for employees & owners
Property display on maps with info cards
Responsive UI (desktop first, mobile friendly)
Admin panel to control entire app (add/edit/delete/disable)
#Non-functional requirements
Secure auth and role-based access control
Reasonable performance with pagination and indexes for lists
Clean, maintainable TypeScript code (frontend & backend)
DB migrations and seed scripts
What I expect from bidders (must include in proposal)
Experience proof: links to 2–3 similar projects (React + NestJS + Postgres). Public repos / screenshots / live demos preferred.
Milestones & timeline: itemized milestones (see suggested below). Do not bid if you can’t deliver fast.
Testing & QA plan: how you ensure quality.
Deliverables: source code (Git), deployment scripts, docs, Postgres schema.
Availability & timezone: working hours and weekly capacity.
Price: fixed-price or hourly rate + estimate of total hours. (No ballpark guesses — give a real bid).
References: at least two client references or GitHub/LinkedIn profiles.
Do NOT apply if you are learning, junior, or have minimal experience with this stack.