Muhammad Ikram Let's talk

Most Real Estate CRMs Break at 10,000 Units

Launch day. 340 agents. One premium project. Zero distributed locks. Three buyers confirm the same penthouse. Payments cleared. Documents signed. Champagne somewhere in the background.
Nobody knew until registration day.
That is not a software problem. That is an architecture problem.
The teams that scale past 10,000 units quietly fix the boring stuff — inventory DB hierarchy, atomic booking locks, payment reconciliation ledgers, document workflows that hold under real pressure.
Features sell the product. Architecture keeps it alive.
Swipe through. Broke down exactly how it works.

Read the slides as text

Slide 1

P R O P T E C H D E E P D I V E
0 1 / 1 0
🏗️ T H E Q U E S T I O N N O B O D Y A S K S A T S T A N D - U P
EVER WONDER HOW
REAL ESTATE CRMS
HANDLE 10,000 UNITS?
Spoiler: it's not a giant spreadsheet named
"final_FINAL_v3.xlsx" — though we deeply respect the
hustle.
I N V E N TO RY D B
B O O K I N G LO C KS
PAYM E N T R E C O N
D O C W O R K F LO W
10K
10K
U N I T S . A L L C H A O S . A L L M A N A G E D .

Slide 2

😅
T H E R E A L I T Y C H E C K
WHEN 1 UNIT IS EASY. 10,000 IS A WAR.
0 2 / 1 0
Managing one apartment? Cute. Now imagine 10,000 units — towers, floor plans,
payment schedules, statuses, owners, all moving simultaneously. Without a
robust CRM, you're playing 4D chess blindfolded.
💡 Here's how the good systems actually handle it. Thread unlocked. 👇
C O N C U R R E N T B O O K I N G S
340+
Happening simultaneously on launch day
P A Y M E N T V A R I A N T S
12+
Installment plans per project type
D O C U M E N T T Y P E S
60+
Per unit across the full lifecycle
S T A T E C H A N G E S
∞
Available → Held → Booked → Sold → Cancelled…

Slide 3

🗄️ C H A P T E R 1 O F 4
INVENTORY DB STRUCTURE
0 3 / 1 0
Forget flat tables. A real estate inventory DB is a multi-dimensional beast —
Projects → Towers → Floors → Units. Every node has its own attributes, pricing,
and status. A tree that never sleeps.
📋 U N I T S T A B L E — S I M P L I F I E D S C H E M A
unit_id
UUID PK
globally unique
project_id
FK → projects
dev umbrella
tower_floor_no
JSONB
flexible layouts
status
ENUM
state machine driven
base_price
DECIMAL(12,2)
USD + modifiers
lock_version
INT
optimistic locking
attributes
JSONB
BR, view, facing…
updated_at
TIMESTAMP
full audit trail
Hierarchical Structure
Project → Phase → Tower → Floor → Unit. Every
level cascades pricing rules and availability logic.
🌳
JSONB for Flexibility
Different unit types need different attributes. JSONB
avoids 200-column tables that haunt your DBA's
dreams.
🔢
Indexed Status Columns
Partial indexes on status = 'available' make your
availability queries blazing fast even at 10K+ scale.
📊
Optimistic Locking
lock_version stops two agents from booking the
same unit simultaneously. This one feature saves
marriages.
🔒

Slide 4

🔐 C H A P T E R 2 O F 4
BOOKING LOCKS
0 4 / 1 0
Two agents. One premium unit. Same millisecond. This is the double-booking
nightmare that keeps architects awake. Here's how a solid CRM wins the race —
without breaking a sweat.
01
🖱️
HOLD REQUEST
Agent clicks "Reserve" — a
soft lock is created with a
15-min TTL in Redis.
02
⚡
ATOMIC CHECK
DB checks lock_version +
status in one atomic
transaction. Zero race
conditions.
03
✅
LOCK GRANTED
Status flips to HELD. Other
agents see it unavailable
instantly via cache
invalidation.
04
⏱️
TTL EXPIRY
No payment in 15 min?
Lock auto-releases. Unit
returns to AVAILABLE
without manual cleanup.
05
💳
CONFIRMED
Payment received →
status upgrades to
BOOKED. Lock becomes a
permanent booking record.
⚠️
The naive approach — checking status before inserting — causes race conditions
under load. Always use SELECT FOR UPDATE or optimistic locking. Your launch day
will thank you.

