When should you use it?
- You are an agent or team lead who scans new listings every morning
- You want price reductions surfaced with context, not just alerts
- You'd like draft outreach you can edit rather than write cold
Not for: Markets where you can't legally obtain listing data the way you plan to; Sending outreach automatically to sellers or other agents
What do you need, and what do you get?
You need
- A permitted feed or export of yesterday's new and changed listings
- Your buyer criteria or farm area
- Your preferred tone for outreach
You get
- Top five listings for same-day showings with one-line reasons
- Price changes ranked by size and days on market
- Three draft scripts you edit before sending
How does it work, step by step?
- Get the listings legallyUse your MLS export, a listing API you are licensed for, or saved-search emails; site scraping may break terms of service.
- Define what makes a showing worth itWrite your buyers' must-haves, price band and areas so picks are ranked against real demand.
- Flag motivated sellersAsk for reductions, relists and long days on market, each with the numbers shown.
- Draft, don't sendHave it write three short scripts per brief, and send them yourself after checking facts.
- Schedule itRun it before your day starts so the brief is waiting at the same time each morning.
The prompt
Our own prompt, inspired by 0xAI42exe (@0xAI42exe) and written to work in Claude, ChatGPT and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here are yesterday's new and changed listings for {market}: {listings}. My buyers want: {buyer_criteria}. 1) Pick the five listings most worth showing today and give one sentence each tied to the criteria. 2) List price reductions and relists, sorted by percent reduced, with days on market and prior prices. 3) Draft three short outreach messages ({tone}): one to a buyer, one to a listing agent, one to a past client. Use only facts from the listings. Mark anything I must confirm before sending.
Inspired by 0xAI42exe (@0xAI42exe): He sells real-estate agents one email a day and cleared $10,237 last month. No license, no ads, no face.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Revenue figures in the original post are the poster's claims; build this for your own workflow before thinking about selling it.
- A price cut is a signal, not proof of motivation; check history before using it in outreach.
Our take
Strip away the income screenshots and there is a genuinely useful daily job here: turn yesterday's listing changes into a short, ranked page with reasons. Agents already do this by hand, inconsistently, and the brief format forces the model to commit to five picks and explain each one. The quality depends almost entirely on two inputs, a clean listing feed and a clear description of what your buyers want, so spend your setup time there. Be careful about the data source; scraping a portal can violate its terms, while your MLS or a licensed API won't. Keep the outreach scripts as drafts, because a wrong square footage or a tone-deaf note to a seller lands on your reputation, not the model's. After a couple of weeks, compare the brief's picks with the homes you actually showed and adjust the criteria. If you later sell this as a service, as the post suggests, every agent will need their own criteria rather than one generic list.
Where the time goes back: It replaces a morning of scrolling listing sites with a ranked page and drafts you only need to edit.
FAQ
Do I need a scraper?
Should the scripts be sent automatically?
Source and credit
Inspired by 0xAI42exe (@0xAI42exe). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- He sells real-estate agents one email a day and cleared $10,237 last month. No license, no ads, no face.
- Creator
- 0xAI42exe (@0xAI42exe)
- Published on
- X
- Original date
- Jun 17, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.