Skip to content
GullySales

Property consultants · Lead scoring

Your sales team has to call one enquiry before another, and needs a reason for the order.

Lead scoring ranks enquiries using evidence about buyer fit and buying activity, so your team has a reason for its calling priority. GullySales builds the scoring rules from your won and lost records, tests them against past orders, and configures them in your existing CRM or shared sheet.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Realistic editorial illustration of property management companies at work in the United States

Start with the buying decision

Which record or handover breaks between the enquiry and its outcome?

Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief.

Your team approves the scope and any commitments to buyers. GullySales does not assume authority over pricing, staffing, or delivery promises unless a specific responsibility is agreed in writing.

The context for Property consultants

Start with the decisions in your own enquiry records.

Trace a real enquiry across the people and systems involved. Record missing information, duplicate work, and the decision that is still waiting for an owner.

How people choose in this industry

Buyers choose a consultant when the decision feels too large to make from brochures. They look for someone with no stake in a single project, and the first question is who pays the consultant. A consultant who answers that on the first page is easier to trust than one who leaves a builder commission unmentioned.

They compare consultants by how well the first conversation explains their own situation back to them: budget, family stage, commute, school, and loan limit. A consultant who can narrow a long list to a clear shortlist, and say why a popular project is not right for this buyer, is remembered.

Sellers and investors come by referral and by search for the locality. Property law, registration and tax rules differ by state and change, so check what you may advise on with your own adviser and send buyers to a lawyer or chartered accountant for those parts.

The decision before implementation

Define the process and access permissions before changing software settings or adding automation.

Existing industry priorities to review

  • Project shortlisting for new launches
  • Resale flat evaluation
  • Locality comparison for families moving cities
  • Investment property guidance for known buyers
  • NRI property purchase support

These describe the industry's wider priorities. The written scope identifies which this service will address.

Industry application review

Test the service against a problem in your own records.

These review scenarios connect the industry context to a possible output and a checkable next step. They are scope questions, not client results or a promise that every industry problem belongs in this engagement.

Our advice is hard to see before someone pays

A buyer cannot judge us from a profile. We have no sample of how we compare projects or what a shortlist looks like.

Confirm the scope first

Check whether this issue belongs in the lead scoring engagement or requires different work. The industry problem alone does not establish that this service will solve it.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Record the scope decision and its reason. If the issue is outside this engagement, identify the responsible team or the separate work required.

Our locality knowledge is not on any page

We know the roads, water, builders' track records and resale gaps, but a buyer cannot see it before the call.

Confirm the scope first

Check whether this issue belongs in the lead scoring engagement or requires different work. The industry problem alone does not establish that this service will solve it.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Record the scope decision and its reason. If the issue is outside this engagement, identify the responsible team or the separate work required.

The problem

What lead scoring is meant to address.

  • “Different calling priorities”

    Each representative chooses the next call differently. A buyer asking for a distributor quotation waits while someone clears enquiries that are easier to answer.

  • “Unexplained scores”

    The CRM displays a number, but nobody can explain its calculation. Without a link to actual orders, the team has little reason to trust it.

  • “Clicks mistaken for buying intent”

    Repeated visits push an enquiry upwards even when the requested product is unavailable or the delivery location is outside your service area. Activity hides the poor fit.

  • “Good buyers marked down”

    A rule borrowed from another market deducts points for a Gmail address. Your own dealer enquiries may show that owners use personal email accounts for substantial purchases.

Who it is for

Check your operating model against the scope.

  • Manufacturers and dealers handling enquiries with very different order quantities
  • B2B sales teams receiving enquiries through IndiaMART, JustDial, website forms, and WhatsApp
  • Sales heads whose representatives use different rules for calling priority
  • Interior design firms or retailers separating serious project enquiries from early browsing
  • Owners with recorded won and lost enquiries, but an unexplained or unused CRM score

Before you decide

When this may not be the right fit.

  • Your enquiries have no reliable outcomes recorded. Record those first; scoring cannot replace missing evidence.
  • One person reads every enquiry promptly and already knows which needs attention. Another field may add no useful decision.
  • Enquiries remain scattered across personal phones and inboxes. Central capture is separate work that comes before scoring.

Choose the right scope

Start with the work your business needs.

  1. Existing score repair

    For a CRM score nobody trusts, compare its current rules with won and lost enquiries. Replace unsupported weights and show the team why the revised ranking differs.

  2. Mixed-source enquiry ranking

    For enquiries arriving from marketplaces and your own channels, use common fit criteria without assuming one source always produces better buyers. Source remains a signal to test against orders.

  3. High-variation order enquiries

    For dealers or manufacturers receiving small requests alongside bulk requirements, test quantity and product fit against outcomes. Keep order potential separate from evidence that the buyer is ready to proceed.

  4. Quiet-buyer priority review

    For suitable enquiries that lose priority as activity fades, distinguish buyer fit from recent engagement. Your team can see why an old quotation still deserves a call without treating silence as fresh intent.

