If your product touches rates, demand, distribution or forecasting, the revenue manager is on your buying committee, and often the person who evaluates you first. Many vendors have never watched one work. They know the job title and the tools, but not the rhythm of the week, which is what decides when a call gets answered and which report your product has to beat.

What follows is a composite week, drawn from the revenue managers I have sold to and sat beside. The property is an independent hotel with around 120 rooms, where the revenue manager is one person who also covers two sister properties. Larger hotels split the job, but the shape of the week is the same.

Monday: pickup and the damage from the weekend

The day starts with the pickup report: which future dates gained or lost rooms since Friday, and how that compares with the same point last year. Three weekends in November have moved, one has gone backwards, and a group block that was supposed to be confirmed is still tentative. The revenue manager opens the booking engine, two OTA extranets and the rate-shopping tool, then changes rates and restrictions for the next 14 days before 10am.

For a vendor, this is the worst morning of the week to call. The revenue manager is making the decisions they will be judged on, and a message about a demo will be read on Wednesday if at all.

Tuesday: the forecast nobody wants to be wrong about

Tuesday is for the 30, 60 and 90 day forecast. It goes to the general manager and, at month end, to the owner, and it drives staffing in housekeeping and the restaurant. The revenue manager builds it from rooms on the books, pace, the events calendar and a feel for what the market is doing. A forecast that misses by a wide margin is the thing that gets questioned in the revenue meeting, so this is the number they care most about getting right.

It is also where the quiet frustration with software sits. The forecast is often assembled in a spreadsheet from exports out of three systems, because none of them agree with each other. The revenue manager has stopped mentioning this to vendors, for the reasons set out in the language gap between hotel tech vendors and operators.

Wednesday: the revenue meeting

The weekly revenue meeting brings together the general manager, the sales manager, the front office manager and, once a month, the owner's asset manager. The agenda is last week's results against budget, the forecast, group business and rate strategy. The revenue manager presents, and the questions are about numbers, not tools. Software is only named in this meeting when it has failed, such as a rate that did not push to a channel or a report that disagreed with the property management system.

A vendor who wants to be discussed here has to give the revenue manager a chart they can put on the screen that makes them look prepared. That is a different product requirement from a feature list, and it is close to what a general manager's day demands too.

Thursday: distribution and the thing that broke

Thursday is for channels: a rate parity check across the OTAs and the booking engine, the hotel's position in OTA search results, a look at which promotions are live and whether the channel manager mapping is still correct. This is often the day the revenue manager discovers that a connection broke on Monday and three days of rate changes never reached one channel. The afternoon goes to a support ticket and a manual fix.

That ticket shapes their opinion of every vendor they use. Response time on the day a connection fails counts for more than any feature, which is why integrations sell hotel software more than features do.

Friday: the weekend and the month

Friday closes the week. Weekend rates and minimum stays are set, the month-to-date figure is compared with budget, and at month end the owner's report is prepared. The revenue manager leaves knowing roughly whether the month will land, and spends part of the weekend watching pickup on their phone.

What they look at, and how often

What this means if you sell to them

• Name the report you replace. A revenue manager already has a pickup report, a forecast and a channel view. Say which one your product makes redundant, not which ones it adds.

• Respect the week. Monday morning and the hours before the revenue meeting are closed. Tuesday and Thursday afternoons are open.

• Speak in their measures. They are judged on revenue per available room against the comp set, on budget, and on forecast accuracy. Frame value in those terms, not in hours saved.

• Expect to be checked against the PMS. If your numbers and the property management system disagree, the PMS wins and your credibility pays.

• Count the maintenance. A tool that needs two hours a week of care from a person who covers three properties is a cost before it is a benefit.

The takeaway

The revenue manager's week is built around a few reports, one meeting and the things that break. A product that fits that rhythm, and gives them a number they can defend on Wednesday, gets evaluated. One that asks them to change the rhythm gets a polite trial and a quiet no.

If your deals stall after the revenue manager says yes, the leak is usually further up the buying group. The 12-point leak audit takes about twenty minutes and shows whether demand, conversion, activation or retention is costing you most.

Frequently Asked Questions