Sooner or later, every growing real estate company asks the same money question about its CRM. Why keep paying every month for something we could just buy once and own?
It's a fair question, and in Egypt and the Gulf it comes with extra weight. Budgets get approved once a year. A monthly fee in dollars moves with the exchange rate. And "ownership" feels safer than renting.
This guide compares a CRM subscription vs a one-time purchase properly, including the third route people often mean when they say "buy": having a CRM built for you. You'll get a worked cost example over 1, 3 and 5 years, the costs neither side mentions in the sales meeting, the real answer on data ownership, and a checklist to decide.
One thing in fairness first: Vilartech sells both. V Estate is a subscription CRM, and our software services team builds systems that clients own. So we have no reason to push you one way, and a good reason to be straight about both.
Three ways to get a CRM, not two
"Subscribe or buy" hides three different deals.
1. Subscription (SaaS). You pay monthly or yearly, usually per user or per plan. The vendor runs the servers, ships updates, fixes bugs and handles security. You stop paying, you stop using it.
2. One-time purchase of a ready product. You pay once for a licence, sometimes sold as a "lifetime licence" or "lifetime deal". The software is either installed on a server you provide, or hosted by the vendor. Updates and support are often a separate yearly contract.
3. A custom-built CRM. A developer builds a system around your process, and you own what is delivered. You pay for the build, then for hosting and maintenance for as long as you use it.
Where the software runs, in the cloud or on your own servers, is a related but separate question, and it's covered in types of CRM. Here we're dealing with the money and the control.
How much does a CRM cost? Subscription vs one-time purchase over 5 years
Comparing a monthly fee with a purchase price is the most common mistake. The fair comparison is the total cost of ownership: everything you pay to have a working CRM over the years you'll actually use it.
The example below is illustrative. The figures are round numbers chosen to show how the costs behave. They are not quotes, and not Vilartech's prices. Replace every one of them with the numbers you are actually offered.
The company: a brokerage with 10 users.
Assumptions (example only, in EGP):
- Subscription: 200 per user a month, so 24,000 a year. 5,000 once for setup and importing data.
- Ready product, bought once: an 80,000 licence, 40,000 to install, configure and move your data across, a server at 1,500 a month (18,000 a year), a support and updates contract of 15,000 a year from year two, and 2,000 a month (24,000 a year) of someone's time for backups, updates and user problems.
- Custom build: 750,000 to build, hosting at 3,000 a month (36,000 a year), and a maintenance contract of 150,000 a year from year two, which is 20% of the build cost (the first year is covered by the developer's support period).
Why 750,000 for the build? 2026 estimates for the Egyptian market put a custom system for a small company at roughly 400,000 to 1,500,000 EGP, with yearly maintenance of 15 to 25% of the build cost (Buildn Tech). International agencies quote 50,000 to 120,000 US dollars for a real estate CRM. We took the middle of the local range. A CRM with a WhatsApp integration, ad lead capture and a mobile app sits at the upper end.
| Total cost (example) | Year 1 | 3 years | 5 years |
|---|---|---|---|
| Subscription, flat price | 29,000 | 77,000 | 125,000 |
| Subscription, price rising 20% a year | 29,000 | 92,360 | 183,598 |
| Ready product, bought once | 162,000 | 276,000 | 390,000 |
| Custom build | 786,000 | 1,158,000 | 1,530,000 |
Three things jump out.
The purchase price is the smallest part of owning. In the "bought once" row, the licence is 80,000 of 390,000 over five years; the rest is running it. In the custom build row, maintenance over years two to five (600,000) comes close to the cost of the build itself.
Even a steadily rising subscription stays cheaper for a team this size. We added a row where the price goes up by a fifth every year, which is a harsh assumption, and it's still less than half the cost of the bought-once product over five years, and about an eighth of the custom build.
The owned options have almost no per-user cost. That's where the maths turns, which is the next section.
When the maths flips
A subscription grows with every seat. An owned system mostly doesn't: adding a user costs little beyond a bit more server capacity.
Run the same example with 50 users. At 200 per user a month, the subscription is 120,000 a year, or 605,000 over five years with setup. A ready product licensed for 50 users from an established vendor lists at around 180,000 EGP one-time; with the same running costs as above, five years comes to roughly 490,000. The bought-once line has crossed below the subscription.
The custom build hasn't. At 1,530,000 over five years, it only matches the subscription somewhere past 125 users, and a team that size needs a bigger server too. For most companies, a custom build is a decision about fit and control, not a way to save money.
So, roughly, and always for your own numbers:
- Small and mid-sized teams, short or uncertain horizon: subscription wins on cost, usually by a wide margin.
- Large teams over a long horizon: a bought-once product can win on cost, as long as you really will use it for the years you are counting. A custom build only competes on cost at well over a hundred users.
- Requirements no product meets: a custom build may be the only option regardless of cost. That's a different decision, covered below.
Two more things to add to your own version. Currency: if the subscription is billed in dollars, its cost in pounds moves with the exchange rate. Local vendors that bill in EGP remove that risk, as the buyer's guide to CRMs in Egypt explains. Messaging: if the CRM sends WhatsApp messages through Meta's official platform, Meta charges for some of those messages whichever route you choose. That cost belongs in all three rows, and our note on WhatsApp's October 2026 pricing change shows how to estimate it.
The hidden costs of a subscription
A subscription is simple, but not free of surprises. Ask about these before you sign:
- Seat creep. The price you were shown is for today's team. Hire five agents and the bill grows by five seats, whether or not they use it much.
- Plan tiers. The feature you actually need, say WhatsApp, an AI assistant, or ad integrations, may sit on a higher plan than the one advertised.
- Price increases. Ask how often prices have changed and how much notice you get.
- Add-ons and usage. Extra storage, message credits, integrations and onboarding may be charged separately.
- Leaving. If you can't export all of your data cleanly, the real cost of a subscription is the cost of never being able to leave. How to access a CRM lists exactly what to ask for.
The hidden costs of owning a CRM
The costs of owning are larger, and they're easier to miss, because none of them appears on the invoice you sign on day one.
- Hosting. A server, whether in your office or rented in a data centre, costs money every month, and needs a backup somewhere else.
- Security updates. Software that isn't updated gets less safe every month. Someone has to apply updates, test them and fix what they break.
- Backups that are tested. A backup nobody has ever restored is a hope, not a backup.
- The person who looks after it. Whether it's an employee or a contractor, their time is a real cost, and it's hardest to replace when they leave.
- Change. Your process will change: a new project type, a new lead source, a new report. On a subscription that's often in the next release. On an owned system, every change is a small paid project.
- Integrations that break. Meta, Google and other platforms change their APIs. Someone has to keep your connections working. CRM integration in Egypt goes into what that involves.
- Developer lock-in. Owning the code doesn't help much if only one person understands it. Ask for documentation as part of the delivery.
Data, control and security: who owns what
This is usually the real reason people want to buy, so it's worth being precise.
Your data is yours in every model. What changes is who holds it.
- On a subscription, the vendor holds it. Your protection is the contract: the right to export everything, at any time, in a standard format, and a clear answer on what happens to it if you stop paying.
- On a bought or custom system, you hold it. That's more control and more responsibility. A breach on your own server is your breach.
- On a custom build, ownership also means the code. Get the source code, the server credentials and the documentation handed over, and say so in the contract. Make sure accounts such as your Meta business account and WhatsApp numbers are registered to your company, not to the developer.
On security, owning doesn't automatically mean safer. A vendor running many companies on one platform has to take backups, updates and access control seriously every day. A single company's server is only as safe as the person maintaining it. Ownership is the better choice when you can resource it properly, or when a rule you must follow says where your data has to sit.
Customisation: where buying really wins
Here ownership has a genuine advantage.
A subscription product is built for many companies. You configure it, fields, stages, users, permissions, but you can't change how it fundamentally works, and your feature request joins a queue.
A custom system does exactly what you describe. If your process is genuinely unusual, say a developer selling across several projects with its own payment-plan rules, or an agency running leads for many clients with its own reporting, a custom build may fit where no product will.
Be honest about one thing, though. Most companies that believe their process is unique mostly need a CRM built for their industry. For real estate, that means one that already understands projects, units, developers, WhatsApp conversations and Meta lead ads. Try that first. What's left over is your real custom requirement, and it's usually much smaller than the whole CRM.
A middle route: subscribe, then build around it
It isn't all or nothing. Three combinations work well:
- Subscribe now, build later. Use a subscription for a year. You'll learn which features your team actually uses, and that becomes the brief for a custom system if you still want one. Just make sure the data will come out cleanly. Switching CRM without losing leads covers the move.
- Subscribe for the core, build the edges. Keep a ready CRM for leads and follow-up, and pay for custom work only where you need it: a link to an internal system, a special report, a client-facing app.
- Buy with a private setup. Some vendors keep each client's records in a separate database of its own rather than one shared by everyone. That answers part of the control question without you running a server.
Decision checklist
Answer these honestly, and the choice usually makes itself.
- How many users will you have in three years? For a small team, a subscription is very likely cheaper. For a large one, run the ownership numbers with your real quotes.
- How long will you keep this system? Ownership only pays back over a long horizon. If your business might change shape in two years, don't lock in capital.
- Do you have someone to run a server? If the honest answer is "we'll figure it out", choose a subscription.
- Does any product already fit 80% of your process? If yes, subscribe and customise the rest. If nothing comes close, consider a build.
- Is there a rule about where your data must be stored? If a regulator or a client contract says so, that may decide it for you.
- Can you pay a large amount up front? A build or licence ties up cash that could be spent on marketing or hiring.
- What is the exit on each option? For a subscription: the export. For ownership: the code, the credentials and the documentation.
- Is the price in your currency? A subscription in EGP, or in your local currency, removes exchange-rate risk from the comparison.
Where Vilartech fits
We sell both, so here's what each looks like with us.
If a subscription fits, V Estate is our real estate CRM for brokerages, developers and property marketing teams. It starts at 750 EGP a month on the Basic plan, which includes 5 users (the minimum team size), or 7,500 EGP a year. Larger teams and plans with the WhatsApp AI assistant, Messenger and Instagram are quoted by sales before you commit. Each client company gets its own database, and you can export your leads, properties and clients whenever you need to. See pricing for what each plan includes.
If you need something you own, our custom software team builds systems and integrations for businesses in Egypt and the Gulf. Our published project tiers start at 15,000 EGP for a website or simple app and 40,000 EGP for a platform with an admin dashboard and API integrations. A full multi-user system like a CRM is quoted after a discovery phase, before any work starts.
Not sure which one you need? Tell us about your team or message us on WhatsApp at +20 111 129 6413. Bring your user count and what you're paying today. We'll run the five-year numbers with you and tell you honestly which route is cheaper for your case, even when the answer isn't the one we sell.