Pipedrive for real estate agencies

What is different in real estate sales

An estate agent sells twice on every property. First to the owner, to win the mandate against two or three competing agencies pitching valuation and fee. Then to the market, turning enquiries into viewings, viewings into offers, and an accepted offer into a completed transfer. The first sale takes days and is won on trust and valuation. The second takes months and is won on process and speed.

Volume is the other defining trait. A residential agent juggles dozens of live buyers against a handful of listings, and enquiries arrive around the clock from portals. The agent who calls back within ten minutes gets the viewing. The one who calls back tomorrow gets vaporised. No industry punishes slow follow-up harder.

The decision makers are emotional and private. Sellers anchor on the highest valuation they heard. Buyers fall in and out of love weekly. And between accepted offer and completion sits a fragile chain of financing, surveys and notaries where deals die through nobody's fault. The CRM has to keep that phase visible, because the fee only exists at completion.

An example real estate pipeline

We split brokerage into two pipelines. Mandates wins the stock. Transactions sells it.

A won mandate automatically opens the transaction deal, carrying the address and the agreed fee. Buyers enter as persons from portal enquiries, qualified in the Leads inbox before they touch any pipeline. Agencies doing lettings add a third pipeline from enquiry to signed lease. The underlying rule is the one from pipeline design: each distinct process gets its own pipeline, and nothing else does.

The fields and automations that matter

On the transaction deal: property address, asking price, fee percentage, buyer financing status, and target completion date. On the mandate deal: valuation given, competing agencies as a number, and source of the instruction. Buyer persons carry search criteria as three or four fields, budget, area, property type, so matching new stock to known buyers takes one filter instead of one memory. The restraint principles from custom fields that earn their place apply doubly in an industry famous for form fatigue.

Automations, in order of payback. Portal lead routing first: every enquiry creates a lead with an instant follow-up task, because response speed decides the viewing. Second, viewing feedback: a task the morning after every viewing to call the buyer and the seller, since sellers judge agents on feedback loops. Third, the completion chase: in the final stage, a weekly task to check financing, survey and notary progress. Wire the portal feeds through workflow automations or a middleware, and let no enquiry wait for a human to copy-paste it.

Commercial and new-build work bend the model without breaking it. Commercial brokerage runs longer cycles with fewer, larger deals, so it behaves like the professional services pattern with the fee still as deal value. New-build sales flips the direction entirely: the project is fixed, buyers are the pipeline, and one deal per reserved unit per buyer keeps absorption reporting honest. Both fit in the same account as extra pipelines, provided each keeps its own stages.

Common mistakes

The most common mistake is one pipeline where mandates and buyers collide. Winning an instruction and closing a sale are different processes with different clocks, and blending them makes conversion reporting useless.

The second is letting portal leads land in email. Every minute between enquiry and contact attempt costs viewings, and inboxes are where minutes go to die.

The third is dropping the deal after offer accepted. A third of accepted offers wobble before completion. The completion stage, with its weekly chase, is where an agent earns the fee twice.

The fourth is hoarding dead buyers. A buyer database full of people who bought elsewhere two years ago drowns the live ones. A quarterly purge, following our data hygiene routine, keeps matching sharp and GDPR happy.

Questions