EXECUTIVE CASE STUDY • REAL ESTATE • REQUEST TO LISTING MATCHING
How a real estate agency replaced fragmented spreadsheets with a visual pipeline agents actually use
In real estate, the speed at which a buyer request meets the right active listing decides whether the deal exists at all. Arpa Imob dropped the spreadsheets each agent kept separately and moved matching into a Kanban pipeline inside a self-hosted CRM.
- Requests matched against active listings
- Visual pipeline per agent
- No fragmented per-agent spreadsheets
The agency’s challenge
Every agent holding part of the picture in a separate file
Buyer requests and available listings were tracked by each agent in their own spreadsheet. A request that did not match one agent’s stock could sit for days while another agent held exactly the right property.
The loss is invisible and continuous: no deal fails dramatically, but matches are missed because no one can see both sides at once. The pipeline had to be shared and visual, not a report produced after the fact.
Stock split across files
Each agent worked from their own spreadsheet, so matching depended on who happened to remember what was available.
One shared board
Requests and active listings sit in the same pipeline, with each item at a visible stage and an owner.
Client testimony
“In real estate, how fast you match requests with active listings decides success. The application let us drop fragmented spreadsheets and gave agents visual control in a Kanban pipeline.”
A Kanban pipeline over shared listings and requests
The installation holds listings and buyer requests as records in one place, presented as a Kanban board so an agent sees stage and ownership without reading a report.
Matching stops being an act of memory. A new request is checked against current active stock, and a listing that changes state is visible to everyone working the same market.
Modules in use
- Listings register — active stock as records, with state and owner.
- Request pipeline — buyer requests at visible stages, from enquiry to viewing to offer.
- Kanban board — drag-and-drop stages so agents work the pipeline rather than a spreadsheet.
- Agent assignment — ownership per record, so nothing sits unclaimed.
The modules are licensed separately, so an installation carries only what it uses.
See the pricingWhat changed in the agency
Matching happens against the whole of the agency’s stock rather than one agent’s file. Managers see the pipeline without asking for an update, and a request that cannot be served today stays visible instead of being forgotten in a closed spreadsheet.
One-time licence
The platform and the active modules are paid once, not every month, for as long as the company uses them.
Unlimited users
People are added without a per-seat cost, so the licence never decides the size of the team.
Own infrastructure
The installation and the database sit on the company’s own server, so the data stays where the company put it.
Related case studies
Other companies running on Zarina CRM
Sixteen deployments across eleven industries, each with the company named and the workflow described, so you can find one close to your own.
STRATEGIC PARTNERSHIP • ENTERPRISE
Move your operation onto a platform you own
The editions, the modules and the one-time licence are the same ones used in this deployment. The installation sits on your server, the users are unlimited, and the licence is paid once.
- Installed on your own server
- Unlimited users
- One-time payment