I'm Andalib, a first-time founder building Traction AI — a startup idea validation service.
To build my first case studies, I'm offering 3 free reports this week.
Here's what you get:
Market size estimate, backed by real sources
Your top 3-5 real competitors
Willingness-to-pay signal
One honest verdict — build it or don't
I research everything by hand first — Google, Reddit, industry reports — then structure the findings. No generic AI output. Real research, real verdict.
If you have an idea you're sitting on and aren't sure if it's worth pursuing — DM me or comment below.
No catch. Just honest feedback.
What I like most about this approach is that you're validating the validation service itself while building the first case studies. That's a smart way to reduce the gap between "I think founders need this" and actual evidence.
One thing I'd be especially interested in seeing in the reports is how you distinguish between interest and real buying intent. A founder saying "I'd use this" is very different from someone actually willing to pay for the solution.
Also, the manual research angle could become a real differentiator if you document your methodology over time. If the first 3–10 reports reveal recurring patterns in how you evaluate ideas, that process itself could eventually become part of the product.
The most valuable outcome may not even be proving that an idea is good—it may be helping someone confidently kill a bad idea before they spend six months building it. That's a much harder promise, but potentially a much more valuable one.
Curious to see what patterns emerge from your first few validations.
That distinction you made — interest vs real buying intent — is actually the core of what the report tries to answer. Anyone can say "I'd use this." The report looks for signals like whether people are already paying for an alternative, searching for a solution, or complaining about the problem in public forums. That's harder to fake.
And you're right about killing bad ideas being the more valuable outcome. Most founders need permission to stop — not just encouragement to keep going.
Appreciate the thoughtful comment. Curious what kind of ideas you've seen founders over-commit to before validating.
The "build it or don't" verdict is the part I'd actually pay attention to over the market-size and competitor sections, a lot of validation reports hedge every finding into "it depends," and a service willing to commit to a binary verdict is taking on real reputational risk if it's wrong, which is a decent signal that the research behind it is genuine rather than padded.
Curious how you handle willingness-to-pay signal specifically, since that's usually the hardest part of manual research to do honestly, are you pulling from things like pricing complaints in existing competitor reviews, forum threads where people explicitly say what they'd pay, or something more direct? That's the piece most idea-validation services either skip entirely or fake with a generic TAM estimate that doesn't actually answer "would a real person hand over money for this."
Great question. For willingness-to-pay I look at competitor pricing pages, Reddit threads where people explicitly mention what they pay or won't pay, and App Store reviews where users complain about pricing. It's not perfect but it's more honest than a TAM estimate.
Smart giving free reports to build case studies, that's you validating your own validation service. One hard truth to face early: founders who ask "should I build this" often want permission, not a verdict. The ones who'll pay are those who'd kill an idea on your "don't build it", a smaller audience than "people with ideas." Your real customer is "people disciplined enough to want a real no."
Other tension: "I research by hand" is both your quality bar and your ceiling, why the reports are good and why it won't scale past your hours. Decide now whether Traction AI is a premium manual service or a scalable tool, the free reports pull you toward one.
What founder do you want these first 3 from?
The 'people disciplined enough to want a real no' framing is exactly right — that's the customer I'm looking for. And yes, manual vs scalable is a tension I haven't fully resolved yet. For now I'm staying manual to learn what good research actually looks like before thinking about scale.
Staying manual to learn what good research looks like is the right reason, most stay manual out of habit, you're doing it to build judgment. Good.
One thing so the manual phase compounds: write down your method as you go. Every report, note what you checked, in what order, what signal predicted "build" vs "don't." You're reverse-engineering your own repeatable process. It's what you'd eventually systematize or hire against, and proof to buyers your verdict is a method, not a vibe. The manual work is research; the documented method is the asset.
Stay manual and never codify, you have a job. Codify, and there's a business inside it. What signal has predicted "don't build it" most reliably so far?
Honestly, the clearest "don't build it" signal so far has been when the founder can't name a single person who's already paying for the problem to go away — in any form. No workaround, no consultant, no spreadsheet they built themselves. If nobody's paying anything adjacent, the pain usually isn't real enough.