Pay-What-You-Want Event Tickets: A Launch Worksheet

Before offering pay-what-you-want event tickets, decide what someone receives at each amount. A workshop with one admission package and a choice of contributions needs different wording and checks from a VIP ticket or a free event with an optional donation.

This guide helps you choose the model, put its terms into a copyable launch worksheet and check whether the finances and attendee journey match the promise. Start with access. Choose the amount rules after that.

How pay-what-you-want event tickets work

For an event, pay what you want usually means the attendee enters an admission amount within the organizer's stated rules. Those rules may include a required minimum. A set menu of contribution amounts is a different implementation, often called sliding-scale ticket pricing. Because labels vary, describe the actual choice on the event page.

A minimum is the amount required to continue. A suggested contribution is guidance unless checkout enforces it. Tell the buyer which is which, in the event's payment currency. If no-payment admission matters to your event, define and test a free-ticket route rather than assuming a variable-price field accepts zero.

Choose the model that matches your access promise

Ask whether paying more changes the event experience. If every contribution includes the same workshop and replay window, say so. If a higher amount buys another session or longer replay access, explain that package difference.

The table compares the decisions you need to make. These are planning models; a platform may combine them or use different labels.

Swipe sideways on a small screen to read every column. You can also focus the table area and use the arrow keys.

Equal-access contribution choices and VIP packages make different promises. For a broader tier structure, use the event ticket pricing guide. Keep this worksheet focused on who chooses the contribution and what it includes.

Complete the launch worksheet

Copy this table into your planning document or spreadsheet. Replace the prompts with your own terms and evidence. Leave a test's observed result blank until someone has run it; an expected outcome is a plan.

Swipe sideways on a small screen to read every column. You can also focus the table area and use the arrow keys.

Use zero extra donations in the conservative forecast unless you have evidence for another assumption. Keep any more hopeful forecast separate, with its source. A contribution choice should not leave the finance owner guessing which costs still need funding.

Check the downside before choosing a minimum

Consider a hypothetical online workshop with 80 registrations and a variable-admission minimum of $10. All amounts below are illustrative USD assumptions. They are neither recommended ticket prices nor observed event results.

Assume fixed costs of $1,200 and delivery/support costs of $2 per registration. Modeled cost is therefore $1,200 + $2 × 80 = $1,360. For this example only, reserve 10% of gross for fees and refunds. That reserve is an invented planning allowance, not a provider quote or tax calculation.

Both scenarios hold registration count constant to isolate the payment mix. Neither predicts how many people will register. The $125 remainder is not accounting profit or cash available today, and the downside can worsen if registrations fall.

For your event, calculate gross as the sum of people multiplied by their payment amount. Calculate modeled cost as fixed costs plus cost per registration multiplied by registrations. Subtract explicit reserves and modeled costs from gross to find the modeled remainder. Replace the illustrative reserve with verified platform/provider charges and your refund assumptions before launch.

If the all-minimum shortfall is unacceptable, revise the minimum, secure committed funding, choose a simpler fixed ticket or plan a free/sponsored event within a known budget. Do not rely on supporters to fill an unexplained gap. Use the virtual event budget worksheet for the complete cost and break-even plan.

Explain the amount and access without pressuring the buyer

Make the decision possible from the event page. State the required minimum and currency, whether the buyer enters an amount or selects a tier, and whether every choice includes the same access. Name the live sessions, resources and replay window. If higher amounts buy extras, describe those differences beside the options.

For an optional contribution, say what someone receives if they skip it. Publish fee/refund terms and a support contact. Check that the page description, amount-field instructions and checkout agree. A suggestion written in page copy must not contradict the amount required by the form.

W3C's form-instruction guidance recommends clear instructions and identification of required inputs. Apply that principle to the contribution field, including currency and whether it is optional. Flexible pricing alone does not establish that an event is accessible.

Use calm labels that let buyers choose without explaining their private finances. Avoid asking for income, debts, health information or household circumstances in this model. A 2012 field study published in PNAS found that some consumers avoided purchases when invited to choose a price. Its consumer experiments do not predict your event's results, but they give you a reason to take buyer pressure seriously.

If choosing an amount makes the offer harder to understand, consider a short list of contribution tiers or a single fixed price. More choice is useful only when people can understand what they are choosing.

Map the chosen model to HeySummit

Once your worksheet is clear, check the price configuration and access configuration separately. HeySummit's flexible-pricing guide describes Fixed and Variable prices for tickets and add-ons. In Ticketing & Payments > Tickets, Add-ons & Donations, open the item's Pricing step. Variable pricing uses a Minimum price, and the displayed currency follows the event's payment currency.

For fixed contribution choices, design the relevant ticket types and reconcile their access and total capacity. A higher contribution should not imply an extra session unless you have deliberately included and checked it. HeySummit's ticket setup guide explains free and paid tickets, checkout availability and access rules. Some checkout and access controls depend on Advanced Ticketing and your plan. Check the current plan and payment setup for the event you will run.

Optional donations have their own settings. HeySummit's donation guide explains pricing, purchase eligibility and optional access controls. For a variable donation, the minimum is also the initial suggested checkout amount; there is no separate default-amount field. You can explain a contribution suggestion in public copy, but do not assume it is an independent checkout control.

Inspect a donation's access settings rather than assuming it always grants access or never can. For free admission, use a free ticket and configure any optional contribution separately as appropriate. Do not infer tax deductibility, charitable status or a particular payment-provider limit from the word donation.

Use event ticketing to assess whether the configuration fits your completed worksheet. Then verify the chosen attendee journey before making its checkout and access promises public.

Test the launch from the attendee's side

Use a test/demo route and authorized payment testing with test identities. Keep private customer records out of the exercise. These are checks for your organizer team to run; this guide does not report a completed purchase or access test.

In your worksheet, record each case, its expected outcome, the observed result, pass/fail, date and tester. Give every failure an owner before registration opens.

1. Read the event page and amount instructions on mobile. Confirm that the currency, required minimum or set prices, inclusions and optional contribution wording are understandable before payment.

2. For variable paid admission, try below-minimum, exact-minimum and above-minimum amounts. Expect the published floor to hold and valid accepted amounts to match the payment record. Check rounding and event currency.

3. For fixed tiers, check every type's promised access and the combined capacity. If you promise equal access, compare live sessions, resources and replay windows for parity.

4. For an optional donation, skip it and confirm that the base ticket still grants the promised admission. Then test a chosen contribution and check that it does not add unintended access.

5. Check successful and failed-payment journeys. Confirm the actual amount, receipt wording and next steps. A failed payment must not look like a successful admission.

6. With a test registration, check the promised live session and replay. Check expiry and an unrelated session that should remain restricted. Use the wider paid webinar setup guide if you also need to plan delivery and follow-up.

7. Check refund and cancellation handling. Establish whether access correction needs a separate organizer action; do not assume a refund automatically revokes access.

8. Check sold-out and sale-window-closed states, the support route and who resolves each failure. Make sure the team can find the original promise when someone asks for help.

Review actuals before repeating the model

After the event, record the contribution distribution, funds remaining after actual costs and reserves, registrations, attendance and support issues separately. A large contribution and a well-attended session answer different questions.

Look for amount instructions buyers misunderstood and access promises the team had to correct. One event cannot establish that flexible pricing caused a change in revenue or attendance. Use what you observed to decide whether to keep the model, simplify the choices or change the wording.

Before opening registration, have the event lead review the worksheet with the people responsible for finance, ticketing and support. If the model fits, explore HeySummit's event ticketing and check how your price and access decisions will work together.