Public listings
Search and filter by locality, budget, configuration and status. Fast, and indexable by Google — the listings are the marketing.
CASE STUDY
Example buildWebsite + CRMReal Estate Listing Portal
Property search, enquiry capture and a lead pipeline a sales team will actually use.
- Type
- Public website + CRM
- Build time
- 9–13 weeks
- Platforms
- Browser, agents on mobile
- Starts at
- ₹90,000*
This is an example build. Tavzuran is a new studio with no client work to show yet. This page describes how the project would be scoped and built — the same thinking you would get on a real one. Nothing here is a past client, and no number on this page is a result.
The price follows the feature list. The number above buys everything scoped on this page. Take features out and it comes down — the shortest route to a smaller number is a shorter list, and deciding what to drop is what the free call is for.
THE SITUATION
What's actually broken.
A property business advertises on the big portals, pays for every lead, and loses some of them because enquiries arrive as emails that someone has to notice. There is no record of which agent called whom, or when.
Two things are being built here, and only one of them is the website. The site brings enquiries in; the CRM decides whether they turn into anything. Most projects like this over-invest in the first and under-invest in the second.
Paid leads sit unread in a shared mailbox
No record of who called whom, or when
Listings live on portals you do not control
Follow-ups depend on an agent remembering
VERSION ONE
What we'd build first.
Every item here earns its place by being something a real user would miss on day one.
Property pages
Photos, floor plans, location, and an enquiry form that is short enough that people finish it.
Lead capture
Every enquiry, from the site or a portal-forwarded email, lands in one inbox and is assigned to an agent within a minute.
Pipeline
New → contacted → visit booked → negotiating → closed or lost. Each move requires a note. This is the discipline the tool is buying.
Follow-up reminders
A lead with no activity for three days surfaces at the top of the agent's list. Most lost leads are lost to silence, not to price.
DELIBERATELY NOT IN V1
What we'd leave out.
Not because these are bad ideas. Because each one is designed better once the first version has told you something.
- Virtual tours and 3D walkthroughs — better bought from a specialist vendor and embedded.
- Document management and agreement generation.
- A public agent-facing mobile app. The CRM is responsive; agents work from their phone browsers in v1.
UNDER THE HOOD
How it's put together.
- Public site
- Server-rendered with Next.js, because search engines have to be able to read the listings
- CRM
- React, behind a login
- Backend
- Node with Postgres
- Images
- Resized on upload and served from object storage — property photos are the heaviest thing on the page
- Email intake
- A parser that turns portal enquiry emails into leads
HOW IT RUNS
Week by week.
-
01
Week 1
Listing structure and the pipeline stages, agreed with whoever runs sales rather than whoever runs marketing.
-
02
Weeks 2–6
Public site, search and property pages.
-
03
Weeks 7–10
Lead capture, assignment and the pipeline.
-
04
Weeks 11–13
Reminders, reporting and the sales team's first weeks on it.
THE HARD PART
A CRM salespeople will actually use
Every build has one problem that decides whether the rest of it matters. This is that problem, written out.
The website is the straightforward half. CRMs fail for a reason that has nothing to do with engineering: they ask a salesperson to do admin, and a salesperson under target will not do admin.
So the design question is not what data would be useful to capture. It is what is the least a person can enter after a call, and how do we make entering it faster than not entering it. In practice that means two taps for the common outcomes — no answer, call back, visit booked — a free-text note that is optional, and never a required field the agent has to think about.
The other half is making the tool give something back immediately. An agent who logs a call should see their follow-up list reorder itself in front of them. If the CRM only takes and never gives, it becomes the thing that gets updated on Friday afternoon from memory, and at that point the pipeline is fiction.
BEFORE A PRICE EXISTS
What we'd ask you first.
A quote given without these answers is a guess. These are the questions that actually move the number.
- 01How many listings, and who keeps them current?
- 02Where do leads arrive from today, and what does each one cost you?
- 03How many agents, and how are leads shared between them now?
- 04What is your follow-up rule — and is it actually followed?
- 05Do you want prices public, on request, or a mix?
AFTERWARDS
How we'd know it worked.
Agreed before the build starts, so there is something to judge it against other than whether it looks nice.
- Every incoming lead is assigned to a named agent within five minutes.
- No lead sits with no activity for more than forty-eight hours.
- Agents log outcomes on the day, not at the end of the week.
- Listing pages appear in Google results for the localities you care about.
BEFORE YOU START
Worth knowing.
A CRM only works if the team enters things into it. Half of this project's success is deciding how few fields an agent has to fill in after a call. Fewer is almost always better.
Websites and apps start at ₹20,000*. Final pricing depends on features and project scope. Third-party costs — cloud hosting, domains, external libraries, APIs, app-store fees and any other paid service — are billed separately and are not included.
KEEP LOOKING
Other example builds.
Mobile App
Delivery Tracking App
Driver app with live location, proof-of-delivery photos and an owner-side status board.
Read the case study First VersionBooking & Scheduling, Version One
Ships in weeks, not months: online booking, reminders and payments for a local service business.
Read the case study SaaS ProductSaaS Subscription Starter
Sign-up, workspaces, plans and recurring billing — the unglamorous half of a SaaS product, built once and properly.
Read the case studyWant this built for your business?
Tell us what you're thinking. We'll figure out the next step together.
Free 20-min idea call · No obligation