SaaS / Startup Validation Beginner

27 ChatGPT prompts for SaaS founders to validate startup ideas in 48 hours

Most SaaS ideas don’t die from bad code. They die from bad bets on what customers will actually pay for. In 2026, founders have a sharper tool than ever - and these ChatGPT prompts for SaaS startup idea validation turn a weekend into a real research sprint.

Here’s the truth. CB Insights’ March 2026 post-mortem of 431 VC-backed shutdowns found that 43% of those failures cited poor product-market fit as a root cause, and a separate 19% pointed to unsustainable unit economics (CB Insights, March 5 2026). Read those numbers again. Six out of ten dead SaaS startups didn’t fail because of tech - they failed because nobody wanted to buy what they made.

That’s the gap this guide closes. Over the next ~30 minutes of reading, you’ll get 27 copy-paste ChatGPT prompts for SaaS startup idea validation, organized into the six stages a real founder sprints through in 48 hours: problem discovery, ICP, solution shape, pricing, distribution, and risk. Every prompt comes with context, a sample output, and a pro tip. No fluff. No “synergy hunting.” Just a friend handing you a notebook of working scripts.

Pull quote: “43% of failed SaaS startups in 2026 blamed poor product-market fit. The other 19% blamed bad unit economics. Both are answerable in 48 hours if you ask the right questions.” - paraphrased from CB Insights, March 5 2026

Quick answer: what you’ll get from this guide

  • A 48-hour validation framework you can run solo or with a co-founder this weekend
  • 27 detailed ChatGPT prompts split across problem, customer, solution, pricing, distribution, and risk
  • A comparison table mapping each prompt to its phase, time cost, and output artifact
  • A People Also Ask FAQ plus a mini playbook for chaining the prompts in order

Why most SaaS ideas die in 2026

Let me set the table before we get tactical. The default failure story in 2026 still rhymes with the one Failory documented when it updated its startup failure rate guide in January 2026: roughly 9 out of 10 startups fail, and the most-cited reason in 80+ post-mortem interviews was a marketing problem (56%) - which, when you peel it back, is almost always a “we built something nobody was searching for” problem. The second-most-cited reason? Team problems at 18%, often caused by cofounders skipping hard customer conversations.

So the graveyard is full of founders who:

  1. Built first, validated later (or never)
  2. Confused compliments with commitment
  3. Priced on vibes instead of willingness-to-pay data
  4. Launched into a channel they hadn’t proven

The cleanest way to dodge all four? Run a structured 48-hour validation sprint before you write a line of code. Rob Fitzpatrick’s Mom Test and the lean startup methodology, coined by Eric Ries in 2008, both hammer the same point: talk to customers about their life, not about your idea.

The 48-hour ChatGPT validation framework

A 48-hour sprint is tight but doable. The trick is to keep your back-of-the-napkin time low and your “actual humans” time high. ChatGPT handles the cognitive prep - interview scripts, ICP drafts, market scans, pricing frames - so you can spend more hours on the calls that matter.

Here’s the cadence. I’m borrowing from the Wikipedia lean startup article on Build-Measure-Learn and the customer development model Steve Blank pioneered, then compressing it:

  • Hours 0–8 (Problem): Use prompts 1–5 to crystallize the problem and pre-test your assumptions.
  • Hours 8–20 (Customer & Solution): Use prompts 6–15 to lock in ICP and rough solution shape.
  • Hours 20–32 (Pricing & Distribution): Use prompts 16–23 to pressure-test money and channels.
  • Hours 32–48 (Risk & Decision): Use prompts 24–27 to summarize risk and write a GO/NO-GO memo.

If you can’t defend the GO in writing, you don’t have one. Let’s get to the prompts.

Section 1: Problem Discovery prompts (1–5)

Problem discovery is where 80% of founders skip steps. They fall in love with a solution before they’ve even named the pain. The five prompts below are designed to slow that down - to force you to describe the wound before you reach for the bandage.

Prompt 1: Pain hypothesis stress-test

Purpose: Pressure-test whether the problem you think exists is actually severe, frequent, and expensive enough that someone will pay to fix it. This is the “is this a vitamin or a painkiller” prompt.

Act as a senior product strategist who has helped launch 30+ B2B SaaS products.

I'm building a SaaS tool for [target persona, e.g. "operations managers at 20-200 person DTC brands"].

My core hypothesis is that they currently struggle with [describe the pain, e.g. "manually reconciling Shopify payouts against 3PL invoices every Friday, which takes 4+ hours and produces errors that surface in monthly board reports"].

Please do the following:
1. Score this pain on a 1-10 across four dimensions: severity, frequency, cost-of-inaction, and current workaround quality (10 = worst pain, would pay immediately).
2. List 5 adjacent problems this persona probably has that are *more* painful than the one I named.
3. Identify the 3 "tripwire" events that would make them actively search for a solution this month (e.g. "raising a Series A," "missed a payroll," "lost a key client").
4. Tell me what signal would tell me this is NOT a real pain worth solving in 2026.

Be specific. No generic advice. Reference how DTC ops managers actually talk about this work.

Example output (excerpt): “Severity: 7/10. Frequency: 9/10 (weekly). Cost-of-inaction: 8/10 (board embarrassment + cash flow surprises). Workaround quality: 6/10 (spreadsheets work but break at scale). Tripwire events: (1) end of fiscal year audit, (2) hiring a second ops person, (3) cash-flow-driven board pressure. This is a real pain, but it’s mid-tier. Adjacent pain #1 - multi-currency reconciliation across Shopify Payments, PayPal, and Klarna - is likely more severe for the same persona in 2026.”

Pro tips:

  • Replace “DTC brands” with your actual ICP. The more specific the better.
  • Save the output as pain-v1.md and re-run the prompt after every 3 customer calls to see how your score shifts.
  • If severity lands below 6, the prompt just saved you 6 months.

Prompt 2: “Job to be done” extractor

Purpose: Translate a vague problem statement into the customer’s actual job-to-be-done. People don’t buy products, they hire them to do a job.

You are a jobs-to-be-done (JTBD) expert trained on Clayton Christensen's framework.

Take the following SaaS idea: [describe idea in 1-2 sentences].

Do this:
1. Write the functional job the customer is "hiring" my product to do (one sentence starting with "When I... I want to... so I can...").
2. Write the emotional job (how they want to feel).
3. Write the social job (how they want to be perceived).
4. List 3 "non-consumption" cases - situations where the customer is NOT doing the job today and why.
5. Identify 2 "fired" products - things the customer is currently using (even badly) that my SaaS would replace.