What we do

Agree the outputs before work begins.

These are the lead scoring deliverables available for property consultants. Your written scope identifies the included work and responsibilities.

  1. Won and lost review

    A comparison of historical enquiries and outcomes identifies possible scoring signals. Your sales head checks the findings against the underlying records, including missing results and lost reasons.

  2. Fit criteria sheet

    Written criteria cover relevant buyer details, such as business type, buying role, product requirement, location, and quantity. Each proposed rule has a reason your sales head can question before approval.

  3. Engagement criteria sheet

    A separate set of points covers actions your systems actually record, such as a WhatsApp reply or quotation response. The sheet identifies the source of each signal rather than assuming tracking exists.

  4. Deductions and fading rules

    Documented deductions address unsuitable enquiries, while fading rules reduce activity points as interest goes quiet. Review examples show how an unreachable contact differs from a suitable buyer awaiting approval.

  5. Score bands and handover rule

    Defined bands explain calling priority and the threshold for sales attention. The handover rule states the receiving role and prevents the same threshold from triggering repeated handovers.

  6. Historical test results

    The draft model is applied to past enquiries, with orders compared across score bands. Your sales head reviews missed buyers and high-scoring losses before approving the model.

  7. CRM or sheet configuration

    Approved rules are built in your existing system where its functions allow, including Zoho, HubSpot, LeadSquared, or a shared sheet. Sample records let your team check the calculation and visible reasons.

  8. Representative briefing and override record

    Your team receives guidance on reading bands and overruling a misleading score. Recorded reasons for overrides give the sales head evidence for later changes.

How the result is measured

  • Share of incoming enquiries with enough information to score
  • Recorded engagement actions, reported separately from qualified opportunities
  • Reply time for priority enquiries against the pre-work baseline
  • Qualified opportunities and completed orders by score band
  • Won enquiries that received low scores
  • Representative overrides and their recorded reasons

Recorded as a baseline before work starts, so every later report has an honest comparison.

Industry baseline

Keep the industry's wider measures beside the service measures.

Use the existing baseline to understand the context. These figures are not all targets for this engagement, and a change must not be attributed to the service without evidence.

  • Consultation requests by page and source
  • Share of requests that become paid engagements
  • Repeat contacts during a long search
  • Clients who book through your advice
  • Reviews and referrals after possession
  • Time from first call to decision

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

AI lead qualification and scoring
Choose AI lead qualification and scoring when enquiries arrive in free text and need reading before they can be ranked, with human review of disputed scores. Choose lead scoring when your enquiries already carry clear fields and your team wants plain rules it can read and challenge.
Lead qualification
Choose lead qualification when salespeople ask the wrong questions on calls, so enquiries move forward without a real need being established. Choose lead scoring when the questions are sound but the team has no reason for calling one enquiry before another.
Lead routing and assignment
Choose lead routing and assignment when good enquiries reach the wrong salesperson or sit unclaimed while someone is away. Choose lead scoring when every enquiry reaches a person promptly but that person cannot tell which one deserves the first call.

A sample of the output

A score rule sheet shows what adds to a score, what takes away, and why.

This sheet lists each signal the score reads, whether it raises or lowers priority, and the past records that support it. Read across a row to see the evidence behind one rule, then challenge any rule you disagree with.

Illustrative example, not client data. Yours is built from your own records.
SignalEffect on scoreEvidence from past recordsFading rule
Buyer is a dealer or contractorRaises priorityPast orders came mostly from trade buyers, not walk-in householdsDoes not fade
Enquiry names a model and a delivery siteRaises priorityWon deals nearly always began with a specific model and siteDoes not fade
Asked for a catalogue onlyNeutralCatalogue requests turned into orders and lost deals in similar measureDoes not fade
Opened the quotation and replied with a questionRaises priorityReplies after a quotation sat close to confirmed ordersFades when buyer goes silent
Asked for a price below the cost of materialsLowers priorityThese enquiries ended as lost deals with no counter-offerDoes not fade
No reply after two follow-upsLowers prioritySilent buyers rarely returned in the won and lost reviewRestores when buyer writes again

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

