CRM for real estate: what an agency actually needs from one

A CRM for real estate is unusual among CRMs because the relationship is not one-to-one. A buyer is matched against many properties; a property is shown to many buyers; a vendor becomes a buyer eighteen months later. Software written for a straightforward sales pipeline handles the first of those and quietly loses the other two.

The other complication is timing. Property work happens in cars, at doorways and between viewings, and a system that requires sitting down to update it gets updated on Friday from memory — which is the same as not being updated.

What a CRM for real estate has to hold

• People, with their side of the transaction — buyer, vendor, landlord, tenant — and the fact that one person is often several of these over time.
• Requirements per buyer: budget, area, bedrooms, must-haves, and the things they said they would never accept but will.
• Properties, with status, price history and the vendor's expectations, which are usually the real constraint.
• The match between the two, because "who should see this property" is the question the business runs on.
• Every interaction with a date: call, viewing, offer, negotiation. Not summaries — the individual events.
• The pipeline stage per deal, from valuation through offer, sale agreed, and the long tail of the legal process where deals actually collapse.
• Next action per person, with a date. In a business of this rhythm, a CRM without next actions is an archive.
• Consent and marketing preferences, because you hold a great deal of personal data and will be asked to account for it.

Where you operate decides much of this. Data protection rules govern how long you keep buyer records and what consent you need to market to them; anti-money-laundering rules require identity checks and record retention for property transactions in most jurisdictions. Check your national requirements — they affect the fields you need and how long the record has to survive.

Making it get used

1. Decide the one thing that must be true after every interaction: a dated note and a next action. Everything else is optional detail.
2. Log from the phone, in the car, before the next viewing. A note written in ninety seconds beats a perfect record written never.
3. Keep requirements as short structured fields rather than prose, so matching is possible without reading forty profiles.
4. Review the pipeline weekly as a team, working from the oldest stalled deal rather than the newest lead.
5. Set a rule for dormant buyers — no contact in six months means a decision to re-engage or archive, not indefinite silence.
6. Record vendor expectations explicitly at valuation. Most difficult conversations later are about a number nobody wrote down.
7. Clean quarterly: duplicate people, properties sold long ago, buyers who bought elsewhere. A CRM that lies about volume gets ignored.

Generic CRM or property-specific

Property-specific systems earn their price on the things that are genuinely specific: feeding listings to portals, generating brochures, matching automatically against a stock list, and handling lettings with rent schedules and compliance dates. If you do lettings at any volume, you want one. If you are a small sales agency, a broker, or an independent doing a handful of transactions a month, a general CRM with a clear structure and a discipline about next actions gets you most of the value at a fraction of the cost and complexity.

Ettex CRM sits in that second category: contact profiles with phones, emails, addresses and custom fields — which is where budget, area and requirements live — groups and tags for buyer segments and property lists, notes and activity logging so calls and viewings sit on one screen, a visual pipeline for valuation through completion, change history showing who edited what and when, and shared address books so the whole office sees the same record rather than a version in one person's phone. Viewing feedback fits Ettex Forms; the agency agreement goes through Ettex Signature; and property documents and compliance certificates belong in Ettex Docs.

Said plainly: Ettex is not a property system. There is no portal feed to Rightmove, Zillow or their equivalents, no listings module, no automatic buyer-to-property matching, no brochure generation, no lettings rent schedules or compliance-date tracking, and no viewing calendar that syncs with a diary of keys. It is a general CRM you can shape to a small sales agency. Anything portal-driven or lettings-heavy needs a specialist product.

Sector tools are narrow by design. Database software for small business is the general alternative: your own tables, your own fields and no assumption about what you sell.

Why property CRMs fail

• Records updated at the end of the week, which turns the CRM into a diary of what someone remembers.
• Requirements written as prose, so nobody can answer "who wants a three-bed in this postcode".
• No next action, leaving buyers to go quiet until they buy from someone else.
• Contacts kept in personal phones, which walk out of the door when the negotiator does.
• Dormant buyers never archived, so the database looks large and performs badly.
• Consent not recorded, which becomes a real problem the first time someone asks why they are receiving your emails.

Two things decide whether any of this survives contact with a busy week. Lead tracking has to record the source of every enquiry, or the portal spend cannot be judged. And the underlying contact list template has to be agreed before import, because a database assembled from four agents’ phones with four different field habits is not searchable by anyone.

A CRM for real estate lives or dies on whether it is updated between viewings. Hold people, properties and the match; insist on a dated note and a next action; and buy a specialist system only when portals or lettings make you.