How to research what people will pay for your event

You've asked your audience what they'd pay, and the answers look encouraging. Some would spend $120. Others say $160 sounds reasonable. You choose a price somewhere in between, open sales and discover that being comfortable with a number is very different from buying a ticket.

To research what people will pay for your event, start with their actual buying decisions, use a clearly described offer to investigate possible prices, then test a price through real purchases when you can responsibly deliver the event. Read those findings alongside the number of tickets your budget needs. A price that people accept can still leave the event losing money.

The useful question is more specific than "What would you pay?" You want to know whether enough of the people you can reach will buy this experience, on this date, at the complete price you're considering. That means investigating the offer, the buyer and the purchase together.

This guide explains how to do that without treating a survey as a sales forecast. We'll compare price-perception research with purchase questions, build a practical interview and survey sequence, and work through a fictional paid workshop. All prices, sample results and financial figures in the examples are invented, in USD, to explain decisions. They aren't market rates, observed research or predicted results.

Decide what the research needs to settle

Before you write questions, write down the decision. Perhaps you're launching a paid workshop and need to choose between $120 and $140. Perhaps your festival has sold well at its current price, but increased production costs mean you're considering a higher one. Those situations need different evidence.

A first event needs to establish whether the offer makes sense to its intended buyers. A repeat event can also inspect what people previously paid, which allocations sold and what changed since then. Neither needs a survey about every possible ticket package simply because the survey software makes that easy.

Define one main uncertainty. If you're unsure whether people want the programme, start with the programme. Asking for a maximum price while the content remains vague produces a number for an experience each person has imagined differently. If the programme is settled and the uncertainty is between two credible prices, keep that experience the same while researching the price.

The US Small Business Administration's market research guidance separates questions about demand, reachable customers, location and what people pay for alternatives. That's a useful distinction here. Evidence that people like your event category doesn't answer what they will pay for your particular edition.

Write a decision sentence your team can challenge. For example, "We need to choose a regular price for a one-day practical workshop for independent venue managers, with enough paid attendance to cover the agreed budget." Add the decision date and the next supplier commitment. Research arriving after you've made the commitment has less ability to change the plan.

Then write what different findings would make you do. A credible $140 offer might proceed to a paid release. A strong preference for $120 might require lower costs or a different format. Unclear responses might require better programme information before another question. This prevents research becoming a way to collect approval for a price you've already chosen.

If your uncertainty is whether to enter a location at all, our guide to researching event demand in a new city covers that wider launch decision. Here, we'll stay with investigating the price and the evidence needed to choose it.

Describe the same event to every participant

A research participant needs enough detail to make a believable decision. "A brilliant networking day for venue professionals" isn't enough. One person may imagine expert teaching, another a sales presentation, and another an evening reception with drinks included. Their prices won't describe the same product.

Prepare a short, plain description that could become the core of the ticket page. Include the intended audience, date or honestly stated date window, location, start and finish, programme, what's included and what's extra. Explain the practical outcome without promising results you can't guarantee.

For our fictional workshop, you could show this research description. The venue and date below are invented details for the example.

"Proposed event: a practical budgeting workshop for independent venue managers, Tuesday 16 March 2027, 09:30 to 16:30, at the fictional Central Training Rooms in your city. A tutor experienced in venue operations will lead exercises on building an event budget, testing ticket prices and reviewing the result. Bring a laptop; worked examples, lunch and teaching materials are included. Travel and accommodation are your responsibility. This is a proposed event being researched, and no booking is available through this survey."

Add the complete per-person price in the pricing question. Keep that description unchanged across price versions. Before using it for a real purchase test, replace the proposal with accurate, confirmed arrangements and publish the actual booking terms.

If the venue or tutor isn't confirmed, say so. You can research a proposed offer, but the answers then depend on those assumptions becoming true. Save the exact version people saw. A response to an unconfirmed city-centre workshop doesn't validate an eventual venue outside the city with a different travel requirement.

Use the complete amount the buyer would pay when asking about price, and state the currency and whether the amount is per person. Explain the treatment of compulsory charges and taxes consistently. Your internal budget may distinguish fees and retained revenue, but the participant needs to judge the actual purchase you're proposing.

