Paywalls

Ask for payment in a context where the user can understand experienced value, added capability, total commitment, and the safe path back to work.

If .agents/marketing-context.md exists, read it first. Read paywall-workflow.md for trigger types, components, timing, upgrade states, and experiments.

Operating contract

1. Define user state, value already experienced, entitlement, blocked or expanded capability, plan choices, price, terms, and baseline.
2. Verify actual billing, trial, renewal, cancellation, refund, tax, and access behavior.
3. Choose a paywall type and timing that matches user intent.
4. Specify complete screen copy, plan comparison, billing states, failures, and return path.
5. Protect trust, accessibility, refunds, support load, retained value, and long-term conversion.

Do not degrade already-promised value, hide total cost, preselect an unwanted commitment, or manufacture urgency.