Paste the week's showings, feedback, portal stats, and comp moves; get a diagnosis, a hold-fix-or-cut verdict with reasoning, and the seller update email, drafted.
The idea
What this does
After launch, sellers hear silence and imagine the worst, and the price conversation arrives armed with feelings. This prompt turns the week's fragments (showing count, feedback quotes, portal views and saves, what competing listings did) into a diagnosis: is this a traffic problem, a conversion problem, or a market problem, and what specifically to do about it. Then it drafts the seller update in your voice. Run it weekly and the dreaded price-cut conversation becomes a data review you have been sharing all along.
Gather these first
Before you start
The week's numbers: showings, portal views and saves from your listing reports, days on market
Feedback quotes, verbatim, however thin
What happened in the competition: new listings, price cuts, pendings in your segment
Honesty about the sample size; two showings is a whisper, not a verdict
Step by step
How to use it
Keep one chat per listing, named for the property; add each week to it so the trend builds.
Copy the prompt, paste the week's data into the brackets, and send.
Read the diagnosis before the recommendation; the "which problem is this" step is the value.
Edit the seller email lightly (it is your voice, your call) and send it the same day.
Copy everything in the box
The prompt
Paste this into your AI toolFill anything in [BRACKETS] with your details
You are a listing-performance analyst for me, a listing agent. Diagnose this week and advise. Be honest about sample size: with thin data, say "too early to conclude" and tell me what would change that, rather than forcing a verdict.
THE LISTING: [ADDRESS], listed [DATE] at [$PRICE], now day [N]. Typical days-to-offer in this segment right now: [YOUR NUMBER or "unknown"].
THIS WEEK'S DATA:
- Showings: [N this week, N total]
- Feedback, verbatim: [PASTE QUOTES, however brief]
- Portal stats: [views, saves, whatever your reports show]
- Competition: [new listings / price cuts / pendings in the segment, with prices]
- Anything else: [open house traffic, agent calls, lender inquiries]
Produce:
1. THE DIAGNOSIS. Which problem does the evidence point to: TRAFFIC (not enough people looking: reach, photos, price band visibility), CONVERSION (looking but not offering: price versus condition, a specific blocker in feedback), or MARKET (segment-wide slowdown the comps confirm). Show the reasoning; if the evidence splits or the sample is thin, say so plainly.
2. THE VERDICT. Hold, fix something specific, or adjust price, with reasoning. If price: a recommended adjustment RANGE anchored to the competition data I gave you, plus the case for one decisive move versus a slow bleed of small cuts.
3. COST OF WAITING. In this segment, what another two weeks of staleness typically does, reasoned from the data available, labeled as a rough estimate.
4. WHAT WOULD CHANGE THE VERDICT. The two or three data points next week that would flip this analysis, so we know what we are watching for.
5. THE SELLER EMAIL. A warm, plain weekly update for my seller: what happened, what it means, what we are doing, no blame, no panic, no hype. Written so that if a price conversation is coming, this week's email makes next week's conversation unsurprising.
Rules: use only the data I provided; do not invent market statistics. Distinguish evidence from interpretation. Sample-size honesty beats confident noise.
→Anything in [BRACKETS] is yours to fill in. Delete a bracket line if it does not apply;
the prompt still works.
The result
What you'll get back
A traffic-conversion-market diagnosis with visible reasoning
A verdict with a range and the decisive-cut-versus-slow-bleed case made explicitly
The "what next week would tell us" list that makes this a system, not a mood
A seller email that builds the trust the eventual price conversation spends
Level it up
Make it yours
Paste last week's chat summary forward each week, or keep one running chat so the trend analysis compounds.
Before listing, ask "pre-draft the week-one and week-two seller emails for likely scenarios" and you will never scramble.
If feedback keeps naming one fixable thing, jump to playbook 17's logic for the fix-versus-credit call.
Keep it honest
Thin data weeks deserve "too early" and the prompt demands it; resist the urge to squeeze a verdict from two showings.
The verdict is advice; the seller decides, and your local read outranks the analysis when they disagree.
Keep feedback quotes verbatim in your records; paraphrase drifts, and drift compounds weekly.