Shannu.
← Back

04 / The Work

LMS

Lease Management Platform · v1.0 Shipped · v1.5 Led Solo · v2.0 In Discussion

Built At Antz →

The Problem

A lease management platform for a US property firm — rent runs, lease payments, holdover, recurring costs, all the moving parts a property team touches daily. I came in on v1.0 as part of the build team, learned the lease domain by shipping it, then took v1.5 end to end on my own.

The Decisions

Learned The Domain By Shipping v1.0

Lease accounting isn't intuitive — I picked it up by building the first version with the team, not by reading a spec and hoping.

Owned v1.5 Solo

Support and enhancements ran through one accountable person instead of a shared queue — issues close faster when someone actually owns them.

Chased The Database Connection Leaks

Explicit connection handling and pool monitoring, not a restart cron papering over the symptom.

Translation, As Much As Engineering

Half the job was turning engineering into something the client's product side would sign off on.

How It Works

  1. 01It's the system a property team runs on — leases, rent runs, payments, holdover, recurring costs, account coding.
  2. 02FastAPI and SQL Server on the back, a React front end, Entra sign-on, shipped through Azure Pipelines.
  3. 03v1.0 I built alongside the team; v1.5 — support plus enhancements — was mine end to end.
  4. 04v2.0 is in discussion now: what it should become, and what that's worth building.

High-Level Design

Web UI (React)API (FastAPI)ORM (SQLAlchemy)DBIdentity (SSO)CI/CD pipelineslegacy stored procs retired
// sanitized · generic pattern, not the real schema or service names

The Outcome

v1.5 support and enhancements shipped and stable in production. v1.0 was a team build; v1.5 I led solo. v2.0 is under discussion.

39 tables · access via SQLAlchemy ORM

v1.0 With The Team. v1.5, Just Me.