The method behind the Build Spec

21 steps. 21 artifacts. One build-ready spec.

21 Steps is the artifact-driven methodology behind RapidIteration. AI helps research, draft, and stress-test. Humans make the decisions. The output is a master build spec that agents and teams can actually execute.

Why it exists

The thinking layer between idea and code editor.

When AI makes building cheap, the cost of building the wrong thing rises. 21 Steps forces clarity, validation, scoping, architecture, and launch thinking before serious build work starts.

01

Artifact-driven

Every step produces a real deliverable, not a vague checkbox.

02

Sequential, not rigid

Steps build on each other, but teams can revisit earlier decisions as new evidence arrives.

03

AI assists, humans decide

AI handles drafting and stress-testing. Strategy, taste, customer judgment, and quality calls remain human.

Phase 1

Clarity

Go from fuzzy idea to sharp, focused opportunity.

01

Idea Sharpening

What is the real opportunity here?

Artifact: Idea Brief + Lean Canvas

02

Market Landscaping

Who else is in this space, and what is missing?

Artifact: Market Landscape Map

03

Customer Discovery

Who specifically has this problem?

Artifact: Customer Discovery Report

04

Beachhead Selection

Which one segment comes first?

Artifact: Beachhead Decision Document

Phase 2

Validation

Prove real demand exists before designing anything.

05

Persona Building

Who is the one person this product is for first?

Artifact: Persona Document

06

Problem Validation

Is this problem real, urgent, and worth paying to solve?

Artifact: Problem Validation Report

07

Demand Testing

Will people commit time, money, or attention?

Artifact: Demand Validation Report

08

Value Proposition

What is the quantified value and unfair advantage?

Artifact: Value Proposition Canvas

09

Positioning

How do you own a space in the customer mind?

Artifact: Positioning Strategy

Phase 3

Design

Design the product, business model, pricing, and user journey on paper.

10

Solution Design

What exactly are you building?

Artifact: Solution Design Document

11

Business Model

How does this create, deliver, and capture value?

Artifact: Business Model Canvas

12

Pricing Strategy

What price fits the value, and why?

Artifact: Pricing Strategy Document

13

MVP Scoping

What is the smallest product that delivers the core value?

Artifact: MVP Scope Document

14

User Experience Mapping

What does the complete user journey look like?

Artifact: UX Blueprint

Phase 4

Preparation

Prepare the architecture, brand, master build spec, and launch plan.

15

Technical Architecture

What stack, system design, integrations, and deployment path make sense?

Artifact: Technical Architecture Document

16

Brand and Identity

What does this product look, sound, and feel like?

Artifact: Brand Kit

17

Build Spec

What exactly does the AI coding agent or build team need to build?

Artifact: Master Build Spec

18

Launch Strategy

How will the right users find, try, and adopt this?

Artifact: Launch Playbook

Phase 5

Build and Launch

Build, ship, measure, and feed real behavior back into the next iteration.

19

Build Sprint

How do you turn the spec into a working product?

Artifact: Working Product + Build Log

20

Launch Execution

How do you get your first real users?

Artifact: Launch Report

21

Feedback and Iteration

What did users actually do, and what gets built next?

Artifact: Post-Launch Assessment

Moment of truth

Step 17 is the Build Spec.

The Master Build Spec turns the method into an executable plan. It becomes the input to agents, agencies, internal teams, and Production Gate reviews.

Request a Build Spec