Domain · Pricing and conversion signals

What it covers

Translating diagnostic signals from the Renter Loop into action by operators. When the Renter Loop sees that certain units are not converting, this domain is where that information becomes a conversation, a recommendation, and ideally a change.

Activities

• Surfacing unit-level conversion data to operators — which units work, which don't.
• Pricing feedback — flagging units mispriced relative to market or to converting peers.
• Availability feedback — flagging restrictive windows that suppress conversion.
• Representation feedback — flagging where photos, descriptions, or data block conversion.
• Unit-level conversion feedback — when a unit repeatedly draws interest but fails to convert, diagnosing why (pricing, representation, availability, or a data issue) and routing to the correct remediation operation.
• Negotiating changes — working with operators to improve the unit-level offer.
• Tracking acted-on signals through to outcome.

Operations

Signal intake operation

Diagnostic signal received from Renter Loop → categorised (pricing, availability, representation, data, unit-level conversion pattern) → severity and revenue-impact assessed → routed to the appropriate sub-operation.

Pricing recommendation operation

Pricing-flagged unit identified → comparison data assembled (market peers, converting equivalents, demand signal) → recommendation drafted → presented to operator → outcome (accepted, modified, declined) logged → re-tested in market.

Representation remediation operation

Representation-flagged unit identified → specific issue documented (photos, description, attribute) → operator engaged with concrete request → updated content validated → outcome tracked.

Signal-to-outcome tracking operation

Every signal sent to an operator → tracked through to a state (action taken / declined / no response) → conversion impact measured post-action → fed back into Renter Loop's diagnostics.

Notes

This domain is the connective tissue between the two primary loops. If signals are produced (Renter Loop) but never become action (Operator Loop), the marketplace stops learning. The discipline here is to close every signal: either action is taken, or the operator explicitly declines with a logged reason. Signals that disappear into a void are signals that won't be sent again.

Cross-loop surface

• Signal inputs come from renter-loop.d.
• Resolved-signal feedback loops back to the Renter Loop, closing the diagnostic cycle described in cross-loop.md.