The operating problem
Property still runs on spreadsheets, and tenants have stopped accepting it
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.
A developer or manager with a portfolio of any size is usually running four or five parallel systems: a leasing tracker, a facilities inbox, an accounting package, a contacts list, and the institutional knowledge of whichever manager has been there longest. Each works on its own. The cost is at the seams — a renewal that lapses because the reminder lived in one spreadsheet, a maintenance complaint that is chased three times because it was never a tracked job, a portfolio report that takes a week to assemble because the numbers have to be re-keyed from four places.
At the same time the tenant’s expectation has moved. A commercial tenant who runs their own business on software finds it strange to report a broken air-conditioning unit by phoning a number and hoping, and a residential tenant compares the experience to every other service they use. The gap between how a property is run internally and how a tenant expects to interact with it has become a competitive fact, not a nicety.
The instinct is to buy a product that promises to fix all of it. The more reliable route is narrower: pick the seam that costs the most — usually renewals or maintenance — join the two systems either side of it, and prove the value there before touching anything else. A portfolio does not need one platform to replace five tools on day one; it needs the breaks between them closed in the order that hurts most.
The lifecycle
The tenant lifecycle, from a viewing to a renewal
One relationship, and the systems that should be carrying it at each stage. Where those systems are separate today, the information is re-entered or lost at the boundary — which is exactly where the record has to become continuous.
Enquiry and viewing
A prospect asks about a unit, books a viewing, compares options.
The enquiry becomes a record from the first contact, so the eventual lease is not the first time this tenant exists in a system.
- Leasing CRM
- Listings
Lease and onboarding
Terms are agreed, documents signed, the unit handed over.
The lease terms, the documents and the handover condition attach to the same tenant record rather than to a folder a manager has to find later.
- Leasing
- Documents
- Accounting
Living and working in it
The tenant reports faults, requests changes, asks questions during the tenancy.
A request becomes a tracked job against the specific unit and asset, visible to the tenant and the facilities team, not a phone call somebody has to remember.
- Facilities
- Tenant app
- Assets
Rent and charges
Payments fall due, charges are raised, arrears are chased.
Billing runs from the lease record, so a charge and its status are visible without reconciling an accounting export against a spreadsheet.
- Accounting
- Payments
Renewal or move-out
The lease approaches its end and a decision has to be made in time.
The renewal window surfaces automatically with the tenancy history attached, so the conversation happens before the lease lapses rather than after.
- Leasing CRM
- Accounting
The parallel systems
The four systems a developer usually runs in parallel
These rarely need replacing all at once. They need the boundaries between them joined, in the order that costs the most, so a fact entered in one is not re-entered or lost in the next.
Leasing and the pipeline
Where enquiries, viewings and deals are tracked. When this is disconnected from accounting, a signed lease is entered twice and a renewal date lives only where whoever set it can see it.
Facilities and maintenance
Where the building is kept running. When requests arrive as calls and emails rather than tracked jobs against an asset, nobody can say what is outstanding or what a recurring fault is costing.
Accounting and collections
Where rent, charges and arrears live. When it is separate from the lease record, billing questions become a reconciliation exercise and the true arrears position is always a few days out of date.
The tenant relationship
Where communication and satisfaction should accumulate. In most portfolios this exists only in inboxes and memory, so the portfolio cannot see which tenants are at risk of not renewing until they have gone.
Our role
What we build for a property portfolio and what stays with your managers
- 01
The record, joined first
We build the tenant record that runs through leasing, facilities and accounting, so the relationship is continuous instead of re-created at each system boundary.
- 02
The seam that costs most
We start where the loss is largest — usually renewals or maintenance — and prove the value on one seam before extending, rather than replacing five working tools in a single risky programme.
- 03
Managers, not developers, in control
Your leasing and facilities managers own the process; we give them the tooling to run it and to change the parts that change often without waiting for a release.
Valuation, brokerage and any regulated advisory stay outside what we do; we build the operational software that joins how the portfolio runs to how tenants expect to deal with it.
Common questions
What buyers ask
Do we replace our property management system or build around it?+
Usually build around it, at least at first. A property management or accounting system that your finance team trusts is expensive to replace and rarely the actual source of pain — the pain is at the boundaries, where it does not talk to leasing or facilities. If that system exposes its data through an interface, we join it to the rest and leave it in place. Replacement only makes sense when the core system genuinely cannot be integrated or is itself the bottleneck, and that is a decision we would reach with you on evidence, not assume at the start.
Which part of the tenant experience is worth digitising first?+
Whichever one is costing you tenants or manager time most visibly, which in most portfolios is maintenance or renewals. Maintenance is a good first target because the failure is concrete — a request that was never tracked, a fault that recurs — and the improvement is measurable in response time and repeat visits. Renewals is the other common starting point because a lapsed renewal is pure lost revenue that a reminder against a continuous record prevents. We would look at your actual data before recommending, rather than starting with the feature that demos best.
Can facilities and leasing teams run this without IT for every change?+
That is a design goal, not an extra. The things a property team changes often — unit details, charge types, the wording of a tenant notice, a maintenance category — belong in a configuration the managers control, so a routine change does not become a support request. What stays with developers is structural work: a new integration, a change to how billing is calculated. Drawing that line clearly is part of the build, because a system that needs a developer for every small edit is one the team quietly stops using.
In this cluster
Start with your systems
A working session that follows one tenant from first enquiry to renewal across your current tools, marking every point where information is re-entered or lost, so the build targets the breaks rather than replacing everything.
Start the conversation
