The Renter Loop

Companion to the Rentiful Organisational Design. This file is the top-level overview; each domain has its own file under renter-loop/.

Vocabulary

This vocabulary is used consistently across the whole spec.

Term	Meaning
Loop	A full accountable chain from problem signal to closed outcome, owned by one person end-to-end.
Domain	A responsibility-shaped grouping of work within a Loop. Classifies the type of work being performed. Domains do not represent progression or goals.
Operation	The smallest executable, signal-driven unit in the system. Has signal, closed state, depends_on, and automation level. Operations are atomic units of execution in the operating model — deliberately named differently from `workflow` to avoid collision with the orchestration-tooling sense of that word (Temporal, Airflow, etc.).
Sub-loop	A problem-to-outcome chain inside a parent loop, owned by a different accountable person. Reserved for the rare case where ownership is genuinely split.
Conversation	The persistent, ongoing interaction with a single renter. May flow across multiple mediums (email, WhatsApp, web chat, phone) but is treated as one continuous thread. Conversations have state and history. Operations act on conversations.
Surface	A branded front-end through which renters enter the loop. Owned surface: rentiful.ai. Partner surfaces: operator-branded microsites produced through White Label.
Vehicle	A commercial configuration of the loops — standard marketplace, White Label. Sits orthogonal to loops: one Operator Loop and one Renter Loop serve all vehicles.

The discipline: do not call something a sub-loop unless it has its own distinct human owner. Do not describe interactions in terms of the medium when conversation is the more honest unit. The vocabulary stays meaningful by being used carefully.

Note on Journeys: A Journey is a goal-directed, ordered composition of Operations within a Loop, used to define progression toward a specific outcome. Journeys are an orthogonal overlay — they reference Operations rather than containing them, and they do not introduce ownership. The Journey construct is introduced in Commit 2 of the operating-model refactor; this Commit (1) establishes the spine.

See ADRs 0002 — Conversation as unit of interaction and 0003 — Concierge as defining feature for why these definitions exist.

The loop in one sentence

The Renter Loop is responsible for the whole chain from demand-generation spend to a signed, invoiced lease for a unit that genuinely matches what the renter needs.

On conversations

From the renter's perspective, they are not using channels — they are having a conversation with Rentiful, and they pick that conversation up wherever's convenient. They might ask a qualification question via web chat on Tuesday, receive a viewing reminder by WhatsApp on Wednesday, reply by email on Thursday. From the renter's side, all of this is one ongoing exchange.

Rentiful's design honours this. The unit of interaction is the conversation, not the medium. Operations act on conversations: they advance them, escalate them, branch them, close them. The medium each message happens to use is operational detail. The conversation is what carries state, history, and meaning.

This matters structurally because it makes Rentiful's interaction model honest. A renter is not "a web enquiry" or "a WhatsApp lead" — they are a person Rentiful is in conversation with, who happens to prefer different channels at different moments. Treating the conversation as the persistent thing makes everything downstream — automation, escalation, hand-off, diagnosis — work the way it should.

On surfaces

Rentiful's Renter Loop operates across multiple branded surfaces. The owned surface is rentiful.ai — Rentiful's own consumer brand, where renters encounter Rentiful directly. Partner surfaces are operator-branded microsites produced through Rentiful White Label — operator identity on the front, co-branded "powered by Rentiful," with Rentiful's matching engine, demand network, and conversation infrastructure underneath.

The loop mechanics are surface-agnostic. Signal, domains, operations, closed state, and owner are identical across surfaces. A renter who starts a conversation on a White Label site moves through the same qualification, matching, nurture, viewing, and signing path as a renter who starts on rentiful.ai. The loop owner's conversation with the renter continues through to lease signing on both sides, running in parallel with the operator's own execution work (viewings, referencing, lease paperwork).

What changes between surfaces is narrow and operational: the brand and domain the renter sees, the acquisition mix (a White Label operator may bring traffic from their own signage, social, or email footer), and the voicing of conversation messages (operator-branded with "powered by Rentiful" on partner surfaces; Rentiful-branded on the owned surface). Accountability, cross-loop dependencies, and closed-state discipline are invariant.

Surfaces are commercial configurations of one loop, not separate loops. The Renter Manager owns every conversation regardless of the surface the renter entered through. Treating surfaces as separate loops would break the single-accountable-conversation model.

