There is one objection that stops more hotel revenue management conversations than any other. It comes up on the first call, on the follow-up call, and sometimes right before the demo. It sounds like a closed door. But it is not.
"We already have a channel manager."
Most SDRs try to argue against it. They explain that a revenue management system is different from a channel manager. They list features. They send a comparison PDF. The prospect thanks them and never books the demo.
The real answer is not to argue. It is to ask one question that changes the entire framing of the conversation.
Why this objection is so common — and why it is not really an objection
A channel manager distributes your rates to OTA platforms. It pushes whatever rate you set to Booking.com, Expedia, and every other connected channel simultaneously. It is a distribution tool.
Revenue management software decides what that rate should be. It reads the market, reads demand, reads your comp set, and recommends or sets the price before the channel manager distributes it.
These are two completely different problems. But to a hotel GM who is not deep in the technology, they sound like the same thing. Both touch pricing. Both connect to OTAs. The names even sound similar.
When a prospect says "we already have a channel manager," they are not rejecting your product. They are telling you they have not understood the distinction yet. That is a qualification gap, not a closed door. And it is entirely fixable in a single exchange.
The one question that reframes everything
"Totally — most properties we work with already use a channel manager. Quick question: is it deciding your rates, or distributing the ones you set?"
This question does something most SDR responses do not. It does not challenge the prospect's statement. It validates it and immediately introduces a distinction the prospect has probably never articulated before.
The answer is almost always a pause, followed by some version of: "Well… we set the rates, and then it distributes them."
You have now moved the conversation from "do you have the right tools" to "who is making your pricing decisions and how." That is the Problem stage of SPIN — and you got there in one question.
The full 6-step response script
Once the framing question lands, the rest of the conversation follows a clear structure. Here is the complete sequence:
- Acknowledge: "Totally — most properties we work with already have a channel manager set up."
- Clarify: "Quick question: is it deciding your rates, or distributing the ones you set?"
- Reframe: "Right — so the channel manager is doing the distribution job really well. What we do is the step before that: figuring out what the rate should be, and when to change it, based on what the market is doing right now."
- Implication: "When your comp set moves rates mid-week — say demand drops off after a MICE event cancels — how quickly can you react before your channel manager pushes out a new rate?"
- Need Payoff: "What would it mean for your weekday occupancy if you could respond to that in under an hour instead of waiting for the next manual review?"
- Close: "That's exactly what I'd like to show you. It takes about 20 minutes — can we find a time this week?"
The sequence works because each step builds on the previous one. By the time you reach the close, the prospect has answered four questions that have led them to their own conclusion: they have a distribution tool, but nobody — or nothing — is optimising the rates going into it.
The implication question is where the demo gets booked
Most SDRs stop after the Reframe. They explain the difference between distribution and rate-setting, the prospect nods, and the conversation ends without urgency. The Implication question is what creates urgency.
The specific version of the Implication question matters. It needs to be time-bound, property-specific, and connected to something the prospect can picture happening at their hotel. Generic versions — "what if you could improve your RevPAR?" — do not land because they do not cost anything to ignore.
The MICE event example works because it is specific, common in APAC markets, and the timing gap is concrete: the event cancels Thursday, the next manual review is Monday, and every night in between is priced for demand that no longer exists.
The Implication question does not ask the prospect to imagine a better future. It asks them to put a number on a problem that is already happening.
What live market data does to this conversation
The channel manager objection response becomes significantly more powerful when the SDR has live OTA comp pricing and STR market data loaded before the call.
Instead of a hypothetical Implication question, the SDR can anchor it to the prospect's actual market: "Looking at your comp set for the next 30 days, weekday demand is running ahead of weekends — which is the inverse of the typical pattern for this market. If your current rate strategy doesn't reflect that, you're either leaving money on the table on weekdays or sitting on empty rooms on weekends. Which direction is your occupancy trending right now?"
That is not a scripted sales question. That is a market intelligence conversation. And it is the difference between a prospect who books a demo out of curiosity and a prospect who books a demo because they feel urgency.
Common mistakes SDRs make with this objection
- Arguing too early: Jumping into a product explanation before the prospect has felt the problem. The reframe only works after the clarifying question has landed.
- Skipping the Implication: Moving from Reframe directly to "let me show you the platform." The prospect understands the difference but does not feel it yet.
- Using the wrong Implication question: Generic questions about RevPAR improvement do not create urgency. The question needs to be time-bound and specific to the prospect's market or property type.
- Closing on features: "It integrates with your existing channel manager" is a feature. It does not close a demo. The close needs to follow a Need Payoff question — something the prospect has answered, not something you have told them.
What to do when the prospect says "we set our own rates and it works fine"
This is the follow-on objection that sometimes appears after the channel manager reframe. The prospect accepts the distinction but claims their manual process is adequate.
The response is a Situation question, not a counter-argument: "How often are you reviewing and adjusting rates right now — is it daily, weekly, or event-driven?"
The answer reveals the review cadence. Once you know it, the Implication question writes itself: "When the market moves between reviews — how quickly are you able to respond before it affects your occupancy?"
The structure is the same. The framing is different. And the outcome — a prospect who has articulated their own problem in their own words — is identical.