form-strategy

# Form Strategy Forms are where intent becomes action. Design them well or lose conversions, frustrate users, and drown in spam. Stack-agnostic. --- ## When to use - Designing or redesigning a form - Conversion is dropping on a key form - Spam volume is overwhelming the inbox or database - Auditing forms across a site - Planning validation logic - Choosing form tooling (form service, custom build, no-code) - Integrating forms with CRM, email, or other downstream systems - Multi-step form decisions ## When NOT to use - Generic conversion optimization (use `cro-optimization`) - The copy on the form (use `landing-page-copy`) - Backend handling beyond form-specific concerns (use `frontend-component-build`, `code-review-web`) - General accessibility (use `accessibility-audit`) --- ## Required inputs - The form's purpose (what action, what outcome) - Current form (URL, screenshot, or fields) - Current performance (completion rate, spam rate, conversion to next step) - Downstream system (where submissions go: CRM, email, database, support tool) - Business context (volume, urgency of leads, cost of false vs missed signups) --- ## The framework: 5 dimensions Every form decision falls into one of these dimensions. ### Dimension 1: Field strategy The biggest lever. Every additional field reduces conversion. **Questions to ask for each field:** - Is this required to deliver value to the user? - Is this required to deliver value to the business? - Can it be inferred from an...