An organiser asks three traders what they charge for a sixtieth birthday. One quotes a minimum spend, one quotes per head, one quotes a flat fee and a fourth says it depends.
She cannot compare any of them, so she books the one whose website had a number on it.
A worked example
Eighty guests, four hours, priced three ways.
Model 1: minimum spend
A guaranteed amount of takings, with guests paying individually and the organiser covering any shortfall. It suits events where guests expect to pay and the trader takes the risk of a quiet crowd.
What to publish for it
The figure, how it is calculated, what counts towards it and what happens if takings exceed it. Organisers fear an open ended liability.
Model 2: per head
A fixed price per guest for a defined offer, with nobody paying at the hatch. It suits weddings and corporate events and it is what most private organisers actually want.
What to publish for it
The price per head, exactly what each guest receives, whether there is a choice, minimum numbers and when final numbers are due.
Model 3: a fixed hire fee
A flat amount for attendance and a stated service period, with food charged separately or included. It suits events where the organiser wants certainty.
What to publish for it
The fee, what it covers in hours and servings, and what happens if the event overruns.
The cost lines behind all three
Staff, stock, fuel, travel, preparation, the unit and the hours. Publishing the reasoning makes any figure defensible.
Travel and distance
Whether it is included, the radius and the rate beyond it. It is the most common addition and organisers should see it, which is the site detail in event booking enquiries that need location and power.
The deposit and cancellation terms
What is payable, when, and what happens if numbers change or the event is cancelled. Private events move and the terms should anticipate it.
The public event position
Where a trader pays a pitch fee, what it costs, whether exclusivity is included and what footfall is expected. It is a commercial decision rather than a booking.
The honest total
For the eighty guest example, under the model you recommend, with everything included. Organisers need one figure to put in an email.
Explain what happens if the weather is poor
An outdoor event in driving rain sells a fraction of what it would on a warm evening, and a minimum spend suddenly matters enormously. Publishing how weather affects each model, and whether an event can be rescheduled, tells an organiser which arrangement actually protects them.
Recommend a model rather than listing them
Based on the event type. Organisers do not know which suits them and a trader who advises wins the booking, which is the ground in private hire enquiries for food trucks at weddings and parties.
Publish what per head actually includes
Because it is the most misunderstood model in catering, as in what per head catering pricing really includes and the general principle in AI chatbot pricing models explained.
Getting started
Publish all three models with a worked example and recommend one per event type, then capture numbers and dates at any hour. SpideyChat for food businesses answers from your published pages, plans are on the pricing page, and the chatbot ROI calculator works through the numbers.