Property record structure
Every property is its own record: type, rooms, size, district, price, status and owner, with photos and documents attached.
Most of our Ankara clients are in real estate. What makes the sector different is that it runs two ways at once: you manage buyers and sellers, demand and inventory, at the same time.
At a glance
In real estate the loss usually comes not from failing to find customers but from failing to manage what you already hold:
What we add on top of a standard CRM build for real estate:
Every property is its own record: type, rooms, size, district, price, status and owner, with photos and documents attached.
Buyer budget, district and feature criteria are recorded, and matching properties surface automatically for the agent.
Portal enquiries land in the CRM, so how many viewings and sales each portal produced can be measured.
Appointments, attendance and feedback are recorded, making it visible how often a property was shown and why it was rejected.
Who sourced the property, who brought the buyer and the split ratio are defined on the record, and entitlement is calculated automatically.
Agency agreements, valuations and title documents attach to the record, with reminders before fixed-term agreements expire.
In agencies most time is lost to bad matches. An agent takes a buyer to three properties that do not really fit and both sides are worn out. The buyer's criteria were already discussed in the first conversation; the problem is that they were never recorded. Once budget, district, room count and floor are captured as structured fields, the system surfaces matching properties by itself. When a new property is added, waiting buyers who match are listed, so it is clear who to show it to on the day it arrives.

Real estate firms spend serious budget on listing portals, yet most do not know which one actually produces business; all they have is the view count the portal itself reports. Once calls and form enquiries come into the CRM with their source, the picture becomes clear: enquiries, viewings and sales per portal can all be measured. More often than not, the portal that produces the most views is not the one that produces the most sales.

In multi-agent offices the most common internal problem is the commission split. One agent sourced the property, another found the buyer, a third closed the deal. If those roles are not defined on the record, the split becomes an argument every time. When the listing owner, the buyer's agent and the closer are held as separate fields, entitlement is calculated automatically and nobody can make a retrospective claim.
Consistent status definitions across the office are the precondition for meaningful reporting.
| Status | What it means | What the system does |
|---|---|---|
| New listing | Record created, agency agreement pending | Agreement task created |
| Live | Active on listing portals | Matching waiting buyers listed |
| In viewing | At least one viewing has taken place | Feedback record requested |
| Under option | Buyer has made a preliminary agreement | Other viewings locked |
| Sold / Let | Transaction completed | Take-down task and entitlement calculation |
| Inactive | Owner withdrew or the agreement expired | Re-engagement reminder created |
How would this work in your process?
In a free 30-minute call we listen to your workflow and map out how this would run in your company.
In real estate we settle the property structure first; the customer side is built on top of it.
Property types, required fields and status definitions are agreed. Reporting quality depends on this decision.
Spreadsheet records are imported with field mapping and duplicates are cleaned.
Buyer criteria, the viewing flow and automatic matching rules are built.
Listing portal connections and commission split rules are defined, followed by team training.
The modules we most often roll out alongside this one; they reinforce each other in the same setup.
Collecting leads is the easy part. Responding quickly, assigning correctly and following up consistently is where deals are won. We build Bitrix24 around those three things.
When the pipeline is unclear, nobody knows which deals are moving and which are stuck. We design your stages around your real sales process and make the next step visible on every card.
Scheduling shouldn't cost you a day of phone calls. We set up a booking flow where clients choose the service, the specialist and the time; and every booking lands in the CRM with its record.
When files live on desktops, in email threads and in personal cloud accounts, nobody knows which version is current. We put your entire document structure on one drive with clear permissions.
Most of our Istanbul clients are in health tourism. What sets the city apart is volume: hundreds of leads a day, shift-based consultant teams and the most expensive advertising competition in Turkey.
Most of our work in Antalya is health tourism and hospitality. Both share the same pattern: inbound demand from abroad, in several languages, mostly over WhatsApp.
Health tourism dominates our work in Izmir too. What differs from Istanbul is scale: fewer leads, but a longer and deeper evaluation process per patient.
It depends on what the portal offers. Where a portal exposes an API, a two-way connection can be built; where it does not, we bring enquiries in through email and calls with a source tag. In the second case publishing stays manual, but you can still measure which portal produces sales.
It is, though in real estate we usually advise against it: if listings are not shared, the matching advantage disappears. The common solution is to keep listings visible to everyone while protecting ownership and commission rights on the record. If you still want a closed model, the permission matrix supports it.
Project sales work differently: instead of individual listings you need block and unit inventory, option management and payment plans. We cover that on our construction and real estate solution page and build it accordingly. If you run both project sales and resale listings, the two can be set up as separate pipelines in one portal.
Yes. Lettings are built as a separate pipeline; contract start and end dates are recorded and a reminder fires when renewal is due. Rent review periods and collection tracking can run on the same record.
Book a free intro call and we'll walk through your process and show which settings fit you.