Discover a Planner's Decision Process Before the Proposal

A planner who tells you to send over your best package is not handing you a green light. Every planner who reaches out sits somewhere inside a decision process you cannot see from an inquiry form. Some planners choose the venue outright. Many gather options for a boss, a finance team, or a committee that meets once a month. If you build a proposal before you understand that process, you are guessing at rooms, pricing, and concessions that might never reach the person who actually decides. The fix is not a sharper proposal. It is a better conversation before you write one.

Why this conversation goes wrong

Most group sales managers want to look responsive fast. A planner asks for a package, and the instinct is to prove it by sending something within the hour. That instinct backfires more often than it helps. A proposal sent before you know who reviews it, what they compare it against, and when they meet, lands as a guess. The planner then has to translate your material into whatever format their finance team or leadership actually needs, and your numbers may not survive that translation.

There is a second reason this goes wrong. Planners do not always describe their own decision process clearly on the first call. Dana, the planner in the example below, opened with a simple request for a package. Dana had not mentioned finance, the chief of staff, or a Friday review meeting. Those details came out only because the manager asked. A planner who has run dozens of these events still may not think to hand you the full picture unprompted. You have to draw it out.

What to learn before you prepare anything

Before you touch room blocks, menus, or concessions, get clear answers to a short set of questions. Ask what the event is for, since a leadership retreat and a sales kickoff get judged on different terms. Ask who else will weigh in and what each person cares about, because a finance reviewer and an executive assistant are not comparing the same details. Ask when the next decision meeting happens, since a proposal that misses that date by a day is a proposal that gets shelved.

Ask what evidence the group actually needs to move forward. That might be a space plan, a room estimate, a food and beverage outline, a budget range, or a site visit. Different planners walk in with different gaps, and sending everything you have is not the same as sending what they need.

Treat any headcount or date you hear on this first call as a working assumption, not a fact. Write it down as an assumption, and confirm it again before you commit rooms or pricing against it. A planner who says about 150 people is giving you a starting point, not a contract term.

What to say when a planner hands you a vague request

Dana was planning a leadership retreat. Dana opened with, "Send me your best package and I will take it to the president."

The manager did not send a package. The manager said, "I can prepare material that helps that conversation. Who else will weigh in, and what will the president need to see before choosing a venue?"

Dana explained that finance would look at total spend and the chief of staff would look at privacy and meeting flow.

The manager asked, "When do those reviews happen?"

"Friday," Dana said.

The manager replied, "I will confirm which dates and spaces the property can offer first. Then I can send an outline built for your finance and chief of staff colleagues, along with a proposed site visit, so you have something ready before Friday."

Notice what happened here. The manager did not refuse the request or slow the planner down for no reason. The manager redirected a vague ask toward the actual decision path, then set a concrete deliverable against a real deadline. Dana left the call with a clear sense of what would arrive and when. The manager left with the names of two evaluators and their criteria.

Mistakes that sink an otherwise good proposal

A few habits show up again and again in these conversations, and each one costs you later.

1. Sending a full package before you know who reviews it. You end up building for an audience of one when the real audience is three people with different priorities.
2. Treating an unconfirmed headcount or date as settled. Numbers stated on a first call shift constantly, and pricing built on a guess has to be renegotiated later, which reads as unreliable.
3. Skipping the question about the next decision meeting. Without that date, your follow up has no natural deadline, and it slides to the bottom of the planner's list.
4. Writing one document for every stakeholder instead of naming what each reviewer needs. A finance lead wants total spend and payment terms. A chief of staff wants flow, privacy, and logistics. One generic packet serves neither well.
5. Closing the call without a named owner and a date for the next exchange. A vague promise to follow up soon gives the planner nothing to hold you to and nothing to hold themselves to.

Assumptions about internal approval also deserve a second look before you finalize commercial terms, since planners sometimes describe an approval path that changes once real budget numbers appear. The post on Compare Promotion Assumptions Before Seeking Approval covers a related version of this problem, where the gap is between what a manager assumes leadership will approve and what leadership actually wants to see.

How to practice and score this conversation

This is a skill you can drill before it costs you a real deal. Give a manager an inquiry that says only "annual meeting, about 150 people," and nothing else. Set a timer for five minutes and have them run the discovery call from that single line.

Afterward, score three things. Check whether they named the actual decision participants and separated each one's criteria from the general event needs. Check whether they treated the headcount and any date mentioned as an assumption rather than a fact, flagging it for confirmation instead of building on it. Check whether they ended the call with a named next step and a real date attached to it, not a vague promise to follow up.

DealSpeak's Hospitality and Travel practice conversations are built for exactly this kind of rehearsal, since a manager can run the same vague inquiry repeatedly against an AI planner that behaves differently each time, and get scored on whether the decision path actually surfaced. That repetition matters more than it sounds like it should. The first attempt usually goes fine. The fifth attempt, against a planner who resists giving up details, is where the habit gets built.

Once the event actually runs, the conversation is not over. What a group actually needed, compared with what you assumed on that first call, tells you something about your discovery process itself. The post on Use Post Trip Feedback to Improve the Next Planning Conversation walks through how to feed that gap back into the way you run discovery calls going forward.

The short version

A proposal only works if it reaches the right person with the right evidence at the right time. Get the decision process out into the open before you write a single page, and treat every number a planner gives you on a first call as something to confirm, not something to build on.