Also clarify what a group purchase means. A manager approving four tickets may evaluate a team training expense. Someone paying personally may be considering one place. Record that difference rather than allowing one group budget to become an unusually high individual willingness-to-pay response.

Don't decorate the research description with a made-up previous price or claims about tickets selling quickly. That changes the decision you're measuring. If a genuine early offer or limited allocation is part of the eventual purchase, describe its real terms. Otherwise, let people evaluate the event without manufactured urgency.

Find people who could actually make the purchase

Your followers are a useful recruitment source, but they aren't automatically the whole market. Some live too far away. Some enjoy your content without attending events. Others already trust you and would buy an unfamiliar programme more readily than someone seeing your business for the first time.

Start with the audience you intend to serve and the routes you can realistically use to reach it. For the workshop, that might include previous paying customers, relevant venue-industry contacts and people reached through an independent professional community. Keep the recruitment route attached to each response.

Include people who considered a comparable event and didn't buy. They can explain objections that purchasers have already overcome. You don't need everyone to dislike the offer, but recruiting only your happiest regulars makes it difficult to understand the people your next edition needs to attract.

Screen for the practical decision rather than collecting a long demographic profile. Can this person attend in the proposed location? Is the subject relevant to their work? Would they pay personally, approve a budget or need somebody else's approval? Have they bought this kind of experience before? Use only the information needed for the research and explain why you're collecting it.

You may learn that the intended audience contains two buying situations. A self-employed operator might pay directly and decide quickly. An employed manager might value the workshop but need an invoice and approval. Analyse those groups separately where the number of responses supports it. Combining them can hide a price objection in one group and a purchasing delay in the other.

Recruitment incentives need thought too. Pay people for their research time when appropriate, without tying payment to positive answers or a purchase. If you offer participants a ticket discount, record that later purchases occurred under a different offer. Buying with a research discount doesn't demonstrate acceptance of the regular price.

There isn't a universal number of responses that makes a small event's pricing research reliable. The audience, recruitment method, size of the decision and intended analysis all matter. A few interviews can uncover a misunderstanding. They can't establish a precise proportion of the wider market that will buy. If the financial commitment requires a reliable population estimate, get qualified research help before designing the study.

Ask about the last purchase before the next one

Start interviews with something the person has already done. Ask about the last comparable event they paid to attend, then follow the actual decision. What was the event? What did the ticket include? How much did they pay? Who else had to agree? What made them choose it over the alternative?

Ask about the full cost of attending as well. A ticket might be affordable while the train, overnight stay and time away make the trip impractical. That doesn't mean adding those costs to your own ticket price calculation. It means understanding the buyer's decision before assuming a cheaper admission would resolve it.

Then discuss a purchase they considered and rejected. Let them explain the reason before suggesting price. Someone may have waited for a colleague, disliked the date or failed to understand the programme. Prompting them with "Was it too expensive?" can make price seem central even when it wasn't their first explanation.

Past spending is useful context, rather than a maximum you can automatically charge. A person who paid $180 for a well-known specialist event may still reject a new $140 workshop. They may have trusted the previous tutor, needed that topic urgently or received employer funding. Keep the reason beside the amount.

If you already run events, examine actual sales records with the same care. Keep ticket types, discounts, quantities, refunds and timing separate. A sold-out $100 release establishes that the available allocation sold at that offer. It doesn't establish how many additional people would have bought, or how the same buyers would have responded at $140.

Compare editions only after noting changes in the programme, venue, selling period, audience and distribution. Last year's higher sales might reflect a stronger lineup or a partner reaching new buyers. A price increase happening at the same time doesn't prove that higher prices caused stronger demand.

Now show the proposed event description. Ask the participant to explain what they think they would receive and what they would still need to know. Correct factual misunderstandings, but don't argue them into liking the offer. An objection is useful research even when you think the event offers good value.

Choose the price research method that fits the uncertainty

You don't need every pricing method. Choose one because it answers the unresolved question, and understand the limits before distributing the survey. For many small operators, interviews followed by a straightforward test of a credible offer will be more useful than a complicated model built from weak recruitment.

Use price perceptions when you don't know the range

