🔥 New · RM Copilot 2.0 - Voice mode is live
Match. Hold. Test ceiling. Every comp move classified with the demand signal that drove the call - and pushed into pricing within the same 15-minute cycle.
Most rate-shopping tools generate data, not decisions. Operators export a CSV, cross-reference the forecast, decide hold-vs-match in their head, and re-key the result into the pricing tool. RevEvolve closes that loop: comp moves classify automatically against your forecast and inventory state, the action signal feeds pricing in the same cycle, and parity violations on your own rates surface within minutes of the drift. No more morning rate-shopping ritual.
Definition
Competitive rate intelligence (CRI) for hotels is the practice of monitoring competitor rates across major distribution channels - OTAs, GDS, brand.com - and integrating those moves into pricing decisions. Modern CRI classifies each comp move (Match / Hold / Test ceiling) against the operator's forecast and inventory state and pushes the recommendation into the pricing engine in the same cycle.
Standalone rate shoppers produce a daily PDF or CSV of comp rates. The operator opens it, eyeballs the variance, decides whether to follow, lead, or hold - and then re-keys the result into the pricing tool.
That's a 90-minute morning ritual that produces no defensible audit log. RevEvolve eliminates the ritual: every comp move ships with a classified action and the demand signal behind it, and the pricing engine reads the result in the same cycle.
Most rate grids show 30 cells of red and green and ask the operator to rank them. CRI ranks them automatically - by projected revenue impact - and surfaces only the moves where action is warranted, with the action attached: Match (follow), Hold (ignore), or Test ceiling (lift while comp is below).
The classification reads from the forecast, the comp hotel's behavior class, and your inventory state. Not a heuristic - a defensible signal you can show ownership.
How CRI works
Seven inputs, classified outputs, real-time cadence, three reasons to trust the result.
Up to 8 hotels per property. You define them - not a vendor proxy. Edit anytime; new comp set rates start collecting within 15 minutes.
Booking.com, Expedia, Agoda, Hotels.com, Hotelbeds. Refreshed every 15 minutes for each comp hotel and each rate plan available.
Each comp hotel's own brand.com - the rate the operator actually controls. Often diverges from OTA rates and matters for parity analysis.
BAR, member-only, mobile-exclusive, advance-purchase. The system separates these so a member-rate drop doesn't trigger a public-rate match recommendation.
Min-stay, max-stay, advance-purchase fences detected on each comp hotel. Restrictions matter for whether a competitor's low rate is actually accessible.
Each comp hotel's own move history - leader, follower, or noise. Behavior class informs whether a single drop is worth matching or holding through.
Read from the AI demand forecast and PMS state. "Match the drop" never recommended when your forecast shows demand strength the comp set hasn't priced in.
15-minute triggers
OTA + direct surface refresh. Every comp hotel rechecked across every channel. New moves → action signal generated within the same cycle.
Real-time triggers
Parity violations on your own rates. Detected within minutes of the drift, before the OTA contract penalty window.
Daily triggers
Comp hotel behavior re-classification. Leader / follower / noise tags update with the latest 90-day move history.
On forecast change
When your forecast tightens or loosens, ceiling-test opportunities re-evaluated against the new demand state.
Every comp move is classified Match, Hold, or Test ceiling - with the demand signal that drove the call. Operators stop scanning rate grids and start acting on the moves that matter.
When the comp set moves, the pricing module reads the new state in the same 15-minute cycle. You don't export a CSV and re-key into a separate tool. The recovery action is one approval click away.
Up to 8 hotels per property, defined by you. Edit anytime; new comp rates start collecting within 15 minutes. Behavior history follows the comp hotel, not the proxy.
Operator use cases
Tuesday 11:14 AM. One of your 5 comp set hotels drops weekend rates by $40 in a 90-minute window. The reflexive response - match the drop - would tank your weekend ADR by ~$28K vs forecast.
CRI classifies the move as Hold. Driver attribution: "Single hotel out of 5. Historical behavior class: noise (12 erratic moves in 90 days). Your forecast is tight, comp set average is +$22 above your rate. No structural reason to follow." RM holds rate. Two days later, the lone hotel walks the cut back. Your weekend closes on forecast.
Without classification, every comp move is a 90-minute analyst exercise - pull the rate shopper, cross-reference your forecast, manually decide hold vs match, then re-key the decision into the pricing tool. Most operators reflexively match drops to be safe and leak revenue every time.
Thursday 8:42 AM. 3 of your 5 comp set hotels lifted weekend rates +$22 overnight. Your current rate is $18 below the new comp set average. Your forecast shows weekend pace strong.
CRI classifies the moves as Test ceiling. Alert: "Majority comp set move. Comp average now +$18 above your rate. Forecast confidence high. Ceiling-test opportunity: lift +$14, leaves $4 buffer below comp average." Pricing module reads the signal in the same cycle and queues the recommendation. RM approves in 30 seconds. Weekend pickup holds; ADR closes +$11 ahead of baseline.
Standalone rate shoppers tell you the comp set moved. They don't tell you whether to follow, lead, or stay put. The decision happens in your head with no defensible math attached for the next ownership review.
Friday 3:18 PM. Your rate plan auto-update pushes a $12 lower rate to brand.com but misses the OTA push. Within 18 minutes you're in a parity violation that, if unaddressed for 72 hours, triggers a rate-parity penalty on the OTA contract.
CRI detects the divergence between brand.com and OTA rates within the next refresh cycle. Parity alert fires immediately to the RM and the GM. Recommended action: "Push brand.com rate up to OTA parity OR push OTA rate down - choose the protective side based on your demand state." RM resolves in under 5 minutes.
Most operators discover parity violations in the OTA penalty notice 72 hours later - losing the override window AND the contract clean record. Manual nightly parity audits catch most but miss the 4-hour drift windows that count.
The dashboard
Your property and up to 8 competitors across 14 forward dates. Each cell shows the current rate, your delta vs comp average, and the parity state. Color-coded by action signal - green Match / amber Hold / blue Test. Hover any cell for the move history and behavior class of the comp hotel.
Today's comp moves ranked by projected revenue impact in dollars. Each alert shows the comp move, the action signal, the demand context, and a one-click drill-down to the rate grid. The 3 highest-impact moves pin to the top - operators act here, not in the grid.
Each comp hotel classified leader / follower / noise based on 90-day move history. Leaders set rates the market follows; followers chase; noise hotels move erratically and shouldn't drive your decisions. Class informs whether a move is worth matching.
Every comp move, your action signal at the time, and what happened to RevPAR after. Builds the playbook over time and gives ownership a defensible record of comp set engagement.
Platform integration
Comp moves don't live in a CSV. They feed pricing, pace, channel mix, what-if scenarios, reporting, and the portfolio view - in one cycle.
Feeds into. When a comp move classifies Match or Test, pricing reads the signal in the same 15-minute cycle and queues a rate recommendation with the comp position attached.
Learn moreReads from. Forecast tightness shapes the action signal - "Hold" requires forecast confidence, "Test ceiling" requires forecast strength.
Learn moreFeeds into. Pace anomalies classified as comp-driven pull from the CRI behavior log so the recovery action explicitly addresses the comp move.
Learn moreBidirectional. Comp set channel mix informs your channel strategy. Your channel inventory state informs whether a comp drop changes your effective rate position.
Learn moreBidirectional. Run "what if comp set drops $30" scenarios against the live state. Simulator results push back as new threshold candidates for the action engine.
Learn moreFeeds into. Comp set audit log is the spine of weekly comp-position reports. Owners see what moved, what you did, and what happened.
Learn moreFeeds into. Multi-property operators see comp position aggregated across portfolio - which properties are above market, at market, and below.
Learn moreCompared
| Capability | Manual rate shop | Standalone shopper | Single Enterprise RMS | RevEvolve |
|---|---|---|---|---|
| Refresh cadence | Manual rate shop · daily | Hourly to nightly | Daily batch | Every 15 minutes |
| Output format | Spreadsheet + screenshots | Exportable CSV | In-tool dashboard | Action signal · Match / Hold / Test |
| Pricing integration | None - manual re-key | None - manual re-key | Same vendor, separate data layer | Same data layer · same-cycle recompute |
| Behavior classification | Tribal knowledge | Not provided | Limited (advanced tier) | Leader / follower / noise - per hotel |
| Parity violation detection | Nightly audit (most missed) | Nightly · alert only | Variable | Within minutes of drift |
| Comp set definition | Operator-defined | Vendor proxy or operator-defined | Operator-defined | Operator-defined · up to 8 hotels |
| Defensible audit log | Email chain | Limited | Available - analyst-built | Built-in · ownership-ready |
A 22-property independent management company in the Midwest replaced a standalone rate shopper with RevEvolve's integrated CRI. The morning workflow - pull the rate shopper, cross-reference forecast, decide hold-vs-match, re-key into pricing - collapsed into reading 3 alert chips on the briefing. Average time on comp-set engagement: 90 minutes per property per day to roughly 8 minutes.
90 → 8 min
Daily comp-set engagement time
+13.7%
RevPAR vs prior 30-day baseline
22
Properties on one comp set engine
I used to start every morning by pulling the rate shopper, eyeballing 30 cells, and trying to decide what to do about each one. Now I read the alert feed - three chips, three actions, math attached. The rest of the grid is there if I want to dig in. Most days I don't need to.
FAQ
Walk through your actual configured comp set with the prior 7 days of moves. We'll show you which alerts triggered Match, Hold, or Test ceiling - and what the recovery action would have been. Bring a recent comp move you couldn't defend.
Comparing comp set tools? See the side-by-side at /compare/ - or run the numbers at /roi-calculator/.
