Hotel groups rarely buy everything at once. They start with one property, one product or one region, and the rest of the account sits there waiting for someone to ask. Most hotel tech vendors leave that conversation to chance: a customer success manager mentions a new module at the end of a support call, or a salesperson sends a price list after a press release. Neither works well with a group that has a procurement team, an owner to answer to and a long memory of vendors who oversold.

This post gives you copyable scripts for the seven expansion conversations that come up most with hotel groups and management companies. Edit the words in brackets, keep the structure, and use them on calls, in business reviews and in follow-up emails.

An expansion conversation is a planned talk with an existing customer, triggered by a real change in their business, that proposes more properties, more products or a higher tier and ties the proposal to an outcome they already measure.

Match the trigger to the script

Expansion headroom in hotel accounts is usually large. Agilysys CEO Ramesh Srinivasan said at a June 2026 William Blair conference that Agilysys customers use an average of 2.3 products per property, while eight or nine modules may apply to a typical property. The gap between those two numbers is what these scripts are for.

Script 1: The group is adding a property

Groups grow in public. When Lark Hotels chose Mews in 2024, the announcement said Lark planned to grow its portfolio by 6 to 12 new properties each year. Every one of those openings is an expansion conversation for each vendor in the stack. Call before the new hotel's tech decisions are made, not after.

"Congratulations on [new property]. When [first property] went live with us, the team got [result they measured] within [time]. Before the opening plan is locked, can we walk through what it would take to have [new property] live on the same setup for opening day? I can bring the rollout plan we used last time and a single price for the group."

If they say the new hotel comes with its own system:

"That makes sense, and we would not rip anything out mid-season. Would it help if I mapped what you lose in group reporting by running two systems, so you can decide at the next contract date rather than now?"

Script 2: The pilot worked, ask for the rollout

A pilot that succeeds and then stalls is one of the most common leaks in group selling. The fix is to agree the success test before the pilot starts, then use this script the week the property hits it. Our guide to account planning for hotel groups covers how to set that test.

"When we started at [pilot property] we agreed success meant [metric] by [date]. You are at [result]. The next step we discussed was [number] properties in [region or brand]. Shall we put a rollout date in the diary with your operations lead this week, so the properties go live before [peak season]?"

If the group sponsor wants to wait for a second pilot:

"Happy to. What would a second pilot need to show that the first did not? If we agree that now, we can run it at [property] and decide by [date]."

Script 3: The second product at a business review

Cross-selling works when the second product solves a problem the customer has already described. Use data from the quarterly business review and let the gap make the case. Vendors such as Cloudbeds describe their ongoing business reviews as a place to uncover new opportunities, and that is the right framing: discovery first, offer second.

"Looking at the last quarter, [metric, for example direct bookings or upsell revenue] is [figure], and your team told us [pain in their words]. That is the problem [second product] was built for. Would it be useful if I showed [GM name] how [comparable property type] set it up, and we agreed a trial goal before any contract?"

Pricing the second product is its own decision. See how to price a second product into an existing account before you quote.

Script 4: A management company takes on a new hotel

Hotels change hands often. Research by EHL published by CoStar found budget hotels had an average holding period of 4.9 years. When a new owner hires a management company you already work with, the operator often decides the stack. Talk to the person who onboards new hotels into their portfolio.

"You now run [number] hotels on [product]. When [new hotel] joins, we can add it to your existing agreement at the group rate, with the same onboarding team and reports your regional managers already use. Who on your side owns the onboarding checklist for new contracts, so we are on it from day one?"

Our guide to procurement at hotel management companies explains who signs and when.

Script 5: Speaking to the owner or asset manager

Owners and asset managers do not care about features. They care about revenue, cost and risk across the portfolio, so talk in those terms and keep it short.

"Across your [number] hotels on [product], we measured [result in money or rooms]. The [properties not yet on it] are running [current setup], which means [specific cost or blind spot]. Bringing them onto the same agreement would cost [figure] a year and, based on the current properties, we would expect [range, stated as an estimate]. Would you like the numbers by property before your next budget meeting?"

Script 6: "It is not in this year's budget"

Budget objections are often timing objections. Find out when the budget is set and get into it.

"Understood. When does [group] set next year's technology budget, and who prepares the request? If I send a one-page business case with the figures from [current properties] three weeks before that, would you put it forward?"

If the budget is set but the problem is urgent:

"Would a phased start help, with [first properties] this year and the rest on the same price from [date]? That keeps the cost inside this year and the group on one contract."

The business case itself should follow the format hotel owners approve.

Script 7: The follow-up email

Subject: [Group] next step on [properties or product]. Hi [name], thanks for the time today. What we agreed: [one line]. What [property] has achieved so far: [result]. Proposed next step: [action] by [date], owned by [name]. Attached: rollout plan and group pricing for [number] properties. If anything is wrong in this summary, reply and I will correct it before we share it with [sponsor].

What not to say

• "We have a new module you might like." Lead with their problem, not your release notes.

• "This price is only valid this month." Hotel groups have budget cycles; fake deadlines damage trust.

• "Everyone in your segment is using this." Name a comparable property type or say nothing.

• Promising results you have not measured. Use their own numbers or state an estimate as an estimate.

Why this conversation deserves a script

Expansion becomes a larger share of growth as vendors scale. ChartMogul's 2025 analysis of SaaS companies that reached $20 million ARR found expansion supplied 15.4% of net-new MRR at $1 million ARR and 34.7% at $20 million. SaaS Capital's 2025 survey reports median net revenue retention of 102% for companies with annual contract values between $25,000 and $50,000, and 111% for the top quartile. Net revenue retention counts upsells, cross-sells and price increases, so the gap between median and top quartile is built from conversations that happen on time, with the right person, using the customer's own data.

For the metric behind this, read net revenue retention for hotel software, and for how expansion fits with acquisition and renewal, see the hotel tech GTM system.

Want to know how much expansion revenue is sitting unasked in your current accounts? Book a free GTM leak audit and we will show you where the gaps are.

Frequently Asked Questions