When should you use it?
- You host one or a few rentals
- Pricing is set and forgotten
- You want a regular check-in on performance
Not for: Large portfolios already on a pricing tool; Listings where you cannot change prices yourself
What do you need, and what do you get?
You need
- Listing calendar and past bookings
- Your minimum and maximum nightly rates
- Local events calendar
You get
- Weekly report: occupancy, rate, upcoming gaps
- Suggested price changes
How does it work, step by step?
- Set guardrailsDefine your floor and ceiling rates and minimum stay rules.
- Pull the numbersEach week, gather bookings, nightly rates and open dates.
- Spot gaps and peaksFlag empty dates and nights with local events.
- Suggest changesPropose specific price moves within your guardrails.
- ApproveApply the changes you agree with in the platform.
The prompt
Our own prompt, inspired by madaxe_again on Hacker News and written to work in Claude Cowork, ChatGPT agent and Grok Bot. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Weekly rental review for {listing}. Guardrails: floor {min_rate}, ceiling {max_rate}, minimum stay {min_nights}. Report occupancy and average rate for the last 7 days, list open dates in the next 30, note local events, and suggest specific price changes within the guardrails with a reason each. Do not change prices.
Inspired by madaxe_again on Hacker News: Hacker News comment on agents running life admin. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Unbounded automated pricing can underprice peak nights; always set limits.
- Comparisons with other listings must be like for like.
Our take
Pricing is where many small hosts leave money on the table, mostly because nobody looks often enough. A weekly report with suggested changes is a gentle way to bring an agent in, since you keep the final yes. madaxe_again lets an agent manage nightly pricing; we kept the weekly report and put an approval step in front of any price change, which suits most small hosts better. Set a floor and ceiling rate and minimum stay rules first, since unbounded automated pricing can underprice the nights that matter most. Each week the report should show bookings, nightly rates, empty dates and nights with local events, then propose specific moves within your limits. Comparisons with other listings only help when they are genuinely similar in size, location and quality. Apply the changes you agree with yourself in the platform. Do not give the agent payout or account control, and keep tax records separate from this report. Larger portfolios already on a pricing tool will gain little.
Where the time goes back: The weekly pricing review happens without you opening the dashboard, and you only approve the changes.
FAQ
Did it raise revenue?
Should it change prices automatically?
Source and credit
Inspired by madaxe_again on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on agents running life admin
- Creator
- madaxe_again on Hacker News
- Published on
- Hacker News
- Original date
- Oct 12, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
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 24, 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.