Set a price ladder by date tier: peak Saturdays highest, then other Saturdays, Fridays and Sundays, and midweek lowest, with a food-and-drink minimum that falls the same way. Set each rung from your cost base and sell-through. AI can model the scenarios and stress-test the grid, but you choose the prices.
The traps sit on both sides: a midweek discount that only moves couples off your Saturdays, and a minimum spend that sounds high but is met by every couple anyway. The worked grid below, for a 120-guest venue with its own catering, shows how four tiers, a minimum spend and a midweek test fit together.
What the grid has to cover before any tier is set
Every price in the grid traces back to three numbers from your own accounts. The ones below belong to an illustrative venue with a 120-guest room, its own catering team and one wedding a day.
- Fixed costs, $520,000 a year: premises $210,000, salaried team $190,000, insurance and licences $30,000, a maintenance reserve of $50,000, base utilities $20,000, marketing and software $20,000.
- Variable cost of the space, $600 a wedding: cleaning, extra utilities and the set-up crew.
- Food and drink contribution, 40%: what is left of each dollar of catering revenue after ingredients, drinks stock and event staff.
A wedding therefore contributes its hire fee minus $600, plus 40% of its food and drink bill, towards the $520,000. The grid has to produce enough of those contributions, on dates that actually sell, to clear the fixed costs. Competitors' prices matter as a ceiling check once you have this arithmetic, not as the place to start. For why asking a chat assistant what the market charges is the weak use of it, see the limits of AI pricing research. Here the assistant works only on your own records.
Read your own calendar first: what sold, when, and at what price
Tiers should follow demand you have measured, not the shape of the calendar. Build a CSV with one row for every wedding date in the last three seasons, including the dates that stayed empty. The columns are event date, weekday, date booked (blank if unsold), hire fee, food and drink spend, and guests. No names, emails or phone numbers belong in it, and nothing in this analysis needs them. If your dates sit in mixed formats, cleaning messy data covers tidying them before you upload.
Some assistants run code on an uploaded file and count rows exactly; others read it as text and can miscount. A tell is whether the reply shows its working. Either way, recreate the headline counts with a pivot table before you trust them.
Attached is a CSV with one row per wedding date at my venue for the last three seasons, including dates that stayed empty. Columns: event_date, weekday, booked_on (blank if unsold), hire_fee, fb_spend, guests.
1. Group every date into: Saturday in my six busiest months, other Saturday, Friday or Sunday, Monday to Thursday.
2. For each group give: dates available, dates booked, median months between booking and event for booked dates, and the share of dates already booked 90 days before the event.
3. List any date that sold much earlier or later than the rest of its group.
4. Show the method as a table I can reproduce with a pivot table. Treat provisional holds as unsold.An illustrative reply, for one season of the venue above:
| Group | Dates available | Booked | Median months booked ahead | Booked 90 days out |
|---|---|---|---|---|
| Peak Saturdays | 16 | 16 | 15 | 100% |
| Other Saturdays | 36 | 20 | 9 | 39% |
| Fridays and Sundays | 104 | 26 | 6 | 16% |
| Monday to Thursday | 208 | 8 | 2 | 1% |
Read it as a pricing document. The peak Saturdays are full 15 months ahead, a sign they are underpriced. The other Saturdays sell steadily but leave 16 of 36 dates unsold on the day. Midweek has 8 weddings across 208 dates and most of them arrive late, which tells you price is not the only barrier: a midweek date needs a reason to exist, not only a discount.
Three things to fix in an assistant's first answer. Dates missing from the CSV vanish from the count, so every group looks fuller than it is; include the empty ones. A wedding moved from one date to another counts once, under the date it took place. And a hold is not a booking, which is why the prompt says so.
Four tiers, and the ladder between them
Four tiers is enough for a couple to remember and for staff to quote without checking a sheet. The tier is a property of the date, so publish it as a list rather than a rule:
- Tier A: the sixteen most-wanted Saturdays, named one by one.
- Tier B: every other Saturday.
- Tier C: Fridays and Sundays.
- Tier D: Monday to Thursday.
A starting ladder for hire fees is 100%, 80%, 60% and 40% of the top rung, with your sell-through moving each rung up or down afterwards. That ladder is my suggestion as an opening position, not an industry standard, and your own table should overrule it. Decide the awkward exceptions in advance, such as a Friday before a public holiday Monday or a Sunday that ends a long weekend, and put those dates in the tier they actually sell like. If you suspect that dates with a pattern, such as repeating digits, sell faster, test it against your history before adding a premium.
The price grid, filled in
Here is the grid for the venue. The food and drink figure assumes a $75 three-course dinner and a $45 drinks package, so $120 a head, and each minimum equals the guest count you would be happy to see on that kind of date at that price.
| Tier | Dates a year | Hire fee | Food and drink minimum | Guests to reach it at $120 a head |
|---|---|---|---|---|
| A, peak Saturday | 16 | $7,000 | $14,400 | 120 |
| B, other Saturday | 36 | $5,600 | $12,000 | 100 |
| C, Friday or Sunday | 104 | $4,200 | $9,600 | 80 |
| D, Monday to Thursday | 208 | $2,800 | $6,000 | 50 |
The minimum does the work of a guest-count floor without anyone having to police one. A couple with 60 guests on a peak Saturday falls well short of $14,400, so they are steered towards a tier that fits them, and your best dates stay with weddings that fill the room. To see what a couple actually pays, take the same 100-guest wedding across the four tiers:
| Tier | Hire fee | Food and drink billed | Total |
|---|---|---|---|
| A, peak Saturday | $7,000 | $14,400 (minimum applies, $12,000 spent) | $21,400 |
| B, other Saturday | $5,600 | $12,000 (exactly the minimum) | $17,600 |
| C, Friday or Sunday | $4,200 | $12,000 (above the $9,600 minimum) | $16,200 |
| D, Monday to Thursday | $2,800 | $12,000 (above the $6,000 minimum) | $14,800 |
The same wedding costs $6,600 less midweek than on a peak Saturday, about 31% less. Notice that between tiers B and D the whole difference is the hire fee, $2,800, because a 100-guest couple clears both minimums anyway. That fact drives the midweek test further down.
Check the top tier against three competitor pages, like for like
Competitor prices are a ceiling check, and only a fair one when each venue is reduced to the same question. Copy the text of three public price pages into the assistant, and ask for one comparable figure: the total for 100 guests on a Saturday in the busiest months, with every assumption listed.
Below is the public pricing text of three venues. For each, return: hire fee, food and drink price per head, any minimum spend or minimum guests, what is included, and the total for 100 guests on a peak Saturday. If a sentence can be read two ways, show both totals and quote the sentence. Do not fill gaps from general knowledge.An illustrative reply, with invented venues:
| Venue | Structure | Total for 100 guests | Flag |
|---|---|---|---|
| One | $195 a head all-inclusive, minimum 100 guests | $19,500 | Page says "from"; is the room included? |
| Two | $6,000 hire plus $140 a head, minimum 80 guests | $20,000 | Service charge not mentioned |
| Three | $9,500 hire only, bring your own caterer | $9,500 plus caterer | Not comparable until you add an outside catering quote |
Your tier A total of $21,400 sits about 7% above venue two and 10% above venue one. A date that sells out 15 months ahead can carry a premium like that, but couples need a reason they can see: a better room, more included hours or freer catering choices. Then verify each row against the venue's own page. Assistants fold "from" prices into totals and drop footnotes, and a competitor figure you got wrong will mislead you for a whole season.
How a minimum spend plays out when the guest list is smaller
Take a couple with 90 guests who want a peak Saturday. At $120 a head their food and drink comes to $10,800, which is $3,600 under the $14,400 minimum. They have two honest options. They can pay the $3,600 as a shortfall, or they can spend it on things they would enjoy: a canapé reception at $22 a head ($1,980) and evening food at $18 a head ($1,620) add up to exactly $3,600. The total bill is identical either way, so the sentence to say at viewings is that up to the minimum, extras cost nothing more.
A couple with 50 guests is a different case. At $120 a head they spend $6,000, which leaves an $8,400 shortfall on a peak Saturday. Do not collect it. Offer them tier C or D, where the same guest count fits, and keep the date for a wedding that fills the room. A shortfall that large selects against small weddings and sours the couple on everything else you sell them.
Whatever the grid, the terms need four plain statements:
- What counts: menus, drinks packages, canapés, evening food. Say whether service charge and any tax are inside or on top of the minimum; this is where a final invoice is most likely to turn into an argument.
- What does not count: the hire fee, accommodation, and anything supplied by an outside company.
- When the shortfall is worked out: after final numbers are confirmed, not on the night.
- Whether unused drinks credit carries over: it should not, and the terms should say so.
If you want the deposit, cancellation and damage wording that sits around these terms, the event venue contract tutorial covers it. Have a solicitor read the final version.
Is the midweek discount paying for itself?
A midweek discount only helps if it brings in weddings you would not otherwise have. Every couple who would have booked a Saturday and switches is a loss. Use the 100-guest couple from the grid. On an other Saturday (tier B) the wedding contributes $5,000 from the hire fee ($5,600 minus $600) plus $4,800 from food and drink (40% of $12,000), so $9,800. The same wedding midweek (tier D) contributes $2,200 plus $4,800, so $7,000.
A switcher therefore costs you $2,800 and a genuinely new midweek wedding adds $7,000. The discount pays while you get fewer than 2.5 switchers for each new booking, because $7,000 divided by $2,800 is 2.5. Here is how it plays out over a season:
| Midweek mix | Gain from new weddings | Loss from switchers | Net |
|---|---|---|---|
| 4 new, 6 switchers | +$28,000 | −$16,800 | +$11,200 |
| 4 new, 10 switchers | +$28,000 | −$28,000 | $0 |
| 4 new, 12 switchers | +$28,000 | −$33,600 | −$5,600 |
To know which mix you have, add one question to the enquiry form: were you also considering a Saturday? Record the answer in your CRM (which CRM features matter for a venue lists the fields worth having). Enquiries that arrive as free-text emails can be tagged by an assistant instead. Paste the email body with names removed and ask it to return one label, weekend first, always midweek or unclear. You read the unclear ones yourself, and you never let the label, which is a guess about intent, stand in for asking the couple.
You can also shape the discount so it attracts new couples rather than switchers. A midweek package that caps guests at 60, includes dinner and drinks, finishes by 11pm and runs only in your quieter half of the year is attractive to a small wedding and unattractive to a 120-guest couple who would otherwise pay tier B. The conditions do the protecting; the price alone does not.
Three scenarios for the year, and where break-even sits
With a grid in hand, ask what a year looks like under three levels of demand. Contribution per wedding comes straight from the tiers: $12,160 for tier A (the average couple has 115 guests and spends $13,800, so the minimum lifts the bill to $14,400), $10,040 for B (105 guests), $7,920 for C (90 guests) and $5,080 for D (60 guests).
| Scenario | A | B | C | D | Weddings | Contribution | After $520,000 fixed costs |
|---|---|---|---|---|---|---|---|
| Cautious | 14 | 15 | 20 | 5 | 54 | $504,640 | −$15,360 |
| Likely | 16 | 20 | 26 | 8 | 70 | $641,920 | +$121,920 |
| Strong | 16 | 26 | 32 | 12 | 86 | $770,000 | +$250,000 |
The likely year averages $9,170 of contribution a wedding, so break-even is $520,000 divided by $9,170, or 57 weddings. That is 13 below the likely 70 and three above the cautious 54, which is why the cautious column loses money. The sensitivity is worth reading too. Losing four peak Saturdays costs $48,640, four other Saturdays $40,160, four Fridays or Sundays $31,680 and four midweek weddings $20,320. A 5% rise on the tier A hire fee adds $5,600 across the 16 dates, so it is only the wrong move if it loses a peak wedding about every second season. With tier A full 15 months ahead, that is a small risk.
An assistant can build this model in a few minutes if you give it the structure, and the structure is where it needs checking:
Build a scenario model in Google Sheets. Inputs tab: fixed costs, variable cost per wedding, food and drink contribution percentage, price per head, and for each tier (A, B, C, D) the hire fee, the food and drink minimum, average guests and weddings in a cautious, likely and strong scenario. For each tier, food and drink revenue per wedding is the larger of the minimum and guests multiplied by price per head. Contribution per wedding is hire fee minus variable cost plus that revenue times the contribution percentage. Show contribution by tier, total, profit after fixed costs, and break-even weddings. No numbers inside formulas.Check it against the table above. Tier A should come out at exactly $12,160 a wedding, and the likely scenario at $641,920. If tier A shows $11,920 instead, the assistant has multiplied guests by price per head and ignored the minimum. The same formula is =MAX(Inputs!B6,C6*Inputs!B4) in a typical layout. Other slips to look for: the 40% applied to the hire fee as well as the food and drink, Fridays and Sundays counted as 52 dates rather than 104, and weddings rounded to whole numbers before the break-even is calculated.
Ask the assistant to attack the grid before couples do
Couples, planners and your own sales staff will find the awkward cases in the first month. Give the assistant your grid and terms and ask it to play a sceptical planner looking for a better deal, listing ten situations where the grid produces a surprising or unfair price, with the arithmetic. These six, from an illustrative reply, are the kind worth deciding on in advance:
| Situation | What the grid does today | Decision you need to make |
|---|---|---|
| A Friday before a public holiday Monday | Prices it as tier C | Move holiday weekends into tier B or A |
| 50 guests on a peak Saturday | $8,400 shortfall | Offer tier C or D instead, as above |
| Couple wants to bring an outside caterer | Minimum cannot apply | Set a hire-only price with a kitchen and clean-up fee |
| Friday welcome dinner plus Saturday wedding | Two separate bookings | Decide whether the second date gets a package price |
| Date changed from midweek to a peak Saturday after booking | No rule | Charge the difference between tiers, at current prices |
| Finish at 1am on a Saturday | No rule | Price each extra hour, with staff and licence checks |
None of the assistant's answers is a decision. What you take from it is a list of questions to settle, each of which becomes one line in the terms. Ask it to find the situations; do not ask it to rule on them.
Explaining the grid to couples in plain words
A grid that is clear to you and baffling to a couple loses bookings at the viewing. Assistants are good at turning internal shorthand into plain sentences, and you are good at checking the numbers. Here is a before and after, using an illustrative internal note:
Before: "F&B min applies per date tier, excl. service and tax, shortfall invoiced after final numbers."
After: "On a peak Saturday your food and drink need to come to at least $14,400, before service charge and tax. If you spend less, we charge the difference, so any course or extra you add up to that figure costs you nothing more."
Check three things in anything the assistant drafts for your price page: that every figure matches the grid, that the shortfall rule is stated rather than implied, and that any "from" price carries the guest count and date type it assumes. A couple who reads "from $2,800" and then sees $14,800 on the quote will not forgive the gap, and it is hard to argue that the headline was fair.
Chasing enquiries once the price has been shown is a separate job, and how wedding venues use AI for viewings and follow-ups picks it up from there. For the cost side of catering, the caterer's cost-per-person sheet shows how to work out your own contribution figure in place of the 40% used here.
Reading the first season: signals and what to do about them
Run the sell-through table again after each release of new dates, and read it against these signals. They are prompts for a decision, not triggers to act on automatically.
| Signal | What it suggests | Option to consider |
|---|---|---|
| Tier A full more than 12 months ahead | Underpriced | Raise the hire fee 5% to 10% on dates not yet sold |
| Tier B dates still empty 90 days out | Priced too close to tier A, or weaker months | Widen the ladder, or add a Friday or Sunday package |
| Midweek couples who first asked about Saturdays | The discount is moving demand rather than adding it | Tighten the package: guest cap, finish time, season |
| Most weddings land exactly on the minimum | The minimum is acting as the price | Check whether your menus are priced to meet it |
| Couples query the final invoice | The terms are unclear | Add the shortfall example to the price page |
Review twice a year, and change prices only for dates you have not sold. Honour quotes already given until their stated expiry, and tell anyone with a live enquiry in writing when the grid changes. Date-stamp each version of the grid so that you can reproduce what a couple was quoted last spring. That record is also the dataset for your next round of modelling, which is the point at which an assistant becomes more useful: it has a year of tier-by-tier results for the same grid, rather than three seasons of mixed pricing.
Questions venue owners ask about date-based pricing
Should a wedding venue charge a hire fee, a minimum spend or both?
If you cater in-house, both. The hire fee covers the space, and the minimum protects food-and-drink revenue on dates you could have sold to a bigger party. Venues that let couples bring their own caterer usually charge hire only, plus a fee for the kitchen and clean-up. Whichever you choose, state exactly what counts towards the minimum.
How big should a midweek discount be?
Set it from your own numbers rather than a rule of thumb. Work out what a typical midweek wedding contributes, what a couple switching from a Saturday costs you, and how many switchers you can absorb per genuinely new booking. Start narrow, for one season and with conditions such as a guest cap, then review who actually booked it.
How long should a provisional hold on a date last?
Long enough for a couple to visit and decide, short enough that a peak Saturday is not lost to a couple who has gone quiet. Put a written expiry on every hold, such as seven or fourteen days, allow one hold per date, and give the holding couple first refusal, with a 24-hour deadline, if another couple is ready to pay a deposit. Count holds as unsold in the sell-through table.
Should I hold this year's prices for a wedding two years away?
Decide it in the terms rather than case by case. One approach is to fix the hire fee and the minimum spend when the deposit is paid, and let menus and drinks follow the price list for the year of the wedding, stated plainly in the contract. The couple then knows the date cost is locked, and you are not catering in two years' time at today's ingredient prices.
Further reads
- Venue Booking Software: Calendar, Deposits and AI Replies Compared — Compare booking tools that hold dates, take deposits and draft replies.
- AI for Event Venues: From Enquiry to Quote Without Missing Details — Turn an enquiry into a quote without missing details.
- Wedding Venue Newsletter: Seasonal Updates to Past Enquiries With AI — Sell quieter dates to past enquiries with a seasonal newsletter.
- AI for Hotel Revenue Management: Weekly Reports for Small Hotels — See a weekly revenue report built the same way for a hotel.
- Is AI Dynamic Pricing Worth It for a Small Hotel? — Check whether dynamic pricing suits a small property.
- How Much Should a Wedding Planner Charge? Model Fees With AI — See how the planner on the other side of the table prices.
- How to Price Wedding Cakes: Build a Quote Sheet With AI — A cake quote sheet using the same cost-first logic.
- Dog Boarding Cancellation Policy: Peak-Season Wording With AI — Peak-season wording for a dog boarding cancellation policy: deposit tiers, holiday blackout dates, an AI prompt and reply scripts you can adapt.
- Event Venue Marketing: Corporate Away-Day Campaign Written With AI — A six-week corporate away-day campaign for a venue: price the package, write the outreach and follow-up with AI, then draft a case study from a real booking.
- Wedding Venue Instagram: Real-Wedding Posts and Couple Consent With AI — How a venue can post real weddings on Instagram with the couple's consent, the photographer's permission, checked supplier tags and AI-drafted captions.
- Wedding Venue Marketing Ideas: Fair Stand and Follow-Ups With AI — A stand checklist, a seven-question lead form and three follow-up emails a wedding venue can draft with AI and send within 48 hours of the fair.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: an illustrative model built for this venue example. Replace every cost, price and booking figure with your own records before relying on it.