How to choose which conference audience to serve first

So you've got a conference idea, and several groups could benefit from it. Department heads want the strategic view. The people doing the work want practical help. Suppliers want to meet both. Every conversation adds another possible audience, and the programme is already getting longer before you've sold a ticket.

Choose the group with the strongest combination of a problem worth paying to solve, a believable way to fund attendance, and people you can actually reach. Then check whether you can deliver a useful day for that group at a ticket price and attendance level that cover your costs. The largest potential audience won't necessarily give you the strongest first conference.

Your primary audience should guide the difficult decisions. Whose questions get the longer session? Who needs to be in the room for the conversations to work? If a sponsor asks you to change the agenda, whose reason for buying are you protecting?

This guide walks through those choices before you commit to a venue or a big speaker bill. We'll compare three possible audiences for a fictional operations conference, test the buying process, and build a decision you can explain to your team. All example figures are invented planning assumptions in USD, not market rates, survey results or predictions of ticket sales.

Start with the decision your conference helps someone make

"Operations professionals" describes a field. It doesn't explain why somebody should leave work, pay for admission and spend a day with you. You need to know what they're trying to do, what makes it difficult, and why learning alongside other people would help.

Imagine an organiser considering a conference about improving multi-site retail operations. A store supervisor might need help preparing a first management rota. A regional operations manager might be choosing how to compare performance across locations. A business owner might be deciding whether to open another store. All three work in retail, but they would buy different days.

Write a working sentence for each candidate. For the regional manager, it could be: "People responsible for several retail locations need to compare ways to reduce avoidable staffing gaps without leaving store managers to improvise." That identifies a responsibility and a problem you can investigate. It also gives you something more useful to discuss than whether people enjoy conferences.

You haven't proved that the problem is urgent, widespread or worth the proposed ticket price. Those are questions for research. At this stage, you're making the audience definition specific enough to test. If you can't describe the work the person is trying to improve, a detailed profile of their age, favourite podcast and preferred social network won't rescue it.

IEEE's guidance on conference scope and audience connects the subject, intended attendees and event objectives. It asks planners to consider relevant specialties, location and audiences beyond their existing network. Although written for IEEE conferences, that connection is useful here: the programme and the people it serves need to make sense together.

Keep your proposed outcome within what an event can deliver. You can offer comparisons, worked examples, useful questions and conversations with experienced peers. You cannot promise that a delegate will fix their entire operation in a day. A credible outcome might be leaving with a shortlist of approaches and a plan for testing one at work.

Make room for the networking reason too. Someone may already have access to written information but struggle to meet peers handling the same responsibility. Ask what they want to discuss privately, what they can share, and which people they rarely get to question. A conference can be worth paying for because of the particular conversation it makes possible.

Compare a few specific audiences before choosing one

Start with a shortlist you can research properly. In our example, the organiser compares independent retail owners, regional operations managers at growing retail businesses, and people moving into their first store-management role. Three is a choice for this exercise, not a rule about the ideal number of market segments.

Describe each group using responsibility, working situation and the change they're facing. "Regional operations managers responsible for several locations during expansion" is much more useful than "senior professionals aged 30 to 50." People with similar job titles can have very different authority, resources and reasons to attend.

Next, record what you know separately from what you assume. You might know that an association publishes a newsletter for regional managers. You might assume those readers have training budgets. The first fact suggests a possible route to reach them. The second needs a conversation with people who buy and approve professional development.

The US Small Business Administration's market research guidance recommends examining demand, market size, location, existing alternatives and what customers pay. For your conference, use those as separate questions. A large population of relevant workers doesn't establish how many are reachable, interested in this programme or able to buy within your sales window.

For each candidate, keep a short comparison record:

• The work problem they would come to address, and what makes it pressing now.

• The person who attends, the person who pays, and anyone who approves the absence.

• The channels through which you can reach relevant people with permission or an agreed partnership.

• The programme and peer group they would find useful.

• The price, travel and time commitments you still need to test.

• The evidence against choosing them, including obstacles you cannot currently solve.

Don't turn this into a contest for the most polished description. One candidate might have a compelling problem but no workable way to attend. Another might be easy to reach because you already know the community, yet have little reason to pay for a full conference. Keep those weaknesses visible.

