Audience survey for creators: what to ask before a course
How to survey your audience before creating a video course: 7 useful questions, the ones to avoid, how to read the answers and how to handle emails.
Before recording a course, it pays to ask your audience what they need. A well-designed survey costs an afternoon and can save weeks of work on a topic few care about. A badly designed one gives false confidence.
This guide offers useful questions, ones to avoid and a method for reading the answers. Keep every survey's limit in mind, though: opinions are cheap, bookings tell the truth.
What is a survey for?
Three things: understanding which problems your audience has, collecting the words they use to describe them and choosing the course format and level. It can't tell you how many people will buy: that's what a pre-sale is for, as we explain in validating a course idea with a pre-sale.
Which questions should you ask?
Seven are enough:
- What's your biggest difficulty with [topic] right now? (open)
- What have you already tried to solve it? (open)
- Have you spent money trying to solve it? On what? (open or multiple choice)
- What would you like to be able to do in three months? (open)
- Which format do you prefer? (recorded lessons, live, mixed)
- How much time can you give it each week? (multiple choice)
- Can we contact you for a 15-minute chat about it? (yes/no, optional email)
| Tells you something reliable | |
|---|---|
| What have you already tried to solve the problem? | Yes |
| Have you already spent money on it? | Yes |
| Which format do you prefer? | Partly |
| Would you buy a course on this topic? | No |
| How much would you pay for this course? | No |
Our editorial framework. Questions about the future tend to get optimistic answers.
The last question is the most valuable: ten 15-minute conversations tell you more than a hundred written answers. Listen to the words people use and take notes.
Which questions should you avoid?
Ones asking people to predict the future: "would you buy?", "how much would you pay?". People answer optimistically or out of kindness, especially to a creator they like. Ask what they've already done and spent instead: past behaviour is a far more reliable signal.
Also avoid leading questions ("Don't you think a lighting course would be useful?") and double-barrelled ones ("Are you interested in lighting and composition?"), which can't be answered precisely.
An example of reading the answers
A creator who teaches productivity gets 240 survey responses. On the biggest-difficulty question he groups the open answers by theme and counts: 92 mention too many emails and notifications, 61 procrastination, 40 project organisation, the rest are scattered. On "have you spent money?", 55 people in the email-and-notifications group mention apps, books or courses, against 12 in the procrastination group. So the first theme has both more answers and more people who've already paid to solve it. Also, 38 people agree to a 15-minute call: in those calls a phrase keeps coming up, "I spend the morning replying instead of working", which becomes the course promise. As a result, he picks the email theme and tests it with a pre-sale. In practice, counting themes and past spending is more useful than averaging the closed questions. The numbers are our example.
How do you collect emails properly?
If you ask for an email to follow up with someone, use it for that. If you also want to send offers or your newsletter, you need separate, free and specific consent. GDPR Article 7 requires withdrawing consent to be as easy as giving it, and says that when assessing whether consent is freely given, account is taken of whether a service is conditional on consent that isn't necessary for it. How to build your list properly is covered in lead magnet ideas for creators.
Which mistakes should you avoid?
- Trusting predictions. "I'd buy" isn't a sale.
- Long surveys. Beyond eight questions, complete responses fall.
- Leading questions. You get confirmation, not information.
- Ignoring open answers. They're the most useful part.
- Using emails for undeclared purposes. You need separate consent.
Key terms. An open question lets people answer in their own words. A closed question offers predefined options. Past behaviour is what people have already done, more reliable than what they say they'll do.
How we checked. We read GDPR Article 7. The questions, frameworks and example are ours: we found no specific studies on creator surveys, so we don't quote response rates. Contact: hi@heytea.app. Editorial note: we check every figure against the sources listed below and correct mistakes openly.
Frequently asked questions
Why survey your audience before making a course?
To find out which problems your audience really has, in their own words, and which format they prefer. A survey doesn't tell you whether people will buy, but it helps you pick the topic and write the promise. The proof of purchase comes later, with a pre-sale.
How many questions should a survey have?
Few: between five and eight. Every extra question reduces complete responses. A few open questions on the problem and some closed ones on format and level beat a long questionnaire nobody finishes.
Which questions should you avoid?
Questions asking people to predict their future behaviour, like 'would you buy a course on this?'. People tend to say yes out of kindness or optimism. Ask instead what they've already done: what they've tried, what they've spent, what didn't work.
Can I use survey emails to send offers?
Only if respondents gave free, specific consent to receive communications, separate from completing the survey. GDPR requires consent to be freely given and as easy to withdraw as to give. If you collect an email only for the survey, use it only for that.
How do you read open-ended answers?
Group them by theme and count how often each comes up. Note the exact phrases that recur most: they become your sales page headings and email subject lines. A theme that comes up often, in strong words, is a good course candidate.
Sources
- Regulation (EU) 2016/679 (GDPR), Article 7. Accessed 19 October 2026. gdpr-info.eu