How to choose estate agent prospecting software
Estate agent prospecting software helps a branch find vendor and landlord opportunities, run controlled campaigns, follow up responses and review what contributed to valuations and instructions. It is not the same as a CRM, a print shop or a general sales tool.
This is a ProspectOS guide. The first half is general evaluation advice for UK estate and letting agents. The second half explains how ProspectOS approaches the same points. It is not an independent review and it does not rank other products.
Decide what problem you are buying for
A useful first question is where instructions are currently lost.
If the gap is early research, you need property and landlord context in the postcodes you actually work. If the gap is inconsistent mailing, you need templates, approvals and a record of what was sent. If the gap is follow up, you need an owner, a stage and a next action after a reply. If the gap is reporting, you need costs and outcomes in the same place.
Do not buy a tool only because it uses the words canvassing, touting or automation. Ask what a user can do with one branch and one postcode on an ordinary Tuesday.
The CRM prospecting gap article explains why many CRMs start after an enquiry exists. Prospecting software should cover the work before that point, then hand a confirmed response to the system your team already uses for applicants, instructions and transactions.
Evaluation criteria
Use these questions with any supplier, including us.
Property data and signals. Which listing, ownership and market changes can the branch see? How current is the information? What should a negotiator verify before contact?
Patch control. Can activity be limited to the postcodes a branch is allowed to work? Can two branches keep audiences, templates and reporting apart?
Audience safety. How does the product avoid writing to your own listings, recent recipients and people who have asked you to stop?
Campaign control. Can a manager require review before a send? Can an automation be paused? Is there a send history that shows the template version?
Letters and postcards. Can the branch keep brand, wording and letter design consistent? Is there a difference between a manual send and an automated one?
Response handling. What happens after a QR scan, a form reply or a phone call? Does the record keep the property and campaign, or does the team retype it?
Reporting. Can you see campaign cost, booked valuations and instructions without treating a scan as revenue? Is attribution described as contribution rather than proof?
Lettings. Can landlord investigation, correspondence addresses and rental context be worked in the same system, or is the product sales only?
Data protection. Who is the controller for campaign data? How are objections recorded? Does the supplier give legal advice, or tools that support your own decisions?
Fit with the CRM. What is the handoff point? Where does a prospecting record stop and the CRM record begin?
Questions to ask in a demo
- 1Show one postcode we already work, not a national showcase.
- 2Show a property we should not contact, such as our own listing, and how the product blocks it.
- 3Show a campaign that waits for approval and a campaign that can proceed after safeguards.
- 4Show what a QR scan creates, and what it does not create.
- 5Show how a phone reply is logged against the same campaign.
- 6Show a report that separates scans, valuations and instructions.
- 7Show a landlord example if lettings matter to the branch.
- 8Show how a user is stopped after an objection.
If a demo cannot do those things with sample data, the product may be a mailing utility rather than a prospecting system.
How ProspectOS approaches the same points
The following is product explanation, not a claim that every agency needs the same setup.
Property intelligence. ProspectOS Map brings supported property and market information into a postcode scoped workspace so the team can filter signals, build shortlists and start a controlled action.
Controlled automations. Automations use supported property signals in the postcodes available to the branch. Eligible matches can enter a review queue or proceed automatically after branch safeguards are applied. Own listing checks, duplicate protection, spend controls and send history are part of that design.
Letters and postcards. Studio holds branded A4 letters, A5 postcards, automation templates and valuation packs, with branch branding and version history for what was sent.
Follow up. Pipeline is the daily working surface. A tagged map property, a landlord record, a campaign reply or a QR scan can land there as something to work. The team manages prospects, enquiries, valuations, follow ups and outcomes. A QR scan is engagement. An enquiry is a genuine inbound request. An instruction is recorded when the opportunity is won.
Reporting. Insights compares tracked costs, attributed fee value, campaign performance and postcode results. Attribution is a contribution model. It does not prove exclusive causation.
Lettings. Landlords is for ownership investigation, linked properties and moving a live landlord opportunity into Pipeline.
CRM fit. ProspectOS is built as the instruction acquisition layer before and around the first enquiry. It is not positioned as a replacement for the CRM that already runs applicants, listings and transactions.
Data protection. Customers remain responsible for the lawful basis, campaign content and objections. The direct mail and data page states that ProspectOS provides tools, workflows and audit records. It does not replace compliance judgement.
A Patch Walkthrough is the practical way to test these points on a postcode relevant to your agency. It is a guided session, not a ranking against other suppliers.
A practical branch workflow
- 1Write down the instruction problem you want the software to help with.
- 2List the postcodes, users and CRM you already have.
- 3Score each product against the criteria above using a demo, not a brochure.
- 4Agree the handoff into your CRM before you buy.
- 5Pilot one branch and one campaign type.
- 6Review scans, conversations, valuations and instructions separately after a defined period.
Common mistakes
- Buying a mailing tool and expecting it to run follow up.
- Buying a CRM add on and expecting it to investigate properties before an enquiry exists.
- Judging a product on template design alone.
- Accepting scan counts as commercial proof.
- Skipping own listing and suppression questions because the demo looked polished.
- Asking for a guaranteed instruction number.
Questions agents ask
Is prospecting software the same as a CRM? No. A CRM usually manages known contacts, applicants and live instructions. Prospecting software is for the work that happens before those records exist, and for connecting campaign activity to later outcomes.
Do we need automation on day one? Not always. Many branches start with map research, a small letter campaign and Pipeline follow up. Automation is useful when the same supported signal repeats and the branch can still review or pause it.
Can the same product cover sales and lettings? It can if landlord investigation, rental context and sales signals are both in scope. Ask to see both workflows in the demo.
What should we bring to a ProspectOS walkthrough? One branch, one priority postcode and one instruction growth objective. We will show a relevant sales or lettings path from property signal to next action.
The related ProspectOS workflow
Start with the ProspectOS features overview, then read the practical guide to estate agent prospecting if you need the method before the software.
Related articles:
Test the criteria on your own patch
Bring one branch, one priority postcode and the evaluation questions above. We will show the relevant ProspectOS workflow in a tailored Patch Walkthrough.
Book your Patch Walkthrough