You can make a provisional choice before every uncertainty disappears. You do need enough evidence to explain why it deserves the next research or sales effort. "We know people in this group" can justify starting interviews there. It doesn't, by itself, justify designing the whole event around them.

Find out whether the problem is urgent enough

Ask people about the last time the problem happened. What did they do? Who became involved? What did it cost in time, money or a delayed decision? What have they already tried? These questions help you distinguish a topic someone finds interesting from work they are actively trying to improve.

For the regional manager, a useful conversation might begin with the most recent staffing gap that affected several locations. You want to understand how they noticed it, what information they had, and which decisions they could make. Let them describe the situation before showing your proposed sessions. Otherwise they may simply repeat the language you've supplied.

The Government Digital Service's guide to in-depth interviews recommends open, neutral questions and discussion of real experiences. It also advises listening and following up rather than sticking rigidly to a script. Applied to conference research, that means finding out what happened at work before asking whether your idea sounds appealing.

Ask what people use instead of attending. They might learn from colleagues, buy a short course, pay a consultant, visit another operation or do nothing until the problem gets worse. Those alternatives explain what your event has to offer. You don't need to persuade everyone that a conference is the best response.

Look for differences within the candidate audience. A manager expanding into new regions may need something different from one consolidating an established network. If the urgent problem belongs mainly to the expansion group, refine the definition. That can make the programme more useful without requiring you to exclude everybody else from buying.

Avoid assigning financial losses to interview comments unless the person can substantiate them and you have a proper basis to use them. "This creates extra work for the store team" is a finding you can record. "Every business loses $20,000 a year" is a claim you cannot manufacture from a frustrating anecdote.

Keep a note of disagreements. If some managers say the issue is already solved, ask what changed and whether their circumstances differ. You may discover that your intended audience needs a different topic, or that the conference should focus on people facing a particular transition. Both findings are more useful than collecting agreeable quotes.

At the end of this stage, you should be able to describe the problem in language your potential delegates recognise. If they repeatedly correct your wording, use theirs where it accurately captures the work. That language will later help you write the event page, but the immediate job is choosing whom you can help.

Speak to people outside your easiest circle

Your own contacts are a sensible place to begin. They're also likely to share some of your interests and assumptions. A conference built entirely from enthusiastic friends can feel convincing long before you've tested whether anyone outside that circle wants it.

Recruit across the circumstances that could change the decision. In the retail example, that might include different numbers of locations, different travel distances, employer-funded and personally funded attendance, and people who have stopped buying conferences. These differences matter because they can change the programme, total attendance cost or approval process.

GDS's participant recruitment guidance says research participants should be actual or likely users. It warns that recruitment methods, timing and location can introduce bias, and recommends varying the approaches used. It also calls for including disabled participants and people with different support needs. Those are useful checks when your first responses all come from one friendly community.

For a small initial exercise, you could plan six exploratory interviews in each of our three candidate groups. That's eighteen conversations chosen for this fictional project, not a representative survey or a validated sample-size prescription. Add or change research as gaps emerge. Six similar answers from the same referral chain don't establish the view of an industry.

Use a short recruitment description explaining what you're researching and who you need to speak with. Don't describe the event as confirmed if it isn't. Explain how you'll use notes or recordings and obtain the relevant agreement before recording. Keep contact details and identifiable accounts of workplace problems secure, with access limited to the people doing the research.

Invite people to decline without becoming sales prospects by default. If you offer compensation for research, record that separately from any later ticket purchase. Someone accepting a research incentive hasn't demonstrated demand for your conference. Nor has a supplier agreeing to an interview necessarily joined your delegate audience.

Check whose voices remain absent. A daytime interview schedule might favour people with flexible work. A referral from one employer might overrepresent its particular operating model. You can still use what those people tell you, but describe the limitation and look for a way to hear from others before making a costly commitment.

Follow the ticket purchase through to approval

The person who needs the conference may have no authority to buy it. This matters especially when you're comparing a personally funded audience with employees whose attendance depends on an employer. Ask about the actual route money and permission would have to take.

