Skip to content

Features

Everything a developer’s sales and finance teams share

Each module below is built and working today. Where something is not built yet, we say so under the module.

Inventory with live layout maps

Projects, phases, blocks and units in one place, drawn on your own layout plan and updated live for everyone looking at it.

  • Units follow a guarded status flow, so a plot cannot jump from available to booked without the steps in between.
  • Upload your layout as an SVG, draw each plot on it and publish the map after a review.
  • Soft and hard holds expire on their own; caps per person stop one executive from parking half a project.
  • List price changes carry a reason, keep their history and go to approval when they exceed your limits.
  • Import units from a CSV with a dry run that shows every error before anything is created.
  • Choose exactly which fields partners and the public map may see; nothing is shown unless you tick it.

Limits today: Map vertex editing and undo are not built yet.

Leads, pipeline and follow-ups

Capture enquiries once, catch the duplicates and make sure every lead has an owner and a next step.

  • Phone numbers are normalised to one format, so the same buyer from two portals becomes one review, not two leads.
  • Duplicate review and merge keeps every source touch and the full history.
  • Assignment rules pick the next owner by round robin; scores show their factors and never assign on their own.
  • An activity timeline, tasks and follow-ups that remind once and escalate to a manager when overdue.
  • CSV import with a dry run, and reports where every number drills down to its leads.

Limits today: Bulk reassignment and booking KPIs in lead reports are not built yet.

Site visits

Schedule visits without double-booking your team, and keep the outcome on the lead.

  • A host cannot have two live visits at the same time unless a manager overrides with a reason.
  • Reschedules keep the old slot in the history; cancellations and no-shows leave a follow-up.
  • Check-in records a location only when the buyer has consented to it.
  • Each team member can subscribe to their own visit calendar feed.

Quotations

Quotes built by the system from the unit, its charges and your project settings, not typed by hand.

  • Location charges and other project charges come from versioned charge settings.
  • A discount above the executive’s limit goes to an approver who is not the author.
  • Each quotation freezes its lines, so a later price change never rewrites a quote already given.

Limits today: Quote expiry and sending quotes to buyers are not built yet.

Bookings, cancellations and settlement

One active booking per unit, enforced by the database, with a second person confirming.

  • A booking request is confirmed by someone other than the requester, once token money is received.
  • Confirmation writes the payment schedule and allocates the token money in the same step.
  • Cancellations are authorised by another person; settlement keeps forfeiture and deductions, and refunds can be paid in tranches.
  • Milestones (agreement issued and signed, registration, handover) move booking and unit together after their checklist.

Payment schedules and collections

Payment plans that always add up, receipts that are never skipped, and a clear view of what is due.

  • Plan templates publish only when their shares make 100%, and every schedule sums exactly to the contract value.
  • Money is allocated to arrears first; reallocations are exact reversals with a reason.
  • Receipts are numbered per fiscal year without gaps; cheques clear or bounce after deposit.
  • Late fees follow versioned rules; waivers are decided by someone other than the requester.
  • A collections view with ageing, a forecast and a follow-up queue that respects each buyer’s consent.

Bank reconciliation

Match bank credits to recorded payments without a spreadsheet in between.

  • Credits are matched automatically on reference, amount and a three-day window.
  • Split credits and anything unmatched are handled by hand, with the decision recorded.

Online payments

Collect through a payment gateway and record the money only once it is confirmed.

  • Payment orders through Razorpay; signed webhooks are stored once and captures confirmed before money is recorded.

Limits today: Razorpay is the only gateway today; there is no checkout widget or refunds through the gateway yet.

Channel partner portal

Give brokers their own sign-in to see what you allow, register referrals and follow their earnings.

  • Partners are onboarded with a KYC step, assigned to projects and can be suspended instantly.
  • Referrals use your versioned attribution rules; conflicts open a dispute for a person to decide.
  • Booking requests from partners carry no price; your team quotes and confirms.
  • Commissions follow the winning rule, frozen at booking, and are earned on collection or milestones.
  • Payouts apply your own TDS and GST settings; each batch is built, approved and paid by different people.

Limits today: Partner PAN and bank details are not captured yet.

Documents

Templates with a review step, numbered documents and share links that expire.

  • Templates move through draft, review and approval before they can be used.
  • Issued documents are numbered per template and fiscal year and never change after issue.
  • Share links expire, cap their downloads and log every access.

Limits today: Booking letters are the first document type; template wording needs your legal review.

Project expenses

Budgets per project, category and fiscal year, with spend tracked against them.

  • Expenses are drafted, decided by another person and then marked paid; only drafts can change.

Across every module

Security, isolation and approvals

The same rules apply everywhere. See also what we have not built yet.

  • 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.

How an approval moves
  1. MakerRequests a change with a reason
  2. CheckerA different person approves or declines
  3. 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.