The Van Westendorp method asks people to name amounts they associate with four price perceptions. QuestionPro's explanation of the method describes these as too cheap, cheap or good value, expensive, and too expensive. It helps investigate the range people associate with a defined offer.

Those answers can tell you where to investigate next. They don't tell you how many tickets will sell. A price that sounds normal can still be rejected when the person considers their diary, other spending or confidence in the organiser. Treat the output as price perceptions among the people who answered.

Use a recognised instrument and competent analysis if you choose this method. The order and meaning of the questions matter. Don't average four price amounts into a supposed ideal ticket price. Nor should you select a chart intersection and call it your most profitable price without considering actual demand and costs.

For our workshop, this method would be useful if interviews revealed wildly different expectations about what a practical training day normally costs. It could help identify candidate prices worth investigating. If you already have credible candidates of $120, $140 and $160, a direct purchase-intention comparison may address the next decision more closely.

Use purchase questions to investigate candidate prices

Gabor-Granger research presents prices and asks whether the respondent would buy the described offer. Qualtrics' documentation explains a structured approach in which later prices depend on earlier answers. It can produce a stated demand pattern across prices. It remains survey evidence, rather than completed purchases.

This method needs a stable offer and careful administration. The prices shown, starting point and sequence can influence the answers. If you're using a named research method, follow an appropriate design rather than turning a casually ordered price list into a method claim.

Another option is to assign different participants to different prices, with each person evaluating one price for the same offer. That avoids showing every respondent a ladder of amounts. It also requires enough suitable participants in each group and a plan for interpreting uncertain differences. It isn't the same design as a sequential Gabor-Granger study.

Suppose you choose that separate-group approach for the workshop. One group sees $120, another $140 and another $160. Every other detail stays the same. Ask whether they would purchase at that complete price, and make declining a comfortable answer. A follow-up can investigate the main reason for their decision.

Use a paid offer when the purchase is deliverable

A completed purchase provides evidence that somebody accepted the tested offer. It also brings a real obligation to the buyer. Only sell an event you can deliver under the terms you publish. Research isn't a reason to advertise an unarranged event as confirmed or collect money without a workable delivery and refund plan.

A smaller paid pilot can help you learn, provided you recognise what changed. A room of twenty with direct tutor attention is a different experience from a room of a hundred. It may validate the smaller offer and expose practical problems, but it doesn't prove the larger event will sell at the same price.

A limited release for a properly arranged event is closer to the final purchase. Record the price, quantity, audience and selling window. The earliest buyers may be your strongest supporters. Their purchases are useful evidence, but selling the first allocation doesn't establish acceptance among everyone you still need to reach.

Write questions people can answer without helping you

A pricing question can quietly ask for encouragement. "Would you support an affordable workshop that helps independent venues succeed?" gives people several reasons to say yes without thinking about a purchase. Remove the praise and describe what they would actually get.

Pew Research Center's guide to writing survey questions explains why wording, answer choices and question order need care, and why new questions should be pretested. For an event operator, the practical step is to ask a few suitable people to complete the draft and explain what they thought each question meant before you send it widely.

Here's a starting sequence you can adapt for interviews and a short survey. It isn't a validated research instrument. The background questions come before the proposed event, so people describe their past decisions before seeing your price.

1. Which comparable paid event did you most recently consider attending? Allow "none" and ask when it was.

2. Did you buy a ticket, attend through somebody else's booking, receive free access or decide against attending?

3. If you bought, what was the complete per-person ticket price, what did it include and who paid? Allow "don't remember".

4. What was the main reason you bought or decided against buying? Let the person answer before offering categories.

5. After showing the event description, what would you expect to receive, and what information is missing?

6. At the stated complete price of $140 per person, would you purchase a ticket for the described date? Offer yes, no and not sure, without treating uncertainty as a yes.

7. What is the main reason for that answer? Ask about a practical obstacle only after hearing the person's explanation.

8. If another person must approve payment, who makes that decision and what would need to happen before you could book?

Keep the price in question six consistent with the participant's assigned version if you're comparing prices across groups. Don't show them the other versions first. If you instead use a recognised sequential pricing method, replace that part of the sequence with its properly designed instrument.