Why concierge matching is defining

Rentiful is positioned as a concierge marketplace. The defining promise is not just access to listings — it is that Rentiful identifies the right unit for each renter and proactively surfaces it. This shapes every part of the loop:

Demand generation focuses on attracting renters who value the concierge experience, not just the broadest possible audience.
Qualification and matching are richer than a simple criteria filter — Rentiful learns enough about a renter to know what would actually be a great match.
Engagement is conversational and personal in tone, even when automated — every touch should feel like it came from someone who knows the renter.
Concierge process quality is a first-class set of metrics alongside throughput — the loop is judged on how it operates (responsiveness, profile-updating, honest brokerage, specific reasoning, escalation judgement, feedback-loop capture) as well as on signed leases. See ADR 0003 and renter-loop/metrics.md.

If concierge matching were ever quietly de-prioritised in favour of pure volume, the Renter Loop would become a generic portal funnel. The defining feature is the discipline that prevents that drift.

Domains at a glance

Domain	Purpose
Demand	Turning budget into qualified renter intent and started conversations
Initiation	Starting conversations, qualifying intent, building the renter profile
Matching	Proactive surfacing of units against active renter profiles — recurring digest and perfect-fit alert
Engagement	Keeping the conversation alive, on-context, progressing — nurture, in-conversation Q&A, stuck-conversation recovery
Conversion	Moving from expressed interest to signed lease — viewing coordination, lease execution handoff
Diagnostics	Producing signals that drive improvement across the business
Attribution	Cohort-level attribution of spend to lease and lease to cash
Platform-inputs	Specifying and validating platform changes that unblock the loop

Sub-loops

There are no sub-loops within the Renter Loop at present. The loop owner owns every activity directly. This is the correct state for the current scale of the business.

The candidates for future sub-loop creation, when volume justifies separate accountable owners, are anticipated here — not because they should be created now, but because anticipating the splits makes them cleaner when they do happen.

Candidate	Signal → Closed state
Acquisition Sub-Loop	Spend on channels → qualified conversation started. Likely first split, because paid acquisition can become a full-time discipline of its own at scale.
Conversion Sub-Loop	Qualified conversation → signed lease. The natural counterpart to Acquisition.
Concierge / Match Sub-Loop	Active conversation with profile → well-justified match identified and surfaced. As Rentiful's matching becomes more sophisticated, this could become a distinct discipline focused on the concierge process and its six quality dimensions per ADR 0003.
Account Management Sub-Loop	If Rentiful evolves toward repeat-renter relationships (renewals, referrals, cross-product), this could emerge.

Sub-loops should not be created prematurely. A sub-loop without a distinct accountable owner is just a chunk of work — naming it as a sub-loop adds organisational overhead without adding accountability. Wait until volume forces the split.

Cross-loop dependencies

The Renter Loop is internally self-contained — no handoffs inside the loop — but it depends on, and produces dependencies for, every other loop. The full dependency graph lives in cross-loop.md; summary here.

Other loop	What flows between
operator-loop	Receives: live, accurate, discoverable units, plus near-real-time notification of new units for perfect-fit matching. Provides: diagnostic signals on unit-level conversion patterns (pricing, representation, availability, data) and concierge-process friction attributable to supply-side issues.
platform-loop	Receives: shipped infrastructure (unified conversation, near-real-time supply, multi-brand config). Provides: specs for blockers, validation of shipped changes.
financial-loop	Receives: invoicing infrastructure, reconciliation. Provides: signed leases for invoicing.
strategy-loop	Receives: priorities and budget envelope. Provides: operational input for strategy cycles.

The two most important cross-loop dependencies

Renter Loop ↔ Operator Loop diagnostic feedback. The single most important cross-loop connection in Rentiful. The Renter Loop sees, in real time, which units convert and which don't, and which matches succeed or fail. The Operator Loop is the only place that can act on what those signals say. If this connection is weak — signals not produced, signals not received, signals not acted on — the marketplace stops compounding and starts decaying.

Operator Loop → Renter Loop new-unit notification. The perfect-fit alert operation is only possible if the Renter Loop is told about new and updated units from the Operator Loop in near-real-time. This is a hard dependency, not a nice-to-have. A new unit that takes hours to become matchable is a missed concierge moment for the renters who would have wanted it most.

