Ticketing

How to Run a Ticketing Platform Demo: A 10-Scenario Script, Scoring Rules and When to Insist on a Pilot Event

To run a ticketing platform demo that proves anything, write the script yourself. Send every shortlisted vendor the same event pack a week ahead, then make them run ten live scenarios on your data, from building the event to exporting your customer file. Each one is tested three ways: show the normal path, break it, and watch the recovery. Score what happens on screen, not what is promised.

How to Run a Ticketing Platform Demo: A 10-Scenario Script, Scoring Rules and When to Insist on a Pilot Event

Part of How to Choose an Event Ticketing Platform: The Complete Buyer’s Checklist

This guide goes one level deeper than the demo stage in our complete buyer's checklist for choosing an event ticketing platform. The checklist tells you what a platform must do. This article tells you how to make a vendor prove it in a two-hour session, and when two hours are not enough.

Why do ticketing demos so often pick the wrong platform?

Because most demos test features, and most regret comes from operations. A vendor-led demo runs on a perfect sample event, with clean data and a presenter who knows every click. None of that resembles your Friday on-sale, your postponement or your gate at 19:40. The demo looks finished; the risk sits in what it never showed.

The software-buying data points the same way. In Gartner Digital Markets' Capterra survey of 3,385 software decision-makers across 11 countries, 66% of buyers experienced unexpected disruption, regret or both after a purchase, and 89% of those who regretted it had first hit an implementation problem: integrations, data migration, delays. In the UK sample, only 27% of buyers were fully satisfied with their latest purchase. A demo that never touches configuration, change and failure is testing the part of the platform least likely to hurt you.

Ticketing makes this sharper. Your platform is judged in a handful of public moments, and a slide about those moments is not evidence.

What should you send vendors before the demo?

Send one identical event pack to every vendor at least five working days ahead, and tell them the session will run on it. A standard pack contains:

  • One real event configuration: capacity, ticket tiers, price points, sessions or dates, and your purchase-limit rules.
  • Your venue context: a seating plan or capacity zones, gate list and entry rules by tier.
  • Your channel mix: box office, own website, partners, and any invitation or complimentary flows.
  • A sample customer file: a few hundred anonymized or synthetic records with the fields you actually hold, including marketing consent.
  • The ten scenarios below, with your pass criteria attached.

Then fix three rules. Every vendor gets the same pack, the same scenarios and the same scoring sheet. Your own staff drive at least half of the clicks, because your box office team will use the platform, not the presenter. And the session is recorded, so scoring happens afterwards against evidence, not memory. A vendor that asks to swap your event for its demo event has answered the first question.

The Show–Break–Recover script: 10 scenarios to run live

The Show–Break–Recover script turns each capability into a three-step test. Show: the vendor runs the normal path on your data. Break: you introduce the failure that happens in real life. Recover: the vendor restores order on screen, without a back-office ticket or a promise to follow up. Most platforms pass Show. The platform you want is decided in Break and Recover.

1. Build the event from your pack, against the clock

Show: create your event, tiers, sessions and inventory rules from scratch. Break: change the capacity of one tier after creation. Recover: inventory updates across every channel, with an audit trail. Time the whole sequence. A platform that needs its own team to configure a standard event will need its own team every week.

2. Open an on-sale and hold the line

Show: a scheduled on-sale with a waiting room and staged release. Break: release a second wave early by mistake. Recover: pause, correct and resume without overselling. Ask to see traffic, wait times and conversion while it runs. webook.com's virtual queue orders buyers by arrival, supports staged and timed releases, and reports exactly those three numbers, which is the standard to hold every vendor to.

3. Buy on a phone and show the all-in price

Show: a full purchase on a mobile phone, from event page to ticket in wallet. Break: decline the payment card, then retry. Recover: the seats or tickets stay held for a fair window and the retry completes. Check that the total price, mandatory fees included, appears from the first price shown. In the United States, the FTC rule on unfair or deceptive fees has required up-front total pricing for live-event tickets since 12 May 2025, and other markets are moving in the same direction.

4. Try to beat your own purchase limits

Show: a purchase limit by tier. Break: the same buyer returns with a second account, a new email and the same card. Recover: the platform detects or blocks it, and the operator can see why. A limit enforced per account only is a suggestion.

5. Change the plan mid-sale

Show: add a new tier and change a price while sales are live. Break: a sponsor returns 40 held tickets an hour before a price change. Recover: the tickets go back on sale at the right price, and baskets already in progress keep their honest price. Commercial teams change their minds; the platform has to keep up without corrupting live baskets.

6. Postpone the event

Show: move the event to a new date. Break: half the buyers want refunds, half want to keep their tickets. Recover: both paths run, buyers are notified in bulk, and finance sees the refund liability by channel. This is the scenario vendors least like to demo, which is exactly why it belongs in the script.

7. Transfer, resell and rescan a ticket

Show: a buyer transfers a ticket under your rules. Break: the original holder tries to use a screenshot of the transferred ticket. Recover: only the new holder's ticket scans. On webook.com, secure ticketing uses QR codes that refresh and expire to limit screenshot abuse, with transfer rules set per event, tier or audience, and validation at scan time that blocks reuse.

8. Run a gate

Show: scan tickets on the devices your staff will actually hold. Break: scan the same ticket twice, then a ticket for the wrong zone. Recover: clear rejections, a reason staff can act on, and live entry counts by gate for the supervisor. Ask what happens to scanning when the venue network drops, and get the answer in writing.