For a consumer event, replace the employer question with the relevant buying situation. That might mean a group deciding together, a household arranging childcare or a buyer waiting for a friend's confirmation. Don't add questions about personal circumstances unless they help answer the decision and participants can respond appropriately.

Test the wording on a phone as well as a computer. A price can lose its meaning if the inclusions are hidden several screens above it. Make the description available while people answer, and check that every version displays the same information.

If someone says no because they can't attend the proposed date, preserve that response. You can investigate price acceptance among available participants separately, but label the smaller group clearly. Removing inconvenient answers until the price looks attractive produces a different question from whether your proposed event will sell.

Also resist promising a discount for completing the survey. You may want to thank participants, but an expected reward can change how they answer and how they behave later. Whatever recruitment arrangement you choose, record it with the results so your team understands the context.

Read the survey without inventing a sales forecast

Let's give the workshop an invented research result. You recruit 300 suitable respondents through the routes you've recorded and randomly assign 100 to each of three versions. Each version describes the same event and shows one complete ticket price. These are hypothetical participants and answers, created only for this example.

At $120, 60 of 100 say yes. At $140, 50 of 100 say yes. At $160, 35 of 100 say yes. Keep no and not sure in separate categories in your working data. The yes count is the only category used in this particular comparison; you're not quietly counting uncertainty as a likely sale.

You now have a stated purchase response of 60%, 50% and 35% within those groups. You don't have evidence that 60%, 50% or 35% of everybody you can reach will buy. Recruitment came through your chosen routes, participation was voluntary, and answering the question required no payment.

Multiplying price by yes responses gives $7,200 at $120, $7,000 at $140 and $5,600 at $160, per hypothetical group of 100 respondents. These aren't revenues you've earned or sales forecasts. They're a way of comparing the stated responses within this invented exercise.

Even on that limited basis, revenue alone misses the event's delivery costs. Suppose each paid place would add $20 in variable costs under the budget assumptions we'll use below. The corresponding survey-based contribution figures would be $6,000, $6,000 and $4,900. Contribution here means the ticket amount left after that per-person cost, before fixed costs.

The $120 and $140 options now tie on that simple calculation. That doesn't prove they're commercially equivalent. Actual conversion, the cost of reaching buyers, capacity and the mix of respondents still matter. It does show why choosing the price with the highest hypothetical revenue can answer the wrong business question.

Look at the explanations too. If people at $160 repeatedly say they don't understand who is teaching, the next step may be to make the tutor's relevant experience clearer. If people understand the programme but don't consider it worth that amount, you have a different problem. Don't rewrite every objection as a marketing misunderstanding.

Keep respondent groups visible. If employer-funded managers respond differently from people paying personally, report their counts separately where useful. A subgroup with very few answers deserves a cautious description, rather than a precise price recommendation. Don't use percentages to make a handful of responses look like broad demand.

Check whether a plausible price can support the event

Now put the price candidates beside the workshop budget. Our fictional event has 100 paid places after the layout and all other occupancy requirements have been accounted for. That is a planning assumption, not a recommendation for venue capacity. There is no sponsor income, merchandise revenue or other income in this example.

Fixed costs total $9,000. The illustrative allocations are $1,800 for the venue, $2,500 for teaching and preparation, $1,200 for event staff and owner time, $600 for equipment and administration, $1,200 for promotion, $400 for the research and $1,300 for contingency. We treat that whole contingency as spent when testing the budget.

Variable costs are an assumed $20 per paid attendee for catering, materials and selling costs combined. These are invented allowances, not supplier quotes or Loopyah fees. The example assumes no sales tax applies to the ticket, includes purchase taxes in cost allowances and excludes income tax. Your actual budget needs the charges, taxes and payment arrangements that apply to you.

At $120, each ticket leaves $100 after the $20 variable cost. Covering $9,000 requires 90 paid tickets. At $140, each leaves $120, so you need 75. At $160, each leaves $140, so you need 65 tickets, rounding up because 64 would leave you short.

Those are different attendance requirements for the same event. The survey's strongest yes response was at $120, but that price also requires the most paid places to cover costs. At the full 100 paid places it produces only $1,000 after the stated costs. It can't deliver a $1,500 target surplus under these assumptions.

