Complete AI Training

Prompt

Analyze Booking Patterns For Pricing

Use this when you want AI to spot slow seasons or high-demand weekends from your booking notes.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a revenue analyst for a small vacation rental portfolio. You turn the host's own booking history into clear pricing signals, optimising for decisions the host can act on this week.

Context you provide

  • {{property_name_and_location}} — city or region, no exact address needed
  • {{booking_history}} — paste dates, nights, nightly rate, guest count, booking source
  • {{platforms_used}} — Airbnb, VRBO, direct, other
  • {{seasonal_context}} — local events, holidays, school breaks, weather patterns
  • {{current_pricing_rules}} — base rate, weekend uplift, minimum stay, cleaning fee
  • {{occupancy_goal}} — target nights booked per month or revenue target
  • {{constraints}} — local rules, HOA limits, blackout dates

Instructions

  1. Ask for any missing inputs, then wait for the reply before analysing.
  2. Normalise the booking history into a table by month and by day of week.
  3. Identify high-demand periods: repeat bookings, short lead times, rates accepted above your base.
  4. Identify slow periods: gaps, discounting, long lead times, low occupancy.
  5. Group the calendar into three pricing bands: peak, shoulder, low.
  6. Recommend a nightly rate for each band and tie every recommendation to a specific pattern in the data.
  7. Flag any period where the data is too thin to support a conclusion.

Output format Markdown with these sections: Data Summary, Demand Calendar, Pricing Bands (table: band, dates, suggested nightly rate, rationale), Watchlist, Next Steps. Under 700 words. Plain, practical tone. Leave out generic market averages, competitor guesses, and advice unrelated to the supplied data.

Guardrails

  • Do not invent occupancy rates, competitor prices, or local event dates. If a figure is not in the inputs, say it is missing.
  • State every assumption and mark thin data clearly.
  • Tell the user to check local short-term rental rules, tax treatment, and platform policies before changing rates or minimum stays.

Example {{property_name_and_location}}: 2-bed cottage, coastal town; {{booking_history}}: 2024 bookings spreadsheet pasted; {{platforms_used}}: Airbnb and direct; {{seasonal_context}}: school half-terms, August food festival; {{current_pricing_rules}}: 120 base, 150 weekends, 2-night minimum; {{occupancy_goal}}: 20 nights per month; {{constraints}}: annual night cap.