A vendor closes a happy pilot at a hotel, learns that the property is run by a management company with forty more in its portfolio, and starts imagining the rollout. Then the general manager says the decision has to go through head office. Head office asks for a security questionnaire, a standard contract review and a conversation with the owner's asset manager. Months pass. The vendor concludes that management companies are slow. They are not slow so much as layered, and each layer is asking a different question.

This is an explainer of how buying software works inside a hotel management company: who is involved, the order things happen in, and what each step is for. Once the structure is clear, most of the delay becomes predictable and some of it becomes avoidable.

Who actually pays

A management company runs hotels it usually does not own. Each hotel belongs to an owner, sometimes a family, sometimes a fund, sometimes a developer, who has signed a management agreement. The management company directs the staff and the standards. The owner pays the operating costs, including most software, out of the property's budget.

That split is the root of most confusion. The management company decides what is allowed. The owner decides what is paid for. The general manager decides whether it gets used. Why hotel owners and operators want different things from software covers the tension between the last two. Inside a management company there is a third party in the middle.

The people involved

Not every company has all of these as separate people. In a smaller management company one person might hold three of the roles. But the questions do not go away, they are just asked by fewer voices.

How a purchase usually moves

1. Interest starts somewhere. A general manager sees a product at an event, a regional director hears about it from a peer, or head office runs a review of a category such as revenue management. Where it starts decides who will champion it.

2. The central team decides whether to look. If the category already has a standard system, the answer is often no until that contract comes up for renewal.

3. Security and integration review. A questionnaire, sometimes a call with the vendor's technical lead. The question is whether the product will create work or risk for a small central team supporting many properties.

4. A trial at one or two properties. Chosen by head office, often the properties with the most capable general managers.

5. Contract review. Usually a master agreement negotiated centrally, with properties signing on under it.

6. Approval at portfolio level. The system is added to the approved list or named as the standard for that category.

7. Owner approval, property by property. Each owner is asked to fund it. Some agree quickly, some wait for their next budget, some refuse.

8. Rollout. Property by property, often in waves timed around each region's low season.

Steps 3 to 6 are where vendors expect speed and find patience instead. Step 7 is the one they forget entirely, and it is why a portfolio approval rarely turns into every property paying in the same quarter.

The approved vendor list

Most management companies of any size keep a list of suppliers that have passed their review. Being on it does not guarantee sales. It means a general manager can buy without restarting the security and contract conversation. Being off it means every sale to a property in that portfolio has to go back to head office.

Lists are usually reviewed on a cycle, and a category with an existing standard is hard to break into mid-contract. The practical consequence is that timing matters as much as product. Knowing when the incumbent's contract ends is worth more than another demo.

Mandated or recommended

Management companies differ in how hard they push their standards. Some mandate a single system per category across every property, often for reporting reasons. Others publish a recommended list and let owners and general managers choose within it. A few leave most decisions to the property.

• Mandated: one long sale at head office, then a rollout. High value, slow start, high switching cost for whoever wins.

• Recommended list: head office gets you on the list, then each property is a short sale. Your sales team needs to sell to general managers as well as to head office.

• Property-led: close to selling to independents, except that head office can still veto, so keep them informed.

Ask which model applies on the first call. It changes who you need in the room and how you forecast the deal. The difference between selling to a hotel and selling to a hotel group covers the forecasting side.

Where vendors get stuck

• Treating the first property's enthusiasm as portfolio approval

• Sending a security questionnaire back weeks late because nobody owns it

• Negotiating a contract that suits one property and then having to renegotiate for the portfolio

• Never meeting an owner, and being surprised when owners decline to pay

• Rolling out in peak season because head office approved in spring

The takeaway

Procurement inside a management company is three decisions stacked on top of each other: head office decides what is allowed, owners decide what is funded, and general managers decide what gets used. Map all three on the first call, find out whether the company mandates or recommends, and learn when the current contracts end. Vendors who build that into their process often go on to build a partner programme with management companies rather than selling to them one deal at a time.

If management company deals keep stalling after a promising pilot, the 12-point leak audit takes about twenty minutes and shows whether the leak is in conversion or somewhere earlier in the funnel.

Frequently Asked Questions