Here’s the framework I use to evaluate any startup idea before committing to it.
I’ve spent years working in tech entrepreneurship — as an inventor, a founder and an evaluator at a tech incubator. I’ve seen hundreds of ideas walk through the door. Most of them failed. Not because the idea was bad. Because the founder skipped the process.
Here’s the framework I use. Four questions, in order.
- Does it already exist?
Before anything else, find out if someone built this. Not just a quick Google search — a real market scan. Patents, existing products, funded startups in the space. If it exists, that’s not necessarily a dealbreaker. But you need to know what you’re walking into.
- Does it have business viability?
A great idea and a viable business are two different things. Who is the customer? What are they paying today to solve this problem? Is the market big enough? Can you price it in a way that makes the unit economics work? I’ve seen genuinely brilliant ideas with no business model. Brilliant ideas don’t pay salaries.
- Do YOU have the unfair advantage to execute it?
This is the one most founders skip — and it’s the most important.
Someone once came to me with an idea for a compact early-warning device for earthquake detection. Great idea. Real problem. I asked about his background. He said marketing. I asked how he planned to build the hardware. He said he’d hire people who know how.
That’s a startup with very low odds.
An idea without execution capability is just a wish. You need domain expertise — engineering depth, industry connections, or something that gives you a real edge over the next person who has the same idea. Because they exist.
- Do you have experience as a founder?
This one might surprise you. I don’t necessarily think prior experience guarantees success. What I care about is whether the founder is aware of the complexity of the journey ahead.
The founders I believe in most are the ones who’ve already failed. Not despite the failure — because of it. Failure shows persistence. And it means they’re arriving at this new venture with real insight, not just enthusiasm.
When I sit across from a first-time founder, I want to hear that they understand what they’re getting into. When I sit across from someone who’s already been through it and is going again — that tells me everything.
I’ve been working on a tool called StartZig that helps founders run through exactly this kind of structured validation — from idea to business plan to investor pitch — before they commit to building anything.
What’s your process for evaluating ideas before you commit? Curious what others use.
One thing I'd add is talking to potential users before building. Every framework looks good on paper, but a few conversations can invalidate months of assumptions . That's been the biggest lesson for me .
Completely agree, and it's honestly the step most people skip because it feels slower than just building. A few honest conversations early on save months of building the wrong thing later.
The "does it already exist" question is actually the wrong starting point—if it doesn't exist, that's often a red flag, not validation. I flip it: if competitors exist, I dig into their public reviews and support forums to find the specific gaps people are actively complaining about. You'd be surprised how many founders waste time on surveys when thousands of frustrated users are already spelling out exactly what's broken in existing solutions.
What type of idea are you trying to validate—something in a crowded market or a completely new category?
This is exactly right, and it's the mechanism I built into StartZig — instead of running surveys, you can dig into what people are already complaining about in existing tools. To answer your question: I'm mostly seeing people validate ideas in crowded markets, where the real opportunity isn't "does this exist" but "what are people still frustrated with in what already exists.
A complete startup ecosystem combining AI guidance, real user feedback and structured venture building tools.
https://www.startzig.com/