Skip to main content

Rapid Prototyping

Customer Module — Step 4

You've done the research. You've talked to customers. You know who you're building for and why they need it. Now you define exactly what to build — and test it before you pour concrete.

This step takes 1 to 3 days. It can save you 1 to 3 years.

Why This Step Exists​

The core principle​

AI makes building fast. That's the trap.

When building is cheap, people skip straight to construction. They generate a product, put it in market, scramble to find customers, spend money on marketing they don't understand yet, guess at pricing, and try to sustain momentum long enough to learn what they could have discovered in a single conversation.

That is not speed. That is expensive education.

A prototype is not a product. It is a question with a shape. The goal is to find out whether your idea is right before you commit the time, money, and reputation required to build the real thing.

The blueprint principle​

Moving a line on a blueprint costs nothing. Moving a wall on the 40th floor costs everything. The same rule applies here.

A bad idea caught in a conversation? Free. A bad idea caught after you've built the product? That's your savings, your reputation, and six months of your life.

Build first vs. Define first​

Build First PathDefine First Path
You prototype. You discover your customer by accident. You learn what they actually needed by watching them struggle with what you built. You rebuild. You remarket. You reprice. Most of that rework was avoidable.You write down what you're building, for whom, and why — before you build it. You pressure-test the idea on paper. You share it with a real customer. You find the flaws before they are load-bearing. Then you build once, with confidence.

"AI doesn't make a bad idea good. It just lets you lose money faster."

What Rapid Prototyping Actually Is​

This is not wireframing. This is not Figma. This is not a clickable mockup.

At this stage, your prototype is a document. Specifically: a press release that does not exist yet, written as if your product has already launched and customers already love it.

This is the Amazon method. They call it Working Backwards. You write the announcement before you write the code. You answer every hard question before you commit resources. If you cannot write a press release that makes people care, you are not ready to build.

What This Step Produces — In Sequence​

Three outputs, each building on the last. All three are required.

1. The Five Customer Questions​

  • Who is the customer?
  • What is the customer problem or opportunity?
  • What is the most important customer benefit?
  • How do you know what customers need or want?
  • What does the customer experience look like?

2. The Positioning Statement​

One sentence. Fill in the template:

[Product name] is a [product or service] that [core value proposition] for [target customer]. Unlike [key competitors], [your product name] [offers unique and differentiated value].

If this sentence requires more than one read to understand, simplify it.

3. The Press Release​

  • One page. Written as if your product has already launched.
  • Written for your customer, not for your team.
  • If you cannot write a press release that makes people care, do not build the product.

The Blueprint Principle — Why Sequence Saves You​

Each step compounds. Skip one, and the next one collapses.

  1. Five customer questions — Compounding contribution: clarity of purpose. You know exactly who you are building for and what problem you are solving. You are not guessing. You are not hoping. You have evidence.

  2. Positioning statement — Compounding contribution: testable clarity. You can say in one sentence what your product does and for whom. If you cannot, you are not ready to write a press release.

  3. Press release — Compounding contribution: forced honesty. Writing a press release forces you to confront every assumption you have been avoiding. A press release that does not compel the reader is a product that will not compel the customer.

  4. Prioritized epics — Compounding contribution: a build plan grounded in customer value. You now know what to build, in what order, for what reason. The most important capability to the customer goes first. Not the most technically interesting. Not the easiest to build.

AI in Rapid Prototyping​

  • What AI changes: the time it takes to go from raw notes to a structured press release. What used to take days now takes hours.
  • What AI does not change: whether your idea is good. A compelling press release built on a bad insight is still a bad idea. AI will make it sound credible. Your customer will tell you the truth.
  • The iteration rule: read every AI output aloud before accepting it. Where you stumble is where your thinking is unclear. Iterate until you can read the whole document without hesitation.
  • Data security: never paste proprietary company data or confidential customer information into a public AI tool without understanding where that data goes.

The AI Prompt Sequence​

Run these in order, in the same conversation. Attach your research notes and customer interview transcripts before entering Prompt 1. Do not start a new conversation between prompts.

Prompt 1 — Customer Definition​

Please read my attached notes in excruciating detail.

Then, based on what you read, will you please answer these questions:

1. Who is the customer?
2. What is the customer problem or opportunity?
3. What is the most important customer benefit?
4. How do you know what customers need or want?
5. What does the customer experience look like?

Prompt 2 — Positioning Statement​

The product is called "[Your Product Name]". Will you now please fill out this template:

[Product name] is a [product or service] that [core value proposition] for [target customer]. Unlike [key competitors], [your product name] [offers unique and differentiated value].

Prompt 3 — Press Release​

Great. Based on this entire thread, would you please create a compelling and comprehensive document that answers these questions:

Headline: Short, compelling description. Write this last.

One-sentence summary: What you're launching and the single most important benefit the customer will receive. This is your elevator pitch. Keep it simple.

Date: A future launch date. This signals it has not launched yet and sets expectation.

Opening paragraph: Assume the reader will not finish the page. Make it count. Do not bury the lead.

Customer first: The first sentence of the body states precisely who the customer is and the benefit you will provide.

Describe what you're launching: Use words your customer will understand. Before naming your product, explain what it is.

The problem: Customer-focused. Factual, but compelling. Do not amplify. Avoid exaggeration.

The solution: Clearly explain your vision for how to solve the customer's problem or make the most of the opportunity.

Leader quote: A quote from [your name], founder and CEO. The quote should capture the value provided to the customer.

Customer experience: How customers will discover, use, and benefit from what you built. The goal is to make the reader want to try it.

Prompt 4 — Epics​

Great. Now, would you please document the epics required for this platform?

Prompt 5 — Review​

Please review this list of epics and ensure it's comprehensive.

Prompt 6 — Prioritize​

Now combine all the epics into one list prioritized by importance to the customer.

Before You Move to the Next Step​

Copy the outputs from Prompts 1, 2, 3, and 6 into a single document.

Read it aloud to yourself. Not silently. Aloud.

Take notes on what sounds right and what does not. Where you stumble reading is where your thinking is unclear. Iterate with AI until you can read the whole document without hesitation.

Then share it with one customer. Not for validation. For reaction. Watch their face. Listen to their questions. The questions they ask are the assumptions you have not tested yet.

Only then are you ready to build.

Output Checklist​

  • A positioning statement your customer can understand in one read
  • A one-page press release you could show an investor today
  • A prioritized list of epics ordered by importance to the customer
  • A clear answer to: what is the one thing we are testing?
  • Confidence that what you are about to build is worth building

Synthesized from the Working Backwards framework, West's Favorite Product Prompt Pattern, the PR/FAQ module, and the customer research and persona development framework. Created by West Stringfellow.