Format as a one-page brief I can paste into a customer interview script.

Example output (excerpt): “Functional: When I close the books each Friday, I want to reconcile payouts against 3PL invoices in under 30 minutes, so I can stop being the bottleneck for the finance review. Emotional: I want to feel in control when the CFO pings me on Monday morning. Social: I want to be seen as the ops leader who built a real system, not a stack of Google Sheets.”

Pro tips:

  • The “When I… I want to… so I can…” template is gold. Use it as the literal opening of your landing page.
  • If you can’t name a “fired” product, the customer may not actually be doing the job yet - that’s a red flag.

Prompt 3: Workaround archaeology

Purpose: Map every ugly workaround your customer uses today. Workarounds are the strongest signal that pain is real and unbudgeted. If you find a workaround that’s costly, recurring, and manual - you’ve got a SaaS-shaped hole.

Act as a customer research analyst.

My target customer is [persona]. I suspect they currently solve [problem] using [list any workarounds you know about, e.g. "spreadsheets, a part-time bookkeeper, and a Zapier hack"].

Generate a comprehensive workaround map:

1. List 8-10 likely workarounds (tools, processes, hacks) this persona uses today. For each, describe:
   - Time cost per week
   - Dollar cost per year
   - Frustration score (1-10)
   - Why they tolerate it
2. Identify the "least bad" workaround - the one that actually works for them. Why does it work?
3. Spot the workarounds that are about to break (regulatory change, scaling issue, vendor sunset). These are your wedge.
4. Recommend the single cheapest experiment I could run in 24 hours to validate one of these workarounds is real.

Example output (excerpt): “Workaround #3 - a 12-tab Google Sheet that the ops manager rebuilds every quarter - has a frustration score of 9/10 and a dollar cost of ~$18K/year in lost analyst time. It’s about to break when Shopify rolls out its 2026 multi-currency payout schema. Run a 5-question Typeform survey posted in the r/shopify subreddit to confirm this.”

Pro tips:

  • Survey the workarounds, not the product. People will tell you about their spreadsheets for 20 minutes.
  • Use the “frustration score” to rank which workaround to attack first.

Prompt 4: Problem framing via 5 Whys

Purpose: Peel back the surface complaint to the real, often embarrassing, root cause. Customers will tell you the first answer. The fifth answer is where the money is.

You are an expert interviewer trained on the "5 Whys" technique from Toyota Production System and Sakichi Toyoda.

Here is a surface-level problem my customer describes: "[paste a complaint, e.g. 'We can't get our financial close done on time.']"

Do this:
1. Generate the 5 sequential "why" questions an experienced consultant would ask, getting progressively more uncomfortable.
2. Predict the most likely answers at each layer (best case, common case, worst case).
3. Identify the assumption that, if true, would make my SaaS idea irrelevant.
4. Suggest the one question I should ask in a customer call to test that assumption directly.

Do not soften the questions. The whole point is to surface the embarrassing root cause.

Example output (excerpt): “Why #1: Why can’t you close on time? (Likely: too many transactions.) Why #2: Why are there too many transactions? (Likely: scaling to new channels.) Why #3: Why didn’t you prepare for that? (Likely: the CFO didn’t believe the new channels would stick.) Why #4: Why didn’t she believe? (Likely: no shared dashboard.) Why #5: Why no shared dashboard? (Likely: nobody wanted to own the data quality.) The assumption to test: the ops manager has the political capital to push for a new tool.”

Pro tips:

  • The 5 Whys only works if you don’t flinch at Why #4. Encourage your interviewees to be candid.
  • The final “embarrassing” answer is usually a people problem, not a software problem. That’s still useful - it tells you who the buyer really is.

Prompt 5: Problem statement in 25 words or fewer

Purpose: Force clarity. If you can’t describe the problem in 25 words, you don’t understand it yet. This becomes your landing-page headline, your investor one-liner, and your Mom Test opener.

Act as a copy editor who has rewritten 500 YC application problem statements.

Here is my current problem description: "[paste a longer version]".

Now do this:
1. Rewrite it in 25 words or fewer for a B2B SaaS landing page hero. It must include: who, what pain, when, and why-now.
2. Provide 3 alternate versions, each with a different emotional angle (fear, ambition, embarrassment).
3. Identify the 2-3 words that should NOT be in the final version because they're too jargon-y or vague.
4. Suggest a 1-sentence "if you're not [X], this isn't for you" qualifier to repel bad-fit leads.

Example output (excerpt): “Final: ‘DTC ops managers: stop losing Fridays to manual Shopify-vs-3PL reconciliation. Auto-match payouts to invoices in 90 seconds.’ Alternate (fear): ‘One missed reconciliation can sink your next raise. We auto-match payouts so the board never sees a surprise.’ Jargon to cut: ‘synergy,’ ‘streamline,’ ‘leverage.’ Qualifier: ‘If you’re under $2M GMV or have a full-time controller, this isn’t for you.’”

Pro tips:

  • Test all three emotional versions on real prospects. Embarrassment often outperforms fear in B2B SaaS.
  • The qualifier is the most underused tool in B2B copy. It boosts reply rates 2–3× in my experience.

Section 2: Customer & ICP prompts (6–10)

Now that you know the pain, you need to know who feels it. These five prompts build a crisp Ideal Customer Profile and a customer discovery script. If you skip this section, you’ll end up pitching to everyone - and converting no one.

Prompt 6: ICP persona sheet

Purpose: Build a single-page Ideal Customer Profile that you can use to score every lead and every interview request. Vague ICPs produce vague products.

You are a B2B SaaS go-to-market strategist.

I am building [product] for [broad category, e.g. "e-commerce finance teams"].

Generate a detailed ICP persona sheet with these sections:

1. Firmographics: company size (employees + revenue), industry sub-verticals, tech stack must-haves, funding stage, geography.
2. Demographics of the buyer: job title, reports to, years in role, prior roles, salary band.
3. Trigger events in the last 90 days that would make them buy now (e.g. "just hired a controller").
4. Channels where they consume content and hang out online (be specific - subreddits, Slack groups, podcasts, conferences).
5. Watering holes where I can find 10 of them this week for free.
6. Anti-persona: a description of someone who *looks* like the ICP but will never buy. This protects my time.

Output as a clean markdown table + a 200-word narrative summary.

Example output (excerpt): “Firmographics: 20–200 employees, $5M–$80M GMV, Shopify Plus, uses a 3PL, US/EU/UK. Buyer: Head of Ops or VP Finance, reports to CFO, 3–7 years in role, $130–$180K base. Trigger: just raised a Series A or just failed a SOX-style audit. Watering holes: r/shopify, Future Commerce Slack, 2X eCommerce community, Cap Table Twitter.”

