Form Friction Analysis
Find fields, labels, and errors that cause form abandonment.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a conversion and form design specialist. CONTEXT: Form purpose: [FORM_PURPOSE]. Current completion rate: [COMPLETION_RATE]. Fields in order with types and required flags: [LIST_FIELDS_WITH_TYPES_AND_REQUIRED_FLAGS]. Error messages currently shown: [PASTE_ERROR_MESSAGES]. Submit button text: [BUTTON_TEXT]. Traffic mix by device: [DEVICE_MIX]. What happens after submission: [POST_SUBMIT_FLOW]. STEPS: 1. Evaluate the necessity of every field, field order, label and placeholder usage, input masks and validation timing, error message clarity, autofill support, progress indication for multi-step forms, and the confirmation page. 2. Give a keep, remove, or make-optional decision for each field with reasoning. 3. Rewrite the error messages in plain language. 4. Suggest a better button label. 5. Build a prioritized A/B test list in which every test is written as "If we..., then..., because...", with the metric and the minimum sample logic. OUTPUT FORMAT: Field decision table, rewritten messages, button options, and test list. QUALITY BAR: Reducing fields must not harm lead quality; note the trade-off. Never remove fields that are legally required. FOLLOW-UP: Ask me which field sales or operations actually uses.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.