The CRM that knows a plot can only be sold once

PropX is a real estate CRM built by Business Compose for builders, developers and brokerages. It holds the four things a property business actually runs on — the lead pipeline, the unit inventory, the site visit calendar and the booking ledger — in one workspace, with a WhatsApp inbox and a workflow builder wired into all of them. It is our own product, so we configure it around your projects, your sales stages and your team structure rather than asking you to change how you sell to fit the software.

Generic CRMs model a deal as a single amount with a close date. Real estate does not work that way. A property deal is attached to a specific unit in a specific tower or layout, that unit has its own lifecycle (available, temporarily held, booked, sold, registered), and two salespeople must never sell it twice. A generic CRM has no concept of inventory, so builders end up running the units in a parallel spreadsheet — and that spreadsheet, not the CRM, becomes the real source of truth. PropX makes inventory a first-class object: a booking moves the actual unit, holds expire on a timer, and the pipeline and the stock ledger can never disagree. We are also a certified Zoho partner, so if Zoho genuinely is the better fit for your business we will tell you and implement that instead.

Both, and they are modelled differently because they sell differently. Apartment projects are structured as towers, floors and units, with configuration and carpet or built-up area on each unit. Plot layouts are structured as sections and plot numbers with individual dimensions and square footage, sitting on an interactive master plan you can click. In the same workspace you can run an apartment project in Chennai and a plot layout in Trichy, each with its own pricing logic, and still see one consolidated portfolio value across all of them.

Yes. Leads come in by CSV import, and units can be imported per project rather than typed in one by one, which matters when a layout has several hundred plots. We handle the migration as part of implementation: we map your existing columns to PropX fields, clean the duplicates, preserve the history you care about, and reconcile the unit list against whatever your sales team has been maintaining in Excel. Live lead sources — your website forms, Meta Ads lead forms, portal feeds and Google Sheets — are connected as ongoing integrations so nothing is ever re-keyed by hand.

It runs on the official WhatsApp Business API, not an unofficial automation layer that risks getting your number banned. That means approved message templates, a real shared team inbox where conversations are assigned, tagged and resolved, and the 24-hour customer service window enforced properly — the app tells you when the free-text window has closed and requires an approved template to re-open the conversation. Every message is attached to the lead record, so a salesperson picking up someone else’s conversation sees the entire history including which project the buyer asked about.

It is a visual builder — you drag nodes onto a canvas and connect them, no code. Workflows start from a trigger (a lead is created, a Google Sheet row arrives, a stage changes, or a manual run) and then chain steps: send a WhatsApp template, send project information or a specific unit’s details, wait for the buyer to reply, delay by a set time or wait until a date, branch on a condition, assign an agent, update the lead’s stage or tags, require an approval with a timeout, or notify an agent internally. Typical uses are instant response to a new portal lead, round-robin assignment, site visit reminders, and discount approvals that need a manager’s sign-off. Workflows are versioned and can be published, paused or archived, so you can change automation safely on a live pipeline.

A typical first go-live is four to eight weeks. Roughly two weeks to configure your projects, unit structures, site plans, sales stages and user roles; a week or two for data migration and integrations; then a supervised period where your sales team runs live on it with us alongside them. Complexity is driven mostly by inventory — a single apartment tower is quick, six layouts with several hundred plots and existing part-paid bookings takes longer to reconcile. Multi-project rollouts are usually phased one project at a time rather than switched over all at once.

That is the point of it. Sales stages, lead sources, unit statuses, qualification fields, WhatsApp templates, approval rules, agent permissions and dashboard metrics are all configured to your business during implementation. Because PropX is our own product rather than something we resell, we can also build genuinely bespoke pieces — a pricing model specific to how you quote, an integration with the accounting or ERP system you already run, a channel-partner portal, or a report your management committee asks for in a particular shape.

Each business gets its own isolated workspace. Inside it, access is role-based: a sales executive sees the leads assigned to them, a sales manager sees the team’s pipeline and approvals, and an administrator controls projects, pricing, users and integrations. Actions on units and bookings are recorded, so you can see who moved a unit to sold and when. Data is hosted in the cloud with encryption in transit and at rest, backed up, and exportable — you can pull your leads, bookings and unit data out at any time, and it stays yours.

Pricing depends on the number of projects and units you are running, how many sales users need access, which integrations you need, and how much bespoke work sits on top of the standard configuration. WhatsApp messaging is billed by Meta on a per-conversation basis and is passed through separately. Send us your project list and team size and we will come back with a fixed implementation scope and a clear monthly figure rather than a range that changes later.