How to Evaluate Your Startup Idea's Potential
Łukasz Balowski
How to Evaluate Your Startup Idea's Potential
Got an idea but not sure if it's worth your time and money? Most startup ideas fail. Not because founders can't build the product, but because they build something nobody wants. This framework helps you figure that out before you quit your job or spend your savings.
1. Define the Problem, Not the Solution
The most common mistake first-time founders make is falling in love with the solution. They dream about features, tech stacks, and product names. But if nobody has the problem, none of that matters.
Instead, describe the problem in plain language. Who has it? How often do they hit it? How much does it hurt?
A good problem statement sounds like this: "Small restaurant owners spend 3+ hours per week manually entering delivery orders into their POS system, and they often make mistakes that cost them $200/month in incorrect orders."
That's specific. You can test it. You can talk to 20 restaurant owners and ask if that matches their experience.
A bad problem statement sounds like: "People need a better way to manage their business." Too vague. Who? Which business? What's broken?
Write down your problem. Show it to five people in your target audience. If they don't say "yes, that's exactly my problem," go back to the drawing board.
2. Verify Market Size (TAM/SAM/SOM)
Before you invest months of work, check if the market can support a real business. Use the TAM/SAM/SOM model:
- TAM (Total Addressable Market) — the total spend of all potential customers. If you're building a dog-walking app for NYC, TAM is what all NYC dog owners spend on dog walking per year. Say there are 500,000 dog owners in NYC and 30% use walkers, spending $200/month. That's $360M/year TAM.
- SAM (Serviceable Addressable Market) — the slice of TAM you can actually reach. Maybe you only serve Manhattan and Brooklyn. That cuts your TAM in half. Your SAM is $180M/year.
- SOM (Serviceable Obtainable Market) — what you can realistically capture in your first few years. Be honest. Most founders assume they'll grab 1% of a huge market. That's fantasy. A realistic SOM is 5-10% of SAM if you execute well. That puts you at $9-18M/year — a solid business.
If your SOM is under $1M/year, you either need a bigger market or a different idea.
3. Check the Competition
No competition is a red flag. It usually means the market doesn't exist. If nobody is trying to solve this problem, ask yourself: why? Maybe customers don't care enough to pay. Maybe the problem isn't real.
Heavy competition is actually a good sign. It means the market is real and money flows through it. Airbnb launched into a crowded short-term rental market. Slack launched into team chat with HipChat, Campfire, and others already established. They won by doing it better.
Study your competitors. Read their reviews. Look at the 1-star and 2-star reviews specifically. Those are your roadmap. Every complaint is a feature you can build or an angle you can exploit.
List your top 5 competitors. Write down what they do well and what they do poorly. Find the gap. That gap is your niche.
4. Calculate CAC vs LTV
Two numbers tell you if your business model works:
- CAC (Customer Acquisition Cost) — everything you spend to get one paying customer, including ads, sales salaries, and marketing tools. If you spend $5,000 on Google Ads and get 50 customers, your CAC is $100.
- LTV (Lifetime Value) — the total revenue one customer brings over their entire time with you. A SaaS customer paying $50/month who stays for 24 months has an LTV of $1,200.
The rule of thumb: LTV should be at least 3x CAC. If you spend $100 to acquire a customer, they need to generate at least $300. Anything less and you lose money on every sale.
Write down your assumptions. How much will you spend on ads? What's your expected conversion rate? What's your monthly churn? Run the numbers. If they don't work on paper, they won't work in real life.
5. Build an MVP in 4 Weeks
The best validation is a real product in real users' hands. Not a slide deck. Not a landing page with an email signup. A thing people can use.
Set a hard deadline: 4 weeks. Cut every feature that isn't core to testing your hypothesis. If you're building a recipe app, you don't need social sharing, meal planning, or grocery lists. You need: can users find and save a recipe? Start there.
Use no-code tools if you have to. Use spreadsheets stitched together. Use whatever gets you to a testable product fastest.
Then watch what people do. Not what they say. Not what they promise in surveys. Watch their behavior. Do they come back? Do they finish the task? Do they pay?
Collect feedback. Iterate. Ship again. Repeat until you find something people actually want — or until the data tells you to move on.
Lukasz Balowski
Entrepreneur · AI Researcher · Founder
Lukasz Balowski has been running businesses for over twenty years. His interest in technology started early, back when having an email address was something you explained to people at parties. These days he is focused on artificial intelligence, which he has been studying seriously for the past several years. He is curious about how AI is changing everyday life, the opportunities it opens for new ventures, and the practical ways it can be put to work in businesses that already exist.
Two decades in business will teach you at least one thing: how to tell the difference between what works and what just sounds good in a pitch deck. Lukasz approaches AI the same way he approaches any new tool, by asking what it can actually do right now, not what the marketing material says it will do next quarter. That practical bias shapes what he writes on this site. He is not interested in hype or in speculative takes about where things might be in ten years. He wants to know which applications are paying off today, which ones look close, and which ones are still more promise than product.
Before AI became the dominant conversation it is today, Lukasz spent years building digital products and running online businesses. That hands-on experience gives him a perspective he finds is often missing from discussions about AI, where too many of the loudest voices belong to people who have never built or shipped anything. He brings an operator's sense of what matters, paired with genuine curiosity about the direction the technology is actually moving.
Lukasz lives and works in Poland. He writes about AI startup ideas because he believes the gap between what AI can already do and what most people are doing with it is still surprisingly wide, and that independent creators and small teams, not large corporations, are the ones best positioned to close it. This site is his attempt to map that space carefully: ideas that are specific enough to act on, with analysis that stays honest about both the upside and the risks involved.