Business Idea Validation Checklist

I have a confession that will surprise absolutely nobody who has followed what I build.

I like starting.

I like buying the domain. I like getting WordPress installed. I like figuring out the plugins. I like seeing an app appear on my phone. I like opening an AI builder and watching an idea turn into something real while I am still thinking about it.

What I have historically been less excited about is sitting down before all of that and asking whether the idea deserves any of it.

That is how you end up learning business lessons through credit card statements.

I have dealt with Apple, WebToNative, app reviews, WordPress, plugins, communities, AI builders and Lovable credits disappearing faster than I expected. Some projects worked. Some did not. Some taught me that the technical problem was not even the real problem.

So this is the checklist I want in front of me now.

Not because a checklist can predict success. It cannot. I want it because it can expose the stupid assumptions while they are still cheap.

You can also run the idea through the free Marketur Reality Check if you want the tool to challenge it for you.

The problem

First I want to know whether there is an actual problem underneath the product idea.

1. Can I describe the problem without mentioning my product?
2. Are people already complaining about this problem publicly?
3. Does the problem cost them money, time, frustration or opportunity?
4. How often does it happen?
5. What happens if they do nothing?

If my answer to most of those is basically “I think so,” I do not have evidence yet.

The SBA recommends market research for exactly this reason. You want to understand demand and customers before committing heavily.

The customer

6. Can I describe the first customer specifically?
7. Do I know where these people gather online or offline?
8. Can I reach them without needing a million-dollar advertising budget?
9. Are they already trying to solve this?
10. Have I seen them spend money on the problem?

“Small business owners” is usually too broad. “WordPress site owners who want AI to actually manage their site instead of just writing copy” is something I can work with.

Specific customers make research easier, content easier and eventually selling easier.

The market

11. Are people searching around this problem?
12. Is interest stable, growing or disappearing?
13. Are there active communities discussing it?
14. Can I find recent evidence instead of relying on a giant industry number from five years ago?

I use search behavior as one piece of this. Google Trends is useful for seeing how interest changes and what related topics people explore. Search volume alone is not validation, but silence everywhere is worth noticing.

The competition

15. Who already solves this?
16. What do they charge?
17. What do their customers complain about repeatedly?
18. Can I explain why somebody would choose me instead?

I used to get discouraged when somebody had already built my idea. Now I would rather find competition than find nothing.

Competition can be proof that money already moves in the market. The question becomes whether there is room for a different angle, audience, price or experience.

The money

19. What can I realistically charge?
20. What will it cost me to acquire a customer?
21. What does it cost to serve that customer?
22. Does the math still work when my rosy assumptions are wrong?

That last one matters.

I have learned that projects rarely cost exactly what I thought they would. AI credits grow. APIs cost money. Hosting grows. App stores create requirements. Plugins need licenses. Support takes time.

If the business only works when everything goes perfectly, I do not consider that a business model anymore. I consider it a prayer.

The dependencies

23. Which companies can change the rules underneath me?
24. What happens if a platform raises prices or blocks something I depend on?
25. Do I own the important parts of what I am building?

This category is personal for me.

Working with Apple taught me that being able to build an app and being able to distribute the app exactly how you imagined are two different things. Using WebToNative taught me about another layer of dependency. Spending heavily with Lovable reminded me that building speed and ownership are not the same thing.

That is a big part of why I eventually moved so much back toward WordPress and why I wrote WordPress vs Lovable.

The proof

26. Has a stranger taken a meaningful action because they want this?
27. Has anybody paid, deposited money, preordered or made another commitment that costs them something?

Those final two questions are intentionally brutal.

Compliments are easy. Likes are easy. Free signups are easier than paid customers.

I have had things get views and attention without producing the business result I wanted. That teaches you quickly that attention and validation are not interchangeable.

How I would use this checklist

I would not score one point for every yes and decide that 22 out of 27 means I am a genius.

I would look for evidence.

A weak answer backed by a real customer conversation can be more valuable than five confident guesses.

And I would pay extra attention to the questions about pain, reachable customers, willingness to pay, distribution and dependencies. Those are the ones that can kill an otherwise cool product.

If you want another set of eyes on the idea, run it through the free Reality Check. Then use the report as a list of things to investigate, not permission to blindly start spending.

I still love building.

I am not trying to become the guy who researches an idea for two years and never ships anything.

I am trying to become the guy who spends an hour asking the ugly questions before spending six months answering them the expensive way.