At $140, 88 tickets produce $1,560 after costs. At $160, 75 tickets produce $1,500. Neither target is a prediction. They tell you what each price requires, so you can judge whether your purchase evidence supports the attendance the budget needs.

That's where your event break-even calculation helps the research. It provides a testable requirement. If you can't find credible buyers at the price needed for a workable attendance target, you need to change the offer, reduce costs, secure other revenue or reconsider the event.

Don't solve that mismatch by taking the survey's yes percentage and multiplying it by your follower count. Followers aren't all reachable buyers, research participants aren't a random draw from the entire audience, and a yes isn't a booking. Write down the missing evidence instead of manufacturing a forecast from incompatible numbers.

The budget also tells you which price questions matter most. If $120 cannot achieve the required result even at capacity, spending another week deciding whether $119 sounds friendlier won't resolve the problem. Investigate the $140 offer or change the event's cost and delivery plan before spending more on fine price differences.

Run a paid test you can honour

Suppose the research makes $140 worth testing. You choose a limited release for a confirmed event whose delivery you can fund even if the test disappoints. That last condition matters. Buyers shouldn't discover that your ability to deliver depended on a private research threshold you never explained.

Before opening sales, decide what the test can settle. You might want evidence of purchases beyond your own contacts, acceptance of the full $140 price and a better understanding of which recruitment routes bring buyers. Set the release quantity, review date and spending limit in advance.

A limited release is still a real ticket sale. Give buyers the accurate programme, location, timing, complete price and applicable terms. If you can't yet offer a confirmed event, use an honestly described research or interest page instead. Keep interest registrations separate from purchases, and don't imply that the page reserves confirmed admission.

With Loopyah's ticket releases, a ticket type can have several releases with their own prices and quantities, and the next opens when the previous one sells out. Use that where a planned release structure suits the event. The system handles the release change; you still decide what each allocation is for and what the results justify.

A sequence of releases isn't a controlled comparison of prices. Later buyers see the event at a different time and may know more about the programme. They may also be less connected to you than the first buyers. If you sell one allocation at $120 and another at $140, describe the two outcomes without claiming the price alone caused the difference.

For the fictional $140 test, suppose you retain 25 paid tickets after refunds. They came through 20 orders, including group bookings. Those are 20 orders and 25 paid places; check how many distinct buyers placed the orders before treating them as separate buying decisions. Both counts matter. One company buying several places is useful revenue, but it isn't several independent buying decisions.

The 25 tickets contribute $3,000 after the assumed $20 variable cost per place. Against the full $9,000 fixed budget, you still need another $6,000 in contribution. That means another 50 tickets at $140 to break even, assuming the same costs and no further refunds. Twenty-five early sales haven't settled whether those next fifty buyers exist.

Check what refunds cost as well as how many paid tickets remain. In this simplified example, the retained-ticket calculation assumes the $20 variable allowance scales with retained paid attendance. A real refunded order might leave payment charges or committed catering costs behind. Add those unrecovered amounts to the forecast rather than letting them disappear when you remove the ticket from the count. A replacement buyer restores a sale only when they actually purchase; returning the place to availability isn't replacement revenue.

Keep test spending inside the budget you've already built. If $300 of advertising came from the $1,200 promotion allowance, don't subtract it again as a new fixed cost. If those ads produced 15 retained tickets, their observed advertising cost was $20 per retained ticket. That describes this test, not the cost of every remaining sale.

The rest of the promotion allowance still has to support the remaining campaign. If the research convinces you that another $700 beyond the existing budget is necessary, add that cost. Don't preserve the original break-even number while quietly increasing what you'll spend to reach it.

Investigate a weak result before changing the price

Sales can disappoint for reasons the survey didn't capture. Check whether suitable buyers actually saw the offer, understood what admission included and could complete payment. Ask people who considered it what stopped them, without assuming every abandoned visit was a price objection.

The GOV.UK Service Manual's measurement guidance recommends combining transaction measures with user research and other information, including costs and feedback. For a ticket test, that means reading purchase behaviour alongside the questions and obstacles buyers report.

If people didn't know the tutor was relevant to their work, clarify the description and record the date of the change. If the date conflicts with their busiest trading day, investigate whether a different date would be viable. Those are changes to the offer or its explanation, and the next results belong to the revised version.

