One of the hardest questions in business is not how to build something.
It is whether the thing is worth building at all.
I have spent a lot of years on the first question. WordPress sites, apps, plugins, communities, AI projects, marketing ideas. Give me something interesting to build and my brain immediately starts working on how to make it real.
That can be a strength. It can also be expensive as hell.
Because a business idea can be technically possible, interesting, useful and still be a bad business.
I have learned that distinction through experience. Sometimes the lesson came from WordPress. Sometimes it came from Apple. Sometimes from trying to turn websites into apps with WebToNative. Sometimes from paying AI builders like Lovable and watching credits disappear while I kept tweaking the product.
The question I am trying to get better at asking is simpler.
Is this worth pursuing?
A good product idea and a good business idea are not the same thing
I love building useful stuff. But useful does not automatically mean profitable.
You can solve a real problem for people who never pay for solutions. You can enter a huge market where customer acquisition is so expensive that the math never works. You can build something people love for free and discover that they disappear the second you put a price on it.
You can also build something technically impressive that depends completely on another platform.
I have felt that one personally. When you build around Apple, an app wrapper, an AI platform or somebody else’s API, you are not the only person making decisions about your business anymore. Their pricing, rules, review process and technical changes become part of your business model whether you like it or not.
That does not mean never build on platforms. Marketur itself is heavily connected to WordPress. It means platform dependency belongs in the evaluation before you start, not in the postmortem after it hurts.
I look for pain before features now
Builders naturally think in features.
What if it had AI? What if users could create profiles? What if there were push notifications? What if I turned it into an app?
Those are implementation questions.
The business question is what painful thing happens before somebody opens your product.
If I cannot explain the problem without describing my solution, I probably do not understand the problem well enough yet.
The SBA’s business planning guidance recommends using market research to understand demand and customers, then competitive analysis to understand the businesses already serving that market. I like that order because it starts with reality instead of features.
Who wants this? Why? What are they doing today?
Competition usually makes me more interested, not less
I used to think finding somebody already doing an idea was bad news.
Now I usually see it as evidence.
Somebody already selling a similar product means I can study pricing, reviews, positioning, customers and complaints. I can see what the market already understands and where people are unhappy.
No competition can be exciting, but it can also mean nobody gives a shit.
The trick is finding a reason you belong in the market. Maybe you serve a narrower group. Maybe the current products are overpriced. Maybe they are too complicated. Maybe they ignore WordPress users. Maybe they solve 80 percent of the problem and users are screaming about the other 20 percent in reviews.
SCORE recommends researching the industry, competition, customers and actual demand before investing heavily. I would rather discover that I have no angle while researching than after I have six months invested.
Can I actually reach the customer
This one gets overlooked because it is not as fun as building.
You can have a good product for a real problem and still lose because you have no practical way to reach the people who need it.
I have seen this difference on my own sites.
Some content gets impressions. Some gets clicks. Some things get attention and almost no signups. Other pieces of content keep bringing people in years later because they answer exactly what somebody was searching for.
Traffic is not customers. Views are not customers. Upvotes are definitely not customers.
Before I call an idea good, I want at least one believable distribution path. Search, YouTube, an existing community, partnerships, direct outreach, paid ads where the numbers work, something.
“We’ll go viral” is not a distribution plan.
Would I still build it if it takes twice as long and costs twice as much
I think this is a useful bullshit detector.
Every new project looks clean before you touch it.
Then Apple wants something changed. A plugin conflicts. The API behaves differently than the documentation. The AI builder burns credits fixing something it broke. The simple integration turns into three days of debugging.
I am not saying every project doubles in cost. I am saying your first estimate is usually made before you know where the bodies are buried.
So I ask whether the opportunity still looks interesting with uglier assumptions.
If the business only works when everything goes perfectly, it does not work.
What evidence would change my mind
This might be the most important question.
When I love an idea, I can explain away almost anything.
No signups yet? Need better marketing. No one will pay? Need more features. Ads are expensive? Need organic traffic. Competitor is crushing it? That proves the market.
Notice how every result can magically become a reason to continue.
That is dangerous.
Before testing an idea, decide what failure looks like. Maybe twenty conversations produce zero serious interest. Maybe a landing page gets traffic and nobody joins. Maybe the economics only work at a price the market clearly rejects.
Give yourself permission to kill an idea.
You are not killing your ability to build another one.
I built Reality Check because I need this too
The Marketur Reality Check is not on the site because I think I have become some perfect business guru.
It is here because I have made enough questionable bets to appreciate a second opinion.
Put your idea into the tool and use the result to find the weak assumptions. Then go verify them yourself.
Use Google Trends to explore whether people search around the problem. Read competitor reviews. Find communities where the target customer hangs out. Ask people what they currently use. Try to get a commitment before you spend months polishing.
If you are at the stage where you already know what you want built but do not want to do all of the technical work yourself, that is also why Marketur has build and WordPress services. But I would rather help somebody validate the right idea before helping them build the wrong one.
I still get excited and build too early sometimes. I know myself.
The difference now is I am trying to put more friction between “I have an idea” and “where is my credit card?”
That little bit of friction can save a lot of money.