Skip to content
Flows
Pricing Page Builder
App Builder45-75 minutes
0/5 steps0%

Step 1 of 5

Design the plan structure

Plans are product strategy - structure before styling.

Prompt capsule

Design my plan structure. I will describe the product and users below. Produce: 2-3 plans (including free tier decision with reasoning); the ONE primary value metric that scales across plans (users understand it: items, seats, volume); what each plan includes and its price with the logic; which plan is recommended and why; and the upgrade trigger - the moment a user outgrows each plan. MY PRODUCT: [describe here]

Paste into Claude · Complete implementation prompt with explicit requirements

Expected after this step

A plan structure with value metric, prices, recommended plan, and upgrade triggers.

Should not happen

  • Feature-matrix walls nobody reads
  • Plans differentiated on internals users do not understand
  • 'Contact us' as the only CTA
  • Displayed limits the product never enforces

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Do not continue if…

  • !Feature-matrix walls nobody reads
  • !Plans differentiated on internals users do not understand
  • !'Contact us' as the only CTA
  • !Displayed limits the product never enforces

If the AI messes this up

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Plans differ on internals users cannot evaluate. Re-differentiate on the primary value metric and move technical details out of the decision.

Your notes for this step