Demand-driven pricing for events

Time on the clock isn't the only thing that should move ticket prices. Weather, holidays, competing events, and social-media velocity all bend the demand curve in ways that a pure time-decay engine misses. This is the catalogue of demand drivers every events team should be feeding their pricing model.

The seven drivers that matter most

1. Day of week and time of day

Friday 8pm and Saturday 8pm clear at 90%+ on most touring shows. Sunday matinees and Tuesday nights need either lower prices or targeted promo. Build the day-of-week effect into your baseline curve — never apply it as an after-the-fact discount.

2. School holidays and bank holidays

Family-oriented events (matinees, kids' shows, family attractions) spike on school holidays. Adult-skewed events (late-night gigs, corporate hospitality) flatten or dip — the audience is on holiday too. Both effects matter; the sign depends on the segment.

3. Weather

For outdoor events, a forecast of rain in the 7-day window cuts last-mile demand by 20–40%. A heatwave does the opposite. Pull weather forecasts daily during the booking window and adjust the last-mile reprice cadence accordingly.

Counterintuitive

Bad weather actually helps indoor cinema, theatre, and bowling-style attractions. People rebook from the outdoor activity they had planned. Always know which side of the weather effect your venue is on.

4. Competing events on the same night

A major football match, a sold-out arena show, or a national TV event in the same city can halve walk-up demand. The information needs to be in your pricing engine before the calendar flips, not after the empty seats appear.

5. Social-media velocity

Mentions per hour, share-of-voice vs the artist's previous tour, and TikTok sound-use are the leading indicators of an unexpected demand spike. The trick is treating them as directional signals, not literal demand forecasts — they tell you to look, not what to charge.

6. Travel cost (transport, fuel, hotel)

For destination events (festivals, tourist-area concerts, sporting finals), the total trip cost drives demand more than the ticket price itself. Track airfare and hotel rates into your venue's catchment as a leading indicator — when travel costs spike, ticket elasticity rises sharply.

7. Comp set ticket inventory

If three other shows in your tier are sold out or near-sold-out for the same week, the available audience for yours just shrank. Conversely, if competitors are dump-discounting, that ceiling drops on your prices too.

How the engine should combine them

The wrong way is to apply each driver as a standalone multiplier and end up with prices ±60% from baseline.

The right way is a layered model:

Baseline = sell-through curve for this event tier (built from historicals).
Calendar overlay = day-of-week × holiday × school term. This is largely deterministic.
External overlay = weather × competing events × travel cost. Updated daily during the last-mile window.
Velocity overlay = pace vs target. The fastest- moving signal; reprice every 6–12 hours during last-mile.
Hard guardrails: floor, ceiling, max daily change. Always.

The most expensive mistake in event pricing is reacting to one driver in isolation — e.g. raising prices on a velocity spike that turns out to be a single bot-driven post. Always require at least two corroborating signals before a non-routine price move.

Where this fits in the bigger picture

Demand drivers are the inputs; the structure that uses them is time-decay pricing. The math underneath both is price elasticity of demand.

Run demand-aware ticket pricing without the spreadsheet

Luska's events engine ingests weather, holidays, competing events, and pace — and turns them into reprice recommendations with full audit trails.

See it for events

Demand-driven pricing for events: weather, holidays, and competing shows