---
title: "Experiments, MVPs and no-code/AI prototypes"
description: "Learn before you build big A minimum viable product (MVP) is the smallest thing you can create to test a key assumption with real customers. It is not a…"
url: https://optimizeall.com/learn/entrepreneurship-and-business-models/experiments-and-mvps
updated: 2026-10-05
---

Entrepreneurship & Business Models · Validating ideas and customer discovery · lesson 3 of 18 · 14 min

# Experiments, MVPs and no-code/AI prototypes

## Learn before you build big

A **minimum viable product (MVP)** is the smallest thing you can create to test a key assumption with real customers. It is not a buggy first version of your full vision; it is an experiment designed for learning. The idea is closely associated with Eric Ries's *The Lean Startup* and the **build–measure–learn** loop.

## Types of experiments and MVPs

| Type | What it is | Tests | Example |
|---|---|---|---|
| **Landing page / smoke test** | A page describing the offer with a sign-up or pre-order button | Interest, message, willingness to act | "Join the waitlist" for a meal-prep service |
| **Concierge MVP** | Deliver the service manually, personally | Value of the outcome; process | Founders personally plan meals for 10 customers |
| **Wizard of Oz** | Customers see an automated front end; humans work behind the scenes | Whether customers use and value the experience | A "smart" scheduling assistant run manually |
| **Pre-sales / letters of intent** | Customers commit before the product exists | Willingness to pay | B2B pilot contracts |
| **Prototype / clickable mock-up** | Non-functional design | Usability, comprehension | Figma prototype tested with users |
| **Single-feature product** | One core feature built well | Core value, retention | A simple invoicing tool before a full accounting suite |
| **Marketplace test** | Sell on an existing platform | Demand at a price | Listing a product on a marketplace before building a store |

## Designing an experiment: step by step

1. **Choose the riskiest assumption** from your assumption map.
2. **Write a hypothesis:** "We believe [segment] will [behaviour] because [reason]."
3. **Define the test and metric.**
4. **Set a success criterion in advance.** Decide what result would count as success or failure before running the test, so you are not tempted to reinterpret results.
5. **Run it quickly and cheaply.**
6. **Decide:** persevere, pivot or stop.

## Experiment card template

```
Hypothesis: Boutique owners in Lahore will pre-pay for 3 months of an inventory tool
Test: Offer a 3-month pre-pay at a launch discount to 30 interviewed owners
Metric: % who pay a deposit within 2 weeks
Success criterion (set in advance): ≥ 20% (6 of 30)
Cost / time: 2 weeks, founders' time, payment link
Result: 7 of 30 paid (23%)
Decision: Persevere; build sync feature for this group first
```

## Measuring the right things

Avoid **vanity metrics** (page views, app downloads, social likes) that look good but do not show real value. Prefer **actionable metrics** tied to behaviour and money: sign-up to active use conversion, retention after 4 weeks, paid conversion, repeat purchase rate, referral rate.

## Pivot or persevere?

A **pivot** is a change in strategy based on learning: a different customer segment, problem, solution, channel or revenue model, while keeping what you have learned. Pivot when evidence repeatedly contradicts a core assumption. Persevere when key metrics are improving toward your targets. Stop when no viable path appears after reasonable testing and resources are running low.

## Ethics and compliance in experiments

