> ## Content Index > Fetch the complete content index at: https://www.datadab.com/blog/llms.txt > Use this file to discover other available public pages before exploring further. # Dear Startup Founder Stop Asking ‘Would You Buy This?’ and Start Asking This Instead - URL: https://www.datadab.com/blog/dear-startup-founder-stop-asking-would-you-buy-this-and-start-asking-this-instead/ - Published: 2025-12-06T08:13:00.000Z - Updated: 2026-08-15T15:32:56.000Z - Description: Tired of fake validation? Use JTBD interviews to get honest insight into what customers actually need. - Author: Amit Ashwini - Tags: Product Marketing *JTBD-style questioning for founders who want real product-market clarity not polite feedback from friends and LinkedIn lurkers* There’s a special place in startup purgatory for well-meaning founders who wander around clutching a half-baked idea and asking unsuspecting civilians the famous seven words: ‘Would you buy this from me?’ It’s the entrepreneurial equivalent of asking someone if they think your baby is cute. Of course they’ll say yes. What kind of monster says no? And thus another founder marches confidently into six months of building something only their mother would use. The Validation Trap Friends praising idea LinkedIn likes Polite "yes" responses Hypothetical interest Zero real demand Compliments don't predict purchase behavior We’ve all been there. Caught in the gravitational pull of hype, Lean Startup oversimplifications, and that intoxicating feeling that one polite comment from a stranger counts as validation. Meanwhile the only people who give us feedback are friends, colleagues, and LinkedIn lurkers who absolutely do not want to hurt our feelings. Lovely people. Terrible data sources. So let’s bin the hypothetical nonsense and upgrade our questions to something that actually reveals demand. JTBD questions. The grown-up version of asking customers what struggle they were in right before they started thrashing around for a solution. It’s painfully simple, just inconveniently honest. Why Hypothetical Questions Fail 0% predictive power Social pressure to agree No actual pain context Imaginary future behavior Polite lies prevail Humans can't predict purchase decisions outside real struggle ## Why Would You Buy This Is a Dodgy Question There’s something suspicious about the question the moment it leaves your mouth. It practically begs for a socially acceptable lie. We can feel the other person trying to protect our ego, as if saying no might cause us to crumble like a damp biscuit. And because everyone is very polite, especially in professional settings, we collect a tidy stack of ‘yes, sounds cool’ responses that have the predictive power of a horoscope. The deeper issue is the nature of hypothetical questioning. Humans are catastrophically bad at predicting their future buying behavior. We think we’re rational creatures, calmly weighing value against price. In reality we buy whatever solves the sharpest current pain, and we buy it at the precise moment that pain is thumping us on the forehead. Opinions detached from actual context are about as useful as imaginary revenue. So the verdict is clear. Would you buy this doesn’t reveal willingness to pay, actual demand, purchase triggers, or alternatives already in use. It mostly reveals who likes you enough to lie gently. Struggle Stories Reveal Truth Actual triggers Real workarounds Emotional intensity Decision criteria Purchase moment Alternatives tried Memory beats imagination when predicting demand ## The Real Gold Lives in Struggle Stories If you want truth instead of flattery, anchor the conversation in the past. Not a hypothetical future, not a hypothetical price, not a hypothetical need. The past. Specifically, the last time the person struggled with the problem your product claims to solve. People remember what actually happened. What they did. How annoyed they were. What bizarre workaround they used instead. Those specifics give you something you can design around. They also have the delightful side effect of making people forget they are being interviewed, which means the truth tends to tumble out naturally. For instance, ask someone whether they’d buy a time-tracking app, and you’ll get vague noises about maybe, possibly, eventually. Ask them to walk you through the last time their team’s time sheets caused chaos, and you’ll get a blow-by-blow account of emotional turmoil plus a precise description of the messy workaround they hacked together in Slack. Now we’re talking. This switch from hypothetical interest to lived struggle is the beating heart of [Jobs To Be Done](https://en.wikipedia.org/wiki/Jobs%5Fto%5Fbe%5Fdone%5Ftheory) thinking. The job is never the feature you’re building. The job is the messy progress someone is trying to make through their day. Once you hear what they hired their current solution to do, even if that solution is a notebook or a Google Sheet older than TikTok, you’re in business. The Question That Changes Everything ASK THIS When did you last try solving this? Reveals triggers Exposes urgency Shows alternatives Uncovers non-customers No memory equals no demand ## The One Question That Changes Everything There’s a JTBD classic that never fails to unmask real demand. It’s calm, harmless, and yet disarmingly revealing. Ask this with genuine curiosity: ‘When was the last time you tried to solve this problem?’ Not ‘Would you buy my thing?’ Not ‘Could this be useful to you?’ Not ‘Be honest does this idea sound exciting?’ Just the simple request to walk back into a real moment. Because if they cannot remember a time they felt the problem strongly enough to do something about it, congratulations you’ve discovered something priceless: they are not your customer. Not now, possibly not ever. And if they do recall a moment, now you have a doorway into what actually matters. What triggered them to act? What did they try first? What worked? What failed spectacularly? How did they choose one solution over another? What trade-offs annoyed them most? This is where your product lives or dies. Not in your pitch deck. Not in your friendly DMs. In the messy reality of what people already do to make progress. ## Your Friends Are Lovely But They Don’t Count It’s not their fault. They want you to succeed. They want to cheer for you. They want to avoid the awkward social moment of saying, ‘I wouldn’t use this even if it came with free snacks.’ But friends, family and professional acquaintances are the most biased feedback sources imaginable. That doesn’t mean they’re useless. They can help refine your pitch and spot glaring holes in your assumptions. But they cannot tell you if your product has a shot at real demand. They won’t give you purchasing triggers, switching moments, or desperation-level struggle. Because most of them don’t have it. They have affection for you, not a job to be done. So stop walking into these validation conversations like you’re testing market demand. You’re not. You’re testing your ability to elicit polite noises. ## How JTBD Questions Turn Conversations Into Data Once you abandon the hypothetical swamp, the JTBD toolkit becomes a surprisingly joyful thing. Instead of guessing what people might want someday, you’re reconstructing a real narrative. And narratives are wonderfully stable. They show you where the energy is. They show you what the must-haves are. They show you which pain points cause wallet-opening behavior. A quick scorecard to illustrate why JTBD questions outperform Would you buy this: Question Type Scorecard Hypothetical Interest Weak Opinions without context Politeness over truth Zero purchase signals Misses alternatives Past Struggle Strong Real triggers exposed Workarounds revealed Decision criteria clear Switching Story Extreme Competitive field mapped Willingness to pay validated Memory-based questions predict behavior The more your questions drift toward memory instead of imagination, the more your data transforms from friendly noise to actual insight. And the more you’ll feel like a founder who knows what they’re building rather than one performing a ritual for luck. JTBD Questions Arsenal Ask about real moments When did this problem last hit you? What steps did you take? What were you trying to achieve? What frustrated you most? What mattered most to you? What had you tried before? Guide tours of reality not collect hypothetical votes ## The Practical JTBD Questions You Should Be Asking Instead There’s a small set of magic questions that gently coax people into giving you the truth. And unlike startup jargon, they don’t require a 90-minute workshop to understand. Use them in conversation, lightly, with curiosity rather than interrogation. Ask about the last time the problem happened. Ask about the steps they took. Ask what they were trying to achieve. Ask what they hated. Ask what mattered most. Ask what they’d tried before. Ask what would have made the whole thing easier or faster. These questions are not hypothetical permission slips. They’re guided tours of the messy reality your product hopes to enter. And they’ll tell you everything you need to know about demand, competition, and pricing before you waste a month designing animations for your landing page. ## Why This Matters More Than Your Pitch Deck Because pitch decks don’t build companies. Products with a job to do do. And the difference between those who uncover real demand and those who drift into feature chaos is almost always the quality of questions they ask at the beginning. Would you buy this is a counterfeit shortcut. It gives you the sugar rush of validation without the calories of real insight. JTBD questions take longer, feel slightly more uncomfortable, and require you to accept answers that may ruin your weekend plans. But they give you something priceless: truth. And truth is what lets you stop building imaginary products for imaginary customers and start building something someone will actually hire. ## Wrap-up If you want clarity not compliments, ditch the hypothetical question everyone asks by default. Anchor your interviews in real stories, real frustrations, and real attempts to make progress. The more past tense your questions become, the clearer your product’s future gets. And for bonus points, if someone can’t remember the last time they struggled with the problem you’re trying to solve, you’ve just saved yourself several months of enthusiastic self-delusion. *Want to build something worth paying for? Try running five JTBD-style interviews this week. They’ll tell you more than any LinkedIn poll ever will.*