product-conversion-readiness

# Product Conversion Readiness ## Cardinal Rule **The product works. The data is correct. Users don't pay because they don't understand the value, don't trust the source, or can't act on the data.** Every pattern in this skill addresses one of these three gaps: comprehension, trust, or actionability. ## The {{PROJECT_NAME}} Conversion Gap QA audits with user personas confirm a recurring pattern: | Persona | Verdict | Blocker | |---------|---------|---------| | Analyst | Would pay, with conditions | Needs legal entity, source references, citable export | | Developer | Won't pay yet | Needs API keys, 30-day uptime, quickstart | | Power User | Won't pay pure | Needs push alerts (messaging channel) | | Beginner | Won't pay yet | Needs onboarding + glossary in local language | | Mobile/Casual | Won't pay | Needs readable main page + fast widget | | Ops Lead (advanced) | Won't pay for execution | Needs row-level detail inline | | Developer (API) | Close to paying | Needs API keys + 30-day history | | Ops Lead (basic) | Won't pay yet | Needs configurable alerts + drill-down | **Pattern**: Zero personas said the data was wrong. Every blocker is either comprehension (onboarding, tooltips), trust (legal entity, uptime, About), or actionability (alerts, export, API). ## 1. Onboarding Flow ### Progressive Disclosure, Not Wall of Text New users see a 3-step guided tour, not a blank dashboard. ```typescript // example: components/shared/OnboardingWizard.tsx interface OnboardingSt...