Sooner or later, a growing estate agency in Poland faces the same question: stay with an off-the-shelf CRM, the software you use to manage clients and listings, or build a system of its own. Both answers can be right. The wrong decision is usually the one made out of habit or in reaction to a single frustration.
We build custom systems, so it would be easy for us to say that a system of your own always wins. It does not. If a ready-made CRM does exactly what your agency needs, building something from scratch would be a waste of money and time.
Below we describe how we approach this decision ourselves: when ready-made software is enough, how to tell that it is starting to pinch, what responsibility you take on together with your own code, and what the middle way looks like. We do not name specific products or give prices, because those change faster than the principle.
When an off-the-shelf CRM is enough
Ready-made software for estate agencies exists to handle the typical way an agency works. If your work fits that pattern, that is good news, not something to apologise for.
- Your process is typical. You take on a listing, publish it, talk to clients and see the deal through, and the software anticipates each of those steps.
- The integrations you need are already there. The software passes listings to wherever you publish them, and you do not have to move anything by hand.
- Your team does not rely on workarounds. Nobody keeps a parallel spreadsheet “because the software can’t do it”.
- The subscription is a predictable cost for you, and the vendor is developing the software in a direction that suits you.
- You can export your data in a readable format, should you ever want to switch.
If most of these points hold true, stay with your off-the-shelf CRM. Your time is better spent configuring it well and training the team than building something that will change nothing.
How to tell that ready-made software is starting to pinch
The problem does not have to appear overnight. It can build up gradually: first one column in a spreadsheet next to the software, then a separate file for the management, then someone who stitches together a report from several sources every week.
- Your process does not fit the software’s fields. You do something it does not anticipate, for example you have your own way of qualifying clients, work with other agencies or handle lettings alongside sales, and you keep it in notes.
- Your data lives in several places. Listings are in the software, owners in a spreadsheet, documents in the inbox, and answering a simple question means looking in each of them.
- An integration you care about is missing. The software does not connect to a tool you use, and the vendor has no plans for it.
- You assemble documents by hand. A client offer is made by copying data into a new file, so it can easily drift away from the database.
- Permissions are too coarse. The agent, the manager and the accounts team see the same things, although each of them needs something different.
- You do not know what will happen to your data if you stop paying the subscription or the vendor changes its terms.
One of these signals is not yet a reason to change. Several at once, recurring for months, are already a cost you pay every day; it just does not show up on an invoice.
What a system of your own gives you, and what it demands
We design a system of your own around the way your team already works, instead of bending the work to fit ready-made software. In practice that means a few things.
- Your processes. Fields, statuses and steps match what you actually do, not what the vendor anticipated.
- Your integrations. The system connects to the tools you use, provided they have an API (an interface for exchanging data between programs) or a data export.
- Your data. The database belongs to you, and you decide on roles and permissions: everyone sees what they need.
- Your code, no subscription. You pay for the work, not for a licence. At the end you receive the source code, the documentation and the access credentials, so you can develop the system yourself or with another company.
It is only fair to say what this demands. You bear the cost up front rather than in monthly subscription payments. Someone on your side has to spend time describing the process and signing off each stage. You are responsible for maintaining and developing the system: on your own, with us or with another company. Ready-made software is available straight away; a system of your own is built in stages.
If this sounds like too big a commitment for the current size of your agency, that is a sign to stay with your off-the-shelf CRM for now or to consider the middle way.
The middle way: an off-the-shelf CRM plus your own add-on
You do not always have to choose one or the other. If your software has an API or a data export, a new system can work alongside it. Agents keep their daily work in the software they know, and the add-on takes over whatever the software does not do well.
Such an add-on could, for example:
- prepare client documents as PDFs from current data, in several languages if needed;
- combine data from the software with the spreadsheets you keep alongside it, and build reports for the management from them;
- read PDF documents with the help of AI and present the extracted data for checking before it reaches the database;
- prepare a draft reply to a client enquiry, which the agent reads, corrects and approves before sending.
With AI, one rule stays fixed for us: AI can make mistakes, so the final word stays with a person, and an employee checks the result. We describe how that division of work looks with documents in our article on AI reading lease agreements with human review.
The middle way has its limits. The add-on depends on what the vendor’s API exposes and on what terms, and two systems mean two places to look after. Before you choose it, check which data you can pull out of the software and whether the vendor allows that kind of connection.
Questions worth asking before you decide
Before you talk to a vendor of ready-made software or to a company that builds systems, answer a few questions for yourself. Ideally in writing, together with the people who use the software every day.
- What does the team do outside the software: in spreadsheets, in email, on paper? Write all of it down.
- Which of these tasks take the most time or most often end in a mistake?
- Which tools does the software need to exchange data with, and does it have an API or an export for that?
- Who in the company should see which data, and who should not?
- Can you export all your data at any time, and what happens to it once you cancel the subscription?
- How far does your way of working differ from what the ready-made software assumes, and is that difference your advantage or just a habit?
- Who on your side will describe the process and sign off each stage if you go for a system of your own?
- Who will develop the system a few years from now: you, the company that built it, or someone else?
If the list from the first question is short, an off-the-shelf CRM will most likely be enough. If it is long and covers what sets your agency apart, it is worth costing out your own system or the middle way.
How we work on a decision like this
We start with a free consultation. We look at how you work today and say so plainly if ready-made software is enough. If it is not, we check what is worth connecting to your current software and what is worth building anew.
We break the quote down into stages, and each stage ends with an acceptance protocol, so you see a working part of the system before the whole is finished. That is how we built a system for managing a commercial real estate portfolio: with an AI module that reads PDF documents, PDF document generation, Excel import and export, and roles and permissions, finishing with team training and the handover of the code.
You can put together an approximate cost from modules in our approximate price builder. It is only an estimate, and every quote is individual. If you would like to talk about your agency, describe in a few sentences how you work today, and we will reply with where it makes sense to start.
