Build a private-event pipeline that never lets a date go cold

Where event revenue actually leaks

Almost no private-event inquiry is lost to a better venue. It is lost to a faster one. The host planning a rehearsal dinner writes to three restaurants on Sunday night; the one that answers Monday morning with real availability and a real proposal is having a different conversation than the two that answer Wednesday with "let me check with our events person." By the time the Wednesday replies arrive, the host has emotionally committed elsewhere and is just being polite.

The pipeline leaks at four specific joints: the first response (slow), the proposal (days late because it requires the one person who knows the pricing), the follow-up (usually never happens at all - the single largest leak), and the overview (nobody can say, on any given morning, which dates are being discussed with whom). This guide seals all four with your AskEleven Employee, using the menus, pricing, and calendar you already have. What you are buying is not a new process. It is your existing process, executed every time, at every hour.

Before you start: gather five things

Your packages and pricing, complete and current. Menus, per-person prices, room fees, minimums by day and season, bar packages, what is included and what costs extra. If this lives in the events manager's head, this is the week it gets written down - the whole system runs on this sheet.
The rules of the room. Capacities seated and standing, which spaces can be private, noise and end-time constraints, deposit and cancellation terms, dates you never book.
The calendar of truth. Wherever event holds actually live - Google Calendar, your reservation system, the book. One source; if there are two, merge them now, because a double-booked Saturday costs more than this whole setup.
Your best past proposal. The document or email that won a booking you were proud of. Your Employee will use its structure and voice as the template.
Won and lost threads. Three email threads that ended in a booking, and three that went cold. The difference between them is usually visible, and your Employee should see it.

Step 1: The instant first response

The race is won or lost in the first hour. This standing instruction runs it:

Prompt - first response

From now on, answer every private-event inquiry - email, website form, or forwarded from OpenTable - within fifteen minutes, at any hour. Check the calendar first and lead with the truth about their date: available, already holding another conversation ("your date has some interest, so sooner is better"), or booked, in which case offer the two nearest open dates. Answer anything the inquiry asked that our packages sheet covers. Then ask, conversationally, for whatever is missing from: guest count, occasion, preferred space or seated-versus-standing, and rough budget if they have one. Close warmly with what happens next: a full proposal from us the same day we have their details. Never quote a number the sheet does not contain, never promise a date without placing a hold on the calendar, and place that hold - marked tentative with their name - the moment a date is discussed seriously. If an inquiry is over [YOUR THRESHOLD - say 80 guests or a full buyout], loop me in before proposing.

What to expect: Sunday-night inquiries answered Sunday night, with the date question - the only one the host actually cares about - answered first. The tentative-hold rule quietly ends double-booking, and the threshold rule keeps you personally in every conversation big enough to deserve you.

Step 2: The same-day proposal

Once the details are in, the proposal goes out the same day - this is the step that used to take three days because it waited for one person:

Prompt - the proposal

When an inquiry has given us date, guest count, and occasion, build the full proposal from our packages sheet and send it the same day. Use the structure and voice of the winning proposal I shared. It must include: their date and space confirmed as held for them until a stated expiry [seven days out, or 48 hours for dates inside a month], two menu options at different levels rather than one take-it-or-leave-it, per-person pricing and the total with room fee and minimum stated plainly - no "pricing available upon request" anywhere - deposit terms, and one specific line that shows we heard the occasion ("for a 70th, we would suggest the round tables in the garden room"). Every number must come from the sheet; if their request needs a price the sheet does not cover, draft everything else and bring me the gap instead of guessing. Log every proposal in HubSpot with date, value, and expiry.

What to expect: proposals that go out in hours, with totals stated like you mean them. Two options beat one because they change the host's question from "yes or no" to "which" - and the stated hold expiry gives the follow-up sequence something honest to say. The no-guessing rule is absolute: a proposal with a wrong number costs more than a proposal a day late.

Step 3: Follow-up that never goes silent, and the Monday review

Now the largest leak - the follow-up that never happens:

Prompt - follow-up and pipeline

Run this cadence on every open proposal: a short check-in at day three ("wanted to make sure this reached you - happy to adjust either menu"), an honest note the day before the hold expires ("your hold on the 14th releases tomorrow; one other party has asked about the date" - only if true), and a graceful close-out if the hold lapses ("we have released the date, and if plans change we would still love to host you"). Any reply stops the clock and routes to a human if it asks anything beyond the sheet. Then, every Monday at 8am, send me the pipeline: every open conversation with date, guest count, value, stage, days since last contact, and holds expiring this week - flagging anything that has sat silent longer than our cadence allows, which should be nothing.

What to expect: most bookings close on the day-three or expiry touch - not because of pressure, but because hosts are disorganized and genuinely grateful for the nudge. The only-if-true rule on scarcity is a house law: the first time a host catches a false "another party has asked," your venue's word is worth nothing. The Monday pipeline turns event revenue from a fog into a list you read in ninety seconds.

A worked example: the rehearsal dinner for forty

Sunday, 9:15pm, the website form: "Looking at your private room for a rehearsal dinner, June 12th, probably around 40 people. Is the room available and what does something like this run?"

9:24pm, the reply goes out: June 12th is open and now tentatively held under her name; the garden room seats 44; dinners like this typically run $95 to $135 per person depending on menu, before the $500 room fee - the sheet's real numbers. Two questions back: seated count once firm, and whether they want a welcome-cocktail half hour. She answers Monday at lunch. By 4pm the proposal is out: the room held through June's second Friday, two menus at $95 and $120, cocktail option priced, deposit terms, total stated plainly, and a line suggesting the long single table "since rehearsal dinners are really about the toasts."

Thursday's day-three nudge gets: "We're deciding this weekend between you and one other place." The day before the hold expires, the honest note - the date has real interest - and she books that evening at the $120 menu. Total value $5,780. Owner's total involvement: reading three lines in Monday's pipeline. The old version of this story ends differently, and it usually ends on Wednesday, unanswered.

Quality tests, then go live

Run one shadow week first - every response and proposal drafted but held for your approval - and apply these tests before releasing anything to send on its own:

The speed test. Submit a test inquiry through your own website form at 10pm. The reply should exist by 10:15 and read like your events manager on a good day, not like software.
The math test. Take three proposals and recompute every number against the packages sheet by hand. Anything the sheet cannot produce means the no-guessing rule needs tightening. Repeat this test monthly - and re-share the sheet the same day any price changes, because the system quotes whatever it was last given.
The hold test. Ask about a date in a test inquiry, then check the calendar for the tentative hold with the right name. Then let a hold expire and confirm it actually releases - phantom holds block real revenue.
The handoff test. Reply to a test proposal with "could we do a custom tasting menu instead?" and confirm it routes to a human rather than getting an improvised answer.

When the shadow week runs clean, go live - first response and follow-ups fully automatic, proposals held for your approval for one more month, then released too if you are approving them untouched. From there, your Monday pipeline is the whole job: every date accounted for, nothing aging in silence, and the Sunday-night host hearing back while the competition sleeps.