Interest Isn't Demand: How to Validate Your Course Idea Before You Build It

Most course ideas don't start with research. They start with a feeling that builds slowly. You know a subject well, people keep asking you about it, and one day you catch yourself thinking there could be a course in this.

Maybe there is. But at that point you have an idea and a few encouraging signs, and it's very easy to read those signs as something stronger than they are. Plenty of course projects go wrong right there, in the gap between "people seem interested" and "people will pay me to solve this." You usually don't find out until months later, after the videos are recorded and the sales page is live.

I've spent years working with clients on websites, Kajabi and online courses, and I keep seeing people get absorbed in the building. They're choosing a platform, planning pages, mapping out lessons and working out how to record video, all before anyone has checked whether the business decision underneath it makes sense. That's real work, and it feels like progress. But the first question is a simpler one, and a harder one: do enough people want this enough to pay for it? Answering it well comes down to judging the evidence you have, which is trickier than it sounds, because some signals look a lot stronger than they really are.

Interest is not the same as demand

The encouraging signs tend to look something like this. A friend tells you she'd love to learn that. One of your posts on the topic gets more reaction than usual. You find a Facebook group with thirty thousand members talking about your exact subject. A free guide you put out gets a decent number of downloads.

I wouldn't dismiss any of that, but none of it tells you people will pay for the course you have in mind. What it shows is that the subject has people's attention. Attention is easy to give, and we all give it to plenty of things we'd never spend money on. Someone can watch twenty videos on fixing their golf swing and never book a lesson. Someone can download your free guide and never open it.

So interest is worth having. You just need to be clear about what kind of evidence it is.

A simple way to weigh any signal: what did it cost them?

One useful way to sort these signals is to ask what each one cost the person who gave it.

A like takes a fraction of a second. Telling you "that sounds great" over coffee costs nothing at all, and is often just good manners. Handing over an email address costs a bit more, because people know what tends to land in their inbox afterwards. Spending forty minutes on a call explaining a problem costs real time. Paying money costs the most. It means the person made a decision, gave up something else they could have spent that money on, and accepted that they might be disappointed.

The pattern is that a signal gets stronger as the commitment behind it grows. The cheaper signals still count for something. A like tells you a little, and an email address tells you more. They just shouldn't be given more weight than the commitment behind them, which is why one sale can tell you more than a long thread of enthusiastic comments.

That same thinking sits behind four levels of evidence worth keeping in mind whenever you look at a course idea:

Hope → Interest → Market Proof → Real Validation

Each step asks more of someone than the one before it, and that's what makes the evidence more trustworthy as you go.

Hope: evidence that comes from you

Every course starts with hope, and it should. Your experience, your belief that you can help people and your sense that the subject is growing are all good reasons to look into an idea. They're not yet reasons to build it.

The problem with hope is that all of the evidence comes from you. Your view of what people need, what they ought to want and what you'd buy in their position hasn't cost anyone else a thing. If most of your confidence is coming from here, put the module outline aside for now and go and find out whether other people see the problem the way you do.

Interest: where to look, and what it can't tell you

At this level you stop listening to your own enthusiasm and start watching what other people do. Look at whether people are searching for help with the problem, whether the same questions keep showing up in forums, groups and comment threads, and whether people are describing things they've already tried that didn't work.

Pay attention to the words they use, too. People describe their problems very differently from the way an expert would label them, and that language will be useful later when you write your course description and sales page.

And be careful with big numbers. A group with thirty thousand members tells you the topic has an audience. It doesn't tell you how many of them are active, how many are dealing with the specific problem you'd teach, or whether any of them would pay for a course when they can post a question and get a free answer from a stranger. Interest is a good guide to where you should look more closely, but it can't tell you what to build.

Market proof: is money already changing hands?

The next question is whether people already spend money on this problem. Look for courses, coaching, books, memberships, workshops, software or consultants aimed at the same need.

