Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The decision
The spreadsheet next to the system is the diagnosis
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
Ask an operations team to show you their property system and watch what else opens. If the answers to real questions — what does this tenant owe with the stepped rent applied, which renewals carry the non-standard break clause, how is the service charge split across these owners — come from spreadsheets beside the system rather than from it, the system does not fit the portfolio. Every one of those spreadsheets is a place where a formula quietly breaks, a version forks, and a number reaches a tenant or an owner wrong.
The expectations around the lease itself have also moved. In Saudi Arabia, digital lease registration through platforms such as Ejar has made an electronic lease record the normal state of a tenancy, and tenants increasingly assume the rest of the relationship — invoices, receipts, requests, renewal notices — will be equally digital and equally traceable. Whichever way the build-or-buy decision goes, a system whose lease records cannot line up with the digital ones a tenancy now generates is behind the market it operates in.
The decision is therefore not ideological. It is a measured comparison between what your agreements actually contain and what the candidate products actually model — made lease by lease, on your hardest cases rather than your easiest ones, before any money moves in either direction.
Three routes
Packaged, custom, or a packaged core with custom edges
The third column is where many portfolios actually land: a packaged product carrying the standard operations, with custom software covering the agreements and workflows it cannot model.
| Option | Fit to non-standard leases and charges | Time until the team is working in it | Cost shape over five years | Control over the roadmap | Best for |
|---|---|---|---|---|---|
| Packaged product | Handles what it anticipated; everything else becomes a workaround or a side spreadsheet. | Fastest — configuration and data migration rather than development. | Subscription per unit or user, predictable, rising with the portfolio. | The vendor’s priorities decide; your feature request queues behind everyone’s. | Portfolios whose leases and charges genuinely follow the standard patterns. |
| Custom build | Models your agreements exactly, including the ones no product anticipated. | Slowest to first use; scoped right, the first release carries the core within months. | Investment up front, then ownership — no per-unit fee as the portfolio grows. | Entirely yours, which also means maintaining it is yours to resource. | Operators whose lease structures are the business model, not an exception to it. |
| Packaged core, custom edges | The product carries the standard cases; custom modules carry the deviations against the same records. | The product goes live first; the custom edges follow where the spreadsheets hurt most. | Subscription plus targeted builds — the custom spend goes only where the product fails. | Shared: the core follows the vendor, the edges follow you. | Portfolios that are mostly standard with a costly non-standard minority. |
What sets the price
The four drivers that size a property-system build
No credible figure exists before these are known. They are the questions we work through in a scoping session, and each one moves the estimate more than the technology choice does.
| Variable | Effect on price | Why |
|---|---|---|
| Lease and charge variety | The largest driver in either direction | Ten lease templates with staged rents, escalations and mixed service-charge rules cost multiples of two standard ones — the model, the billing and the testing all scale with the variety. |
| The integration surface | Each system joined adds scope | Accounting, payment collection, banking files and the digital lease records a tenancy generates each add a connection to build and test; the count of those connections is a better cost predictor than the screen count. |
| The data being carried in | Migration is a project inside the project | Years of tenancies in spreadsheets arrive with duplicates, gaps and contradictions. Cleaning and loading them so opening balances reconcile is real work, and skipping it means the new system starts life distrusted. |
| The tenant-facing surface | Optional at first, decisive later | A portal or app where tenants see invoices, pay and raise requests roughly doubles the design and support surface. Phasing it after the internal core is stable is usually the right sequencing. |
Ask any supplier quoting this
- Show me my three hardest leases modelled in your system, end to end, including the bill each one generates.
- What happens to my data and my billing history if we part ways in year three?
Our role
What we build around the lease record and what stays commercial
- 01
The assessment before the recommendation
We test your hardest leases against the candidate products before advising a route, because a build recommended without that test is a preference, not an assessment.
- 02
The lease as the single record
Whichever route wins, we build towards one lease record that billing, renewals and reporting all read, so a number never has to be computed twice to be trusted once.
- 03
Migration treated as first-class work
We clean, reconcile and load the existing tenancy data as its own workstream with its own acceptance test: the opening balances agree with the accounts, or the system does not go live.
Lease terms, rent levels and tenancy obligations are matters for your commercial and legal advisers; we build the system that administers whatever they decide, accurately and without a spreadsheet shadow.
Common questions
What buyers ask
When is packaged property-management software simply the right answer?+
When your leases and charges genuinely follow the patterns the product was built around — and the test is empirical, not a feeling. Take your three most complicated agreements and have them modelled in the candidate product end to end, through to the bill each one generates. If they fit without workarounds, buy the product; the faster go-live and the vendor carrying maintenance are real advantages a custom build has to beat, not dismiss. We say this as a firm that builds custom software: recommending a build where a product fits would cost you money to our benefit, which is exactly the advice worth distrusting.
Can a custom property system stay aligned with digital lease platforms like Ejar?+
Alignment is a design goal we build for, and its exact mechanics depend on what the platform offers at the time, which is a scoping question rather than an assumption. Where a platform provides an integration route, the system exchanges records directly; where it does not, the system keeps its lease data in a shape that matches the registered record — same parties, same terms, same dates — so the two never tell different stories about the same tenancy. What we deliberately do not do is hard-code assumptions about any platform’s current rules into the system’s core, because those rules are the platform’s to change, and a system built on them ages badly.
Our tenancy records live in a dozen spreadsheets. Is that a blocker?+
It is the normal starting point, not a blocker — but it is real work that belongs in the plan rather than in a footnote. The spreadsheets will contain duplicated tenants, missing dates, charges that were adjusted in one copy and not another. We treat migration as its own workstream: profile the data early, reconcile it against the accounting system, and load it with an acceptance test the finance team signs — the opening balances in the new system agree with the books. A migration done that way takes weeks and produces a system people trust on day one; one done as an afterthought produces a system the team double-checks against the old spreadsheets for a year, which quietly defeats the point.
In this cluster
Map it to your portfolio
A build-or-buy assessment against your three most complicated leases — if a packaged product can carry them, we will say so before any build is proposed.
Start the conversation