Devlly

get in touch

Devlly — a software studio. We automate business: from a Telegram bot to a full CRM/ERP system.

Get updates

A CRM for a real estate agency: what to take into account

A realtor is a person who simultaneously holds forty properties in their head, thirty buyers, and the fact that the owner of the flat downtown doesn’t pick up the phone before eleven. When an agency grows from three agents to fifteen, that head stops scaling: properties get duplicated, clients vanish, two agents show up for the same viewing, and when a manager quits the database walks out with them. A CRM for a real estate agency solves exactly these problems — but only one that accounts for the specifics of the market. Let’s look at what belongs inside it, and where implementations usually stumble.

The property database and the client database are two different entities

The key difference between real estate and classic sales is that here you have two full-blown databases, not one. There is the property database: address, area, floor, condition, price, documents, photos, layout, price history, the owner and their real motivation to sell. And there is the database of buyers or tenants with their own brief: a budget range, districts, number of rooms, «definitely not the ground floor», mortgage readiness, timing. In a generic CRM people try to cram all of this into a single deal card — and the system falls apart in the second month. The right model is simple: a property lives its own life and may pass through a dozen buyers; a buyer lives their own and may view twenty properties. The deal is the point where the two intersect.

This is exactly why automatic demand-to-supply matching works. When an agent adds a new property, the system immediately shows which clients in the base it could suit by budget, district and parameters, and notifies the agents responsible for them. And the other way round: a new buyer brief is instantly matched against everything in the base, including colleagues’ listings. It isn’t magic, it’s a weighted filter: an exact match on district and room count, a plus-or-minus ten percent tolerance on budget, a penalty for a floor the client asked to avoid. The effect is immediate: a property that would have sat for two weeks until the next mailout gets three viewings on day one. Without matching, a property database is just an expensive archive.

The deal funnel in a realtor’s CRM: lead, viewing, deposit, closing

The funnel in real estate is longer and heavier than in retail: two to six months pass between the first call and the signature, and the stages have a completely different nature. The classic sequence is: lead, needs qualification, shortlisting, viewing, negotiation, deposit, document preparation, notary, closing, post-sale contact. Each stage drags mandatory actions behind it: after a viewing, feedback from both the client and the owner within a day; after a deposit, a hard deadline for the document check, because the closing date is written into the contract. A CRM shouldn’t just draw columns, it should nudge: the viewing was yesterday, no feedback logged — call. And it should record rejection reasons: «too expensive», «didn’t like the entrance hall», «went to another agency». That is what honest analytics is later built from.

A viewing deserves to be its own entity, not a line buried in the comments. It has a date, a time, a property, a client, an agent, an access method (keys at the office, the concierge, the owner opens up themselves) and an outcome. Then the system can see that an agent already has three viewings on Thursday across town, and won’t let a fourth be squeezed in between. Then the owner automatically gets a weekly report: how many listing views, how many calls, how many viewings and what people said — the best possible argument in a conversation about lowering the price. And then the manager sees conversion not as an agency average but per agent: how many viewings it takes to close one deal, and at which stage that agent loses clients.

Exclusivity, «whose client is this» and protecting the base from leaks

The sharpest question in any agency is whose client this is. Two agents work with the same buyer, each considers them theirs, and the commission is later divided in the manager’s office at raised voices. The technical fix is deduplication by phone number at the entry point: the system refuses to create a contact that already exists and instead shows who it is assigned to and when the last touch happened. The rule lives in the system, not in verbal agreements: a client is assigned to an agent for a fixed period, say 30 or 60 days, and if there is no activity in that window the card is released back into the common pool. The same goes for properties: an exclusive agreement with the owner should be a separate field with an expiry date, because exclusivity is what justifies spending money advertising that property.

Access rights follow from this. An agent sees their own properties and their own clients, the manager sees everything, an intern sees nothing extra. Owner contacts on other people’s listings are hidden: an agent can see the property in the shared base and offer it to their buyer, but it’s the responsible agent who dials the owner, not them. This isn’t paranoia, it’s basic hygiene: the most common way a base is lost isn’t hackers, it’s a manager who dumped everything into Excel before resigning. So bulk export must be closed off for ordinary roles, and every contact view must be logged: who, when, how many cards opened. An anomaly like «an agent opened two hundred contacts in one evening» should be flagged to the manager the next morning, not discovered six months later.

Commission splits between agents, and documents nobody wants to fill in by hand

In real estate the commission almost never goes to one person. A deal involves the listing agent and the buyer’s agent, sometimes an outside agency joins in, sometimes the manager who pushed the negotiation over the line. The CRM must calculate this automatically by the rules you set: for example fifty-fifty between the listing agent and the buyer’s agent, ten percent straight to the manager, the rest to the agency, with a separate scheme for co-operation with outsiders. The rate can depend on the deal type: one for rentals, another for sales, a higher one for exclusives. When the system does the math, the most toxic conflict in the team disappears, and at any moment an agent can see in their own dashboard how much they earned this month and how much money is «in transit» at the deposit stage.

Documents are the second area where agents burn hours on copy-paste. The owner agreement, the deposit contract, the inspection act, the earnest money receipt, the service agreement — all of them are roughly eighty percent made up of data that already sits in the system. A template with field substitution produces a ready file in ten seconds, with correct legal details, area to two decimals and the amount written out in words. Errors in passport numbers and addresses drop, and the agency has one version of each contract rather than «Kate has her own file from 2021». The logical next step is an electronic signature and delivery to the client in a messenger — and a whole category of trips to the office simply disappears from the process.

Agency automation: portals, mobile access, and why boxed CRMs don’t fit

Publishing listings is where agencies lose the most manual hours. A single property goes onto OLX, DIM.RIA, the agency website, a Telegram channel and various groups — and every price change means logging into five back offices. It should work the other way round: the property is entered once in the CRM, and the system itself builds the listing to each portal’s requirements, watermarks the photos, publishes via API or feed, and updates the price everywhere at once. Once it’s sold, the listing is withdrawn automatically, not a week later while people are still calling about it. View statistics flow back from the portals into the property card, giving an honest answer to the question of which channel actually brings buyers and which one just burns budget.

And finally: all of this has to work from a phone. A realtor spends most of the day away from a computer — in a stairwell, in the car, at a viewing. They need to open the property card on the spot, show the client the floor plan, photograph the flat and upload the pictures straight into the base, log feedback before they forget it, and check the next address. That’s why a mobile interface — and often a Telegram bot for quick access — matters more than beautiful dashboards. This specificity is exactly why boxed CRMs usually fail to take root: they are built around one deal and one contact, they have no two bases, no matching, no commission splitting, no exclusivity, and every customization runs into someone else’s architecture. At Devlly we build CRMs for real estate agencies around their actual processes: a property and client base, matching, a viewings funnel, access rights and portal integrations — the things that genuinely save an agent hours and save the owner their database.

Need software for your business? Get in touch