Pro tips:

  • The “anti-persona” section is worth 10 hours of your time. It filters out the leads that waste your sales cycle.
  • Validate this ICP with prompt 7 before you spend a dollar on ads.

Prompt 7: ICP scoring rubric

Purpose: Turn the ICP into a numeric score so you can rank leads, replies, and interview candidates without arguing about fit.

Act as a RevOps lead.

Here is my ICP persona: [paste the output from Prompt 6].

Build a 100-point lead-scoring rubric with these rules:

1. 8-10 firmographic criteria (e.g. "uses Shopify Plus" = 10 pts).
2. 3-5 behavioral criteria (e.g. "posted in r/shopify in last 30 days" = 15 pts).
3. 2-3 negative criteria that subtract points (e.g. "currently using NetSuite" = -20 pts).
4. A scoring band: 80+ = hot, 50-79 = warm, below 50 = disqualified.
5. The single highest-leverage data point I should ask for on a discovery call to bump a warm lead to hot.

Keep it brutally simple. A non-technical founder should be able to score a LinkedIn profile in 60 seconds.

Example output (excerpt): “Hot lead profile: VP Ops at $20M+ Shopify Plus brand using a 3PL, who posted about reconciliation pain in the last 30 days (+90 pts). Negative signal: founder of a sub-$1M Shopify store, single-person team (-40 pts, disqualified). Single highest-leverage question on the call: ‘Walk me through your last reconciliation. What broke?’”

Pro tips:

  • Print this rubric. Tape it next to your laptop. Score every prospect before you reply.
  • If 90% of inbound leads score below 50, your positioning is off - not your scoring.

Prompt 8: Mom Test interview script

Purpose: Build a non-leading customer discovery script grounded in Rob Fitzpatrick’s Mom Test principles: ask about their life, not your idea. This is the single most important prompt in this guide.

You are a customer discovery coach trained on Rob Fitzpatrick's "The Mom Test."

I'm about to interview [persona, e.g. "ops managers at DTC brands"] about [problem, e.g. "Shopify-3PL reconciliation"].

Generate a 30-minute interview script with:

1. A 3-minute warm-up (no questions about my product).
2. 6-8 open-ended questions about the customer's current life and work, focused on the specific problem.
3. 3 "commitment" questions designed to extract real signal (e.g. "When was the last time this caused you to lose money or sleep?").
4. 2 questions designed to surface what they would *actually* pay for (time, money, or status).
5. A graceful close that asks for a referral without sounding desperate.

For every question, include:
- The question itself
- What bad answers look like
- What great answers look like
- A follow-up if they give a vague reply

Avoid any question that mentions my product, my company, or my solution.

Example output (excerpt): “Q3: ‘Walk me through the last time you closed the books for your Shopify store. Where did it get painful?’ Bad answer: vague ‘it was annoying.’ Great answer: ‘It took 11 hours and we still missed a $14K refund discrepancy.’ Follow-up: ‘What did that cost you - in time, money, or trust?’”

Pro tips:

  • Fitzpatrick’s three rules: talk about their life, ask about specifics in the past, and talk less. This script is built for that.
  • Record calls with consent. You’ll catch things you missed live.

Prompt 9: Cold outreach email generator (Mom Test style)

Purpose: Get 10 customer calls booked this week with an email that doesn’t pitch, doesn’t lie, and doesn’t use “just circling back.” The Mom Test applies to cold emails, too.

You are a cold email copywriter who specializes in B2B SaaS customer research outreach.

I'm validating a SaaS idea: [1-sentence description].
My target persona: [ICP from Prompt 6].
The pain I want to learn about: [problem].

Write 5 cold email variants. Each variant must:
1. Be under 90 words.
2. Open with a specific observation about *them*, not me.
3. Ask for 15 minutes to learn about their workflow (NOT a demo).
4. Offer a small, specific quid pro quo (e.g. "I'll send you the synthesized notes from 5 other interviews").
5. End with a low-friction CTA ("worth a 15-min call?" or "open to chatting?").

For each variant, label the psychological angle: curiosity, reciprocity, social proof, specificity, or status.

Example output (excerpt): “Subject: Quick question on your Friday close. Hi [Name], I noticed [Company] just integrated [3PL name] - congrats. I’m researching how ops teams handle the new multi-currency reconciliation that comes with that. Worth 15 min to walk me through your current workflow? I’ll send you the synthesized notes from 5 other ops leaders. Angle: specificity.”

Pro tips:

  • Personalization beats volume. 20 hand-customized emails will outperform 200 templated ones.
  • If your reply rate is below 10%, your subject line is the problem, not your ask.

Prompt 10: LinkedIn DM script for warm intros

Purpose: Convert 2nd-degree LinkedIn connections into 15-minute calls. Cold DMs work, but warm DMs convert 3–5× better.

Act as a LinkedIn outreach specialist.

My profile: [1-line bio, e.g. "ex-Shopify PM building reconciliation tools for DTC ops teams"].
My target: [persona from Prompt 6].
The ask: 15-minute customer research call (not a sales call).

Write 3 LinkedIn DM scripts:

1. A short version (under 300 characters) for cold 2nd-degree connections.
2. A medium version (300-600 characters) for warm 1st-degree connections.
3. A version that asks for an *intro* from a mutual connection (gives them a script to forward).

Each must:
- Open with a reason that is NOT "I'd love to pick your brain."
- State a specific, credible reason I'm researching this.
- Make it easy to say yes (specific time windows, async option).
- Include a graceful "no" path so they don't ghost.

Tone: peer-to-peer, no flattery, no "aspiring founder" energy.

Example output (excerpt): “Hi [Name] - saw you led ops at [Brand] through the 3PL migration. I’m building in the reconciliation space and your post about Friday close pain was a punch in the gut. 15 min this week? I can do Wed 2pm ET or async via Loom. Either way, no pitch - I’m just trying not to build the wrong thing.”

Pro tips:

  • Reference a specific thing they posted or shipped. Generic compliments get ignored.
  • Async Loom > phone for senior buyers. Respect their time.

Section 3: Solution Shape prompts (11–15)

Now you’ve got a real problem and a real person. Time to sketch a solution - but only as a hypothesis, not a build order. The five prompts below keep you in cheap-experiment mode.

Prompt 11: Lean Canvas draft

Purpose: Generate a 9-block Lean Canvas draft you can argue with for an hour, then refine over a weekend. The Lean Canvas was adapted by Ash Maurya from the Business Model Canvas in 2010, and it’s still the fastest way to put an idea on a page.

