He shipped it on a Tuesday. Spent the weekend refreshing the analytics dashboard, watching the numbers like they owed him something. By Friday he had 11 page views, 0 signups, and a fresh understanding of what “validation” actually means. Three months of building. One week of silence. Classic.
Most founders skip validation because building feels like progress and talking to customers feels like delay. There’s something deeply satisfying about writing code, designing screens, and watching a product take shape. So they ship first and hope the market corrects them gently. It doesn’t.
A thread in r/PromptEngineering shared seven copy-paste prompts designed to do exactly what most builders skip — pressure-test your idea before a single line of code gets written. Not to get a green light. To find the holes.
🔍 Why Skipping This Costs You Months
The trap is always the same: you fall in love with your solution before you understand the problem. You convince yourself the market wants it because you want it. You start picturing the users, the revenue, the Product Hunt launch. And somewhere in that daydream, the actual customer disappears.
The thing is, most bad ideas don’t look like bad ideas at the start. They look like obvious opportunities. “Nobody has solved this yet” feels like a gap in the market. Sometimes it is. More often, it means everyone who tried it quietly walked away.
These prompts don’t ask AI if your idea is good. They ask it to play devil’s advocate — to surface every assumption you’re making before those assumptions cost you real time and real money. The goal isn’t a yes. It’s a smarter question.
📋 The 7 Prompts (In Order)
- Problem Reality Check , Ask AI to list 10 signs your problem is real and painful enough for people to pay to fix — then 5 signs it might just be a “nice to have.” No pain, no payment. People tolerate inconveniences every day without ever spending a dollar to fix them.
- Existing Solutions Audit , Prompt AI to act as a market researcher and map the top 10 solutions people already use, including strengths, weaknesses, and pricing. Study the pricing especially. It tells you what the market has already decided this problem is worth. If nothing exists, that’s usually a warning, not an opportunity.
- Customer Interview Generator , Before you talk to a single real person, use AI to write 15 open-ended interview questions that uncover whether the problem actually exists and what they’d pay to fix it. The key rule here: ask about their life, not your idea. “Walk me through the last time this frustrated you” gets you truth. “Would you use a tool that does X?” gets you politeness.
- Willingness-to-Pay Test , Ask for 10 ways to test whether people will actually pay — landing pages, pre-orders, fake door tests — ranked by cost and speed. “I’d use that” is not the same as “here’s my card.” The distance between those two statements is where most startups die. A fake checkout button that tracks clicks costs you an afternoon. Three months of building costs you everything.
- Market Size Reality Check , Ask AI to estimate your realistic market size, where those people hang out online, and how hard it would be to reach them with no budget. Be honest with yourself here. A small market with no distribution is a hobby. Nothing wrong with hobbies, but know what you’re building before you quit your job for it.
- The Kill-Switch , Define failure before you start. Ask AI to help you set clear validation milestones for 2 weeks, 1 month, and 3 months — so you know when to keep going and when to walk away. Write these down somewhere you’ll actually look at them. Sunk cost is the silent killer of indie founders. The goal isn’t persistence for its own sake. It’s knowing the difference between a hard problem worth solving and a dead end worth leaving.
- Assumption Stress-Test , Ask AI to list every assumption behind your idea — about the customer, the problem, distribution, pricing, your ability to execute — and rank them by risk. Then ask which ones you can test in the next 48 hours with zero budget. The biggest risks are always the ones you never questioned. The ones that felt so obvious they didn’t seem like assumptions at all.
💡 A Few Things Worth Knowing
- Run them in order. Each prompt builds on the last. Jumping to #4 before doing #1 is wishful thinking with extra steps.
- Don’t soften the inputs. Vague prompts get vague answers. Be specific and honest about what your idea actually is. If you can’t describe the problem clearly to an AI, you can’t describe it to a customer either.
- Treat the output as a checklist, not a verdict. AI can’t tell you if your idea will work. It can show you which questions you haven’t answered yet. Those unanswered questions are your actual to-do list.
- Share the outputs with one person who will tell you the truth. A co-founder, a mentor, someone who doesn’t care about your feelings. Fresh eyes catch things you’ve already rationalized away.
- If your idea survives all seven, you’ve earned the right to build it. Most don’t.
🎯 Try It Right Now
Pick an idea you’ve been sitting on. Open your AI tool. Paste in prompt #1 and see what comes back.
If the answer makes you uncomfortable, good — that’s the whole point. Discomfort before you build is research. Discomfort after you ship is a Tuesday with 11 page views.
7 AI Prompts That Help You Validate a Business Idea Before You Build It (Copy + Paste)
by u/InvestmentMission511 in PromptEngineering