# The Prototyping Loop Playbook

> Thesis to decision in 5 days. Test the thesis before you scope the project.

*P10 · Module M4 — Prototype to Production · The CEO AI Playbook by Stephen Forte*

Canonical: https://academy.buildclub.com/m4/p10-prototyping-loop

## Thesis

Test the thesis. Then scope the project.

## Key Takeaways

- Test the thesis. Then scope the project.
- 53% — of enterprise AI pilots stall before reaching production.
- 6–9 mo — typical pilot-to-production timeline at mid-market firms.
- 5 days — from thesis to kill-or-scale decision in the prototyping loop.
- Name one repetitive internal task that has clear inputs and outputs — write the one-sentence thesis.

## The Playbook

1. **State the thesis** — In one sentence. If you cannot, the project is not ready to be scoped, let alone built.
2. **Build in 5 days** — A working prototype against a real data sample. Not a deck. Not a flowchart. Running code.
3. **Wire to one flow** — Connect it to one workflow that exists today. No greenfield.
4. **Measure against one metric** — One named number moves or it does not. If the metric does not move, kill it.
5. **Kill or scale** — The Friday decision. Prototype cost under $5K and five days either way.
Mon. **State the thesis** — One sentence. Business owner plus one engineer only.
Tue. **Build against real data** — Perplexity prototype. Real data sample. No synthetic.
Wed. **Wire to one workflow** — The actual live workflow. Real system access.
Thu. **Measure against the one metric** — Run the comparison. Collect the output.
Fri. **Kill or scale** — Present to the sponsor. Make the call. If kill, document why.

## Key Numbers

- **53%** — of enterprise AI pilots stall before reaching production. (McKinsey AI deployment research)
- **6–9 mo** — typical pilot-to-production timeline at mid-market firms. (BuildClub field interviews · 2026)
- **5 days** — from thesis to kill-or-scale decision in the prototyping loop.

## What to Do Monday

- Name one repetitive internal task that has clear inputs and outputs — write the one-sentence thesis.
- Open Perplexity, state the thesis, build against real data — start today.
- Wire it to one workflow that exists today — no greenfield, no synthetic data.
- Name the one metric it must move by Friday — write it on the calendar invite.
- Make the kill-or-scale decision on Friday — no extensions.

## FAQ

**What is the core idea of The Prototyping Loop Playbook?**

Test the thesis. Then scope the project.

**What does the data say a CEO should pay attention to?**

53% of enterprise AI pilots stall before reaching production. 6–9 mo typical pilot-to-production timeline at mid-market firms.

**What should a CEO do Monday morning after reading The Prototyping Loop Playbook?**

Start here: Name one repetitive internal task that has clear inputs and outputs — write the one-sentence thesis; Open Perplexity, state the thesis, build against real data — start today; Wire it to one workflow that exists today — no greenfield, no synthetic data.

**What are the steps in The Prototyping Loop Playbook?**

1) State the thesis; 2) Build in 5 days; 3) Wire to one flow; 4) Measure against one metric; 5) Kill or scale.

**Where do the claims in The Prototyping Loop Playbook come from?**

The playbook cites McKinsey AI deployment research; MIT NANDA — 95% pilot-stall figure; YPO Technology Network AI Daily Brief "Stop Prompting. Start Briefing." (Mar 7, 2026); YPO Technology Network AI Daily Brief #20 (Rokt 135 apps in 24 hours).

## Sources

- [McKinsey AI deployment research](https://www.mckinsey.com/capabilities/quantumblack/our-insights)
- [MIT NANDA — 95% pilot-stall figure](https://nanda.media.mit.edu/)
- YPO Technology Network AI Daily Brief "Stop Prompting. Start Briefing." (Mar 7, 2026)
- YPO Technology Network AI Daily Brief #20 (Rokt 135 apps in 24 hours)

---

Work with BuildClub: https://buildclub.com/amplify