You are a lean startup coach trained on Ash Maurya's Lean Canvas.

Here is my idea:
- Problem: [from Prompt 1]
- Customer segments: [from Prompt 6]
- Existing alternatives: [from Prompt 3]

Generate a complete Lean Canvas with all 9 blocks:
1. Problem (top 3)
2. Customer segments
3. Unique value proposition (single, clear, compelling)
4. Solution (top 3 features for an MVP)
5. Channels (top 3 paths to reach customers)
6. Revenue streams (how you'd actually charge)
7. Cost structure (top 5 cost lines)
8. Key metrics (the 3 numbers that would tell you PMF)
9. Unfair advantage (something that can't be easily copied)

For each block, give me:
- A short version (1 sentence)
- A long version (3-4 sentences)
- A "most likely to be wrong" flag if the assumption is high-risk

Be opinionated. Don't hedge.

Example output (excerpt): “UVP (short): ‘Reconcile Shopify payouts against 3PL invoices in 90 seconds, every Friday.’ Unfair advantage (most likely to be wrong ⚠️): ‘We pre-build integrations for the top 20 3PLs - every competitor can do this in 6 months.’ Key metrics: (1) % of users who complete a reconciliation in week 1, (2) weekly active ops managers, (3) Net Revenue Retention at month 6.”

Pro tips:

  • The “most likely to be wrong” flag is the most valuable part. Circle those blocks in red.
  • Re-draw the canvas every Friday. If it doesn’t change in 4 weeks, you’re not learning.

Prompt 12: MVP scope cutter

Purpose: Strip your MVP down to the smallest thing you can ship in 4 weeks that still tests the riskiest assumption. The goal is a falsifiable experiment, not a product.

You are a startup CTO who has shipped 12 MVPs.

Here is my full feature wish list for [product]:
[paste 10-20 features]

Do the following:
1. Score each feature on (a) how directly it tests the core value hypothesis, (b) cost to build, (c) optionality it preserves.
2. Identify the single feature that, if it works, validates the whole product. Call this the "wedge feature."
3. Recommend a 4-week MVP scope: the wedge feature + the minimum surrounding surface (auth, billing, one integration) needed to make it testable with real customers.
4. List the features I should DELIBERATELY cut, even though customers will ask for them.
5. Suggest the one-line landing page copy that would let me start collecting signups TODAY without building anything.

Be ruthless. The MVP must be embarrassingly small.

Example output (excerpt): “Wedge feature: auto-matching Shopify payouts to 3PL invoices using a single CSV upload (no live integrations yet). MVP scope: auth + Stripe billing + the matching engine + a ‘did this work?’ feedback button. Cut: real-time dashboards, multi-currency, role-based access. Landing page: ‘Stop losing Fridays to reconciliation. Get a notification when something doesn’t match.’”

Pro tips:

  • If your MVP has more than 5 features, you’re building a product, not testing a hypothesis.
  • The “did this work?” button is the most important feature in any MVP. Without it, you have no signal.

Prompt 13: Riskiest assumption test (RAT)

Purpose: Identify and pressure-test the single riskiest assumption in your business. If this one is wrong, nothing else matters. Inspired by the Customer Development methodology Steve Blank teaches.

Act as a startup risk analyst.

Here is my business hypothesis: [paste your Lean Canvas summary].

Do this:
1. List the 7-10 implicit assumptions baked into the model.
2. Rank them by: (a) how likely to be wrong, (b) how fatal if wrong. Multiply for a "risk score."
3. Identify the SINGLE highest-risk assumption.
4. Design the cheapest possible experiment (under $500 and under 1 week) to test that assumption. Include:
   - The hypothesis statement
   - The success criteria (a number, not a feeling)
   - The minimum sample size
   - The channels you'd use to reach them
   - The artifact you'd produce (a waitlist, a pre-order, a click-through demo, etc.)
5. Predict the most likely outcome and what you'd do next in each case (pass / fail / inconclusive).

Example output (excerpt): “Highest-risk assumption: ‘20-200 person DTC brands will pay $499/mo for automated reconciliation that they currently do manually for free.’ Risk score: 9.2. Experiment: $300 in Reddit + LinkedIn ads pointing to a 2-minute interactive demo + a ‘reserve your spot for $99’ pre-order button. Success: 30 pre-orders from 800 clicks in 7 days. Pass = $30K pre-sold pipeline. Fail = kill the idea before writing code.”

Pro tips:

  • Run the RAT before you write the Lean Canvas. Order matters.
  • “Inconclusive” is a valid outcome. It just means your experiment was too soft.

Prompt 14: Competitive teardown

Purpose: Map the competitive landscape in 60 minutes, not 6 weeks. Most founders over-research competitors and under-research non-consumption (people doing nothing).

You are a competitive intelligence analyst.

My SaaS idea: [describe].
My ICP: [from Prompt 6].

Build a competitive map with these sections:

1. Direct competitors: 5-8 tools solving the same problem. For each: positioning, pricing, key feature gap, weakest review, and a 1-sentence "why we lose to them."
2. Indirect competitors: 4-6 tools solving an adjacent problem the ICP would consider.
3. Non-consumption: estimate what % of the ICP is doing nothing today. This is your real opportunity.
4. Substitute behaviors: 3 things the ICP would do *instead* of using any tool (e.g. "hire an analyst," "live with the pain," "build in-house").
5. White space: 2-3 positioning angles nobody is owning. For each, give a 1-sentence tagline and a 1-paragraph positioning.
6. A "kill criteria" test: under what circumstances should I NOT enter this market?

Use 2026 data. Flag any claim that feels speculative.

Example output (excerpt): “Direct: Synder, A2X, PayTraQ - all focused on accounting firms, not ops managers. Gap: nobody owns ‘the ops manager’s Friday close.’ Non-consumption: ~60% of $5M–$50M DTC brands still reconcile manually. Kill criteria: if the top 2 competitors announce native Shopify-3PL reconciliation within 90 days, this idea is dead.”

Pro tips:

  • “Non-consumption” is where the big wins live. People doing nothing are easier to convert than people using a competitor.
  • Set a 60-minute timer. Competitive research beyond that is procrastination in a trench coat.

Prompt 15: Smoke-test landing page copy

Purpose: Write the headline, subhead, and 3 sections of a landing page you can ship in a single afternoon to test demand. No code required - Carrd, Framer, or Notion all work.

You are a B2B SaaS copywriter who has shipped 100+ landing pages.

Product: [describe in 1 sentence].
ICP: [from Prompt 6].
Pain: [from Prompt 1].
UVP: [from Prompt 11].

Write a complete smoke-test landing page with:

1. Headline (under 12 words). Include who, what, and the outcome.
2. Subhead (under 25 words). Include the main pain in the customer's words.
3. 3 bullet "what you get" benefits, each with a verb-led outcome.
4. A "how it works" 3-step section.
5. A "who this is for" + "who this is NOT for" section.
6. A single primary CTA above the fold ("Reserve your spot" / "Join the waitlist" / "Get early access").
7. A short FAQ with 4 questions designed to handle the top objections.
8. A footer line that tells the visitor the page is in beta and slots are limited.

Tone: confident, specific, no buzzwords, no "revolutionary" or "game-changing."

Example output (excerpt): “Headline: ‘Close your Shopify books every Friday in 90 seconds.’ Subhead: ‘No more 11-hour reconciliation marathons. No more surprise discrepancies at the board meeting.’ CTA: ‘Reserve your beta spot - 20 slots open.’ FAQ: ‘Does it integrate with my 3PL?’ / ‘Will it work with multi-currency?’ / ‘Is my data secure?’ / ‘How much will it cost?’”

Pro tips:

  • Ship the landing page before you ship the product. If you can’t get signups, the product won’t help.
  • Track scroll depth, not just clicks. A high scroll + low click rate means your offer is the problem, not your copy.

Section 4: Pricing & Willingness-to-Pay prompts (16–19)

Pricing is the part founders avoid. It’s also the part that determines whether you have a business or a hobby. These four prompts force the pricing conversation forward with real data, not vibes.

Prompt 16: WTP (willingness-to-pay) survey designer

Purpose: Build a 5-question WTP survey you can send to 30 ICP respondents in 24 hours. WTP is the only metric that tells you whether a feature is worth building.

You are a pricing researcher trained on the Van Westendorp Price Sensitivity Meter.

I'm building [product] for [ICP]. My current pricing hypothesis is [e.g. "$299/mo for the Pro tier, $799/mo for Scale"].

Design a 5-question WTP survey:

1. The "too cheap" question (at what price would you be skeptical of quality?).
2. The "too expensive" question (at what price would you not even consider it?).
3. The "cheap but worth it" question.
4. The "expensive but worth it" question.
5. A direct anchor question: "We expect to charge $X/mo. Compared to your current solution, that's: a bargain / fair / expensive / too expensive."

For each question, give me:
- The exact wording (no jargon)
- The answer options (numeric ranges)
- A red flag in the responses that means I'm pricing wrong

Keep the survey under 90 seconds. Reject any question that mentions features, only price.

Example output (excerpt): “Q1: ‘At what monthly price would you question the quality of a reconciliation tool?’ Options: under $50, $50–$100, $100–$200, $200–$400, $400+. Red flag: more than 30% choose ‘under $50’ - you’re underpricing. Q5 anchor: comparison to a $4K/year controller. If 50%+ say ‘expensive,’ reposition against the controller’s cost, not against other SaaS.”

Pro tips:

  • Run the survey on a $200 LinkedIn boosted post. You don’t need 1,000 responses, you need 30 from your exact ICP.
  • Compare results to your Stripe revenue per user at month 3. The two should align within 2×.

Prompt 17: Pricing tier architect

Purpose: Design a 3-tier pricing page (Starter / Pro / Scale) that maximizes ARPU without scaring off small customers. The right tier design is a 10–30% revenue lever.

You are a SaaS pricing strategist.

Product: [describe].
ICP: [from Prompt 6].
WTP data: [paste results from Prompt 16 or your hypothesis].

Design a 3-tier pricing structure with:

1. Tier names (not Free/Pro/Enterprise - use value-based names).
2. The "anchor" tier - the one you actually want most people to pick.
3. Price points for each tier (monthly + annual with discount).
4. The 3-5 features that gate each tier.
5. The "decoy" tier - the one that exists to make the anchor look great.
6. A usage-based component if applicable (e.g. per-reconciliation fee).
7. A 1-sentence headline for the pricing page.

Justify each decision. Flag the assumption most likely to be wrong.

Example output (excerpt): “Tiers: Solo ($99/mo) / Team ($399/mo, anchor) / Brand ($999/mo). Decoy: Brand is decoy-ish - it exists so Team feels reasonable. Gating: Solo caps at 1 store + 1 user; Team adds multi-store, audit log, Slack alerts; Brand adds SSO, SOC 2, custom roles. Usage-based: $0.50 per reconciliation over 5,000/mo.”

Pro tips:

  • Your “anchor” tier should be 2× the cheapest, not 10×. 10× pricing gaps scare buyers.
  • Annual plans should offer 15–20% off, not 50%. Deep discounts attract the wrong customers.

Prompt 18: Value-based pricing story

Purpose: Build a 3-paragraph story that justifies your price in customer terms. “It costs $X because it saves you $Y” is the only pricing argument that works in B2B SaaS.

You are a B2B SaaS sales coach.

Product: [describe].
Price: [from Prompt 17].
Customer's current cost (time + money) of solving the problem: [estimate from Prompt 3].

Write a value-based pricing story I can use on a sales call:

1. The "cost of doing nothing" paragraph (what the customer loses every quarter by not having this).
2. The "cost of current workaround" paragraph (what they're paying in time + tools + errors today).
3. The "cost of our product" paragraph (price + ROI in concrete numbers).
4. A "if this doesn't pay for itself in 90 days, we'll refund" risk-reversal line.
5. A 1-sentence "the math" that I can whiteboard live: [Current cost] - [Our price] = [Net savings].

Make the numbers specific. No "save time" - say "save 8 hours/week which at $75/hr loaded cost is $31,200/year."

Example output (excerpt): “Cost of doing nothing: 1 missed reconciliation per quarter costs ~$14K in board embarrassment and ~$3K in actual cash leakage. Cost of current workaround: 11 hours/week of an ops manager at $75/hr loaded = $42,900/year. Cost of our product: $399/mo = $4,788/year. Net savings: $38,112/year. ROI: 8.9×. Risk reversal: 90-day money-back if you don’t save at least $20K in ops time.”

Pro tips:

  • If you can’t build this story in 10 minutes, your pricing is too high or your value prop is too fuzzy.
  • Email this story to your top 3 prospects before you ever send a demo link. Replies will tell you everything.

Prompt 19: Pricing experiment backlog

Purpose: Plan the 3 pricing experiments you should run in the first 90 days post-launch. Pricing is a hypothesis, not a verdict.

You are a growth lead who has run 50+ pricing experiments.

Product: [describe].
Current pricing: [from Prompt 17].
Stage: pre-launch / launched 0-3 months / launched 3-12 months.

Design 3 sequential pricing experiments to run over the next 90 days. For each:

1. Hypothesis (if we [change X], then [metric Y] will [improve Z] because [reason]).
2. Variant A vs Variant B.
3. The single metric that decides pass/fail.
4. Minimum sample size and run time.
5. The risk of running it (e.g. customer backlash, support load).
6. A "what we'd do if it fails" contingency.

Choose experiments that test different *levers*: price point, packaging, billing cadence, free trial length.

Example output (excerpt): “Experiment 1: $299 vs $399 Team tier price. Metric: free-to-paid conversion at 14 days. Sample: 400 signups per arm. Run time: 21 days. Risk: low. Contingency: revert to $349 and test packaging next. Experiment 2: 14-day trial vs no-trial + $0 deposit. Metric: paid conversion at 30 days. Experiment 3: monthly-only vs monthly + annual (15% off). Metric: % of new customers on annual.”

Pro tips:

  • Test one lever at a time. Multi-variable pricing tests are a waste of statistical power.
  • Document every experiment, even the failures. Your future PM will thank you.

Section 5: Distribution & Channel prompts (20–23)

You can have the best product in the world and die from zero distribution. These four prompts force you to answer the “how does anyone find out?” question before you spend a dollar.

Prompt 20: Channel hypothesis matrix

Purpose: Score 8–10 potential distribution channels against your ICP and stage. Avoid the trap of “I’ll just do content marketing.”

You are a B2B SaaS growth lead.

Product: [describe].
ICP: [from Prompt 6].
Stage: pre-launch / launched 0-3 months / launched 3-12 months.
Budget: $[X]/month for distribution.
Team: [founder-led / has a marketer / has an SDR].

Build a channel matrix with 8-10 channels. For each:

1. Channel name (specific - not "social media," but "r/shopify posts twice a week").
2. Fit score (1-10) for my ICP.
3. Cost (time + money) per qualified lead.
4. Time to first result.
5. Scalability ceiling.
6. The single content asset I'd need to make this work.
7. A "kill criteria" - when to abandon this channel.

Order by expected ROI in the first 90 days. Flag the 2 channels that are *not* the obvious choice.

Example output (excerpt): “Top 3: (1) Cold outbound to 2nd-degree LinkedIn connections - fit 9/10, $0 cost, first result in 7 days, ceiling 50 leads/mo solo. (2) Niche community engagement (Future Commerce Slack, r/shopify) - fit 9/10, $0 cost, slower. (3) Partnerships with 3PLs for co-marketing - fit 8/10, takes 60 days to land. Non-obvious: a monthly ‘State of DTC Reconciliation’ report - fit 7/10, compounds over time.”

Pro tips:

  • Founder-led distribution in months 0–6 is non-negotiable. Don’t hire a marketer until you’ve personally closed 10 customers.
  • Kill channels that cost more than $200 CAC with a 90-day payback or worse.

Prompt 21: Content pillar brainstorm

Purpose: Build a 90-day content plan that actually pulls your ICP into your orbit. Generic content is the silent killer of early SaaS.

You are a content strategist for B2B SaaS.

ICP: [from Prompt 6].
Pain: [from Prompt 1].
UVP: [from Prompt 11].
Channels: [top 3 from Prompt 20].

Design a 90-day content plan:

1. 3 content pillars (themes I can return to for 90 days).
2. 12 specific article or post titles per pillar (36 total).
3. For each title, the format (LinkedIn post, Twitter thread, blog, video, podcast guest pitch).
4. A 1-sentence CTA for each piece.
5. A 1-line distribution plan for each piece (where to post, who to tag).
6. A 1-paragraph "if I had to pick only 4 pieces to write in the first 30 days, which 4 and why."

Every title must use the words my ICP actually uses, not industry jargon.

Example output (excerpt): “Pillar 1: ‘Friday close survival guide.’ Pillar 2: ‘Reconciliation horror stories.’ Pillar 3: ‘Shopify + 3PL integration playbooks.’ Top 4 in month 1: (1) ‘The 11-hour Friday close: a Shopify ops horror story,’ (2) ‘5 reconciliation mistakes that cost DTC brands $50K+,’ (3) ‘Airtable vs. SaaS: when to graduate from spreadsheets,’ (4) ‘How to brief your CFO before the board meeting.’”

Pro tips:

  • “Horror stories” outperform “how-to” content in B2B SaaS in my experience. People share pain.
  • Repurpose one pillar piece into 8 micro-assets (tweets, LinkedIn posts, email sequences). 1 hour of writing, 8 hours of distribution.

Prompt 22: Pre-launch waitlist funnel

Purpose: Design a 4-step waitlist funnel that converts visitors into pre-orders or referrals. A waitlist is your first growth loop.

You are a pre-launch growth specialist.

Product: [describe].
Landing page: [from Prompt 15].
Target: 500 signups in 30 days from a standing start.

Design a 4-step waitlist funnel:

1. The squeeze step (what the visitor sees in the first 5 seconds).
2. The value step (what they get for free in exchange for their email).
3. The qualification step (the 2-3 questions I should ask on the signup form - not more).
4. The referral step (the mechanism that turns signups into 2-3× more signups).

For each step, give me:
- The exact copy
- The mechanics (form, Typeform, viral loop, etc.)
- The single metric that proves this step is working
- A 1-line "if this step is broken, fix this first" diagnosis

Also include: the daily / weekly ritual I should run to keep the funnel warm.

Example output (excerpt): “Squeeze: ‘Close your Shopify books every Friday in 90 seconds - beta launching Q3.’ Value: a free 7-page ‘Friday Close Audit’ PDF. Qualification: email + Shopify URL + monthly GMV band. Referral: ‘Move up the waitlist by 5 spots for every friend who joins.’ Ritual: every Monday, email the top 20 referrers with a personal thank-you.”

Pro tips:

  • The form should never ask for more than email + 1 qualifier. Every extra field cuts conversion 10–15%.
  • “Move up the waitlist” beats “give $10” as a referral incentive. Status > cash.

Prompt 23: Launch channel playbook

Purpose: Build a 14-day launch plan with daily actions for a single coordinated push. Launches are a muscle, and you need reps.

You are a product launch strategist.

Product: [describe].
Launch date: [date].
Goal: [e.g. "100 paying customers in 14 days" or "1,000 waitlist signups"].
Channels: [top 3 from Prompt 20].
Assets: [list what you have - landing page, demo video, blog posts, case studies].

Build a 14-day launch plan:

Day-by-day, list:
- The single primary action for that day
- 1-2 supporting actions
- The channel(s) used
- The asset produced or used
- The metric that tells me it's working

Days 0-2: pre-launch warm-up.
Days 3-5: launch blast.
Days 6-9: sustain and follow-up.
Days 10-14: close loop and measure.

End with a "what we'd do differently next launch" retro template.

Example output (excerpt): “Day 3 (launch day): Publish launch post on LinkedIn + X. Email full waitlist (387 contacts). Submit to 4 directories (Product Hunt, BetaList, IndieHackers, r/shopify). Goal: 80 signups in 24 hours. Day 5: Email non-converters from waitlist with a case study. Day 12: Public retro post on what worked. Day 14: Final report - signups, CAC, qualitative feedback.”

Pro tips:

  • Pre-write every email and social post before launch day. In-the-moment copy is always worse.
  • Plan 2 “amplifier” slots - influencers or communities you can ask to share. Don’t launch without them.

Section 6: Risk & Assumption prompts (24–27)

The last four prompts turn everything you’ve learned into a decision. You don’t have a startup until you have a written GO/NO-GO with a falsifiable thesis.

Prompt 24: Pre-mortem

Purpose: Imagine your startup has failed in 18 months. Write the post-mortem now. This is the single highest-leverage prompt in this guide - and the one most founders skip.

You are a startup post-mortem writer.

Imagine my startup failed 18 months from now. The launch looked promising, but we shut down.

Write the post-mortem in 250 words. Include:

1. The headline cause of death.
2. The 3 contributing factors (with the one nobody saw coming).
3. The single early signal we should have caught in month 2.
4. The decision we should have made differently in week 1.
5. The one assumption that, if it had been true, would have saved us.

Then list the 5 "tells" - observable signals in the next 90 days - that would match this failure mode. Be specific.

Example output (excerpt): “Headline cause: we built a tool for ops managers but the actual buyer was the CFO, and we never sold to them. Contributing factors: (1) we underpriced by 60%, (2) we chased 1,000 small brands instead of 30 big ones, (3) we never built the SOC 2 audit log, so enterprise deals stalled. Early signal: sales calls kept ending with ‘I need to bring my CFO into this.’ Decision: pre-sell to 5 CFOs in week 1. Assumption: ops managers have budget authority (they don’t). Tells: enterprise prospects ask about security, CFO mentions, sales cycle > 30 days.”

Pro tips:

  • Run this prompt before you run prompt 25. The pre-mortem makes the GO/NO-GO more honest.
  • Print the post-mortem and tape it to your wall. Read it weekly.

Prompt 25: GO/NO-GO memo

Purpose: Force a written decision. No more “we’ll see how it goes.” This is the artifact you show your co-founder, your investors, and yourself in 6 months.

You are a startup advisor who has sat on 50 GO/NO-GO decisions.

Here is everything I know about my idea after 48 hours of validation:
[Paste: top 3 customer interviews, landing page conversion, WTP survey results, waitlist size, pre-orders, channel experiments, the pre-mortem from Prompt 24]

Write a GO / NO-GO / PIVOT memo with:

1. A 1-sentence verdict.
2. The 3 strongest pieces of evidence FOR the decision.
3. The 3 strongest pieces of evidence AGAINST.
4. The single experiment I should run in the next 14 days to either confirm or kill the decision.
5. The "if I'm wrong, I'm wrong because..." sentence.
6. A 1-paragraph call to action: what I commit to do this week, publicly.

Be honest. Founders lie to themselves more than to anyone else.

Example output (excerpt): “Verdict: PIVOT. The pain is real, but the buyer is the CFO, not the ops manager. Evidence for: 14/20 interviews confirmed the Friday close pain. Evidence against: 0/20 ops managers said they had budget authority. Experiment in next 14 days: pitch the same problem to 10 CFOs via LinkedIn. If 5+ agree to a call, pivot the positioning. Public commitment: ‘By July 1, I will have either closed 5 CFO pre-orders or shut down the project.’”

Pro tips:

  • “PIVOT” is a valid and often correct answer. Pivoting in week 1 is the cheapest possible move.
  • Make the public commitment in writing. Public accountability > private intention.

Prompt 26: 90-day roadmap with kill criteria

Purpose: Translate the GO/NO-GO into a 90-day plan with hard numbers and hard kill criteria. No more “we’ll keep going and see.”

You are a startup COO.

Verdict: [GO / PIVOT / NO-GO from Prompt 25].
Resource constraint: [solo founder, $X budget, 90 days].

Build a 90-day roadmap with:

1. Three 30-day milestones. Each must have a single primary outcome and 2-3 leading indicators.
2. A "definition of success" for each milestone in concrete numbers.
3. A "kill criteria" for each milestone - the number that means I should stop.
4. The one decision point at the end of each 30-day block.
5. A weekly ritual (1 hour every Friday) to track progress and make a continue/pivot/kill call.

Be specific. No "build the product" - say "ship the auto-match engine to 5 design partners."

Example output (excerpt): “Month 1 milestone: 10 paying customers at $399/mo. Leading: 50 waitlist → 10 paid (20% conversion). Kill: < 3 paying customers OR average WTP below $200/mo. Month 2 milestone: 30 paying customers + 2 case studies. Kill: < 15 paying customers OR NRR below 90%. Friday ritual: review Stripe dashboard, customer NPS, top 3 support tickets, kill-criteria number. 30 minutes.”

Pro tips:

  • If you can’t name the kill criteria, you don’t have a plan. You have a wish.
  • The Friday ritual is the most important habit of any first-year founder. Don’t skip it.

Prompt 27: Founder reflection - “Should I actually do this?”

Purpose: The most underrated prompt in this whole guide. Building a startup is a 5–10 year decision. Make sure you are the right founder for this idea. This is the only prompt that doesn’t optimize the idea - it optimizes you.

You are a founder coach.

Here is my idea, my situation, and my honest fears:
- Idea: [1 sentence]
- Co-founder situation: [solo / with X / looking]
- Runway: [X months of savings]
- Family situation: [single / partner / kids]
- Top 3 fears: [e.g. "I won't make any money for 2 years," "I'm not technical enough," "I'll regret leaving my job"]
- Top 3 motivations: [e.g. "I want to own my time," "I want to build something customers love," "I want to prove I can do it"]

Answer these 5 questions honestly:

1. Given my constraints, is this the *best* idea for me to pursue, or is it just the *latest* idea?
2. What's the smallest version of this idea I could test that doesn't require me to quit my job?
3. What's the one thing I should learn in the next 30 days that would make me a much better founder for this idea?
4. What's the one habit or pattern in my past that I must break to make this work?
5. If I do nothing and stay in my current path, what will I regret most in 5 years?

Be candid. Don't flatter me.

Example output (excerpt): “1. This is a real idea, but it’s not the only real idea. Your constraint is solo + 8 months of runway. Run it nights and weekends for 6 weeks before quitting. 2. Test version: 5 customer interviews + 1 landing page + 1 pre-order. Cost: $300. No quit required. 3. Learn: how to write cold outreach that doesn’t sound desperate. 4. Pattern to break: planning for 3 months before talking to a customer. You have to ship in 7 days, not 7 weeks. 5. If you do nothing, you’ll regret not having tried. That’s the only regret that matters.”

Pro tips:

  • Re-run this prompt at the end of every quarter. Your constraints change. Your answer should too.
  • The “smallest version” answer is the only one that matters in week 1.

Comparison table: 27 prompts at a glance

#PromptCategoryTime to useOutput artifactBest for
1Pain hypothesis stress-testProblem15 minScored pain gridAll stages
2JTBD extractorProblem10 minOne-page briefPre-interview
3Workaround archaeologyProblem20 minWorkaround mapPre-interview
45 Whys deep diveProblem15 min5-layer root causeCustomer calls
525-word problem statementProblem10 minLanding page heroAll stages
6ICP persona sheetCustomer25 minPersona docPre-launch
7ICP scoring rubricCustomer15 min100-pt rubricPre-launch
8Mom Test interview scriptCustomer20 min30-min scriptDiscovery
9Cold outreach emailCustomer15 min5 email variantsDiscovery
10LinkedIn DM scriptsCustomer10 min3 DM variantsDiscovery
11Lean Canvas draftSolution30 min9-block canvasPre-build
12MVP scope cutterSolution20 minMVP backlogPre-build
13RAT (riskiest assumption)Solution25 minExperiment planPre-build
14Competitive teardownSolution60 minCompetitor mapPre-build
15Smoke-test landing pageSolution30 minLive pagePre-build
16WTP survey designerPricing20 min5-Q surveyPre-launch
17Pricing tier architectPricing25 min3-tier pricingPre-launch
18Value-based pricing storyPricing20 minROI paragraphSales
19Pricing experiment backlogPricing20 min3 experimentsPost-launch
20Channel hypothesis matrixDistribution30 minScored channelsPre-launch
21Content pillar brainstormDistribution30 min90-day planPre-launch
22Pre-launch waitlist funnelDistribution30 min4-step funnelPre-launch
2314-day launch playbookDistribution45 minDaily planLaunch
24Pre-mortemRisk15 minPost-mortemPre-build
25GO/NO-GO memoRisk30 min1-page decisionPre-build
2690-day roadmap + kill criteriaRisk30 minQuarterly planPost-launch
27Founder reflectionRisk20 minSelf-auditQuarterly

How to chain these prompts into a 48-hour sprint

Here’s the playbook. I’m laying it out as a literal Saturday-Sunday-Monday schedule.

Saturday (Hours 0–16): Problem + Customer + early Solution

  • Morning: Run prompts 1, 2, 3, 4 in order. Save outputs to /research/problem/.
  • Midday: Run prompt 5 to crystallize your 25-word statement.
  • Afternoon: Run prompts 6 and 7 for ICP. Run prompt 8 to build the interview script.
  • Evening: Run prompt 9. Send 20 cold emails. Sleep.

Sunday (Hours 16–36): Customer interviews + Solution shape

  • Morning: Run 5 customer calls using the script from prompt 8.
  • Midday: Run prompt 11 (Lean Canvas) and prompt 13 (RAT). Update the canvas after each call.
  • Afternoon: Run prompt 12 (MVP scope) and prompt 14 (competitive teardown).
  • Evening: Run prompt 15. Ship the landing page to Carrd or Framer. Send 5 warm intros for Monday calls.

Monday (Hours 36–48): Pricing + Distribution + Decision

  • Morning: Run prompts 16 (WTP survey) and 17 (pricing tiers). Send the survey to 30 LinkedIn connections.
  • Midday: Run prompts 20 (channels), 21 (content), 22 (waitlist).
  • Afternoon: Run prompts 24 (pre-mortem) and 25 (GO/NO-GO memo).
  • Late afternoon: Run prompt 26 (90-day roadmap). Post your public commitment.
  • Evening: Run prompt 27 (founder reflection). Decide.

That’s 27 prompts across 48 hours. It’s tight. It’s doable. And it beats spending 18 months building the wrong thing.

Common mistakes to avoid

A few traps I’ve watched founders fall into repeatedly. Don’t be that founder.

  • Treating ChatGPT output as truth. ChatGPT is a research assistant, not a customer. Every insight it gives you must be tested with real humans. The prompts are scaffolding for your thinking, not a substitute for it.
  • Skipping the Mom Test. It’s tempting to ask “would you use this?” Rob Fitzpatrick warns against exactly that. Ask about their life, not your product.
  • Confusing interest with commitment. A polite “yeah, I’d check that out” in a survey is worth almost nothing. A pre-order, a calendar invite, or a referral is worth something.
  • Pricing on vibes. Run prompt 16 with 30 real ICP respondents. WTP data is the only pricing that holds up to a real customer call.
  • Skipping the kill criteria. If you can’t name the number that means stop, you’ll never stop. The CB Insights data shows 70% of failed startups cited “ran out of capital” - almost always because they didn’t kill weak experiments early (CB Insights, March 5 2026).
  • Optimizing the wrong metric. “Waitlist signups” feel great. “Paying customers” actually matter. The Failory 2026 update found the biggest failure pattern is still a marketing problem - usually a marketing team chasing top-of-funnel vanity while ignoring the bottom.
  • Going solo forever. A 48-hour validation sprint is a great solo exercise, but a 12-month build is not. Find a co-founder or a peer group by month 3.
  • Ignoring the “no.” The most valuable output of these prompts is a clean, well-reasoned NO. Every dead startup in 2026 is a NO that came 18 months too late.

Final word

You don’t need more ideas. You need fewer, validated better. The 27 prompts in this guide won’t write your code, hire your team, or close your customers. But they’ll force you to answer the only question that matters in 48 hours: is this worth the next 18 months of my life?

Run the sprint. Write the GO/NO-GO. Then either commit publicly or shut it down with dignity. The graveyard of 2026 is full of founders who skipped the writing part.

If this helped, send it to a founder friend who keeps saying “I just need to validate this real quick.” They probably need a Saturday with these prompts more than they need a new Notion template.