Speak to potential delegates about their most recent professional event purchase. Who selected it? Who approved the ticket? Was travel approved separately? Did someone need to cover their work? How long did the decision take? If they haven't attended recently, find out whether that reflects lack of interest, budget restrictions or something about the available events.

Then, where possible, talk to people who approve attendance. A manager may want to know which work problem the programme addresses, how the employee will use what they learn, and what the total absence costs. A finance team may need supplier details and payment documentation. Ask what their process requires rather than guessing from the delegate's enthusiasm.

Explore each group's needs before showing an offer. Then, if you're testing the same conference concept across groups, keep the proposed format, location and price consistent so you can understand the differences in response. In this example, show a one-day regional conference about multi-site staffing, its core sessions and intended peer group, with a proposed $300 total admission price. Make clear that this is a research concept, with no ticket currently offered.

If first-time managers need introductory rota training instead, record that as a different event option. It may deserve its own programme and budget. Their rejection of the multi-site conference doesn't mean they're a poor audience for every paid event. It tells you the current offer doesn't match what they need. Document any changes you make between research rounds rather than mixing responses to different offers.

Consider a fictional manager whose admission would cost $300 and travel $120. Their direct outlay is $420 before any additional accommodation, meals or other expenses, and the employer still has to consider work coverage. If the company funds tickets but not travel, the $300 event price doesn't describe the person's whole decision.

Don't infer affordability from salary or seniority. An owner may control spending but be reluctant to leave the business. A less senior employee may have a well-supported development budget. Record what the person says about the process and what you've actually confirmed with the payer.

Give potential approvers something concrete to react to. A brief outline with the work problem, session outcomes, date, location, total admission price and inclusions is enough for an initial discussion. Ask what they would need before considering a real purchase. Don't treat a request for more information as approval.

In your comparison record, distinguish confirmed procedure from expected funding. "This employer requires manager approval and an invoice" describes a route. "This employer will buy ten places" requires an actual commitment from someone authorised to make it. Keeping those statements separate prevents an orderly purchasing process from becoming imaginary ticket revenue.

Check whether you can reach enough of the right people

Once an audience looks attractive, explain how people in that group will hear about the event. A market can be large and still be expensive for a new organiser to reach. You need a practical distribution plan alongside the audience definition.

List specific routes you can investigate. These could include an association newsletter, relevant professional communities, previous eligible buyers, speakers with a closely matched audience, or paid campaigns you can afford to test. Name an owner for each conversation or activity. "LinkedIn" on its own is a platform choice, not a plan for reaching regional managers.

For a possible partner, ask who receives the communication, what the partner can actually offer, when it could run and what it would cost. A warm conversation with an association doesn't mean it will send your invitation. Confirm the arrangement before placing its promised reach into the sales plan.

Our guide to selling conference registrations through professional associations covers those arrangements in more detail. Here, the decision is whether the route is plausible enough to support choosing this audience. You can investigate a partnership before committing to build the event around it.

Keep overlapping audiences in mind. Suppose two potential partners each report 1,000 relevant newsletter subscribers. Their combined figures represent 2,000 subscription records, not necessarily 2,000 different people. Even a verified unique audience wouldn't tell you how many will receive, read or act on your invitation.

Compare how much work each candidate requires. You may have a strong existing relationship with owner communities but no permission-based route to employed regional managers. That doesn't automatically make owners the better choice. It means reaching managers is an assumption you must test before spending heavily on their conference.

Set a limit on what you'll spend to learn. You might investigate a partner placement or a small campaign with a defined budget, useful destination page and review date. Measure relevant enquiries and completed purchases when sales begin. Views, reactions and free registrations can help diagnose interest, but they don't replace evidence that the paid offer works.

Also ask what happens if the strongest channel falls through. If one partner is your only credible route to the audience, you need its distribution agreement before relying on that route. Confirm it, find another way to reach enough people or choose a format whose costs reflect the uncertainty. Don't compensate by assuming a much higher response from an untested channel.

Put the audience choice through a simple budget

You need to know how many paid delegates make the proposed conference viable before deciding whether your reachable audience is large enough. Otherwise you'll choose a group, fall in love with the programme, and discover too late that the business requires attendance you have no credible way to deliver.

