On 9 May 2026, Bangladesh’s state news agency reported the country’s telecom figures like this: mobile subscribers at “18 crore 60 lakh 60 thousand." Not 186 million. Crore, lakh, thousand — because that is how the country counts. It is a small thing, and it is exactly the kind of small thing that decides whether a real estate CRM in Bangladesh is still open on a salesperson’s phone in week three.
Global sales software is not badly built. It is built for somewhere else, and the gap shows up in five specific places, all of them testable in a demo.
A flat sells for one crore twenty-five lakh. Foreign software renders that as ৳12,500,000 and expects a sales manager to find the decimal himself. The local format is ৳1,25,00,000 — three digits, then twos.
Nobody invented this locally. Unicode’s Common Locale Data Repository — what most operating systems and browsers use to format numbers — carries a grouping pattern for exactly this case: #,##,##0.###, worked example 1,00,00,000.00. It exists because a large part of the world groups digits this way, and software that ignores it is choosing to.
The effort here is not about looking neat. On a target-versus-revenue chart, ৳12,500,000 and ৳1,25,00,000 are the same money — and the work goes in so the person whose incentive rides on that number can read it at a glance. Skip it and every figure needs a second look, every month, by everyone.
In Sofia Estate CRM every currency figure runs through one shared formatter — lakh and crore, three-then-twos. One formatter, not one per screen, so two screens can never disagree about the same amount.
Test it: ask to see any number above one crore. Then the same number on the printed report.
The Bengali Language Introduction Act, 1987, section 3(1), requires records and correspondence, laws and court proceedings to be in Bangla across courts and government, semi-government and autonomous offices. Paper in Bangla is not nostalgia here — it is the operating norm of every institution a developer deals with.
That habit carries into the monthly review. The printed sheet is the only part of a sales system that physically leaves the building — into the meeting, onto the owner’s desk, into the file.
So printing cannot be an export you rebuild at month end. In Sofia, print is one click, at any time, from the screen you are already looking at. What comes out is a document rather than a screenshot: a report header saying who it is about, which period it covers and when it was printed; navigation, buttons and action links removed, because you cannot click paper and a dead link on a printed page reads as a defect.
Test it: mid-month, on a normal screen, press Ctrl+P. Look at what lands.
Bengali is a unicameral script — it has no distinct upper and lower case letterforms. It hangs from the matra, the horizontal line running along the tops of the letters, and a sentence closes with the daṛi, ।
Two consequences follow, and foreign design systems get both wrong by default:
Uppercase does nothing. Capitalising every label is a Latin habit. In Bangla it changes nothing, and in some rendering paths it damages the shaping of conjuncts.
Negative letter-spacing breaks the sentence. Tightened tracking is a Latin display trick. In Bengali it pulls the daṛi into the glyph before it, so a sentence’s ending reads as part of the last letter. We caught this on our own homepage at −0.022em — an ordinary value for an English headline.
Bangla in Sofia runs at zero tracking, never uppercased, and at a looser line height than the Latin around it — roughly 1.3 for headings and 1.6 to 1.7 for body — because the conjuncts and the vowel marks above and below the line need the vertical room.
Nobody writes this into a requirement. Everyone notices it on day one and cannot say why the screen feels wrong.
Test it: put a full Bangla sentence into a heading, a badge and a table cell. Look at the ending.
The telecom regulator’s March 2026 figures, reported on 9 May: 11 crore 48 lakh 50 thousand mobile internet users against 1 crore 47 lakh 50 thousand fixed-line, out of 12 crore 96 lakh 20 thousand in total. Roughly seven mobile connections for every fixed one — about 89 percent of the country’s internet is a phone.
For a sales floor that is not a statistic but a description of where the work happens. The person logging what a client said is standing in a sample flat or walking back from a site visit. The desktop is where the coordinator builds the month; the phone is where the day is actually recorded. Software that treats the phone as a shrunken version of the desktop gets used by managers and abandoned by the people whose data it needs.
Test it: run the entire demo on a phone. Not a tablet.
This is the one that no amount of configuration fixes. Global CRM assumes two levels: a rep and a manager. A developer here runs a Head of Sales — CBO, Director of Sales, the title varies — over a Manager who holds an area, Supervisors under him, Team Leaders under them, agents under those. Beside that sits a coordinator, and a marketing side with a control panel of its own. And what the owner actually reads is verified output, not a document somebody assembled the night before.
Those are different questions, not different permission levels. A Manager compares teams. A Supervisor compares people inside a team. A Team Leader works alongside his. Four consequences that foreign software gets wrong by default:
Lead age is days since the lead reached the person — not since it entered the software. Get this wrong on day one of migration and every historic lead resets to zero days old, which is a very common dispute in any CRM rollout.
Every rate shows its denominator. “Contact rate 90%" means nothing until the screen says ninety percent of what, over which period.
The same fact is worded for whoever is reading it. On a salesperson’s own screen it reads as standing — days since his last booking. On his supervisor’s screen the same data is a risk flag with the months counted plainly. A product that only judges salespeople is one they stop using.
The handover line. Marketing is a first-class user with its own screen, not a department the sales floor describes. Its record ends where the lead is handed to sales. Draw that boundary on the funnel itself, and the old argument on the floor — “marketing gave us bad leads" / "sales never called them" — gets settled by the chart instead of by whoever talks louder.
One more that only bites as a company grows: a list must not grow with the headcount. Name the extremes at both ends, carry one summary row with real aggregates for everyone else, and state the true total in the header. Otherwise a screen that worked at twenty agents is unreadable at two hundred.
REHAB was founded in 1991 by eleven companies. Its own site now puts the sector at nearly 15 percent of national GDP, and its member roll runs past 900. That is several hundred sales floors, most running a version of the same hierarchy, with the same arguments in the same order.
The software serving them comes from two directions. ERP houses do inventory, collections and accounts properly; that is what they are for. Generic CRM does contacts and stages properly; that is what it is for. Neither was built to watch a sales floor — to know that a booking follows a site visit, that a Team Leader needs a different screen from his Manager, or that the number has to print in crore.
Sofia Estate CRM is built by Sofia Technologies for this market first: a Real Estate Sales Revenue Engine that does not fight your ERP — it is built for your sales, your revenue, and your control of both. Don’t take the claim. Run the five tests above on us.
There is no demo and no free trial. You see it first, and you pay if you think it is worth paying for. Then you have seven days: if it hasn’t worked properly in that time, or you decide it is of no use to you, you get all of your money back. Setup is ours, training your team is on us.
If you want the shape of the leak before you talk to any vendor, us included, the Sales Health Check takes under three minutes and gives you a number.
Sources: Bangladesh Sangbad Sangstha, 9 May 2026 (BTRC figures for March 2026) · Unicode CLDR, number and currency patterns · Bengali Language Introduction Act, 1987, s. 3(1) · REHAB’s own site.