Claritas One
All case studies
Real Estate13 months·UK / EU

Institutional REIT — 3,800 Property Portfolio

Consolidated fourteen property systems into a unified operating platform at £6.2bn AUM

An institutional REIT with 3,800 properties and £6.2bn AUM was taking nine days every month to produce portfolio-level NOI reporting across fourteen fragmented operational systems. Thirteen months of platform engineering took reporting to under four hours, lifted tenant ticket velocity 2.2×, and made M&A integrations a two-week exercise rather than twelve months.

−96%
Reporting time
2.2×
Ticket velocity
3,800
Properties
14
Systems unified
Pattern study · Client is anonymised; details may be composited across engagements to preserve commercial confidentiality. Outcomes reflect the kind of result these methods are designed to deliver.

The REIT had grown largely through acquisition. Fourteen portfolio acquisitions over the preceding decade had each brought with them a different property management system — a mixture of Yardi, MRI, RealPage, and several bespoke platforms inherited from the acquired operators. The CFO's commercial point was direct. Every month, the finance team spent nine working days preparing portfolio-level net operating income reports because the underlying data had to be manually extracted from fourteen systems, normalised in spreadsheets, and reconciled against the group ledger. Every new acquisition initiated a twelve-month integration effort that typically ran over time and over budget, and the quality of portfolio-level reporting genuinely degraded in the period between an acquisition closing and that integration completing. The board's next acquisition pipeline — valued at over nine hundred million pounds — was being actively slowed by the integration overhead.

The engagement scope was unusual for a property technology effort because the commercial stakes required an enterprise-grade data architecture rather than an operational-systems rationalisation. The CFO did not want to force fourteen portfolios onto a single property management platform — the change management cost and the operational risk made that infeasible. What the CFO wanted was a single source of truth above the fourteen systems that produced authoritative portfolio-level data without requiring any of the underlying systems to change. We designed that layer as a property operations data platform built on Snowflake, with dbt for transformations and Fivetran connectors where available plus bespoke connectors for the three legacy systems that lacked native extraction support.

The property data model was the piece that required the most careful work. A unified lease, rent roll, and expense model across residential, commercial, and industrial asset classes had to accommodate the structural differences between those asset types — triple-net leases, percentage rent, service charge reconciliations — without collapsing into a lowest-common-denominator schema. We worked with the REIT's finance leadership, their external auditor, and the senior asset managers for each asset class to build a dimensional model that preserved the commercial richness of each asset class while exposing a consistent portfolio-level view. Every metric in the portfolio dashboard was documented with its definition, its source systems, and its reconciliation logic — a documentation artefact that the external auditor subsequently used as part of their year-end audit preparation.

The tenant portal and maintenance workflow work was a parallel track. The REIT's residential portfolio, in particular, had high tenant-service costs driven by a telephone-only maintenance reporting channel that routed to a call centre operating during business hours. We built a tenant self-service portal with a mobile-first maintenance reporting flow that included photo attachments, auto-classification of the issue type, and priority routing to the correct on-site property team. Completed work orders triggered automatic tenant notifications and satisfaction surveys that fed into the portfolio operations dashboard. The portal was deployed progressively across the residential portfolio over five months with tenant adoption reaching sixty-eight per cent by the end of that window.

The executive reporting layer was the visible outcome of the platform work. The CFO's portfolio NOI dashboard — refreshed daily rather than monthly — gave the executive committee a live view of the portfolio broken down by asset class, region, acquisition vintage, and tenancy status. The same data fed the board reporting pack, the investor relations deck, and the underwriting model used by the acquisitions team. Crucially, when a new acquisition closed, the data platform's standardised connectors meant that the acquired portfolio could be added to the reporting within two weeks rather than twelve months — a shift that directly unblocked the next stage of the acquisition programme.

The measured outcomes were those the CFO had asked for. Monthly portfolio reporting compressed from nine working days to under four hours, freeing the finance team to work on analysis rather than extraction. Tenant-originated maintenance tickets were resolved two point two times faster, with a thirty-eight per cent reduction in the call-centre volume the REIT had historically paid for. M&A integration shortened from twelve months to two weeks for data and reporting, with operational systems integration now a subsequent and separate decision. The acquisitions pipeline that had been slowed now resumed at its intended pace, with three transactions totalling four hundred and thirty million pounds closing in the nine months following platform go-live.

Tags
PropTechData UnificationTenant PortalNOI
Stack
SnowflakedbtFivetranYardi / MRI / RealPageLooker

Need a similar outcome for your organisation?

Brief our principals on your current state and target outcome. You will receive a scoped proposal within three business days.

Start a conversation