TRETThe Real Estate Thingy

Why we built TRET: the spreadsheet, the WhatsApp groups and the lost leads

What we saw inside real estate sales teams before TRET, why generic CRMs didn't fix it, and the five rules we built the product around.

TRET team5 min read

Before we wrote a line of TRET, we sat with sales teams at builders and channel partners in Mumbai and Thane and watched how a home actually gets sold. Not in a slide deck: at the site office, on the phone, in the WhatsApp groups. This is what we saw, and why TRET looks the way it does.

Why do real estate leads go cold so fast?

A buyer who fills a form on 99acres or clicks a Meta ad is usually talking to three or four builders at once. The first one to call back with a clear answer gets the site visit. The rest get “already finalised, thanks”. A lead has about five minutes.

Most teams we met found out about a new lead hours later. The portal emailed one person, who forwarded it to a group, where somebody said “I'll take it” and then got pulled into a visit. Nobody was careless. There was simply no single place where a new lead showed up and someone was clearly on the hook for it.

That is why capture comes first in TRET. Every lead lands in one de-duplicated list and is assigned in seconds, whether it came from a portal, an ad, your website, WhatsApp or a walk-in, and a response clock starts the moment it arrives.

Why is the inventory spreadsheet always out of date?

Inventory lived in an Excel file that someone updated “every evening”. By lunch the next day two salespeople had offered the same 2BHK on the eighth floor to two different families. Holds were promises made on a phone call. The sales head found out a unit was sold when the accounts team asked for the booking form.

In TRET a hold is a record, not a promise. Everyone sees who it is held for and until when, and when it runs out the unit goes back on sale by itself.

Why do site visits get lost between enquiry and booking?

The single most expensive thing a builder does to sell a home is a site visit: a pickup, an hour of someone's time, sometimes lunch. And yet visits were tracked in a notebook or a personal calendar. No-shows weren't followed up, and nobody could say which source actually brought people to the site, only which one brought form fills.

So every visit in TRET moves through the same steps: scheduled from the lead, confirmed, checked in, and marked done with the next follow-up. A no-show is marked as one, so somebody chases it.

Why didn't generic CRMs fix it?

Many of these teams had tried a CRM. They gave up because it spoke the wrong language. A generic CRM has deals and contacts. A builder has projects, towers, floors and units; channel partners who expect credit for the clients they bring; token amounts, payment schedules and demand letters. Bending a deals pipeline into that shape took more effort than the spreadsheet it was meant to replace. Here is how TRET works as a real estate CRM for builders instead.

What rules did we build TRET around?

  • Every lead lands in one list within seconds, from every portal, ad, form and WhatsApp, with someone assigned and a clock running.
  • The phone comes first. Site teams don't sit at desks, so everything they need works on the app.
  • Inventory is live. A hold or a booking shows up everywhere the moment it happens.
  • The sale doesn't end at “won”. Bookings, payment schedules and demand notes are part of the same system.
  • It speaks the builder's language: units, towers, CPs, tokens, possession. Nothing has to be bent into shape.

How do you check whether your sales office has the same gaps?

You do not need a CRM to find out. Run these checks with your sales head, using last week.

  1. Trace yesterday's leads. Pick a few enquiries from yesterday and ask who owns each one and when it was first called. If nobody can answer from one screen, leads are slipping between inboxes.
  2. Ask about one unit. Ask two salespeople, separately, whether a particular flat is free. Two different answers mean your inventory is a snapshot, not a live record.
  3. Look at last weekend's visits. Count the no-shows and ask which ones got a follow-up call. Then ask which source brought the families who came, not just the form fills.
  4. Follow one channel partner client. Pick a recent client a partner introduced and see whether you can show, with a date, who registered them first.
  5. Trace a booking after “won”. Find where the payment schedule, the next demand note and the money received are kept, and whether sales can see them without asking accounts.

TRET answers each one by default: an owner and a response clock on every lead, holds that expire, visits with outcomes, partner links where the first registration wins with a timestamp, and bookings with payment schedules. More on the first in the first five minutes: lead response time and auto-assignment.

What does built in India for Indian builders mean?

TRET prices in lakh and crore, issues GST invoices, keeps your data in India, and knows what a channel partner is. We built it in Mumbai, with the people who use it every day looking over our shoulder.

If any of this sounds like your office, try TRET free for seven days with one project and a couple of salespeople. Or book a demo and we will set it up with your own projects and lead sources.

FAQ

Who is TRET for?

Indian builders, developers, channel partners and brokerages with a sales team. If your leads come from portals, ads and WhatsApp and your inventory lives in Excel, it was built for you.

How is TRET different from a generic CRM?

Generic CRMs track contacts and deals. TRET understands projects, towers, floors and units, site visits, channel partners and what happens after the booking.

Can I try TRET before paying?

Yes. Every workspace starts with a 7-day free trial with everything switched on, and no card is needed. You can also book a demo and we will set it up with your own projects and lead sources.

Related reading

All posts →