PROTOCOL — PROTO-02

Pressure-test the idea before you build the whole thing.

Prototype-led market validation gives the team a sharper answer than a brainstorm: what buyer cares, what promise lands, and what should happen next.

Pressure-Test the Market Build a Prototype

PROTO-02-SPEC

Entry 01 Spec sheet Market Validation

The spec, on one sheet.

A short scoping pass, then something testable. Here is who the protocol is for, what comes out, and how the run ends. Every run ends the same way the bench does: with a verdict.

Protocol	PROTO-02 — Market Validation
Best for	Founders testing a SaaS wedge · Agencies productizing client insights · SaaS teams validating roadmap bets
Output	Landing or concept page · ICP messaging · Outreach scripts · Feedback system · Market signal report
Decision	Kill it, refine it, pilot it, or productize it — logged either way

the artifact is the deliverable. the deck is not.

PROTO-02-02

Entry 02 What gets validated 4 items

What gets validated

The sprint looks for buyer pull, workflow pain, pricing signal, and whether the concept deserves more product investment.

Audience map Customer interview notes Pricing signal test Go/no-go recommendation

PROTO-02-XREF

Entry 03 Cross-reference — other protocols 6 on file

Pick the protocol that matches the decision you need.

LAB-HIRE App R&D Studio The lab, for hire RUN → PROTO-IDX Services Every protocol, indexed RUN → PROTO-01 Prototype Sprint Idea → working app surface RUN → PROTO-04 Agency R&D Client insight → productized tool RUN → PROTO-05 SaaS Prototypes Roadmap bet → tested proof RUN → PROTO-03 Operator Tools Broken workflow → useful software RUN →

Pressure-Test the Market