A lot of first-time course creators get a sinking feeling when they find competitors. I see it the other way around. It's far easier to sell into a market where people already pay for solutions than to convince people that a problem is worth paying to fix in the first place. Competition changes the question from "will anyone pay for this?" to "why would someone choose mine?", and I'd much rather be working on the second one.

One caution, though. A course existing is not the same as a course selling, because anyone can put up a sales page. What you want are signs that people keep buying: offers that have been around for years, programs that run again and again, reviews from actual students, creators who keep adding new products. Read those reviews carefully, and pay particular attention to the disappointed ones. When students complain about an existing course, they're often telling you what they still haven't been able to find.

Market proof is strong evidence, but it's evidence about someone else's offer. The money is changing hands, just not with you.

I learned this on one of my own projects. Several years ago I helped build an Indian vegetarian cooking course called Spice Inspired Kitchen. We knew people bought Indian cooking courses because successful ones already existed, and that gave us confidence. It was real market proof for the category. What we didn't have was any evidence that people wanted to buy our course in particular, and at the time I didn't see those as two separate questions. I think that's one of the easiest places for a course idea to get stuck. The market is real and other courses are selling, but you still don't know if anyone will choose yours. I wrote earlier this year about what that project taught me about whether a course idea is worth building, and it's a big part of why I take the next level so seriously.

Real validation: someone makes a decision about your offer

This is the level people tend to want before they've earned it. Real validation is when someone makes a real commitment to your specific offer. They pay for a pilot version, put down a deposit, buy an early release, or pay you for a workshop or consultation built around the problem your course will solve.

Every one of those involves paying, and that's where the line falls between useful evidence and purchase validation. A free call is good evidence, because someone gave you their time, but it's still research. A waiting list is good evidence too, and a lot stronger than a like, since people have given you their email address and permission to contact them. It still doesn't tell you they'll buy. You only find out what a list is really worth when you open the doors and see how many of those people do.

The payment doesn't have to be large, and it doesn't have to be for a finished course. What matters is that someone decided. Until that happens you're still testing, and that's fine as long as you know it.

Don't ask people whether they like your idea

Almost everyone falls into this one at some point. You describe your idea to ten people and ask, "Would you be interested in a course like that?" Several of them say yes, and most mean it when they say it. But you haven't asked anyone to decide anything. There's no price and no commitment, so saying yes costs them nothing. By the measure we've been using, that's about as weak as evidence gets, however warmly it's offered.

Rob Fitzpatrick wrote a whole book about this called The Mom Test. His argument is that when you ask people about your idea, they tend to tell you what you want to hear, and that you learn far more by asking about their lives and what they've actually done. He wrote it for startup founders, but it applies just as well to course ideas.

So rather than asking people what they think of your course, ask what they've already done about the problem. Find out what they've tried, what they spent, what frustrated them, and what they're doing about it right now. What people have actually done will tell you far more than what they say they might do.

Watch for the evidence you want to see

This is the part that's hardest to notice in yourself. Once you're attached to an idea, research can slowly turn into a search for agreement. You remember the enthusiastic comment and forget the three people who shrugged. You treat curiosity as demand, and you find perfectly reasonable explanations for a weak response.

But you're not doing this research to prove that your course deserves to exist. You're doing it to make a better decision. Sometimes the evidence will say build. Sometimes it will say the problem is real but your solution is wrong, or that you're talking to the wrong people. Sometimes it will tell you not to build at all, and that can feel like failure. It's still a much cheaper thing to learn before three months of recording videos and setting up a sales funnel than after.

The question to ask instead

"Is this a good course idea?" is a hard question to answer fairly, because almost every idea sounds good to the person who had it. I think a more useful question is: what evidence do I have that this problem matters enough for people to pay to solve it, and what did that evidence cost them?

Then go through what you know and sort it. Separate what you believe from what you've seen, what people have said from what they've done, and what they've paid other people from what they've paid you.

You won't get certainty. Business rarely gives anyone that. What you need is enough evidence to justify the next step, whether that means building, testing a smaller version, talking to more of the people you want to serve, or changing direction before you put in more time and money. That's the difference between building from evidence and building from hope.