For our fictional regional-manager conference, assume an approved layout allows 120 paid delegate places after all non-paying allocations. The venue and organiser still need to account for speakers, workers and everyone else in the occupancy arrangements. The 120 figure is a planning assumption for saleable inventory, not a safe-capacity calculation.

Assume fixed event costs of $24,000. This includes $5,000 for the venue, $4,000 for production, $4,000 for speakers and their agreed expenses, $3,000 for staffing, $3,000 for promotion, $2,000 for access provision, insurance and administration, and a $3,000 contingency allowance. Treat the entire allowance as spent in every calculation. These amounts are invented allocations, not supplier quotes or recommended spending ratios.

The ticket costs the buyer $300 in total. Assume $60 per paid delegate covers all variable costs, including applicable ticketing and payment charges and catering. This is an invented combined cost, not a Loopyah fee quote. Costs associated with non-paying participants are already included in the fixed budget. Purchase taxes are included in the assumed costs; the model assumes no sales tax deducted from admission, excludes income tax and has no sponsor or other income. Replace those assumptions with the treatment that applies to your event.

Each retained full-price ticket therefore leaves $240 towards fixed costs. Divide $24,000 by $240 and the event needs 100 paid tickets to break even. At 90 paid tickets it loses $2,400. At the full allocation of 120 it has a $4,800 surplus before any excluded business expenses or taxes.

If you want a $3,000 surplus on the same basis, you need 113 full-price sales. Those tickets contribute $27,120, leaving $3,120 after fixed costs. A target that requires 113 of 120 places gives you little room for weaker sales. It may be possible, but you should recognise how demanding the plan is before taking on the commitments.

Now return to your audience comparison. Can you explain a credible way to sell that many places to regional managers within the actual buying window? If the answer relies on a partner who hasn't agreed to promote, employer budgets you haven't checked and a programme nobody has reviewed, the budget has exposed the work still ahead.

Our event break-even guide explains the wider calculation. For audience selection, use the result as a challenge to your assumptions. You can reduce the fixed commitment, change the format, test a different price or investigate another group. Adding an unrelated audience isn't automatically the best fix.

Check discounts before using them to make demand look stronger. If twenty of the 120 tickets sell at $250, each contributes $190 under the same $60 variable-cost assumption. The other hundred at $300 contribute $24,000. Total contribution is $27,800 and the sellout surplus falls to $3,800. Lower prices change what the audience must deliver financially.

Finally, check cash dates separately. A hypothetical event that breaks even at 100 tickets may still require deposits before buyers finish their approval process or ticket receipts become available. Record when supplier payments fall due and when money can actually reach your bank. Choosing an employer-funded audience can make sense while still requiring you to fund a longer sales cycle.

Make sure the people belong in the same programme

A primary audience is useful because it helps you build a coherent experience. That doesn't mean every delegate must have the same job title. It means they share enough context and purpose for the sessions and conversations to be worth their time.

For the regional managers, a session comparing ways to cover staffing gaps across locations could work well. A session teaching someone to write their first rota might be too introductory. A session about selling a retail business might be valuable to owners but unrelated to the managers' immediate responsibility. These are programme decisions you can make once the primary audience is clear.

Test a rough agenda before booking names. Show potential delegates the session purpose, level of assumed knowledge and expected takeaway. Ask which parts help with their work and which don't. If the answer is "I'd come for one session and leave," find out whether the programme is too broad or the format should be shorter.

Then test the peer mix. Would managers be able to discuss their difficulties candidly with suppliers in the same room? Would owners add useful experience, or turn every discussion towards investment decisions the managers don't control? You can invite different perspectives while setting clear expectations about how sessions and introductions work.

For this example, the organiser could keep regional operations managers as the main group and welcome owners who directly manage several locations. An owner attending in that capacity shares the central work problem. That is a stronger reason for inclusion than hoping any business owner might buy a ticket.

Suppliers could take part through clearly defined sponsorship, a relevant demonstration or an ordinary ticket under published participation rules. Their presence still needs to serve the promised experience. Don't sell managers a day of peer learning and then allow every discussion to become a prospecting session because suppliers were easier to recruit.

