STR Self-History Pricing Model

    1

    A nightly pricing model that prices each short-term rental only from its own trailing-12-month achieved stays, with floors, ceilings, and holiday and far-forward overlays.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    STR Self-History Pricing Model

    Example session with this skill installed

    Run the pricing model for the Beach House listing. Pull the trailing-12-month history, calculate the three factors including the DOW residual, and apply the holiday overlay for the upcoming month.

    • Read your context and instructions
    • Compiled the str self-history pricing

    I have completed the pricing run for

    Beach House. Input A (TTM History) and Input B (Live Calendar) were successfully refreshed.

    Pricing Run Results: Beach House

    Date RangeBase PriceFactors (DOW/Sea/Pace)OverlayTarget PriceStatus
    2026-12-01 - 2026-12-03$250.000.92 / 1.10 / 1.00None$253.00Verified
    2026-12-04 - 2026-12-05$300.001.15 / 1.10 / 1.00None$380.00Verified
    2026-12-24 - 2026-12-26$300.001.12 / 1.15 / 1.00Holiday (1.25x)$483.00Verified

    Parameter Summary

    • TTM ADR: $285.00
    • 10th Pct Floor: $210.00
    • Pace Delta: -4% (Factor: 1.00)
    • DOW Source: Own (82 stays)
    • Seasonal Source: Own (Smoothed)
    • Holiday Window: Christmas (Dec 24-26) + 3-night minimum applied.

    Notes: The ceiling was not triggered on any dates. The holiday overlay (1.25x) successfully bypassed the standard ceiling for Dec 25th as per the safety rules.

    Next steps

    1. Review the Floor-bound report; 4 dates in early December are sitting at the $210.00 historical floor.
    2. Confirm the 3-night minimum for the Christmas window has synced to your Channel Manager.
    3. Perform the twice-weekly revenue review on Monday to assess the impact of these new rates.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most pricing tools price your home off other people's homes — and quietly sit at their minimum-price floor on some listings while chasing single-date spikes on others. This pack is a complete alternative: a nightly pricing model that prices each home only from its own trailing-12-month achieved stays. For every open date, the target is the home's base price × a day-of-week factor × a seasonal factor × a booking-pace factor, clamped between a floor (the home's 10th-percentile achieved nightly ADR) and a ceiling (the higher of 2× base or its best-ever achieved night). You get the exact math for every piece: building night-level achieved history from your reservations, normalizing the weekday and monthly curves, the circular smoothing that keeps one noisy month from whipsawing its neighbours, and the pace bands that nudge a whole listing up or down against its own realized occupancy. Two details separate this from a naive spreadsheet: the residual method — if your base price already carries a weekend pattern, the model divides it out instead of double-counting the weekend uplift — and the fallback thresholds that decide when a home's history is thick enough for its own curves (≥30 stays for weekday, ≥50 for seasonal) and when it borrows the portfolio's instead. On top of the formula sit the two standing overlays, specified in full: the holiday rule (every US federal holiday, day before/of/after at ≥125% of the model's non-holiday price, plus a raise-only 3-night minimum that also covers the night before the window opens) and the far-forward premium (every date 12+ months out at 125% of baseline), non-stacking, with the overlay explicitly beating the ceiling. Then the operating system around the model: a daily dry-run → grouped-range apply → verify-every-written-date cycle, a twice-weekly review judged on pace, ADR, and revenue, the base-price sanity check that catches the one input that can silently misprice an entire calendar, and the failure modes that wreck pricing setups in the real world — two systems fighting over the same dates, and the premium that compounds daily because it was computed off the current price instead of a fixed basis. The limitations section is equally direct: no event calendar, a known bias in the pace benchmark (explained, with the cleaner v2 benchmark named), and a validation status stated for exactly what it is — a full dry-run comparison against an incumbent dynamic-pricing tool, not a promised revenue lift. Includes a per-listing parameter sheet, a daily run checklist, a review scorecard, and a copy-ready holiday-window definition.

    No event awareness. Pace benchmark skews negative. ADR for long-stays is diluted. Requires manual base price sanity checks. No revenue-lift guarantees.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Permissions

    Network Access
    Listedtoday

    What's inside

    Frequently Asked Questions

    Traditional tools often use 'market data' from neighbors who might not be booked; this model ignores the noise and anchors your rates exclusively to the actual revenue your specific unit has generated over the last 12 months.

    The logic is platform-agnostic and can be integrated with any PMS or AI agent framework capable of processing JSON/CSV data and interacting with calendar APIs.

    You receive the complete logic system, including the three-factor math formulas, the seasonal smoothing algorithms, the safety clamping rules, and the verification routine for calendar syncing.

    Setup involves connecting your 365-day booking history and current calendar data to the model; the system includes fallback rules to handle properties with thinner data sets.

    The model focuses on stability and historical realized value; it does not automatically scan for one-off local events or festivals unless they are already reflected in your year-over-year historical data.

    The built-in verification routine performs a dry-run before every execution and re-pulls the calendar after updates to ensure the written rates perfectly match the model’s targets.

    New in Business & Operations