A plot is sold the way a flat is sold — a call, a visit, a price, a booking. It is paid for the way land is paid for: a long schedule, often longer than a building’s, with the registry sitting at the far end of it.
Software written for apartments handles the first half and improvises the second. Here is what a land development company should ask for instead.
The price is per katha, not per square foot. Rates, discounts and commissions all have to follow the same unit, or every figure needs translating in someone’s head.
The schedule is longer, and so is the relationship. Three to six years of instalments is normal. In that time a customer changes their phone number, their address and sometimes their mind.
A plot can be shared. Two or three buyers on one plot is common, and each one wants their own statement.
The far end is the handover and the registry. Those are dates the customer asks about from the second year onwards, and the answer should not depend on who picks up the phone.
| Stage | What the system should do | The question to ask before you buy |
|---|---|---|
| Project and plots | Blocks, roads and plots with size, rate per katha and status | “Does the status change by itself when a deal moves, or by hand?” |
| Booking | Price, schedule and the money taken, on one record | “Can the same plot be booked twice?” |
| Instalments | Due dates, reminders before the date, part payments, advances | “Does the customer get a reminder before the due date, not after?” |
| Documents | Acknowledgements, receipts, statements and letters, numbered and never edited | “Can a receipt be quietly changed afterwards?” |
| The far end | Clearance, handover, the registry, and cancellations with refunds | “Who can cancel a sale, and what does cancelling touch?” |
Most land development companies run instalments on a register — a book, or a spreadsheet that behaves like one. It works, for a while, because one person holds it all in their head.
The trouble starts at the edges. Someone pays in two parts. Someone pays ahead. A cheque comes back. A customer sells their share to a relative. Each of these is a correction in the register, and after a few hundred corrections the register and the bank stop agreeing.
A system solves it a different way: the schedule is on the sale, every payment is an event against it, and nothing is ever rubbed out. A correction is a new line that says what changed and who changed it.
A payment acknowledgement on their own phone within a minute of paying, which they confirm — “yes, this is my payment” — or dispute. A statement they can open any time. Reminders before the due date. Letters that carry the company’s name and a number, kept exactly as they were issued.
That is not a courtesy. It is how a company stops arguing about money years later.
Every project on one page: plots sold, plots free, money scheduled, money collected, money overdue. Any figure opens to the plots and the customers behind it.
Cancellations, refunds and discounts are decisions. They should need the owner’s approval, and the record should show who asked and who allowed it.
Sofia Estate CRM is CRM + ERP for real estate and land development in one system. Projects, plots and units with their own rates — per square foot, or per katha for land — sit on the same record as the sale, the schedule, the collection and the accounts.
Yes. A unit’s rate can be a price, a rate per square foot, or a rate per katha, and commission follows the same unit.
Yes, with a statement each.
The sale goes through your company’s own steps — reminders, letters, then a cancellation with a refund if that is what you decide. Nothing happens automatically that you have not allowed.
No. The record stays open until the last instalment, and so does the customer’s statement.
Yes. Book a live demo and bring one real project with you.