Market validation before full development
SaaS / AI Tool
Pre-development startup with a product hypothesis: an AI tool to automate an operational task repeated by marketing and communications teams. The team had the technical skills to build it, but zero certainty the market wanted it — at least not in that form and at that price. Build first, validate later is the most expensive way to be wrong. We built a validation system before writing a single line of code: three landing pages with distinct angles (time savings, fewer errors, process scalability), a waitlist with a qualifying micro-survey (main use case, how often the problem shows up, tools currently used, monthly spend capacity), Meta campaigns optimized for form completion on specific professional audiences. Anyone who completed the survey with consistent answers was classified as high intent. The answers revealed three usage segments the team hadn't anticipated — one accounted for 34% of high-intent signups and wasn't in the original roadmap. The "time savings" promise performed 40% better than the other two, redefining the product's positioning before development.
1,240
Waitlist signups
€1.82
Cost per signup
18%
High-intent users
3
Value promises tested
The context
Pre-development startup with a product hypothesis: an AI tool to automate a specific operational task repeated by marketing and communications teams. The team had the technical skills to build it, but no certainty the market wanted it — at least not in that form and at that price.
The problem
Build first, validate later is the most expensive way to be wrong. The temptation was to start with development to "have something to show." The risk: 6 months of work on a product the market doesn't want, or doesn't want in that form, or not at that price.
The system we built
Three landing pages, three different promises. Instead of testing a single value proposition, three landing pages were created with distinct angles: time savings, fewer errors, process scalability. Each page had a different tone, headline and main benefit. Meta traffic was split evenly across the three to see which angle resonated most.
Waitlist as an intent filter. Signing up for the waitlist didn't require payment but included a micro-survey: main use case, how often the problem shows up, tools currently used, monthly spend capacity. Anyone who completed the survey with consistent answers was classified as high intent.
Meta Ads with a lead objective, not traffic. Campaigns optimized for form completion, not for clicks. Audiences built on specific professional interests (marketing managers, content creators, agencies), not generic ones.
Pattern analysis. The survey answers revealed three usage segments the team hadn't anticipated — one of which accounted for 34% of high-intent signups and hadn't been considered in the original roadmap.
The result
1,240 waitlist signups at an average cost of €1.82 per signup. 18% classified as high intent — 223 people who had stated a real problem, a compatible budget and concrete urgency. The "time savings" promise performed 40% better than the other two, redefining the product's positioning before a single line of code was written.