What success looks like

Primary metrics

Signed leases per month at CAC < £350 per channel × bedroom, growing month-over-month. See renter-loop/metrics.md for the full north-star definition and CAC convention.
Concierge process quality — the six observable dimensions defined in ADR 0003 and instrumented in renter-loop/metrics.md. These are the leading indicator for whether the concierge mechanism is working in-flight.
Outcome quality (retention, post-move satisfaction, referral) is held as a future instrumentation target and is not currently claimed; see ADR 0003 · Outcome quality held for later.

Supporting metrics

Cost per acquired lease (CAC at the lease level, not at the conversation-started level).
Conversion rate at each funnel stage — conversation started to qualified, qualified to viewing, viewing to signed.
Cycle time from conversation start to signed lease.
Channel-level CAC and conversion.
Perfect-fit alert response rate — what fraction of perfect-fit alerts produce engagement, viewing, or signature.

Conversation health metrics

Time to first response on a new conversation.
Conversation continuity rate — fraction of conversations that maintain context cleanly across medium switches.
Escalation accuracy — when AI escalates to personal handling, how often is that the right call.
Active conversations in flight — the working inventory of the loop.

Leading indicators of loop health

Manual interventions per 100 conversations (should trend down as automation matures).
Conversation quality score — how well conversations are being conducted overall.
Diagnostic signals produced and resolved — feedback loop to other parts of the business.

Financial integrity metrics

Leases signed but not invoiced — must remain at zero.
Lease-to-cash cycle time — how long from signature to money in bank.
Revenue attributable to the loop per month.

What this loop is not

The Renter Loop owner is not a marketer. Not a salesperson. Not a customer success manager. They are the accountable owner of a chain that traditional organisations split across all three of those functions, with the additional twist that Rentiful's defining promise — concierge matching — sits inside this loop and shapes how every operation runs.

The breadth is the point. Anyone treating the role as just one of those functions has misunderstood it. Anyone hiring for the role using a marketing job description, a sales job description, or an ops job description will hire the wrong person.

Specifically, this loop does not include:

Operator acquisition, onboarding, or retention — operator-loop.
Unit-level quality improvements — specced by this loop, owned by operator-loop.
Platform architecture or product build — specced by this loop, owned by platform-loop.
Setting company strategy — strategy-loop.

Failure modes

The Renter Loop fails in predictable ways. Naming them now makes them cheaper to spot and easier to correct.

Splitting the loop prematurely. Separating acquisition from conversion re-introduces the CAC blame seam the merged loop was designed to eliminate.
The loop owner treating their role as marketing. Doing the parts they know (ads) and under-investing in the parts they don't (conversion, financial close, diagnostic feedback).
Optimising for conversation volume instead of signed leases. Vanity metrics at the top of the funnel that don't translate to revenue.
Optimising for signed leases instead of justifiable surfaces. The more dangerous version. Under this failure mode the concierge silently starts surfacing options that cannot be justified against the renter's current brief — the honest-brokerage rule degrades, the silence clause gets overridden by engagement pressure, and the damage shows up only later in retention, referrals, and brand. The failure tripwires in ADR 0003 exist specifically to catch this.
Concierge matching quietly becoming "just send a digest like everyone else." The loop drifts into being a generic portal funnel, and Rentiful's defining promise erodes.
Treating each medium as a separate channel rather than part of one conversation. The renter experiences fragmentation and Rentiful loses the concierge feel.
Acknowledging but not acting on supply-quality signals. Pointing at the Operator Loop without packaging the diagnosis effectively.
Running on autopilot once automation is built. The loop requires continuous diagnostic work, not just execution.
Founder absorbing gaps silently. When the loop owner is part-time or under-resourced, the founder takes on parts of the loop without naming it. The loop appears owned but actually has a hidden handoff.

Using this document

When something inside the loop is unclear or contested — find the domain, find the operation, ask whether the structure or the execution is the issue.
When considering a change to how the loop runs — check whether the change is at the operational level (small, frequent) or at the structural level (rare, requires updating this document).
When hiring for the loop or for an eventual sub-loop — the domains and operations here are the source material for the job specification.

Changes to this document should be deliberate and tracked. Changes to specific tools, automation platforms, or week-to-week tactics should not require updating this document — those live one layer below the operations described here.