ExecuteWorking Backwards

Working Backwards

Amazon-style PRFAQ adapted for AI-native venture building. Write the launch before you build it.

Why backwards

If you cannot write a credible press release and FAQ for the launch, the product is not ready to build. The PRFAQ forces clarity on customer, problem, narrative and KPI before a single line of code.

PRFAQ template

Customer problem

Who is hurting, how often, and what do they do today?

Why now

What changed in the market, technology or ecosystem to make this viable?

Launch narrative

A one-page press release written as if the product is live today.

Customer FAQ

Top 10 questions a real customer would ask, answered honestly.

Internal FAQ

Top 10 questions leadership will ask: unit economics, risks, dependencies.

KPI framework

The 1–3 metrics that prove this thing is working at Beta.

Kill criteria

The exact conditions that trigger a kill or pivot.

Length

PRFAQ is 6 pages max. If you need more, you do not understand the customer well enough yet.

Kill criteria

Every PRFAQ ends with the conditions under which we will kill the product. Written before launch, revisited at every stage gate. This is non-negotiable.

Example: If weekly active accounts < 100 by week 12 of Beta, with no clear path to 500 by week 20, kill.