Skip to main content
GullySystem
Requirements checklist

What to ask for when choosing software for real estate developers.

A checklist built from how real estate developers work, to print or save as a PDF and bring to any supplier meeting.

Share your requirements

What the software should cover

Tick each one that matters to your business.

  • Enquiries and site visits
  • Live project inventory with holds
  • Cost sheets and bookings
  • Payment plans and slab demands
  • Loan tranches and receipts
  • Channel partner registrations and brokerage
  • Booking documents

Roles that need their own access

Who logs in, and what each person may see or change.

  • For owners and directors
  • For sales heads
  • For salespeople
  • For CRM and accounts executives

Reports to ask for

Ask to see each one with your own sample data.

  • Enquiries by source and project, and how many reached a site visit
  • Site visits by week, with visits that got no follow-up
  • Inventory by project: available, on hold, booked and sold
  • Bookings by salesperson and channel partner
  • Instalments due, received and overdue
  • Channel partner commission due and paid

Systems it may need to connect to

Note which ones you already run.

  • WhatsApp
  • Email
  • SMS
  • Property portal lead feeds
  • Google Calendar
  • Accounting package

Questions for any vendor

Put these to every supplier you are comparing.

  • Will it fit how our projects sell?
  • Is it a CRM for builders or for agents?
  • Does it work as a site visit app on a phone?
  • How does it settle two partners claiming the same buyer?
  • Does it make us compliant with property regulation?
  • Can it be connected to our accounting package?
  • Can existing leads and bookings be brought across?
  • Who owns the data?
  • What does it cost?
  • Why not use a large CRM such as Salesforce?
  • How soon can the sales team work from it?
  • What should the developer provide up front?

Where the work usually breaks today

Circle the ones you recognise. They set the order of the project.

  • Two executives block the same flat
  • Slab demands go out late
  • Channel partners argue about brokerage
  • A buyer asks what they have paid
  • Cancellations and transfers leave loose ends

Check the difficult cases before choosing software.

Use examples from your own records to test the workflows that matter in your business.

Loan tranches and receipts

Can the same receipt be allocated without counting the money twice?

Take an unallocated amount in “Loan tranches and receipts” and apply it to the intended balance. Review the remaining amount and the original receipt reference together.

Background reading: ERPNext: payment allocation

Booking documents

What becomes available when a booking is moved or cancelled?

Use “Booking documents” to move a booking, then cancel a second example. Check the released slot, the person or resource still assigned, and any amount left to settle before accepting the revised schedule.

Background reading: ERPNext: appointment records

Prefer to talk it through? See the real estate developers page.