05 · The owner one-pager | PriceLabs

Owner relations Single listing ~3 min Read-only

Who it’s for — and what to expect: you owe a homeowner an update and want it grounded, honest, and done in three minutes — a summary you can forward as-is. Expect a clean one-pager: what the property earned (counted by stays that actually happened, so this month’s update never contradicts last month’s), how its rate and occupancy compare to the market, three highlights, and one honest recommendation — with no guest names and no blended numbers.

Before you start

Same connection; new chat; read access is enough.

The prompt

Copy-paste as one message:

The owner one-pager

Create an owner-ready performance summary for my listing [ID] on [your PMS].
Use these PriceLabs tools: get_listings, get_listing_performance_metrics, get_pms_reservations, and get_neighbourhood_data (summary) for market rate context.
Rules: count stays that happened in the last 3 months, not bookings made; use bookings-only occupancy — owner-blocked nights aren't demand; exclude cancelled reservations; do not include guest names or contact details; if any tool aggregate doesn't reconcile with your stay-window sum, say so explicitly.
Output: a clean one-pager I can forward to the homeowner — a results table (stays, nights, revenue, my achieved nightly rate vs the market's booked median, my occupancy vs the market's), three highlights, one honest recommendation, and short data notes.

Pro tip

The “stays that happened, not bookings made” rule is the whole recipe — the two revenue numbers can differ by 50%, and owners notice when updates contradict each other.

Goes well with: The full picture · The monthly report