CRM for Estate Agents: Leads, Viewings, Follow-Up
By CodexierPublished 5 min read
An estate agent's transaction system handles the deal from listing to closing, and does it well. What it does not do is remember that the couple who requested a valuation in March said they would sell after the summer, or that a viewer at last year's bidding lost by a small margin and is still looking. That memory is what a CRM is for, and for an agency it is where the next year's listings come from.
Leads from valuations and viewings
Two sources feed almost all future business: people who asked what their home is worth, and people who came to viewings. Both arrive through the website, the portals and the transaction system, and both are usually lost within weeks because they sit in an inbox. The CRM's first job is to receive them automatically, with the source, the object type and the stated timeline, and to create a follow-up task that someone will see.
Tracking objects and buyers
The CRM should hold a light picture of each object and each buyer, enough to match them, without duplicating the transaction record.
| Record | Lives in the CRM | Stays in the transaction system |
|---|---|---|
| Object | Address, type, price range, status, agent | Contract, bidding journal, documents |
| Buyer | Search profile, budget, area, viewings attended, bids lost | Identity checks, bid history as legally required |
| Seller lead | Valuation date, stated timing, decision status, next contact | Nothing until listing |
| Past client | Deal date, object, likely next move, referral consent | The closed transaction |
Match buyers to new objects by profile the day a listing is created. That match is the highest-value automation an agency can run.
Timely follow-up with past clients
A past client sells again after a number of years, refers friends in between and expects to be remembered. The CRM makes that routine rather than personal heroics.
- Anniversary tasks: one year after closing, a call to ask how the home turned out; a few years after, a market update for the area.
- Life-event triggers the client shared: growing family, retirement, a second home. Recorded at closing, surfaced on schedule.
- Referral tracking: who recommended whom, so thanks are sent and the best sources are known.
- Newsletters only with consent and a working unsubscribe, since past clients are consumers under the marketing rules.
Portal and mäklarsystem integration
Transaction system to CRM
Objects, viewings and closed deals flow into the CRM on creation and status change. Most Swedish systems have an API or export; the direction is one way.
Website and portals to CRM
Valuation forms, viewing registrations and portal enquiries create leads with source and timestamp, deduplicated against existing contacts.
CRM to calendar and phone
Follow-up tasks appear in the agent's calendar and call list. A task nobody sees is not a task.
The integration is usually the larger part of a CRM implementation for an agency, and it is what makes the difference between a CRM that is used and one that is a second place to type. How integration work is priced is explained in our guide to system integration cost.
GDPR for buyer lists
Buyer and viewer lists are personal data, and estate agents already keep records under the Estate Agents Act for the transaction itself. The CRM holds a different set with a different purpose, and needs its own basis and retention.
- State the purpose at collection: matching to future objects and follow-up on your enquiry. Legitimate interest usually covers it; marketing mail needs consent.
- Set retention per record type: a viewer with no activity for a defined period is deleted; a past client is kept as long as the relationship is real.
- Give agents a simple way to honour opt-outs and deletion requests, and log that they were done.
- Keep the legally required bidding and transaction records in the transaction system, not the CRM, so retention rules do not collide.
If you already have a CRM and are unsure whether it is set up this way, a CRM setup audit reviews the data model, the integrations and the GDPR side in a week. Both services are fixed prices on the pricing page.
When you do not need a separate CRM
If your transaction system already has lead and follow-up features that your agents actually use, extend that rather than adding a system. If you are a single agent with a manageable client list, a disciplined calendar and a spreadsheet can carry you for a while. A separate CRM pays when several agents share leads, when valuation leads are being lost, or when past clients are not hearing from you. A 15-minute call with your current lead flow described is enough to say which applies.
Frequently asked questions
Which CRM suits an estate agency?
One that integrates with your transaction system and website, has task and calendar features agents will use on a phone, and lets you define retention rules. HubSpot and Pipedrive both work with the right setup; the choice depends less on the product than on the integration and the follow-up routine around it.
Can we email past viewers about new objects?
Matching a viewer's stated search profile to a new object and contacting them about it is follow-up on their enquiry, which legitimate interest generally supports if they were told and can opt out. General newsletters to consumers need consent. Record which basis applies to each contact.
How long does the setup take?
A CRM with website and transaction-system integration, follow-up routines and GDPR settings is typically a few weeks, most of it integration and data clean-up. Agents should be using it for real leads within the first week, with the rest added around them.
Losing valuation leads between the inbox and the calendar?
Bring your transaction system, website and current lead routine to a short call. We tell you what a CRM would need to integrate with, how follow-up would work, and what a fixed-price implementation would cost.
Book a free 15-minute call