How our hotel demand forecasting tool works (methodology)

It helps hoteliers ask: “What external demand pressure should we discuss for this city and date window?” The output is meant to frame pricing and restriction conversations—not to replace your PMS pace report.

The tool combines user-selected city/context inputs with structured demand cues available to the product (such as calendar-style demand markers and publicly oriented demand proxies configured for the experience). Exact feature availability can evolve; the constant is transparency: treat outputs as directional signals.

We do not claim secret access to OTA extranet demand curves you did not authorize, and we do not publish fake accuracy percentages.

• You provide: market, dates, and any property context the UI asks for
• Tool provides: organized demand cues + interpretation prompts for operators
• You still own: BAR decisions, floors/ceilings, and channel pushes

Do not use it as the sole input for autopilot pricing. Do not treat it as audited financial forecast for lenders. Do not ignore your on-the-books group blocks—those often dominate a specific hotel even when the city looks soft.

Open the tool before the revenue huddle, note 2–3 demand cues for the next 14–28 days, compare against your pace, then decide actions. Log what you changed so you can learn whether the cue was useful.

The free tool is an education and planning surface. The AI Revenue Manager agent is the productized, policy-governed specialist on the HMS property model. Use the tool to sharpen judgment; use the agent when you are ready for in-stack recommendations and execution modes.