Chapter 3: Pre-MVP Validation Techniques

The Most Efficient Code is Code You Never Write

Most founders skip straight to building. They assume the only way to test an idea is to create a working product. This is the most expensive mistake in entrepreneurship.

"Pretotyping" (a term coined by Alberto Savoia) involves simulating the core experience of a product to validate demand and usage patterns with near-zero engineering effort. The goal: answer the question "Should we build this?" before asking "Can we build this?"

The concept is deceptively simple, yet most founders resist it. They argue that their product is too complex to simulate, that their customers expect a polished experience, or that manual processes don't scale. All of these objections miss the point. Pretotyping isn't about building a business -- it's about answering a question. The question is: "If this product existed exactly as we envision it, would people use it and pay for it?" If the answer is no, then the sophistication of your technology is irrelevant. You're building the wrong thing.

Consider the cost asymmetry: a typical pretotyping experiment costs between $100 and $1,000 and takes 1-2 weeks. A typical MVP costs between $25,000 and $150,000 and takes 3-6 months. If the pretotype reveals that your core assumption is wrong, you've saved five figures and months of your life. If it validates your assumption, you now have the confidence and customer insights to build a much better MVP. There is no scenario in which pretotyping first makes you worse off.

The Three Pretotyping Techniques

Each technique has its place. The key is matching the technique to the assumption you're testing:

Technique #1: The Wizard of Oz

Create a highly polished, functional-looking interface where humans secretly do the work that would eventually be automated. The user believes they're interacting with technology.

The name comes from the 1939 film: behind the impressive facade of the "Great and Powerful Oz" was just a man pulling levers. Similarly, behind the impressive facade of your "AI-powered" or "automated" product is a team of people doing the work manually. The user sees the output and judges the value, blissfully unaware that there's no technology behind it.

When to Use Wizard of Oz

How to Run a Wizard of Oz Experiment

A practical tip for Wizard of Oz experiments: set response time expectations that match what the automated version would deliver, not what is convenient for your manual team. If the future AI will respond in 30 seconds, your human operators should respond in approximately 30 seconds. If the future system would deliver results overnight, deliver results overnight. Testing with unrealistically fast or slow response times compromises the validity of the experiment because response time itself affects the user's perception of value.

Technique #2: The Concierge MVP

Similar to Wizard of Oz in its manual execution, but with a critical difference: the human involvement is explicit. You deliver the value as a high-touch service, openly acknowledging that it's not yet automated.

The Concierge MVP is particularly powerful for startups in the discovery phase because it generates the richest qualitative data of any pretotyping technique. When you manually deliver the value, you see every facial expression, hear every hesitation, and witness every workaround. This intimacy with the customer experience is impossible to replicate through surveys, analytics, or even formal user interviews.

When to Use Concierge

The Concierge Learning Framework

Every concierge interaction should generate learning. Use this framework:

Keep a structured log of every concierge interaction. After 10-15 interactions, patterns will emerge. You'll notice that certain pain points come up in every session while others are unique to individual customers. The recurring patterns are your "must have" features. The unique ones are "nice to have" at best. This data is worth more than any feature prioritization framework because it comes directly from observing real behavior, not from asking hypothetical questions.

The Concierge-to-Product Transition

The goal of the concierge phase is not to run a services business forever -- it's to learn enough to build the right product. Here's how to know when to transition:

Technique #3: The Fake Door (Smoke Test)

Create a marketing asset (landing page, ad, or button) for a feature that doesn't exist. When users click "Buy" or "Sign Up," show them a waitlist or "Coming Soon" message. This measures actual behavior -- not what people say they'd do.

The Fake Door technique exploits a fundamental truth about human psychology: what people say and what people do are often very different. Surveys and interviews measure stated preferences. Fake Door tests measure revealed preferences. A user who clicks "Buy Now" on a landing page and enters their credit card information is demonstrating genuine intent in a way that no survey response ever could.

How to Run a Fake Door Experiment

A crucial detail that many founders miss: the quality of your landing page directly affects the validity of your test. If your page looks amateur, low conversion rates might indicate poor marketing rather than weak demand. Conversely, if your page uses misleading or exaggerated claims, high conversion rates might not represent sustainable demand. The landing page should honestly represent your value proposition with professional-quality design. You're testing the offer, not your design skills.

LeanPivot's Market Signal Test tool can help you design and analyze your fake door experiment, including recommended ad spend, audience targeting, and statistical significance calculations based on your business model.

Fake Door Benchmark Thresholds

Interpreting Fake Door results requires nuance. A 3% CTA click rate might seem low in absolute terms, but if you're selling a $500/month B2B product, that conversion rate could represent a viable business. Meanwhile, a 10% click rate for a $2.99 consumer app might be insufficient if the lifetime value is too low to justify customer acquisition costs. Always interpret conversion rates in the context of your unit economics.

Advanced Fake Door: Multi-Variant Testing

Once you've validated basic demand, you can use Fake Door tests to answer more specific questions:

Choosing the Right Technique

Match your pretotyping technique to the assumption you need to test:

What You're Testing	Best Technique	Why
"Is there demand for this?"	Fake Door	Measures actual purchase intent at scale
"What price will they pay?"	Fake Door + A/B	Test different price points on landing pages
"Will the solution work?"	Wizard of Oz	Test the full experience without building backend
"What do they actually need?"	Concierge	Deep discovery through high-touch service
"Will they keep using it?"	Wizard of Oz	Measure retention over multiple interactions
"What features matter?"	Concierge	Learn from manual delivery before automating

The Pretotyping Decision Tree

This sequential approach -- Fake Door, then Concierge, then Wizard of Oz -- represents increasing investment at each stage. You start with the cheapest, fastest test (Fake Door) and only proceed to more expensive, slower tests (Concierge, then Wizard of Oz) after each previous stage validates. Think of it as a funnel of confidence: each stage narrows your uncertainty and increases your conviction before you invest more resources.

The entire pretotyping sequence -- from Fake Door to Concierge to Wizard of Oz -- can be completed in 4-8 weeks with a total budget of $1,000-$5,000. Compare that to the typical "build first, ask questions later" approach of 3-6 months and $50,000-$150,000. The pretotyping path delivers more learning at a fraction of the cost, and it produces the specific insights you need to build a product that customers actually want.

Key Takeaways

Now that you can validate demand without building, let's explore how to prioritize features and make build-vs-buy decisions when you do start developing.