operating-model / loops/operator-loop/health.md
id: operator-loop.healthtype: domainstatus: activeversion: 2.0loop: operator-loop

Domain · Operator health and retention

What it covers

Keeping signed operators active, engaged, expanding, and renewing. This is the relationship-and-commercial domain, distinct from the unit-and-data domains above. Critically, operator health is in service of unit-level outcomes — not an end in itself.

Activities

  • Regular check-ins with operators — commercial, operational, relational.
  • Monitoring operator-level activity — adding units, confirming leases, responding to signals.
  • Renewal conversations — held ahead of contract renewal points.
  • Expansion — bringing more of an operator's inventory onto Rentiful.
  • Identifying and acting on churn risk early.
  • Maintaining the commercial relationship.

Operations

Monthly operator check-in operation

Scheduled monthly touchpoint per operator → standing agenda (unit performance, signals, commercial, expansion) → conversation held → outcomes logged → actions assigned. The drumbeat of operator engagement. A check-in that doesn't touch unit performance is just a chat.

Operator health scoring operation

Operator-level signals continuously aggregated (activity level, signal responsiveness, financial close compliance, lease volume trend) → composite health score → segments operators by status → at-risk operators escalated for intervention.

Churn-risk intervention operation

At-risk operator identified → root cause diagnosis (commercial, performance, relational, market) → intervention plan → execution and tracking → status re-assessed.

Expansion operation

Expansion opportunity identified (operator has off-platform inventory, or new acquisitions) → commercial proposition prepared → conversation held → expansion onboarded through Area B's operations.

Renewal operation

Approaching renewal point → renewal preparation (performance review, commercial review, market context) → renewal conversation → renewed terms agreed and documented, or planned exit. Started well in advance of renewal date.

Notes

The discipline in this domain is resisting the gravity of relationship-work-for-its-own-sake. Operator health is in service of unit-level outcomes; it is not the outcome. A monthly check-in that doesn't surface unit performance, signal action, or commercial reality is a missed opportunity. Operator happiness is a lagging indicator of the loop doing its job — not a leading indicator, and not a substitute for it.

Cross-loop surface

  • Health scoring consumes signals from Area G (financial-close compliance) and Area E (signal responsiveness).
  • Expansion operation feeds back into Area B onboarding for the new inventory.
Comment on GitHub →