Skip to content
Concept · Tier 4Layer

Portfolio Yield Intelligence

An owner or manager holding units across several properties, with income in one place, maintenance costs in another, and occupancy in a spreadsheet, unable to say which property is actually performing.

The problem

Gross rent is known. Net yield per unit, after voids, arrears, maintenance and management cost, is not — so capital decisions about which property to keep, improve or sell are made on gross figures that conceal the answer.

In scope

  • Ingestion from existing sources
  • Agreed metric definitions
  • Yield per unit and property
  • Void and arrears analysis
  • Maintenance cost attribution
  • Owner reporting

Out of scope

  • Property valuation and market appraisal.
  • Investment advice of any kind — this reports performance, it does not recommend transactions, and that boundary should be explicit on the page.
  • Replacing the source systems.

What this would cover

Grouped by module — open the ones you want to read.

Ingestion
  • From the Property and Tenancy Management Platform, Rent Collection and Reconciliation, Facility Maintenance Request System, an existing manager's system, or spreadsheets
Metric layer
  • Gross yield, net yield, void rate, arrears rate, maintenance cost per unit, collection rate; each defined once, agreed in writing, versioned
Unit view
  • Performance per unit, which frequently shows that one or two units carry the losses
Property and portfolio view
  • Aggregated, with properties comparable on a per-unit basis rather than by total income
Void analysis
  • Periods unlet, duration, and the income forgone, which is the cost most consistently absent from a landlord's mental accounting
Arrears exposure
  • Current, aged, and as a share of expected income
Maintenance attribution
  • Cost per unit and per property, with recurring-fault cost surfaced separately, because a unit consuming repairs is a capital decision
Owner reporting
  • Scheduled, per owner, in a format a non-specialist reads

Data model

  • Read-mostly over sources.
  • Unit
  • Tenancy (read)
  • Invoice, Payment (read)
  • MaintenanceCost (read)
  • VoidPeriod
  • MetricDefinition → MetricVersion
  • OwnerReport

Invariants

  • Metric definitions are versioned and dated; a figure quoted last quarter still reconciles.
  • Void periods are derived from tenancy records rather than entered, so they cannot be quietly omitted.
  • Every aggregate traces to source rows.

Offline behavior

Not applicable.

Hard trade-offs

The difficult decisions, stated plainly — not trimmed for length.

Net yield depends on cost attribution, and most portfolios cannot attribute cost to a unit.

Maintenance is recorded against a property, or against nothing. Management overhead is not allocated at all. Phase 1 establishes what can actually be computed, and where the answer is "gross only," that is the honest deliverable rather than a net figure built on an invented allocation. Where the manager wants net yield, the Facility Maintenance Request System usually has to come first.

Owners compare themselves to each other, and a manager acting for several owners must decide what each one sees.

Cross-owner comparison in a shared report is a confidentiality problem waiting to happen, and access rules need settling before the first report is issued.

End state

What would be true about their day once this is running.

  • Yield is known per unit, not only per property, on whatever basis the data genuinely supports.
  • Voids are counted and costed.
  • Arrears exposure is visible as a share of expected income.
  • Units consuming disproportionate maintenance are identified.
  • Owners receive scheduled statements generated from one agreed set of definitions.

Let's map how your operation actually runs.

One session. We look at what's breaking, and what we'd build around it — whether or not you hire us afterward.

Start the operations review