How a Bangalore real estate developer answers every buyer enquiry in minutes

The client: A residential developer and brokerage in Bangalore with three active projects and a 40-person sales team. Name withheld for confidentiality.

The situation

Enquiries arrived from property portals, the company website, WhatsApp and walk-ins. Each one had to be copied into a spreadsheet, checked against which flats were still available, and answered by a salesperson — who was usually on a site visit.

By the time a buyer got a reply, many had already spoken to two other developers. Site visits were booked over phone calls and occasionally double-booked. Every evening, coordinators spent hours chasing home-loan documents from buyers who had already paid a booking amount.

Before and after

• Replying to a new enquiry

  BeforeCopied into a sheet, answered when a salesperson was free — often the next day

  AfterMatched to available homes and a reply drafted within minutes; salesperson approves with one tap

• Booking a site visit

  BeforePhone calls back and forth; occasional double bookings

  AfterBuyer picks from live slots; site manager’s calendar updates automatically

• Morning planning

  BeforeEach salesperson scrolled through the sheet and WhatsApp

  AfterAn 8am briefing: hot leads, follow-ups due, today’s visits

• Home-loan paperwork

  BeforeCoordinators checked every upload by hand

  AfterClaude checks each document and lists exactly what is missing

What we built

1. A lead desk that never sleeps

   Every enquiry — whatever its source — is read by Claude, matched against live inventory by budget, size and location, and turned into a personal reply with the right brochure and floor plan. The salesperson reviews and sends it.

2. Self-service site visit booking

   Buyers choose a time from real availability. The site manager and salesperson get the visit on their calendars, with a short summary of what the buyer is looking for.

3. A daily sales briefing

   At 8am each salesperson receives a short list: who to call first, which follow-ups are due and which buyers are visiting today.

4. A buyer document portal, hosted in India

   Buyers upload ID, income and loan documents to a secure portal we built. Claude checks each one and tells the buyer — and the coordinator — what is still needed.

5. A live pipeline page for leadership

   Founders see enquiries, visits and bookings by project, updated through the day, without asking anyone for a report.

The Claude tools we used — in plain English

• Claude for Google Workspace

  Claude working inside Gmail, Google Docs, Sheets and Calendar, where your team already spends its day.

  How we used it here: Reads enquiry emails, drafts replies in Gmail and keeps the inventory sheet and visit calendars in sync.

• Connectors (MCP)

  Secure links that let Claude read from and write to the tools you already use — your CRM, email, calendar, file storage — with only the access you allow.

  How we used it here: Links Claude to the CRM and property-portal lead feeds, with read and write access limited to what the workflow needs.

• Scheduled tasks

  Jobs that run by themselves on a timetable — every morning at 8am, every Monday — like a reliable assistant who never forgets.

  How we used it here: Sends every salesperson their 8am briefing and an evening list of buyers still waiting on documents.

• Artifacts

  Live, shareable pages — dashboards, previews, checklists — that Claude builds and keeps up to date, so nobody waits for a spreadsheet to be emailed.

  How we used it here: Powers the live pipeline page that leadership checks instead of asking for reports.

• Claude Code (desktop app)

  The workbench our engineers use to have Claude build and test software with them. It is why we can ship a custom app in weeks rather than months.

  How we used it here: Our engineers used it to design, build and test the buyer document portal in under four weeks.

• Claude API

  The engine behind the custom applications we build for you: your own branded app, with Claude doing the thinking in the background.

  How we used it here: Runs the document checks inside the portal, behind the developer’s own branding.

Where it runs

Buyer identity and income documents are sensitive, so the document portal, its database and every uploaded file are hosted in India. Access is limited to named staff and every action is logged.

The results

• Average first response to a new enquiry fell from over four hours to seven minutes.
• Site visits booked from the same volume of leads rose by 31% in the first quarter.
• No double-booked site visits since launch.
• Sales coordinators saved around 25 hours a week between them, now spent on buyer calls and handovers.