The private-dining proposal that closes

A private-dining proposal has one job: make it easy to say yes. Most proposals fail that job not because the room is wrong or the price is high, but because the document is slow to arrive, hard to read, and unclear about what happens next.

Here is what closes, in the order it matters.

What makes a private-dining proposal close?

Three things, in this order:

1. Speed. The first restaurant to answer with something concrete usually wins.
2. Clarity. One readable page that shows the night, the menu, and one price.
3. One next step. A single link to sign and pay the deposit — not "let us know your thoughts."

Everything else — photography, paper stock, prose — helps only after these three are true.

How fast should you reply to an event inquiry?

Within the same service day, and sooner when you can. A guest planning a dinner for forty is usually writing to three or four restaurants in the same sitting. The reply that arrives first frames the decision; everyone else is compared against it.

You do not need the finished proposal in the first hour. Send a warm, specific holding reply — "The 14th is open, the Cellar Room seats 40, full proposal to follow this afternoon" — and then beat the time you promised. This is exactly the step worth automating: Excellent drafts the reply and the proposal from the inquiry itself, and a person approves both before anything is sent.

What belongs in the proposal?

In this order:

1. The night, described as the guest imagined it. Two or three sentences that prove you read the inquiry: the occasion, the date, the party, the feel. This is the difference between a proposal and a price list.
2. The space. Name, capacity as it applies to their party, and one or two honest photographs.
3. The menu. The specific menu you propose for this event — not the full catalog. Offer one alternative at most.
4. One price. A total for the evening with what it includes stated plainly: food, beverage, room, service. Line items support the total; they do not replace it.
5. The terms that matter. Deposit amount, final-count date, and cancellation window. Three lines, in plain language.
6. The next step. One link, one sentence: "To hold the date, sign and pay the deposit here."

What should you leave out?

• The whole menu book. Choice is your job; homework is not hospitality. A guest sent forty options will ask for a call, and the booking slows down.
• Internal words. "F&B minimum," "BEO," and "buyout" mean nothing to most hosts. Say "food and beverage spend," "event plan," "the whole room."
• Legal boilerplate up front. The contract belongs at signature, not on page one. Lead with the dinner, not the indemnity clause.
• Hedged pricing. "Starting at" invites doubt. Price the event you described.

How should the minimum spend be presented?

As a plain sentence, not a defensive one: "This room books at a food and beverage minimum of $6,000 on Saturdays. Your menu as proposed comes to $7,200, so the minimum is already met." Guests do not resent minimums; they resent discovering them late.

What happens after the guest says yes?

The distance between "yes" and "signed" is where bookings die. Every extra step — print, scan, mail a check, wait for the office to run a card — is a day for plans to change. Put the signature and the deposit in the same link, confirm the date the moment both land, and send the confirmation while the enthusiasm is still warm.

From there the details flow into the event plan the kitchen will run from — we wrote about that in What a great BEO actually contains.

The short version

• Reply the same service day, even if only to hold the date.
• Describe their night before your rooms.
• Propose one menu and one price; say plainly what it includes.
• Keep terms to three lines a host can understand.
• End with one link that signs and takes the deposit.

If you want to see a proposal like this drafted in minutes instead of an afternoon, watch the three-minute demo or read how Excellent runs the whole event flow.