- Be honest: do not take money for products you have no intention of delivering. Pre-sales must be refundable or clearly disclosed.
- Protect personal data collected in tests, following applicable data protection laws (for example the UK GDPR, the UAE and Saudi data protection laws, US state privacy laws and Pakistan's applicable rules).
- For regulated sectors such as health, finance and food, check what you can legally test before involving customers.

## Worked example

*Illustrative.* A founder in Riyadh wanted to launch a subscription for healthy school lunches. Instead of building a kitchen, she ran a concierge MVP: she partnered with an existing licensed caterer, took orders via a simple form for four weeks from 40 families recruited through parent groups, and delivered personally. She measured weekly reorder rate and willingness to pay. Reorders were strong among families with two working parents but weak elsewhere, leading her to focus marketing on that segment and to negotiate a supply agreement before investing in her own kitchen.

## 2026 update: prototypes in days with no-code and AI builders

The cost of building a convincing prototype has collapsed. AI app builders (for example Lovable, Bolt, v0 or Replit's agent), no-code tools (Bubble, Webflow, Glide, Softr), form builders (Tally, Typeform, Google Forms) and automation tools (Zapier, Make, n8n) let a non-technical founder put something real in front of customers within days. That is a gift and a danger: because building is easy, founders build *more* instead of *learning* more.

Use this rule: **build the least that produces the behaviour you need to observe.**

| What you need to learn | Fastest honest test | Typical 2026 tooling |
|---|---|---|
| Will anyone click "buy"? | Landing page with price and a pre-order or waitlist | Webflow/Carrd/Framer page, Stripe Payment Link or a form |
| Do they value the outcome? | Concierge: deliver it by hand | Email, WhatsApp Business, a shared doc |
| Will they use a workflow repeatedly? | Clickable or AI-built prototype with real data | Figma prototype, Lovable/Bolt/v0 app, Glide on a spreadsheet |
| Can AI do the job well enough? | Wizard of Oz: AI drafts, a human checks before sending | Claude/ChatGPT with a written prompt and a review checklist |

## Hands-on: a one-week AI-assisted MVP plan

```text
Day 1  Write the experiment card (hypothesis, metric, success threshold set in advance).
Day 2  Generate a landing page draft with an AI builder; rewrite the copy yourself
       using customer quotes. Add a real price and a "Reserve / Join pilot" button.
Day 3  Build the minimum workflow: a form -> spreadsheet -> automation that alerts you.
       If AI produces the output, add a human review step before anything reaches a customer.
Day 4  Recruit 20-50 target users from your interview list and communities.
Days 5-6  Run it. Deliver manually where needed. Log every interaction.
Day 7  Compare results with your threshold. Decide: persevere, pivot, or stop.
```

**Guardrails for AI-built prototypes:** do not collect payment card data yourself (use a regulated payment provider's hosted page or link); do not store personal data you do not need; check the builder's data and hosting terms; tell users when they are testing a pilot; and have a human check AI output in any domain where errors cause harm.

## Worked example: a Wizard of Oz AI service

*Illustrative.* A founder in Riyadh believed small e-commerce stores would pay for weekly Arabic and English product descriptions. Instead of building software, she offered a pilot: stores sent product photos and notes through a form; an AI model drafted descriptions using a tested prompt; she edited each one, checked claims against the notes, and returned them within 24 hours. Success threshold, set in advance: 6 of 20 pilot stores pay for a second month. Result: 9 paid, and her edit log showed which kinds of products needed the most human correction, which became the spec for the real product and the basis for its cost model.

## Common mistakes

- Building a full product as the "MVP".
- No success criteria set in advance.
- Measuring vanity metrics.
- Running experiments too long without deciding.
- Testing with the wrong segment.

## Quick self-check

What is your riskiest assumption right now, and what is the cheapest experiment that could disprove it within two weeks? Write the experiment card today.

## Video lecture: Experiments, MVPs and no-code/AI prototypes

Lecture coming soon · 11 chapters · about 9 minutes. Read the full transcript below.

1. Experiments, MVPs and AI prototypes
2. Why it matters
3. MVP types
4. Experiment card
5. Worked example 1: dog walking
6. Worked example 2: Wizard of Oz with AI (illustrative)
7. Watch me: a pilot in an hour
8. Ethics and metrics
9. Deciding after a test
10. Common mistakes
11. Recap and try this now

## Lecture transcript

### Experiments, MVPs and AI prototypes

In 2026, you can build an app over a weekend. You describe it in plain English to an AI builder, and out comes a working prototype. So here's the uncomfortable question. If building is now that easy, why do most new products still fail? Because the hard part was never building. It was learning what people will actually do. In this lecture, you'll learn to design experiments that answer one risky question at a time, choose the right kind of MVP, set success criteria before you look at the results, and use no-code and AI tools to learn faster, without fooling yourself.

### Why it matters

Why does this matter? Because every week you build without learning, you're spending your most limited resource: runway and energy. A minimum viable product, an idea associated with Eric Ries and The Lean Startup, isn't a smaller version of your dream product. It's the smallest thing that lets you observe real customer behaviour and test a specific assumption. Build, measure, learn. And here's the key idea for today. Build the least that produces the behaviour you need to observe. If you want to know whether people will pay, you don't need an app. You need a price and a way to pay.

### MVP types

Here's an analogy. A film studio doesn't shoot a whole film to find out whether audiences like the story. They test a script reading, then a trailer, then a rough cut with a test audience. Each step is cheap compared with the next, and each answers a different question. MVPs work the same way. A landing page with a price tests whether anyone clicks buy. A concierge MVP, where you deliver the service by hand, tests whether people value the outcome. A Wizard of Oz test, where the front end looks automated but a human does the work, tests whether people use the experience. And a clickable or AI-built prototype tests whether a workflow makes sense to them.

### Experiment card

Now the method, step by step. First, pick your riskiest assumption from your assumption map. Next, write a hypothesis: we believe this segment will do this behaviour because of this reason. Then choose the test and one metric. And here's the step most founders skip. Set your success threshold before you run it. For example, at least six of thirty will pay a deposit within two weeks. Write it down. Why? Because once results arrive, you'll be tempted to reinterpret them. Four out of thirty will suddenly feel promising. Finally, run it fast, then decide: persevere, pivot, or stop.

### Worked example 1: dog walking

A simple worked example. Sam in Bristol thinks dog owners will pay for a weekend dog-walking subscription. Instead of an app, he makes a one-page site with a price, twenty-five pounds a weekend, and a button saying reserve your first weekend. He puts up posters in two parks and shares it in a local community group. His threshold, set in advance, is ten reservations in two weeks. He gets four. So what does he learn? At that price, in that channel, demand is weak. He hasn't wasted months on an app. He can now test a different price, a different segment, like busy couples in flats, or a different channel.

### Worked example 2: Wizard of Oz with AI (illustrative)

Now a realistic business scenario, with illustrative numbers. Noura, in Riyadh, believes small online stores will pay for weekly product descriptions in Arabic and English. Instead of building software, she runs a Wizard of Oz pilot. Stores submit photos and notes through a simple form. An AI model drafts descriptions using a prompt she's tested. Then she edits every one, checks claims against the notes, and sends them back within twenty-four hours. Her threshold, written in advance: six of twenty pilot stores pay for a second month. Result? Nine pay. And there's a bonus. Her edit log shows which product types need the most human correction. That becomes the spec for the real product, and the basis for its cost model.

### Watch me: a pilot in an hour

Watch me do it. I'll set up Noura's pilot in under an hour. Step one, I write the experiment card. Step two, I ask an AI builder for a landing page, then rewrite the headline myself using real customer words, like, stop writing product descriptions at midnight. I add a real price and a join the pilot button. Step three, I create a form that feeds a spreadsheet, and an automation in a tool like Zapier, Make or n8n that alerts me when a store submits. Step four, and this is non-negotiable, I add a review column. Nothing reaches a customer until a human marks it approved. For payments, I use a hosted payment link from a regulated provider, never a homemade card form.

### Ethics and metrics

What about ethics and compliance? Keep it simple. Tell people they're joining a pilot. Don't take money for things you won't deliver, and make pre-orders refundable. Don't collect personal data you don't need, and follow the data protection rules where your customers live. Check your no-code or AI builder's data and hosting terms. And in health, finance, legal or anything safety-related, a human must check AI output before it reaches anyone. Now, what about metrics? Avoid vanity numbers like page views or likes. Measure behaviour that costs the customer something: time, data, money or reputation, like a referral.

### Deciding after a test

Once the results are in, how do you decide? Look at three things together. First, the headline number against your threshold. Did you hit it, miss it narrowly, or miss it badly? Second, the quality of the behaviour. Nine people paying once is different from nine people paying, using it weekly and telling a friend. Third, what surprised you. Often the most valuable result isn't the metric at all. It's the unexpected segment that responded, or the objection you heard five times. Then choose. Persevere if the numbers are near or above target and improving. Pivot if the evidence keeps contradicting a core assumption. And stop if, after honest testing, no path looks viable. Stopping early is a success. It frees you for the next idea.

### Common mistakes

Now, the common mistakes. Building the full product and calling it an MVP. With AI builders, this is more tempting than ever. No threshold set in advance. Measuring vanity metrics. Running a test for months without deciding. Testing with the wrong segment, usually people who are easy to reach rather than people with the problem. And letting AI output reach customers unchecked, then blaming the customer when they don't return. One more. Don't confuse a pivot with giving up. A pivot keeps what you've learned and changes one big thing: the segment, the problem, the solution, the channel or the revenue model.

### Recap and try this now

Let's recap. An MVP is an experiment, not a small product. Pick the riskiest assumption, write a hypothesis, choose one metric, and set the threshold before you look. Choose the cheapest test that shows the behaviour: a landing page, a concierge service, a Wizard of Oz pilot or a prototype. Use AI and no-code tools to build less and learn faster, with a human checking anything that matters. Your try this now: write one experiment card today, and use the one-week plan in the lesson to run it. In the next module, we'll turn what you've learned into a business model.

## Key takeaways

- An MVP is the smallest experiment that tests a key assumption with real customers.
- Choose from landing pages, concierge, Wizard of Oz, pre-sales, prototypes and single-feature products.
- Write hypotheses with success criteria set in advance; measure actionable, not vanity, metrics.
- Pivot, persevere or stop based on evidence; run experiments ethically and lawfully.
- AI and no-code builders make prototypes cheap; build the least that produces the behaviour you need to observe, and keep a human check on AI output.

## Try it

Write one experiment card with a success threshold set in advance, then run the one-week plan: an AI-drafted landing page with your own copy, a form-to-sheet workflow with a human review column, and a hosted payment link or waitlist.

- [Previous: Customer discovery interviews](https://optimizeall.com/learn/entrepreneurship-and-business-models/customer-discovery-interviews)
- [Next: The Business Model Canvas](https://optimizeall.com/learn/entrepreneurship-and-business-models/business-model-canvas)
- [All lessons of Entrepreneurship & Business Models](https://optimizeall.com/learn/entrepreneurship-and-business-models)