Skip to content
04PropTech / Property Management SaaSConcept Project

EstateFlow

Rental operations for landlords and property managers — tenants, leases, rent and maintenance.

Type
Web application · SaaS
Platform
Responsive web, tenant mobile views
Scope
Product design, architecture, full-stack
Status
Concept Project

Owner dashboard. Portfolio performance, rent collection, occupancy and properties at a glance.

01

Overview

EstateFlow is a concept for a property management SaaS used by independent landlords and small property management companies looking after several buildings and units.

It focuses on the recurring operational work of renting property — leases, rent, arrears and maintenance — and gives owners an accurate picture of how each property is performing.

02

Problem & solution

The business problem

Property operations are recurring, deadline-driven and detail-heavy. Without a system, they quickly spread across spreadsheets, banking apps and messaging threads.

  • Rent due dates, partial payments and arrears are tracked manually.
  • Lease terms, renewals and deposits live in files that are hard to search.
  • Maintenance requests arrive by phone or message and are easily lost.
  • Owners receive irregular, manual reports on how their properties perform.
  • Communication with tenants is scattered and undocumented.

Proposed solution

A structured system of record for properties, units, tenants and leases, with automated rent schedules and a trackable maintenance workflow.

  • A portfolio → property → unit hierarchy with listings and occupancy status.
  • Lease records that generate rent schedules automatically, including escalations and deposits.
  • Rent tracking with partial payments, arrears ageing and receipts.
  • Maintenance requests with priority, assignment, progress updates and costs.
  • Owner dashboards and statements generated from the same underlying records.
03

Key features

  • 01

    Property listings

    Properties and units with details, amenities, photos and availability status.

  • 02

    Tenant management

    Tenant profiles, documents, contacts and complete rental history.

  • 03

    Lease & contract records

    Lease terms, dates, deposits, escalations and renewal reminders.

  • 04

    Rent collection tracking

    Automated schedules, partial payments, arrears ageing and receipts.

  • 05

    Maintenance requests

    Tenant-submitted requests with photos, priority, assignment and status.

  • 06

    Owner dashboard

    Occupancy, collected rent, arrears and open issues across the portfolio.

  • 07

    Multi-property management

    Manage many properties and owners from one account with clean separation.

  • 08

    Property performance analytics

    Income, expenses, occupancy and yield trends per property.

  • 09

    Tenant communication

    Logged notices and messages tied to tenants, units and requests.

04

Interface design

Tenant & lease record. Lease terms, rent schedule and payment history for a single tenancy.
Tenant maintenance request. Mobile request flow with photos, priority and live status tracking.
05

User roles & workflows

Runs day-to-day operations across the portfolio.

  1. 1

    Onboard a property and its units

  2. 2

    Create a lease and rent schedule

  3. 3

    Track payments and arrears

  4. 4

    Coordinate maintenance

06

Architecture

L1Clients
  • Manager web app
  • Owner portal
  • Tenant portal (mobile-first)
L2API
  • REST API
  • Multi-tenant auth & RBAC
  • File uploads
L3Domain services
  • Lease & rent scheduler
  • Payments & arrears
  • Maintenance workflow
  • Statements & reports
L4Data
  • PostgreSQL
  • Redis — job queue
  • Object storage — documents & photos
L5Integrations
  • Email & SMS notices
  • Bank import (concept)
  • PDF statements
Architecture overview — proposed design

Rent schedules as generated data

Creating a lease generates its schedule of charges from the terms. Changes such as escalations create a new schedule version rather than editing history.

Predictable payment allocation

Payments are allocated to the oldest outstanding charges first, with explicit handling of partial payments and credits — so arrears are always explainable.

Organisation-level isolation

Every record belongs to an organisation; owners see only their properties and tenants only their own lease, enforced in the data-access layer.

Measurable maintenance

Requests move through Reported → Assigned → In progress → Resolved, and each transition is timestamped so response times can be measured.

07

Technology stack

Frontend
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
Backend
  • Node.js
  • NestJS
  • REST API
  • BullMQ
Data
  • PostgreSQL
  • Prisma ORM
  • Redis
Infrastructure
  • Docker
  • S3-compatible storage
  • Email & SMS provider

Proposed stack for the concept; choices would be validated against a real client's constraints.

08

Engineering considerations

  1. 01

    Dates are harder than they look

    Pro-rated first months, leases starting mid-month, month-end edge cases and escalations all need predictable, well-tested behaviour.

  2. 02

    Three audiences, one dataset

    Managers, owners and tenants see the same records through very different lenses. Permissions and views were designed together from the start.

  3. 03

    Mobile-first for tenants

    Tenants mostly use their phones, so maintenance requests and payment history were designed for small screens first.

  4. 04

    Statements that always reconcile

    Owner statements are generated from the ledger of charges and payments, never edited by hand.

09

Project status

Concept Project

EstateFlow is a self-initiated concept project, created to explore product design and engineering for rental property operations. It has not been delivered to or deployed for a client. The interface designs and architecture are presented as a case study, and all names, businesses and figures shown in the mockups are illustrative.