Two executives, one plot
Availability lives in a spreadsheet someone forgot to update, and the same unit is promised twice.
Holds lock the unit in the database, expire on their own, and the map updates for everyone at once.
For Indian real estate developers
Sell every unit once. Collect every rupee on time.
PROPCRMGO brings inventory with live layout maps, leads, site visits, quotations, bookings, payment schedules, collections and your channel partners into one system, with each company’s data kept apart by the database itself.
- Row-level security per company
- Maker-checker approvals
- Append-only audit trail
The problem
Property sales should not run on a shared spreadsheet
Availability in one sheet, prices in a chat group, receipts in an accounts file. The gaps between them are where double bookings, missed dues and commission disputes come from.
Price lists that drift
Rates change on WhatsApp, quotes are typed by hand and nobody knows which discount was approved.
Every price change has a reason and a history; quotations are built by the system and big discounts need an approver.
Schedules tracked by hand
Payment plans are rebuilt per buyer, receipts are numbered manually and dues surface too late.
Schedules always sum to the contract value, receipts are numbered without gaps and ageing is always current.
Partner payouts by argument
Two brokers claim the same buyer, and commission is worked out at the end of the quarter.
Referrals follow your attribution rules, disputes go to a person, and commission is earned as money comes in.
The product
From first enquiry to final partner payout
One system for sales, finance and your partners, so each team works from the same unit, the same price and the same ledger.
- Inventory with live layout mapsProjects, phases, blocks and units in one place, drawn on your own layout plan and updated live for everyone looking at it.
- Leads, pipeline and follow-upsCapture enquiries once, catch the duplicates and make sure every lead has an owner and a next step.
- Site visitsSchedule visits without double-booking your team, and keep the outcome on the lead.
- QuotationsQuotes built by the system from the unit, its charges and your project settings, not typed by hand.
- Bookings, cancellations and settlementOne active booking per unit, enforced by the database, with a second person confirming.
- Payment schedules and collectionsPayment plans that always add up, receipts that are never skipped, and a clear view of what is due.
- Bank reconciliationMatch bank credits to recorded payments without a spreadsheet in between.
- Online paymentsCollect through a payment gateway and record the money only once it is confirmed.
- Channel partner portalGive brokers their own sign-in to see what you allow, register referrals and follow their earnings.
- DocumentsTemplates with a review step, numbered documents and share links that expire.
- Project expensesBudgets per project, category and fiscal year, with spend tracked against them.
How it works
Four steps from spreadsheet to system
Set up your company
Create projects, phases and blocks, invite your team with the right roles, and import units from a CSV.
Put inventory on the map
Upload your layout, draw the plots, publish the map and decide what partners and the public may see.
Sell with guard rails
Capture and assign leads, schedule visits, hold a unit, quote it and send the booking for confirmation.
Collect and pay out
Record receipts, reconcile the bank, follow up on dues, and pay partner commission in approved batches.
Security and data isolation
Your data stays yours, enforced by the database
Isolation is not a filter in the screens. PostgreSQL itself refuses to show one company’s rows to another, and every sensitive change needs a second person.
Row-level security per company
Every company table has forced row-level security in PostgreSQL. Without a company and a known audience on the connection, the application sees and writes nothing.
Append-only audit trail
Sensitive actions write an audit entry in the same transaction. Audit tables reject updates and deletes, so the history cannot be edited afterwards.
Maker-checker approvals
Price changes beyond your limits, large discounts, booking confirmations, cancellations, refunds, waivers, expenses and payouts are decided by someone other than the person who asked.
Roles, scopes and MFA
Preset roles scoped to company, branch, project or team, with no way to grant more than you hold. Owners and finance roles must use two-factor sign-in.
Personal data masked by default
Phone numbers and emails are masked unless a role allows full view; unmasking an export asks for a fresh password and a reason.
Support access on your terms
Our support team sees only basic company details until your owner approves a time-boxed, read-only session. Every read is audited, and support never sees files, exports or contact details.
- MakerRequests a change with a reason
- CheckerA different person approves or declines
- SystemApplies it only if nothing changed meanwhile, and records it
See it with your own project
Tell us about your projects and how you sell today. We will walk you through PROPCRMGO and be straight about what fits and what is not built yet.