Use a straightforward programme test. Take each proposed session and ask what the primary delegate should be able to compare, understand or attempt afterwards. Then ask whether the expected starting knowledge is reasonable. If most sessions need separate beginner and advanced explanations, you may be combining audiences whose needs are too far apart for this format.

Make access part of this choice early. W3C's accessible events checklist covers accessible venues and materials, asking about requirements, and planning support such as captions or interpreters. Use it to investigate what delivery requires. A focused professional audience still includes disabled people and people with different ways of participating.

Also ask about practical barriers that don't show up in a job description. Can the intended delegates leave their sites on the proposed weekday? Would the start time require an overnight stay? Can a business release only one regional manager at a time? Those answers may change the date or format even when the topic is right.

You might decide that a shorter regional day makes more sense than a destination conference, or that the audience needs a repeat date. Cost those alternatives separately. Don't quietly add recordings, remote attendance or another edition to solve every objection. Each promise creates delivery work and may change the ticket's economics.

Choose using evidence, with unresolved problems visible

By now, you should have enough information to compare candidates without pretending to predict the whole market. Keep the decision readable. A long scoring spreadsheet can hide the assumptions just as easily as a vague discussion can.

For each candidate, write what supports the choice, what weakens it, and what you would need to establish next. State where the information came from. Distinguish an interview account, an agreed partner arrangement, a supplier quote and a completed purchase. They answer different questions and deserve different weight.

Here is how a fictional comparison might develop. The independent owners recognise the staffing problem, but the research suggests many are more interested in expansion finance. The first-time managers want practical help, but the proposed $300 conference and employer-release process remain unresolved. The regional managers describe a shared multi-site responsibility and a plausible buying route, while a relevant association is willing to discuss distribution.

Those are illustrative findings invented to show the decision, not results from a real study. Even within the example, the regional managers haven't proved the event will sell. They have given the organiser the clearest next offer to test. The association discussion still needs an agreement, and the employer route still needs actual purchases.

Avoid forcing these differences into a single score unless the scoring helps your team. An unsupported rating of five for willingness to pay remains unsupported after you multiply it by a weighting. A specific unresolved obstacle is easier to act on: "We haven't established whether employers will fund travel to this location."

Some problems should stop the current plan regardless of a candidate's other strengths. If you cannot deliver the promised specialist content, the available venue is unsuitable, or the required sales exceed saleable inventory at the tested price, enthusiasm elsewhere doesn't fix the problem. Change the plan or select another audience.

Write a decision paragraph that your producer, sales lead and programme lead could all use. For example: "We will test a one-day conference for regional retail operations managers handling staffing across several locations. Owners doing the same work may attend. The core programme will compare practical approaches to that responsibility. We will hold further fixed commitments until the distribution agreement, buying process and revised cash plan support proceeding."

Name who can approve those commitments and when the decision will be reviewed. "We'll see how it goes" gives nobody authority to stop an attractive but unworkable idea. You need a decision before the next payment or contractual deadline makes changing direction more expensive.

Test the chosen offer before expanding the audience

The next test should answer the biggest remaining question. If you don't understand the work problem, do more research. If the problem is clear but the buying route is uncertain, test that route with a specific offer. If the route works but the programme is doubtful, get detailed feedback on the agenda and expected outcomes.

When you are ready to sell, provide a real offer you can honour. Explain the confirmed date, venue, programme, intended audience, ticket inclusions, total price and applicable terms. A paid test creates obligations to customers. Don't collect money for an event you cannot deliver and treat refunds as an informal escape from the research.

Set your review point before announcing the offer. Tie it to a real decision, such as whether to release a further venue payment or add an optional production element. Your threshold needs to reflect retained sales, remaining costs, cash availability and what you've promised buyers. There is no universal number of early tickets that makes a new conference safe to proceed.

Suppose our example sells 24 full-price tickets that remain valid and unrefunded at the review. Their combined contribution is $5,760 under the stated assumptions. If fixed costs stay at $24,000, another $18,240 remains to cover, requiring 76 further full-price tickets to break even. Twenty-four tickets is evidence that some people bought. It is not evidence that the remaining 76 will arrive.

