Leads decay before contact
An enquiry answered four hours later reaches someone who has already booked two other viewings.
Search with map
Filterable listings with saved-search registration
Transaction
Real Estate Agencies
A lead has a half-life measured in minutes.
Property enquiries decay faster than in almost any other sector. The agency that replies in two minutes wins the instruction; the one that replies at the end of the day is providing free market research to a competitor.
Where the work leaks
4 failure points
Listing distribution is manual
The same property typed into four portals, with prices and photos drifting out of sync between them.
Matching depends on recall
A new instruction should notify every registered buyer whose criteria it fits — instead it notifies whoever the agent thinks of.
Pipeline is invisible until exchange
Deals stall between offer and completion with no system flagging which ones have gone quiet.
What I build
10 modules
Public site
What the market sees
01
02
Listing detail
Gallery, floorplan, tour, and area data on one page
03
Valuation request
The instruction-generating form, routed instantly
04
Area guides
Local depth that earns search traffic and credibility
Back office & portal
Where the operation actually runs
01
Listing manager
One record syndicated to every portal automatically
02
Lead inbox with SLA
Owned, timed, and escalated if unanswered
03
Viewing scheduler
Agent availability, vendor approval, and confirmations
04
Buyer match engine
New and reduced listings pushed to matching criteria
05
Deal pipeline
Offer through completion, with stall detection
06
Commission calculator
Splits and referrals resolved at completion
What stops being someone’s job
When
Enquiry received
The system
Assign, acknowledge, and start a 5-minute response clock
When
Listing published or reduced
The system
Alert every buyer whose saved search matches
When
Viewing booked
The system
Confirm all parties, remind at T−2h, request feedback after
When
Deal inactive 7 days
The system
Flag to the manager with last-contact context
What moves
Typical baseline → target
Lead first response
2–4 hours
Under 5 minutes
Listing to portals live
Half a day, manual
Minutes, automatic
Buyers alerted per new listing
Whoever is remembered
Every match, instantly
Stalled deals detected
At month-end review
Day 7, automatically
These are sector baselines and the targets a system of this shape is built to hit — not results measured on a past engagement. Delivered work with implementation notes is on execution logs.
Where we start
Lead routing with a response SLA and the saved-search match engine — instructions won on speed.
Integrations
Portal feedsSMS gatewayE-signatureMapsCRM
Typical stack
Next.jsNode.jsPostgreSQLn8nTwilio