Won and lost records with outcomes
The rules are built from what actually happened, so each past enquiry needs a recorded result, won or lost. Rough notes are acceptable if the outcome is clear. Without outcomes, any score would be guesswork and the work pauses until they are recorded.
Read access to the CRM or sheet
We need to see the fields your team fills in, because a rule can only use information you actually hold. A read-only export is enough to test rules. Configuration needs edit rights, and without them we deliver the rules as a document.
A named owner of the score
Someone must decide when a rule changes and answer when a salesperson disputes a result. A sales manager fits well. Without an owner, the score drifts away from how the team actually sells and loses the trust of the people using it.
Agreement on what counts as a win
Teams differ on whether a win is a confirmed order, a paid advance or a delivered job. Choose one definition before testing starts. A mixed definition makes the test results unreadable and sends the review back to the beginning.
Time from the callers
Representatives who make the first calls should read the draft criteria and say where they look wrong. Their view catches rules that fit the records but not the buyers. If they cannot take part, the handover will meet resistance.

Marketing and sales together

Your sales head receives a ranked enquiry with reasons to act.

The handover record contains the score band, its supporting reasons, and the action that triggered attention. The sales head uses it to set calling priority; the representative then records the qualification result or explains an override. Marketing can compare sources against qualified opportunities and orders, rather than claiming success from clicks alone.

Decisions to make before the work starts

  1. Outcome quality

    Incomplete results or inconsistent lost reasons weaken historical testing. Limited preparation of scoring fields is included as agreed; wider cleansing, deduplication, or migration needs a separate scope.

  2. System limits

    CRM functions and available activity records determine what can be calculated automatically. New integrations, tracking connections, or broader CRM implementation are separate work, with any requirements identified before approval.

  3. Model maintenance

    A new product range or service area can change what counts as a suitable enquiry. The written scope states which outcome reviews and rule revisions are included; ongoing CRM administration is not assumed.

How it works

How lead scoring runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Record selection

    You share historical enquiries and outcomes. We agree which records are usable and identify gaps that would make the comparison misleading.

  2. 2

    Criteria approval

    GullySales proposes fit points, engagement points, and deductions. Your sales head approves the business meaning of each rule before configuration.

  3. 3

    Historical test review

    We score past enquiries and examine where the ranking disagrees with orders. The sales head decides which rules need revision and approves the score bands.

  4. 4

    Configuration acceptance

    The approved model moves into your CRM or sheet. Your team checks sample calculations, visible reasons, and the threshold behaviour before using it for calling priority.

  5. 5

    Sales handover

    Representatives receive the band definitions and override instructions. The person responsible for sales accepts how priority enquiries will reach the calling list.

  6. 6

    Outcome review

    New wins, losses, and overrides are compared with their earlier scores. Proposed changes return to your sales head for approval rather than silently changing calling priorities.

Approval and acceptance

Use an observable check before accepting an output.

These are proposed review checks for the named outputs. Agree the final conditions in the written scope, then record any missing requirement before accepting the handover.

  • Won and lost review

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Fit criteria sheet

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Engagement criteria sheet

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Deductions and fading rules

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Score bands and handover rule

    Walk the selected record through the proposed steps. Identify who acts at each handover, what information they receive, and how an exception is assigned without inventing a missing step.

  • Historical test results

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • CRM or sheet configuration

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • Representative briefing and override record

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How is lead scoring scoped for property consultants?
Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief. Define the process and access permissions before changing software settings or adding automation.
How much historical data do you need?
There is no fixed record count that makes a model reliable. We need enough completed enquiries to compare buyers who ordered with those who did not, using fields your team actually records. An export is enough for the initial review; missing outcomes may mean record repair comes first.
Does this include AI scoring, qualification calls, or lead assignment?
No. This scope establishes the scoring criteria and implements the agreed ranking rules. AI interpretation of incoming messages, qualification conversations, and territory or workload-based assignment are separate services.
Will low-scoring enquiries be ignored?
No. A low score changes priority, not the obligation to respond. Representatives should overrule it when a conversation reveals stronger buying intent and record the reason so the model can be reviewed.
Can you score WhatsApp replies and website visits?
Only when your systems record those actions and connect them to the right enquiry. We check signal availability before including it, rather than treating every click as a buying decision. Your own adviser must review the proposed data use and any consent or privacy requirements; regulated firms also need their compliance review.
How will we know whether scoring is useful?
Compare qualified opportunities and completed orders across bands, not just the number of enquiries scored. We record a baseline before work starts, including enquiries by source, reply time, conversion, and cost per order where records support it. Reporting frequency and the review period are agreed in writing before work starts.

Continue your review

Compare the service scope and the related work.

The scope, responsibilities, fee, reporting frequency, and term are agreed in writing after the requirements brief and conversation. Tell us what you need.

Your brief

Tell us what you need, and we will read it before we call.

Eight short steps about your business, what you want and who decides. Most questions are a tap, and you can skip any you would rather answer on the call.