Separate places from buyers and employers. Twenty-four tickets might come from one employer, several team orders or many individuals. Those patterns matter for the next sale and for the peer mix. A large order can be valuable while leaving you dependent on one organisation and learning little about demand elsewhere.

With Loopyah ticketing, you can set releases with their own prices and quantities, and the next release opens when the previous one sells out. Use those controls after deciding the offer and allocation. Keep the audience test in your research notes and sales review; an automatic release change doesn't tell you whether enough people will buy.

Pay attention to non-buyers who fit the audience. A person may recognise the problem yet need a different date, clearer employer documentation or stronger evidence about the sessions. Those responses can suggest an improvement. They can also reveal that your preferred format asks too much of the audience.

Don't widen the target simply because early sales are slow. First check whether the offer reached the right people, whether the programme answers their need and whether the buying journey works. Adding beginners, suppliers and owners to the headline can make every message less specific while leaving the original obstacle untouched.

If another group repeatedly asks for a genuinely different day, keep that evidence for a separate decision. A later workshop or edition may be commercially attractive. Cost and validate it as its own offer rather than allowing it to reshape the conference people have already bought.

Turn the choice into a brief your team can use

Once you've selected the primary audience, record the practical implications in one short brief. This keeps the decision useful when speakers, partners and sponsors start bringing their own preferences. The brief should explain who you're serving and how that affects the work, rather than becoming a decorative persona document.

For our example, a usable brief would say that the core delegate manages staffing across several retail locations, is comparing practical ways to reduce gaps, and can benefit from hearing how peers have handled similar decisions. It would identify employer approval and work coverage as parts of the buying process, with the current price and travel assumptions attached.

The programme lead then knows which session proposals fit. The marketing lead knows which responsibility to name in the invitation. The partnerships lead knows why a broad audience of retail enthusiasts isn't equivalent to reaching regional operations managers. Finance knows which ticket allocation, cost assumptions and review dates need monitoring.

Include what you haven't established. Perhaps a partner has agreed to review the proposal but not distribute it. Perhaps the chosen location works for nearby delegates but creates an overnight stay for another region. Recording those limits gives someone a clear research task and prevents uncertain information becoming a promise in the sales copy.

Set a change process proportionate to the event. A new speaker can improve the programme without changing its audience. Adding a track for a different buyer group may change room requirements, production costs and the reason existing customers bought. Require someone to assess those consequences before approving it.

Use ticket history sensibly when you already run other events. With Loopyah's attendee email tools, you can build and test an email and use purchase-based audiences for relevant invitations. Your existing buyers still need to fit the new conference's responsibility and topic. A previous purchase doesn't establish someone's job, budget authority or current need.

Keep research recruitment separate from promotion, and use the current marketing permissions and applicable rules for any campaign. You can ask a partner to share an appropriate invitation without asking for its entire member database. You need a way to reach relevant people, not unnecessary copies of personal information.

Review the choice after the conference

The first edition gives you better evidence about the audience, but only if you record what happened clearly. Compare the intended delegates with the people who bought and attended, using information you legitimately collected. Keep purchaser, employer and attendee identities separate where they differ.

Review whether the main sessions worked for the promised experience level. Look at the questions delegates asked, which examples they found useful, and where the programme assumed too much or repeated things they already knew. A busy room shows attendance. It doesn't establish that the people you wanted to serve received the value you promised.

Return to the financial assumptions too. Compare retained ticket income, discounts, refunds and actual delivery costs with the plan. If you filled the room by discounting heavily, the next decision is different from selling the same places at the planned price. If one employer bought a large share, understand why before forecasting broad repeat demand.

Then decide whether to deepen the same offer, make it easier for the same audience to attend, or test another group separately. Expanding can be sensible when the evidence points there. It can also create a larger event with a weaker reason to buy if the original audience loses the programme it valued.

Our guide to organising a paid conference covers the venue, speakers, operations and ticketing work that follows. Before you take on those commitments, write the audience decision in a form your team can challenge. Who has the problem, who can fund the day, how will you reach them, and can the event work at the sales you can reasonably support? Choose the group for which you can answer those questions most convincingly, then test the remaining uncertainty before spending more.