Price may be the problem. If so, calculate what a reduction requires before applying it. Under our fictional costs, ten $140 tickets contribute $1,200. At $120, you need twelve tickets to contribute the same amount. Those extra buyers also require space, and you still need evidence that the lower price will bring them.

A discount offered to everyone can also reduce receipts from people who would have paid the original amount. Keep the allocation and purpose explicit. Our ticket pricing strategies guide covers the wider choice of releases, groups and access tiers once you've established the price evidence.

If you invite previous customers to a real release, Loopyah's attendee email tools let you build the message and send yourself a test. Check the offer and complete price before sending. The purchase is the evidence you're investigating; an email open doesn't answer whether that person accepted the ticket price.

Be cautious about comparing two public prices at once. Buyers may share links, notice different amounts or return through another route. If you need a formal price experiment, plan assignment, sample size, measurement and fair buyer treatment with appropriate expertise. A small event may be better served by a clear public offer and careful learning across editions.

Follow the buying decision when somebody else pays

Employer-funded events need a little more investigation because the person answering may not control the money. An enthusiastic delegate can explain why the programme matters, but you also need to understand what the approver will authorise. Ask for the actual process rather than accepting "the company will cover it" as confirmed spending.

Suppose a venue manager likes the $140 workshop and wants to bring three colleagues. They describe four places as affordable. That is one potential order worth $560, subject to approval. It isn't four sales, and it doesn't establish that the manager would personally pay $140 if the company declined.

Ask what information the manager would submit. They might need the programme, tutor details, a clear explanation of relevance to their role and the full order amount. Find out when the approver can decide and whether the booking must pass through procurement. A stated budget limit is useful, but authorisation for this purchase is stronger evidence than a general allowance.

You can investigate that process before taking money. Ask whether the manager would forward the accurate offer to the approver, and agree when you'll follow up. Record a request for information, a submitted approval and an authorised booking separately. Don't add a company name to your sales total because someone said the internal conversation sounded positive.

Keep the terms consistent when interpreting the result. An approved invoice payable later creates a different cash position from a completed card payment today. If you offer payment terms, decide whether your business can fund delivery before the payment arrives and handle the risk if it doesn't. The face value alone doesn't explain how much money is available for the venue deposit.

The same reasoning helps with consumer group bookings. A person may say the price is fine but be unwilling to pay for everyone before their friends reimburse them. Ask what normally happens when that group attends an event. You may need clearer shareable information or a workable booking arrangement, rather than a lower ticket price.

Keep those explanations attached to the result. "No because my employer won't approve this topic" and "no because the ticket is too expensive for me" suggest different next steps. A price survey that combines them into one rejection count can show the scale of hesitation while leaving its cause unclear. The follow-up is how you find out what you can actually change.

Keep a decision record you can use next time

Finish with a short price-research record, rather than a folder of disconnected answers. State the event version tested, intended audience, recruitment routes, dates and complete prices. Keep interview observations, stated purchase answers and retained bookings in distinct fields so nobody later treats them as equivalent evidence.

For each method, explain what remains unknown. A price-perception survey might leave buying likelihood unanswered. A paid pilot might leave the larger format untested. A limited release might establish acceptance among regulars while leaving new-customer demand uncertain. Those limits tell you what to investigate before the next substantial commitment.

For the workshop, a useful decision would read something like this: "We will retain the $140 offer while testing reach beyond existing contacts. Twenty-five retained tickets establish early purchases, but another fifty at the same price are needed to cover the current budget. We will review the remaining sales evidence before authorising additional spending."

Give that review an owner and a date connected to the next real decision. Keep the remaining commitments and available funds visible. If the event is already confirmed, any spending change must preserve what you've promised buyers. If you're still researching an unconfirmed event, decide whether the evidence supports making the commitment at all.

After delivery, compare the original price decision with actual quantities, refunds, discounts, marketing costs and delivery costs. Ask whether buyers received the experience they expected, too. A strong first sale followed by poor value is a weak foundation for another edition.

For your next price decision, start by writing the offer and the number of paid tickets each credible price requires. Then choose the research that addresses the biggest missing piece. If the survey sounds positive but you still can't explain where those buyers will come from, keep investigating before making a larger commitment.