Case study·Build-to-rent

Occupancy and pricing brief

From a Friday spreadsheet scramble — to a reviewed pricing brief waiting for the revenue meeting

75%
Weekly pricing prep reductionFrom two days of reconciliation to a one-hour reviewed brief
“The colleague gave us pricing context before the meeting, not after.”
Revenue Lead · BTR multifamily operator
UK BTR / multifamily operator·1,400 units across 3 pilot assets·6-week pilot·United Kingdom
Talk to us about this workflowTry Unify
01Pilot envelope
Pilot length6 weeks
First signal6 days
First ROI30 days
Team alongside5 seats · 2 colleagues

6-week revenue pilot; anonymised pricing inputs first; Co-ordinator aligned pricing exceptions, rent bands and occupancy definitions with the asset team.

02What it owns
Reports toRevenue Lead, with a dotted line to asset management on renewal exceptions.
Owns
  • Weekly occupancy and pricing brief — circulated to the revenue meeting one working day in advance
  • Reconciled pricing baseline — YieldStar, OneSite rent roll and HubSpot demand joined into a single asset view
  • Renewal exception queue — every offer outside band carries a named owner, rationale and approval state
  • Definition guardrail — physical and economic occupancy agreed once and applied across the brief and Power BI
Does not do
  • Final pricing decisions — escalate to the Revenue Lead for sign-off
  • Asset-level strategy — surfaces inputs; asset managers set direction
  • Sending renewal offers — drafts only, never sends without approval
Done looks like

The revenue meeting opens with a reviewed brief, not a reconciliation. Pricing exceptions and renewal positions are decided in the room and signed off the same day.

03The team
AI teammates2
OwenReads YieldStar, the OneSite rent roll and HubSpot demand each morning, reconciles definitions and surfaces pricing exceptions before the revenue meeting.
MayaDrafts the weekly occupancy and pricing brief, links every claim to source and pre-fills the renewal exception list for the asset team.
Human team5
  • Revenue LeadRevenue
  • 3 Asset managersAsset
  • 3 Property managersOperations
  • 2 AnalystsRevenue
  • BI ownerReporting
04Connected stack
YieldStarOneSiteHubSpotExcelPower BIMicrosoft Teams
05What it returned
75%Weekly pricing prep reductionFrom two days of reconciliation to a one-hour reviewed brief
23Rent exceptions reviewed in pilotEach with a named owner and source-linked rationale
+2.1%Renewal uplift on pilot assets vs baselineCaptured against the pre-pilot renewal trend
  • Day 0
    Co-ordinator sessionRevenue lead, asset managers and BI owner aligned pricing exceptions, rent bands and occupancy definitions in one call.
  • Day 6
    First reviewed briefYieldStar, OneSite and HubSpot joined on anonymised pricing inputs; Owen drafts the first read-only pricing brief for the Revenue Lead.
  • Day 12
    Read-only goes liveBrief lands in the revenue Teams channel ahead of the weekly meeting; asset managers correct two band definitions.
  • Day 20
    Renewal exception queueMaya pre-drafts the renewal exception list; property managers add affordability context inline before the brief goes out.
  • Day 30
    ROI reviewSponsor signs off on three baseline metrics and approves expansion to a fourth pilot asset.
↗Get started

Want this for your team?

Each design-partner pilot starts the same way: one workflow, the minimum useful context, and a first ROI signal measured in days.

Talk to us about this workflowTry Unify