Named users
The largest single driver. Count everyone who needs a login: sales executives, collections, accounts, site engineers, HR, and management. Read-only management dashboards usually cost less than full operational seats.
Pricing
What real estate ERP software really costs in Bangladesh
Nobody publishes real estate ERP software prices in Bangladesh, which makes budgeting impossible and comparison meaningless. This page explains what actually drives the number — users, active projects, units under management, modules, deployment and migration — with indicative ranges, so you can build a budget before you take a single sales call.
Why every vendor says "contact us"
Partly because the answer genuinely varies: a developer with three projects and eleven users is a different implementation from one with twenty-two projects, a site HR module and an on-premise server requirement. And partly because an opaque price protects a weak one.
The variance is real, but it is also predictable. Six variables account for nearly all of it, and you can estimate your own position on each of them in about ten minutes. That is more useful than a rate card, because a rate card that ignores your project count would be wrong anyway.
What follows is how quotes in this market are actually built, what the numbers tend to look like, and which line items are worth negotiating.
The six variables that move the number
Ranked by how much each typically shifts a quote for a Bangladeshi developer. Two companies with the same unit count can land a bracket apart on modules and deployment alone.
Pricing / What moves the number
- 88%
Named users
Sales, accounts, site, management
- 74%
Active projects
Each project = its own ledger
- 62%
Units under management
Flats + plots + parking
- 55%
Modules switched on
JV, deeds, HR, contractor billing
- 41%
Deployment
Cloud vs on-premise
- 34%
Data migration
Years of Excel, one-time
Relative influence on a typical quote, not a price list. Two developers with the same unit count can land a bracket apart on modules and deployment alone.
Indicative annual ranges
Cloud subscription, including hosting, updates and standard support. Figures are indicative bands seen in this market, not a rate card — your quote depends on the variables above.
| Developer profile | Typical users | Active projects | Indicative annual range (BDT) |
|---|---|---|---|
| Small — first system | 8–15 | 1–3 | ৳ 3,00,000 – 6,00,000 |
| Mid-size — multi-project | 16–40 | 4–10 | ৳ 6,00,000 – 15,00,000 |
| Large — REHAB-scale | 40–120 | 10–25 | ৳ 15,00,000 – 40,00,000 |
| Enterprise / on-premise | 120+ | 25+ | Quoted per deployment |
Implementation, data migration and any custom development are separate one-time costs. On-premise deployment replaces the hosting component with your own infrastructure and adds an annual maintenance and support fee instead.
What drives the number, in detail
Active projects
Each project carries its own inventory, price rules, payment plans and ledger. A dormant completed project costs far less to keep than a selling one.
Units under management
Flats, plots, parking and commercial units across all projects. This drives storage, reporting load and the size of the migration.
Modules switched on
Sales, CRM and collections are the core. Joint venture, deeds and mutation, contractor billing, site HR and payroll, and tax modules are priced on top — you only pay for what you turn on.
Cloud versus on-premise
Cloud is a subscription with hosting included. On-premise means your server, your backup discipline and your IT staff, with a licence plus annual maintenance instead — usually cheaper over five years and more expensive in year one.
Data migration
A one-time cost driven by how many years of Excel exist and how consistent they are. Clean sheets with one row per booking migrate cheaply; twelve differently-structured files per project do not.
What implementation should include — check before you sign
The gap between vendors is usually here, not in the licence fee.
- Configuration of your real projects, towers, unit types, rate rules and payment plans — not a generic template.
- Migration of existing bookings, buyers, paid amounts and remaining schedules, with a reconciliation report you sign off.
- Document templates on your letterhead: money receipt, quotation, demand letter, allotment letter, in Bangla and English.
- Role and permission setup matching your actual org chart.
- Training for each team separately — sales, collections, accounts — because their screens are different.
- A defined go-live date and a parallel-run period where the old process continues alongside.
- Named support contact, response time commitment, and what counts as support versus billable change.
Cloud versus on-premise, honestly
| What you need | On-premise | Cloud |
|---|---|---|
| Year one cost | Higher — licence plus server hardware. | Lower — subscription only. |
| Five-year cost | Often lower if the server is already there. | Predictable, no hardware refresh. |
| Data location | Your own premises. | Managed hosting, with your database isolated. |
| Updates | Scheduled, needs your IT to coordinate. | Continuous, no action required. |
| Site office access | Needs VPN or a public IP you maintain. | Works over mobile data out of the box. |
| Right for | Larger groups with existing IT staff and policy requirements. | Most developers, and anyone with multiple site offices. |
Frequently asked questions
Why not publish a fixed price list?
Because it would be misleading. The same user count can mean a ৳ 4 lakh implementation or a ৳ 20 lakh one depending on project count, modules and migration scope. The ranges above are honest bands; a fixed number would be either padded or immediately renegotiated.
Is it priced per user or per project?
Both are inputs. Named users are the largest driver, active projects the second. A developer with many users on few projects and one with few users across many projects can land at similar figures for different reasons.
What is the implementation cost separately?
A one-time cost covering configuration, data migration, document templates, role setup and training. For a mid-size developer it typically runs at a meaningful fraction of the first year's subscription, and it scales with how much historical data has to be migrated.
Can we start with one module?
Yes, and most developers should. Bookings and collections first, because that is where the leakage is. Joint venture, deeds, contractor billing and HR are switched on later without a migration, since they sit on the same database.
Is on-premise deployment available?
Yes, for developers with a policy or infrastructure requirement. It is licensed differently — a licence plus annual maintenance rather than a subscription — and you take on backup, uptime and update scheduling.
Are there hidden costs after go-live?
The ones to ask about in any quote, from any vendor: SMS and WhatsApp message costs, which are passed through at gateway rates; additional user seats mid-term; custom report development; and the boundary between included support and billable change requests. All four should be written into the agreement.
Do you offer a trial?
A guided demo on your own project structure rather than a self-serve trial. A real estate ERP with no configured projects, rate rules or payment plans does not demonstrate anything useful, so the first call is spent setting up one of your projects.
Related pages
Next step
Get a number for your own shape
Tell us user count, active projects, units under management and whether you need on-premise. That is enough for a specific figure rather than a range.
40 minutes · walked through on your project structure · no card required