How to Validate B2B SaaS Demand Before Writing a Single Line of Code
The 5-step customer discovery framework to secure pre-orders and letters of intent before building your prototype.
The greatest trap for software engineers is treating customer discovery as an obstacle between them and their text editor. Coding feels productive; talking to potential customers feels uncomfortable.
As a result, founders build for six months, launch to zero customers, and write a post-mortem about "market timing." Market timing was fine—the problem was building a solution for an unverified problem.
Here is how to validate real commercial demand in 14 days without opening an IDE.
1. The Mom Test: How to Ask Questions That Don't Invite Lies#
If you ask a prospect: "Would you use an AI tool that organizes your inbox?", they will always say "Yes, sounds cool!" because being polite costs zero dollars.
According to Rob Fitzpatrick's The Mom Test, you must never ask prospects about the future or what they would do. Only ask about what they have already done and paid for in the past.
The 4 High-Signal Validation Questions:
- "When was the last time this specific problem happened in your workflow?" (If they can't remember, it is a minor nuisance, not a business priority).
- "What did you do to try to solve it?" (If they haven't searched for tools or tried a workaround, they won't pay for yours).
- "How much does that manual workaround cost your team each month?" (Anchors the financial value of the problem).
- "What other tools did you evaluate, and why did they fail?" (Reveals the competitive gap you must target).
2. The Concierge MVP Test#
Before automating a process with complex code, deliver the outcome manually as a service:
- If your SaaS idea is an automated lead enrichment scraper: Manually scrape 50 leads in Google Sheets, verify the emails by hand, and email the prospect: "Hey, I curated these 50 verified leads for your niche. Would you pay $100 for 500 more next week?"
- If they pay you through PayPal or Stripe invoice for the manual work, you have validated demand. Now you can write code to automate your own manual effort.
3. The Paid Pilot Agreement#
Before writing production code, ask your warmest discovery contacts for a Letter of Intent (LOI) or a 50% discounted annual pre-order.
"We are building the closed beta for this exact system now. We are taking 5 founding design partners at $49/mo (locked forever, standard price will be $199/mo). If it doesn't solve your problem in 30 days, 100% refund guaranteed."
If you cannot convince 2 people to pre-pay $49 for a software solution to their "huge problem," they will not pay $49 after you spend 300 hours building it.
Found this blueprint valuable?
Share it with fellow engineers and indie makers building in public.
DevCastle Editorial Team
AUTHORProduct Strategy
Engineering, product strategy, and growth systems for DevCastle. Building open tools, market intelligence trackers, and launchpad infrastructure for software builders worldwide.
Related Engineering Blueprints
Continue learning with battle-tested architectures and growth breakdowns.
How to Find Profitable SaaS Ideas on Reddit: The 2026 Developer Blueprint
Stop brainstorming in a vacuum. How to mine high-intent complaints and unmet software demand directly from Reddit communities.
Product Hunt Alternatives in 2026: Where Independent Builders Actually Launch
Product Hunt is flooded with paid upvote syndicates and enterprise VC launches. Here are the authentic platforms where devs get real customers.
The Indie Hacker Tech Stack (2026 Edition): Next.js 14, Tailwind, Prisma & Serverless AI
How modern solo founders ship production-ready SaaS in 7 days without drowning in infrastructure maintenance.