9. Reconcile the money

Show: a live sales dashboard during scenarios 2 to 8. Break: ask for a settlement view that reconciles gross sales, fees, refunds and payouts for the session you just ran. Recover: the numbers match what happened on screen, and finance can export them. If the platform cannot reconcile a two-hour demo, it will not reconcile a season.

10. Leave with your data

Show: export the full customer file, including consent flags, in a standard format. Break: request only buyers from one channel who opted in to marketing. Recover: the filtered export arrives during the session, not after contract signature. If export is slow or partial in the demo, read our guide to who owns your ticketing data and what to settle before you sign before the next call.

How should you score a ticketing demo?

Score each scenario Pass, Partial or Fail against the criteria you sent in advance, and track one extra number: the backstage count. Every "we'll follow up", every colleague pulled in to finish a step and every "that's on the roadmap" adds one. Two vendors with the same feature scores and very different backstage counts are not equal choices.

Weight the scenarios to your business before the first demo, not after your favorite vendor presents. A stadium operator weights scenarios 2, 7 and 8; an attraction weights 1, 3 and 9; a touring promoter weights 5 and 6. Feed the results into the weighted scorecard in our event ticketing RFP template so the demo becomes one scored stage rather than a separate beauty contest.

When is a demo not enough, and you need a pilot event?

Insist on a pilot event when the risk you care about only appears with real buyers, real payments and real gates. A demo proves the platform can do something. A pilot proves your team can do it, in your market, on your payment mix and with your audience's behavior. It is the right step for a new market, a new event format, or a move from a reseller to direct ticketing.

A pilot that produces evidence has five fixed parts:

  • A contained real event: one date, a few hundred to a few thousand tickets, real money, real entry.
  • Success metrics agreed in writing before launch: checkout conversion on mobile, payment approval rate, scan throughput per gate, support contacts per 1,000 tickets, and the date the settlement statement arrives and reconciles.
  • Your team in the operator seat: the vendor supports, your staff run the event.
  • Commercial terms that keep you free: a defined pilot fee or commission, no exclusivity, and a clean exit if the metrics are missed.
  • A written debrief: what broke, what was fixed and how long each fix took.

What a pilot cannot prove is peak load. A 2,000-ticket event says nothing about 200,000 buyers arriving in one minute. For that, require the scripted load test described in our 40 questions that predict ticketing platform fit, and treat a refusal as an answer.

What does this script look like at marquee-event scale?

At marquee scale, every scenario in the script happens in a single week, often on the same day. webook.com serves more than 20 million users, processes more than 25 million tickets a year and reaches more than 180 countries, for clients including Formula 1, the Saudi Pro League, Riyadh Season, WWE and the Esports World Cup. A race weekend or a season launch combines an on-sale, mid-sale changes, transfers, multi-gate entry and same-week reconciliation. That is why the script tests Break and Recover: at this scale, the normal path is the easy part.

The same discipline applies on a smaller stage. webook PRO is built so an organizer can set up an event in minutes, design reserved seat maps and run daily operations from a phone, which is exactly what scenario 1 should prove for any vendor, including us.

Which vendor answers should worry you?

Treat these as warning signs during the session:

  • "Let's use our demo event; yours would take time to configure." Configuration time is the thing you are testing.
  • "We'll send that report after the call." Reconciliation that cannot happen live will not happen on settlement day.
  • "Postponements are handled by our support team." Then your postponement runs on their queue.
  • "That's on the roadmap." Score roadmap items as Fail; contract them separately if they matter.
  • "Our customers don't usually need that." Your scenario came from your operations, not theirs.

Bring your event pack to a webook.com demo

If you are shortlisting ticketing platforms, run the Show–Break–Recover script on us first. Book a demo with the webook.com team, send your event pack in advance, and we will run your scenarios on your data.

Frequently asked

What should I ask to see in a ticketing software demo?

Ask to see your own event built from scratch, an on-sale with a waiting room, a mobile purchase showing the all-in price, purchase-limit enforcement, a mid-sale change, a postponement, a ticket transfer, gate scanning, a live reconciliation and a full data export. Run each on your data, and introduce a failure each time.

How long should a ticketing platform demo take?

Plan two to three hours for a full scripted demo of ten scenarios, plus a 30-minute debrief without the vendor present. Shorter sessions push the hard scenarios, postponement, reconciliation and data export, off the agenda. Schedule demos within the same week for all shortlisted vendors so your team compares them while memory is fresh.

What is the difference between a ticketing demo and a pilot event?

A demo shows that a platform can perform a task in a controlled session. A pilot event runs a real, contained event with real buyers, payments and entry, measured against metrics agreed in advance. Use demos to shortlist, and pilots when market, format or payment risk can only be proven live.

Should a ticketing vendor charge for a pilot event?

Often yes, and a fair pilot fee or standard commission is reasonable. What matters more is the terms: no exclusivity, success metrics written before launch, your team operating the event, and a clean exit if metrics are missed. A pilot that locks you into a multi-year contract is a sale, not a pilot.

Related on webook.com

All articles

Get started

Let's build your event's ticketing

Tell us about your event and what you want it to achieve, and we'll put a dedicated team on the setup that fits.

Get started now
Partner with us