Case study·Build-to-rent

Arrears early-warning workflow

From end-of-month arrears surprisesto a daily ledger of risk with approved resident drafts

-14%
30+ day arrearsAgainst the prior 90-day ledger baseline
It separated genuine risk from noise in the ledger.
Finance Manager · BTR multifamily operator
01Pilot envelope
Pilot length5 weeks
First signal5 days
First ROI30 days
Team alongside4 seats · 2 colleagues

5-week finance pilot; mapped ledger ageing and approved resident comms; the colleague produced drafts and payment-plan candidates only.

02What it owns
Reports toFinance Manager, with property managers consulted on resident-specific context.
Owns
  • Daily at-risk list — every resident with an ageing or partial-payment signal, ranked with a documented reason by 9am
  • Ledger and gateway match — RealPage receipts reconciled against Stripe settlements, with partial payments and chargebacks called out
  • Approved-template comms drafts — reminder, partial-payment acknowledgement and payment-plan offers prepared for finance or resident support to send
  • Payment-plan candidates — proposed against ledger history and resident tenure; never offered without Finance Manager approval
  • Weekly arrears review pack — source-linked summary for the Finance Manager and property managers, with movement against the prior week
Does not do
  • Sending resident comms — drafts only, finance or resident support reviews and sends every outbound
  • Approving payment plans — proposes candidates only; the Finance Manager signs off every plan
  • Eviction or legal escalation — surfaces evidence; legal owns the decision and the action
Done looks like

Finance walks into Monday with a daily list of at-risk residents and approved drafts, not an Excel tracker. 30+ day arrears are visible the moment they form, and payment-plan offers are made earlier and from a shared template library.

03The team
AI teammates2
NoraReads RealPage ageing and Stripe settlements daily, matches partial payments and chargebacks against the ledger, and surfaces a ranked list of at-risk residents with a documented reason.
CallumDrafts approved-template resident messages for review, proposes payment-plan candidates against the ledger history, and queues outbound comms for finance or resident support to send.
Human team4
  • Finance ManagerFinance
  • 3 Property managersOperations
  • 2 Resident supportResident services
  • 2 Site leadsOperations
04Connected stack
RealPageStripeOutlookResident appExcelMicrosoft Teams
05What it returned
-14%30+ day arrearsAgainst the prior 90-day ledger baseline
47Payment-plan candidates surfacedReviewed by finance in the first 30 days; offers approved one-by-one
6 hrs/wkFinance admin removed per analystReallocated to plan reviews and resident conversations
  • Day 0
    Co-ordinator sessionFinance Manager, property managers and resident support align on ageing buckets, approved comms templates and the first three answerable questions.
  • Day 5
    First signalNora completes a read-only pass over RealPage ageing and 90 days of Stripe settlements; partial-payment mismatches are sized for the first time.
  • Day 12
    Read-only daily list liveDaily at-risk list lands in Teams; finance and property managers correct two reason codes and one ageing-bucket threshold.
  • Day 20
    Approval-gated draftsCallum drafts reminder and partial-payment acknowledgement messages from approved templates; finance and resident support send every outbound.
  • Day 26
    Payment-plan candidatesPlan candidates proposed against ledger history; the Finance Manager approves the first cohort and they are recorded back against the resident record.
  • Day 30
    ROI reviewSponsor signs off the three baseline metrics and approves expansion to the 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.