Skip to content
L Latch

Product

Two surfaces. One database. One week to live.

Your VP Sales runs the portal on Monday morning. Your buyer opens the app at the sample flat on Saturday. The same data flows both ways — payments, documents, updates, tickets. Nothing in between is a WhatsApp group.

Book a 15-min call
[SCREENSHOT: split-frame — admin portal on laptop left, buyer app on phone right, both showing the same unit.]

Half 1 — Admin Portal

Your team logs in at yourfirm.latchcrm.com

Sales head, projects head, site ops lead, support desk. Role-based access — each sees only what their role allows.

1. Projects, units and payment plans, set up once

Model a project the way RERA asks for it — tower, floor, unit, total price, carpet area. Build a payment-plan template per project (Booking, Agreement, Plinth, Slab, Possession). Assign a unit to a buyer and the schedule locks to the booking date.

Before: Per-buyer Excel. "What did we agree in the allotment letter?" goes around three people.

After: One template per project. One schedule per unit. One screen for every answer.

[SCREENSHOT: payment plan wizard with milestone templates]

[SCREENSHOT: unit detail with buyer assignment and schedule]

2. Support tickets with an SLA clock

Every complaint carries a priority, an SLA auto-calculated from that priority, an owner and an escalation path. Internal comments stay between your team. Buyer-visible comments go to the buyer in their app. Photo evidence on both ends.

Before: Complaints spread across WhatsApp, Gmail and personal phones. Escalations happen because someone is angry, not because the SLA expired.

After: The SLA is the escalation trigger. The buyer sees the status. Your ops head sees the queue.

[SCREENSHOT: ticket list with priority and SLA countdown]

[SCREENSHOT: ticket detail — internal vs buyer-visible comment split]

3. Broadcasts, document catalog and audit log

Publish a construction update with photos or a short video, tick "notify", and buyers receive it on the app, WhatsApp and email. Share an allotment letter or receipt from the catalog with one click. Every share, edit, payment and reply — audit-logged with actor, timestamp and before / after.

Before: The WhatsApp group of 300. An angry buyer pastes a screenshot and 299 panic. No record of who emailed what, when.

After: One update, sent to every buyer in the right channel, tied to the milestone it belongs to. Audit log for everything.

[SCREENSHOT: project updates composer with photo upload and milestone link]

[SCREENSHOT: audit log viewer filtered by entity = payment]

What we deliberately do not do

Latch picked four things (payments, documents, construction updates, tickets) and refused the fifth.

  • —No lead / pre-sales CRM. Keep Sell.Do or Salesforce for that.
  • —No society management or visitor entry. MyGate is that category.
  • —No loan origination, broker commission or vendor payables.
  • —No email marketing or drip campaigns beyond transactional notifications.

This is the reason the product ships in a week, not a year.

Half 2 — Buyer App

Your buyer downloads your app

Your name, your logo, your colour — from the Play Store or App Store. Signs in with their mobile and the password sent at allotment.

Status: Flutter buyer app is in active development. Early access from May 2026. Every feature below maps to the shipped PRD. Until the app ships, this page carries a standing "early access" banner.

1. Their unit, their schedule, their receipts

The buyer opens the app to their flat — tower, floor, unit number, carpet area, booking date. Below, every payment milestone with status: paid, due in 21 days, overdue. Tap a paid milestone, download the receipt.

Before: Buyer calls your sales office to ask "did my 20% registration payment go through?". Your junior sends the receipt on WhatsApp.

After: Buyer opens the app. Your sales office is free.

[SCREENSHOT — Early access May 2026]

2. Documents and construction updates, in one feed

Allotment letter, agreement for sale, receipts, possession documents — filterable by type, viewable in-app. Construction updates in a chronological feed with photos and video, tied to the milestone they belong to.

Before: Buyer asks when the last slab was cast. You re-forward a WhatsApp photo from 11 days ago.

After: Buyer opens the app, scrolls the feed.

[SCREENSHOT — Early access May 2026]

3. Raise a ticket without joining a WhatsApp group

Buyer opens a ticket with up to five photos, sees the status stepper, gets notified when your team replies. Your ops head sees the same ticket in the portal with the SLA already running.

Before: Buyer adds a problem to the group chat. 299 others read it. You either reply in public or reply in DM — and now there are two versions of the story.

After: Ticket. Photos. SLA clock. One thread, one audit trail.

[SCREENSHOT — Early access May 2026]

See it with your own project's numbers plugged in.

Fifteen minutes on Google Meet. Bring one project's payment plan; leave with a demo that already reflects it.

Book a 15-min call