Slide 5

💰 C H A P T E R 3 O F 4
PAYMENT RECONCILIATION
0 5 / 1 0
Real estate payments aren't a single charge — they're a saga. Booking amounts,
milestones, tax withholding, penalties, refunds. The recon engine is a mini
accounting firm inside your CRM.
T O T A L C O L L E C T E D
$101M
P E N D I N G M I L E S T O N E S
$25.2M
O V E R D U E ( 3 0 D + )
$2.1M
R E C O N C I L E D T O D A Y
99.7%
📅
MILESTONE ENGINE
Custom payment plan per unit — slab-
linked, time-linked, or construction-linked.
Auto-generates demand notices on trigger.
🔄
MULTI-GATEWAY SYNC
Wire, ACH, checks, Zelle, PDCs — every
channel reconciles into one ledger per unit.
Webhooks fire instantly on confirmation.
⚖️
TAX WITHHOLDING
Buyers withhold applicable taxes;
developers collect state/local sales tax.
IRS-ready records, always audit-proof.
🔁
REFUND WORKFLOWS
Cancellations trigger refund calculations
factoring forfeiture clauses, penalties, and
fees. No manual math. No drama.
📊
LEDGER PER UNIT
Every unit has its own double-entry ledger.
Credits, debits, pending, overdue — a
finance team's best friend.
🚨
OVERDUE ALERTS
Missed milestone triggers escalation:
buyer notification → agent alert → legal
flag. Zero manual follow-up needed.

Slide 6

📄 C H A P T E R 4 O F 4
DOCUMENT WORKFLOW
0 6 / 1 0
Every unit generates a mountain of documents. A smart workflow engine doesn't
just store them — it orchestrates who signs what, when, and in what order. Think:
choreographer for paperwork.
01
📝
BOOKING APPLICATION FORM
Auto-generated from unit + buyer data. No more copy-pasting into Word templates at 11 PM before a
launch.
A U T O - G E N
02 ✍️
E-SIGN WORKFLOW
DocuSign / HelloSign sends allotment letters, NDAs, and purchase agreements to the buyer's inbox with
a full audit trail.
E - S I G N
03 🏦
LENDER & MORTGAGE DOCUMENTS
CRM packages docs for 20+ lender integrations automatically. One click sends the complete
mortgage dossier.
L E N D E R - R E A D Y
04 ⚖️
CLOSING & TITLE WORKFLOW
Generates county recorder-ready documents, tracks closing dates, and auto-reminds buyers, attorneys,
and accounts.
L E G A L
05 🗄️
POSSESSION & HANDOVER KIT
CO copy, snag list, warranty cards, handover letter — bundled digitally. Buyers scan a QR code.
Humans rejoice.
H A N D O V E R

Slide 7

🤣
T H E H O N E S T T R U T H
CRM WITHOUT ARCHITECTURE =
CHAOS IN A SUIT & TIE
We've all seen it. The "CRM" that's actually a WhatsApp group + Google
Sheet combo held together by one overworked ops manager and pure
willpower. Respect. But there's a better way.
😵
WITHOUT ARCHITECTURE
Double bookings at closing. Refund math in a
calculator app. Payment status? Just call the
buyer directly.
VS
😎
WITH SOLID ARCHITECTURE
State machines prevent double bookings.
Ledgers auto-reconcile. Docs are one click
away. Sleep is possible again.
0 7 / 1 0

Slide 8

