Tutorial

Part of a tutorial: Step 6 of 9 in From inquiry to match

Open in tutorial
In this section · 3 articles

Record a client requirement

Write down what a buyer or tenant is looking for: purpose, property type, size, budget and location. Property CRM then lists the properties that match.

Applies to
Property CRM 5.0 and later
Who can do this
Team member
Permission
feature.pcrm.requirement.create
Where
Property CRM › Requirements
On this page

Before you start

  • You need feature.pcrm.requirement.create. Property CRM Admin, Manager and Agent have it.
  • Work in your business's workspace, not All Workspaces. See Switch workspace.
  • The buyer must be a client with the Buyer role. If they aren't in Laramin yet, you can create them from the form.
  • If the requirement came from an inquiry, convert the inquiry instead: Laramin can create the requirement from it. See Work through new inquiries.

Steps

The form has two steps. The required fields on the first step are enough to save; select Save from either step.

Buyer & Intent

  1. In the Property CRM sidebar, open Requirements. In the Platform Administration sidebar, it's Property CRM › Requirements.

  2. Select Create.

    The Create Requirements form on the Buyer & Intent step, with Title, Purpose Buying, Priority High and Status Active filled in, and the empty Buyer field and its New buyer (+) button highlighted.
  3. In Buyer, choose the client. If they're new, select New buyer, enter their Full name and Mobile, and select Create.

  4. Enter a Title, for example "2 BHK to rent near the station".

  5. Choose the Purpose: Buying, Rent, Lease or Joint Venture.

  6. Set the Priority: Low, Medium or High. It starts at Medium.

  7. Leave Status at Active. Only active requirements are matched.

  8. Optional: choose the Source, and check Client From, which is Direct Client unless the buyer came through someone else.

Criteria & Budget

  1. Choose the Category, then the Property Type. Both are required.

    The requirement form on the Criteria & Budget step, with Residential, Apartment, 2 BHK and 3 BHK, a ₹70–80 lakh budget, 1,000–1,200 sq.ft, a Bengaluru location and notes filled in.
  2. For homes, tick each BHK the buyer would accept.

  3. Enter Budget (min) and Budget (max). The maximum can't be lower than the minimum.

  4. Enter Area (min, sq.ft) and Area (max, sq.ft) if size matters.

  5. Enter where they want to be: State, City, Area / Locality and Pincode.

  6. Add any Notes, such as a preferred floor.

  7. Select Save.

What happens next

The requirement gets a code, such as REQ-000031. Open it to see its Matches: the available properties with the same purpose and category, best first.

MatchScore
Strong75 or more out of 100
Good50 to 74
FairBelow 50

The score weighs budget, city, property type, BHK, area and locality. The chips on each match say what fits, for example Within budget or Locality. Select Find More Matches to recalculate the list and jump to it, for example after you add new properties.

From a match, select Schedule visit to book a viewing. This needs the Activities add-on and feature.pcrm.requirement.site_visit.

The Site visit dialog on Book a viewing, with the option to record one that happened, the Property PROP-000018, an empty Date and time field, a Note box and the Save button.

An active requirement that hasn't changed for a while is flagged in the Requirements list. The number of days is Requirement Stale After (days) in Property CRM settings.