How to Validate a SaaS Idea Before Writing Code
A two-week process to find out whether anyone cares — using conversations, a landing page and a price.
Promtly Editorial Desk
Published · 8 min read
Validation is not asking friends whether they like your idea. It is collecting evidence that strangers have the problem, already spend time or money on it, and will pay you to solve it.
Days 1–4
Ten problem interviews. No pitching.
Days 5–6
Write a one-page offer in the customer's words.
Days 7–12
Share it where those people already gather.
Days 13–14
Ask for a pre-order or a deposit.
Interviews that tell the truth
Ask about the last time the problem happened, what they did, and what it cost them. Past behaviour beats future promises.
Three questions to always ask
What did you try last? What did that cost? What would you change if you could?
Keep reading
Illustrative Case: How a Meal Planning App Could Reach $1K MRR
A composite case built from common indie patterns: narrow niche, one acquisition channel, and pricing that changed twice.
7 min read
The Real Cost of Building Your First SaaS
Tools, hosting, domains, payments and your own time — what a lean first SaaS typically costs in year one.
9 min read
Lovable vs Cursor: Which One Should You Choose?
One is a full-stack app builder in the browser; the other is an AI code editor. The right choice depends on your starting point.
8 min read