🏛️ U N D E R T H E H O O D
THE TECH STACK THAT MAKES IT TICK
0 8 / 1 0
Behind every smooth sales launch is an architecture that handles concurrency,
consistency, and scale without breaking a sweat. Here's what production-grade
CRMs lean on.
🗄️DATABASE LAYER
→PostgreSQL with row-level locking for unit state
management
→Partitioned tables by project for blazing-fast inventory
queries
→Read replicas to offload analytics from the transactional
DB
→Event sourcing for a full audit trail of every state change
⚡CACHING & LOCKS
→Redis for distributed soft locks with configurable TTL per
project
→Availability cache invalidated on every status change via
pub/sub
→Rate limiting per agent to prevent booking spam on
launch day
→Lua scripting in Redis for atomic check-and-set
operations
🔄PAYMENT & EVENTS
→Webhook consumers with idempotency keys — zero
duplicate credits
→Message queue (Kafka / RabbitMQ) for async payment
processing
→Saga pattern for distributed transactions across payment
+ booking
→Dead letter queues for failed events — nothing is ever
lost
📄DOCUMENT ENGINE
→Template engine (Handlebars/Jinja) for dynamic doc
generation
→S3-compatible storage with access-controlled presigned
URLs
→e-Sign webhooks update document status in real-time
→Version control per doc — always know what was signed
and when

Slide 9

💡 T H E T L ; D R
5 THINGS THAT SEPARATE GOOD CRMS FROM
GREAT ONES
0 9 /
1 0
Building or evaluating a real estate CRM? Run it through these five filters. The
ones that pass all five? Rare. Worth every dollar.
1
STATE MACHINE FOR UNIT STATUS
Not just a field — a proper FSM controlling every allowed transition. Available → Held → Booked → Registered. No
shortcuts.
2
ATOMIC BOOKING + PAYMENT COUPLING
Booking record and payment ledger must be created in the same transaction — or not at all. Partial states are ticking time
bombs.
3
IDEMPOTENT WEBHOOK HANDLING
Payment gateways WILL send duplicate webhooks. Handle them gracefully — no double credits, no 2 AM panic.
4
DOCUMENT VERSIONING WITH AUDIT TRAILS
Courts care about what was signed, by whom, and when. Every doc must be versioned, timestamped, and tamper-proof.
5
REAL-TIME AVAILABILITY WITHOUT DB HAMMERING
Cache availability data. Invalidate on change. Don't hit your inventory table 200×/sec on launch day.
🔁 Found this useful? Save this post — you'll want it when someone
asks you to build the next $1B PropTech unicorn.
S A V E T H E T H R E A D ↗

Slide 10

🏗️
T H A T ' S A W R A P — F O R N O W
BUILD THINGS THAT
SCALE WITHOUT SCREAMING
Real estate tech is one of the most underrated engineering
challenges out there. Inventory, money, legal documents — all at
once, all at scale. If you're in this space, you're building something
genuinely complex. Own it. 🫡
👋 FOLLOW FOR MORE
👍 LIKE THIS POST
🔁 SHARE THE THREAD
# R E A L E S TAT E T E C H
# P R O P T E C H
# S Y S T E M D E S I G N
# C R M
# B A C K E N D E N G I N E E R I N G
# D ATA B A S E D E S I G N
# S O F T WA R E A R C H I T E C T U R E
# P R O D U C T E N G I N E E R I N G
© P R O P T E C H D E E P D I V E — B U I L T W I T H ☕ A N D E X I S T E N T I A L D R E A D A B O U T L A U N C H D A Y S
1 0 / 1 0

More insights

Keep reading

All posts
Carousel

CRM & PropTech 2 min read

Your Search Bill Grows Fastest When Sales Peak

A common trap: a search engine gets priced on an average month. Then November arrives. Algolia Grow charges $0.50 per 1,000 searches after 10,000, so traffic spikes hit cost and conversion at once. Budget search on peak demand.

Carousel

CRM & PropTech 1 min read

Your Lead Score Is Useless If Sales Won't Trust It

A lead score is a promise to sales. Break it once with a "hot" lead that goes nowhere, and reps return to their own lists. Open criteria, a feedback loop and a quarterly review turn scoring into pipeline that converts.