Post-booking CRM
Latch is the post-booking buyer CRM Indian residential developers use for the 18 to 36 months between agreement for sale and possession. One white-labelled app for your buyers, one portal for your team. Bring the Excel you have today — we import it in the onboarding week.
For residential developers in Pune, Mumbai, Thane, Navi Mumbai and Bangalore handing over 50 to 500 units a year. Five to forty live projects. A team that runs on WhatsApp, Excel and Gmail today.
Live since
1 Pune developer live in production since April 2026
Infrastructure
AWS Mumbai (ap-south-1) — your data stays in India
Network
CREDAI Pune member outreach in progress
Onboarding
[QUOTE: placeholder — VP Projects at a Pune developer on the "same Friday WhatsApp question" problem, pending standing permission.]
Thirty are the same question: “when is slab done?”. Twelve are a father-in-law forwarding something. Five are a buyer who has already been told twice. Your VP Projects is typing the same answer to three different groups. Your Gmail has a thread from 2024 you now need for a RERA response by Monday and cannot find. The project is 14 months from possession. You have 11 more Fridays like this before slab on the next tower.
The cost of this is not efficiency. It is the founder answering a buyer at 11pm, a sales head who cannot go on leave, and no written record when a legal notice lands.
What ships
Every milestone — Booking, Agreement, Plinth, Slab, Possession — materialises per unit from a project template. Buyers open the app and see what is paid, what is due in 21 days, what is overdue. They download receipts themselves. Your collections team stops forwarding PDFs from Gmail.
[SCREENSHOT: admin payment plan wizard with Booking → Possession milestones]
[SCREENSHOT: buyer app payment schedule — paid / upcoming / overdue. Early access May 2026.]
Allotment letter, agreement for sale, receipts, OC, possession documents — shared from a vault with your logo on the buyer’s phone. Slab and plinth photos published as titled updates, tied to the payment milestone they matter for. Each update logged, each share logged.
[SCREENSHOT: document vault in admin portal, filterable by type]
[SCREENSHOT: project update composer with photo upload and milestone link]
Buyer raises a complaint in the app with photos. SLA auto-calculates from priority. Internal comments stay internal. Buyer-visible comments go to the buyer. Escalations route to the right person. Nothing sits in anyone’s personal Gmail or WhatsApp.
[SCREENSHOT: ticket detail — SLA countdown, priority, internal vs buyer-visible comment split]
Customer edit, payment recorded, ticket comment, document shared, broadcast sent — actor, timestamp, before / after, admin-viewable. When RERA or a buyer’s lawyer asks for proof of communication, you open a URL instead of searching a phone.
[SCREENSHOT: audit log viewer filtered by entity = payment]
How it works
Day 1
You share one project’s price list, payment-plan template and RERA number. Our onboarding team sets up your tenant at yourfirm.latchcrm.com with your logo and colours.
Day 3
We load your units, buyers, paid history and open tickets from whatever you have today — Excel, Tally export, or a Google Sheet. You review on a shared screen.
Day 7
Sales, projects and site ops log in with role-based access. First buyer broadcast goes out. Buyer app access lands when early access opens in May 2026.
Objections
"I already have Sell.Do or Salesforce."
Keep it. Latch starts the day the buyer signs — a job your lead CRM was not built for. We coexist, not replace.
"My buyers are fine with WhatsApp."
Your loud buyers are. The silent 290 of 300 are not telling you anything. Latch gives each of them their own unit view and you keep the audit trail.
"₹9,500 a month is real money."
One junior ops person costs ₹3 to 4 lakhs a year to do half this job badly. First quarter ROI is in the RERA defence alone.
"How do I know you will be around in three years?"
One live Pune tenant today and a team focused on post-booking residential. On-prem Model 2 gives you the code on your infra for ₹4.99 lakhs — you can run Latch yourself if we vanish.
Trust
One database per client on AWS Mumbai — not a shared pool with a tenant_id column. Your buyer data cannot comingle with another developer’s.
Admin, sales, staff. Sales reps cannot drop customers. Staff cannot edit payment plans. Enforced in every controller, not only the UI.
Razorpay handles every rupee. SES handles every email with bounce and complaint suppression so your sender reputation stays clean.
Offboarding is one command. You walk out with your full database.
Wildcard TLS, HTTPS only, RS256 JWT sessions, bcrypt password hashing, lockout after 5 failed attempts. Daily backups with point-in-time recovery.
No. Latch picks up the day the buyer signs the agreement for sale. Keep your lead CRM for pre-sales. We run the 18 to 36 months after.
AWS Mumbai (ap-south-1). Data physically stays in India. Your database is named after your firm. Offboarding is one command.
One week on the SaaS plan. Setup covers configuration, branding, your first project’s payment-plan template and a training session for your sales and ops leads.
The portal is live — that is where your team runs payments, documents, updates and tickets from. The Flutter buyer app is in early access from May 2026. Until then, buyers receive documents and receipts by email and WhatsApp from the portal.
Each tenant has a WhatsApp wallet with Razorpay top-up — pre-fund, we debit per send, you see the ledger. Meta Cloud API goes live once your firm’s number is registered. {{TODO: current template-approval status to quote to prospects.}}
Fifteen minutes on Google Meet. You will know in the first ten whether Latch fits your team.