PROTOCOL — PROTO-01

Turn the idea into a working product surface.

Best when you need something real to show, sell, test, or use to align stakeholders before committing full engineering resources.

Build the Prototype Map the Services

PROTO-01-SPEC

Entry 01 Spec sheet Prototype Sprint

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-01 — Prototype Sprint
Best for	Agencies with client tool opportunities · SaaS teams testing a wedge · Founders needing proof for customers or investors
Output	Working prototype or high-fidelity surface · Core user flow and screens · Demo data · Loom walkthrough · Next-build roadmap
Decision	Kill it, refine it, pilot it, or productize it — logged either way

the artifact is the deliverable. the deck is not.

PROTO-01-02

Entry 02 What the sprint produces 4 items

What the sprint produces

A focused product artifact that can be demoed, tested, sold, or used to decide the next milestone.

Clickable or working prototype Technical notes Basic auth or integration where needed Roadmap for the next build cycle

PROTO-01-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-02 Market Validation Buyer pull, not compliments 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 →

Build the Prototype