/systems — real estate

ERP for real estate developers in Egypt

One database under every department — inventory, sales, payment plans, brokers, collections — instead of six spreadsheets that disagree with each other. Built in Cairo, bilingual by default, and yours outright.

Start a project See the work

Nobody chooses to run a development company on six disconnected sheets. It accumulates. You start with one unit list. Sales copies it and adds buyer columns. Finance needs to track who paid which installment, so that becomes its own file. Brokers need registering and commissions calculating, so the commission sheet is born — and immediately disagrees with the sales sheet about which deals are real.

We counted eleven open tabs across two monitors at a New Cairo developer that had closed 340 million EGP the previous quarter. The operation worked, but only because one operations manager carried the whole map in her head. That is the actual risk: the business does not run on the spreadsheets, it runs on the one person who remembers which spreadsheet is the real one this week.

What the system replaces

Why month-end stops being a forensic exercise

On six spreadsheets, reconciliation means working out which sales actually closed, who collected, which broker is owed what, and why finance and sales are 1.2 million apart. Half the commission disputes are about deals nobody logged cleanly.

When every department writes to the same record, the reconciliation is the dashboard — it is already done. The commission dispute disappears because the commission was computed off the deal rather than off a separate sheet maintained by a different person with a different definition of 'closed'.

Systems we have already shipped

How a project runs

  1. We start with the friction, not the feature list — where the current setup actually breaks, and what it costs when it does.
  2. A written scope: which modules go in phase one, what each one does, the timeline and what is explicitly out.
  3. We build in phases, so one department is live and useful before the next starts. You see working software early, not a demo at the end.
  4. Handover in your name: code, database, hosting and documentation. You can move all of it to another team without asking us.

Common questions

Why custom instead of a monthly SaaS seat?

Because property sells differently here. Your top closer logs six fields out of forty-seven and keeps closing anyway, because the tool fights the way the work actually happens. A system shaped around your process gets used; a generic one gets worked around. And at the end you own it outright rather than renting it per seat, forever.

How long does a build like this take?

Six to twelve weeks for a first working version, depending on how many modules go in the first phase. We build in phases so one department is live and useful before the next one starts, rather than disappearing for six months.

Is it bilingual?

Arabic and English by default, built from the start rather than bolted on. Your sales team works in Arabic and your Gulf investors read English, so both have to be first-class — including proper right-to-left layout.

Do I own it at the end?

Yes, outright. The code is yours, the database is yours, the hosting is in your account, and you can hand all of it to another team without our permission.

Related systems

Talk to us about yours Message us on WhatsApp