A brokerage moved off spreadsheets onto a CRM built for it
Properties, leads, site visits and a matching engine in one system, with each salesperson seeing only their own leads.
- System and automation
- In user acceptance testing
At a glance
Client Luxe Realty
Client
Luxe Realty
Industry Residential and commercial real estate, Pune
Industry
Residential and commercial real estate, Pune
Time to build 3 months
Time to build
3 months
Year 2026
Year
2026
Status In user acceptance testing
Status
In user acceptance testing
Every case on this site answers the same four questions, so you can compare them.
Before
Properties and leads lived in two spreadsheets: society, flat, floor, facing and owner on one, name, budget and location on the other. Nothing stopped two people working the same lead.
What it does now
Staff add properties with photos, and create new property types and locations as they need them.
A new lead is checked against every existing lead by phone number, including old ones, and the system shows who already owns it.
Leads move through a pipeline: new inquiry, follow up, site visit, negotiation, closed.
Site visits are booked on a calendar with their outcome recorded.
A matching engine scores properties for each lead on budget, location, configuration, type and area.
Every change is logged, and the data can be backed up as JSON or CSV.
Where a person decides
Salespeople decide every stage move, visit outcome and which matched properties to share. They see only their own leads. Only admins can export or delete.
Result
In user acceptance testing with the Luxe team. We'll publish results after a full sales cycle on the system.
How we built it
Started from the two spreadsheets the team already used, so every column had a home.
Built the property and lead modules with duplicate protection on phone numbers.
Added the pipeline board, the site visit calendar and the matching engine.
Set three roles with their own permissions: super admin, admin and salesperson.
Connected a lead webhook so web inquiries land in the CRM, and wrote the handover document.
Stack
- Next.js
- TypeScript
- Supabase
- Tailwind
- FullCalendar
- Vercel
More work like this
One inbox for every inquiry a Dubai studio gets
An email engine that pauses itself before it hurts the domain
A distributor's back office rebuilt to sell nationally
Your case study starts with an audit.
One to two weeks inside your operations. You get a map of where time and money leak, the return on each fix, and a fixed scope before we build anything.
Most businesses we meet have paid for an AI tool nobody uses. We start from your numbers, so the first build is chosen by payback.
Zain Khan and Anwar Sheikh
Founders, OutGrow