Form CRO
You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.
Initial Assessment
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, identify:
Form Type
- Lead capture (gated content, newsletter)
- Contact form
- Demo/sales request
- Application form
- Survey/feedback
- Checkout form
- Quote request
Current State
- How many fields?
- What's the current completion rate?
- Mobile vs. desktop split?
- Where do users abandon?
Business Context
- What happens with form submissions?
- Which fields are actually used in follow-up?
- Are there compliance/legal requirements?
Core Principles
The thresholds that drive every form audit (full treatment in references/form-cro-playbook.md):
- Field count: every added field costs conversions. Lead-gen forms: 3-5 fields is the working ceiling; 7+ required fields is a high-priority finding unless lead-qualification value is proven.
- Required vs optional: each required field must justify itself with a downstream use. "Nice for sales" is not a justification — make it optional or cut it.
- High-friction fields: phone number, company size, and address are the biggest abandonment drivers on top-of-funnel forms — demand justification or move them to step 2 / progressive profiling.
- Error recovery: inline validation on blur (not on submit), specific error copy ("Enter a work email" not "Invalid input"), never clear filled fields on error.
- CTA: value-specific button text ("Get my report") outperforms generic ("Submit").
Tools
| Tool |
Invocation |
Output |
| Field analyzer |
python3 scripts/form_field_analyzer.py forms.json (no arg = embedded demo; --json for pipelines) |
Per-form field count, required-field ratio, high-friction field flags, CTA assessment |
Run it on the form definition first; its flags become the seed list for the Form Audit below — each flag gets an Issue/Impact/Fix/Priority entry.
Output Format
Form Audit
For each issue:
- Issue: What's wrong
- Impact: Estimated effect on conversions
- Fix: Specific recommendation
- Priority: High/Medium/Low
Recommended Form Design
- Required fields: Justified list
- Optional fields: With rationale
- Field order: Recommended sequence
- Copy: Labels, placeholders, button
- Error messages: For each field
- Layout: Visual guidance
Test Hypotheses
Ideas to A/B test with expected outcomes
Experiment Ideas
Form Structure Experiments
Layout & Flow
- Single-step form vs. multi-step with progress bar
- 1-column vs. 2-column field layout
- Form embedded on page vs. separate page
- Vertical vs. horizontal field alignment
- Form above fold vs. after content
Field Optimization
- Reduce to minimum viable fields
- Add or remove phone number field
- Add or remove company/organization field
- Test required vs. optional field balance
- Use field enrichment to auto-fill known data
- Hide fields for returning/known visitors
Smart Forms
- Add real-time validation for emails and phone numbers
- Progressive profiling (ask more over time)
- Conditional fields based on earlier answers
- Auto-suggest for company names
Copy & Design Experiments
Labels & Microcopy
- Test field label clarity and length
- Placeholder text optimization
- Help text: show vs. hide vs. on-hover
- Error message tone (friendly vs. direct)
CTAs & Buttons
- Button text variations ("Submit" vs. "Get My Quote" vs. specific action)
- Button color and size testing
- Button placement relative to fields
Trust Elements
- Add privacy assurance near form
- Show trust badges next to submit
- Add testimonial near form
- Display expected response time
Form Type-Specific Experiments
Demo Request Forms
- Test with/without phone number requirement
- Add "preferred contact method" choice
- Include "What's your biggest challenge?" question
- Test calendar embed vs. form submission
Lead Capture Forms
- Email-only vs. email + name
- Test value proposition messaging above form
- Gated vs. ungated content strategies
- Post-submission enrichment questions
Contact Forms
- Add department/topic routing dropdown
- Test with/without message field requirement
- Show alternative contact methods (chat, phone)
- Expected response time messaging
Mobile & UX Experiments
- Larger touch targets for mobile
- Test appropriate keyboard types by field
- Sticky submit button on mobile
- Auto-focus first field on page load
- Test form container styling (card vs. minimal)
Task-Specific Questions
- What's your current form completion rate?
- Do you have field-level analytics?
- What happens with the data after submission?
- Which fields are actually used in follow-up?
- Are there compliance/legal requirements?
- What's the mobile vs. desktop split?
Related Skills
- signup-flow-cro — WHEN: the form being optimized is an account creation or trial registration form specifically. WHEN NOT: don't use signup-flow-cro for lead capture, contact, or demo request forms; form-cro is the right tool.
- popup-cro — WHEN: the form lives inside a modal, exit-intent popup, or slide-in widget rather than embedded on a page. WHEN NOT: don't use popup-cro for standalone page-embedded forms.
- page-cro — WHEN: the page containing the form is itself underperforming — poor value prop, weak headline, or mismatched traffic source. Fix the page context before or alongside the form. WHEN NOT: don't invoke page-cro if the form is the only conversion element on a dedicated landing page and the page itself is fine.
- ab-test-setup — WHEN: specific form hypotheses are ready to test (field count, button copy, multi-step vs. single-step). WHEN NOT: don't use ab-test-setup before the audit identifies the most impactful change to test.
- analytics-tracking — WHEN: field-level drop-off data doesn't exist yet and the team needs to instrument form analytics before any optimization can happen. WHEN NOT: skip if analytics are already in place.
- marketing-context — WHEN: check
.claude/product-marketing-context.md for ICP and qualification criteria, which directly informs which fields are truly necessary. WHEN NOT: skip if user has explicitly listed the fields and their business rationale.
Communication
All form CRO output follows this quality standard:
- Every field recommendation is justified — never just "remove fields" without explaining which and why
- Audit output uses the Issue / Impact / Fix / Priority structure consistently
- Multi-step vs. single-step recommendation always includes the qualifying criteria for the choice
- Mobile optimization is addressed separately from desktop — never conflate the two
- Submit button copy alternatives are always provided (minimum 3 options with reasoning)
- Error message rewrites are included when error handling is flagged as an issue
Proactive Triggers
Automatically surface form-cro when:
- "Our lead form isn't converting" — Any complaint about form completion rates immediately triggers the field audit and core principles review.
- Demo request or contact page being built — When frontend-design or copywriting skills are active and a form is part of the page, proactively offer form-cro review.
- "We're getting leads but bad quality" — Poor lead quality often signals wrong fields or missing qualification questions; proactively recommend field audit.
- Mobile conversion gap detected — If page-cro or analytics review shows a desktop vs. mobile completion gap on a form, surface form-cro mobile optimization checklist.
- Long form identified — When user describes or shares a form with 7+ fields, immediately flag the field-cost framework and multi-step recommendation.
Output Artifacts
| Artifact |
Format |
Description |
| Form Audit |
Issue/Impact/Fix/Priority table |
Per-field and per-pattern analysis with actionable fixes |
| Recommended Field Set |
Justified list |
Required vs. optional fields with rationale for each |
| Field Order & Layout Spec |
Annotated outline |
Recommended sequence, grouping, column layout, and mobile considerations |
| Submit Button Copy Options |
3-option table |
Action-oriented button copy variants with reasoning |
| A/B Test Hypotheses |
Table |
Hypothesis × variant × success metric × priority for top 3-5 test ideas |
1---2name: form-cro3description: When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.4license: MIT5metadata:6 source: https://skillmd.com/skills/bestagentkits/form-cro7 version: 1.0.08 author: Alireza Rezvani9 category: marketing10 updated: 2026-03-0611---1213# Form CRO1415You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.1617## Initial Assessment1819**Check for product marketing context first:**20If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.2122Before providing recommendations, identify:23241. **Form Type**25 - Lead capture (gated content, newsletter)26 - Contact form27 - Demo/sales request28 - Application form29 - Survey/feedback30 - Checkout form31 - Quote request32332. **Current State**34 - How many fields?35 - What's the current completion rate?36 - Mobile vs. desktop split?37 - Where do users abandon?38393. **Business Context**40 - What happens with form submissions?41 - Which fields are actually used in follow-up?42 - Are there compliance/legal requirements?4344---4546## Core Principles4748The thresholds that drive every form audit (full treatment in references/form-cro-playbook.md):4950- **Field count**: every added field costs conversions. Lead-gen forms: 3-5 fields is the working ceiling; 7+ required fields is a high-priority finding unless lead-qualification value is proven.51- **Required vs optional**: each *required* field must justify itself with a downstream use. "Nice for sales" is not a justification — make it optional or cut it.52- **High-friction fields**: phone number, company size, and address are the biggest abandonment drivers on top-of-funnel forms — demand justification or move them to step 2 / progressive profiling.53- **Error recovery**: inline validation on blur (not on submit), specific error copy ("Enter a work email" not "Invalid input"), never clear filled fields on error.54- **CTA**: value-specific button text ("Get my report") outperforms generic ("Submit").5556## Tools5758| Tool | Invocation | Output |59|---|---|---|60| Field analyzer | `python3 scripts/form_field_analyzer.py forms.json` (no arg = embedded demo; `--json` for pipelines) | Per-form field count, required-field ratio, high-friction field flags, CTA assessment |6162Run it on the form definition first; its flags become the seed list for the Form Audit below — each flag gets an Issue/Impact/Fix/Priority entry.6364## Output Format6566### Form Audit67For each issue:68- **Issue**: What's wrong69- **Impact**: Estimated effect on conversions70- **Fix**: Specific recommendation71- **Priority**: High/Medium/Low7273### Recommended Form Design74- **Required fields**: Justified list75- **Optional fields**: With rationale76- **Field order**: Recommended sequence77- **Copy**: Labels, placeholders, button78- **Error messages**: For each field79- **Layout**: Visual guidance8081### Test Hypotheses82Ideas to A/B test with expected outcomes8384---8586## Experiment Ideas8788### Form Structure Experiments8990**Layout & Flow**91- Single-step form vs. multi-step with progress bar92- 1-column vs. 2-column field layout93- Form embedded on page vs. separate page94- Vertical vs. horizontal field alignment95- Form above fold vs. after content9697**Field Optimization**98- Reduce to minimum viable fields99- Add or remove phone number field100- Add or remove company/organization field101- Test required vs. optional field balance102- Use field enrichment to auto-fill known data103- Hide fields for returning/known visitors104105**Smart Forms**106- Add real-time validation for emails and phone numbers107- Progressive profiling (ask more over time)108- Conditional fields based on earlier answers109- Auto-suggest for company names110111---112113### Copy & Design Experiments114115**Labels & Microcopy**116- Test field label clarity and length117- Placeholder text optimization118- Help text: show vs. hide vs. on-hover119- Error message tone (friendly vs. direct)120121**CTAs & Buttons**122- Button text variations ("Submit" vs. "Get My Quote" vs. specific action)123- Button color and size testing124- Button placement relative to fields125126**Trust Elements**127- Add privacy assurance near form128- Show trust badges next to submit129- Add testimonial near form130- Display expected response time131132---133134### Form Type-Specific Experiments135136**Demo Request Forms**137- Test with/without phone number requirement138- Add "preferred contact method" choice139- Include "What's your biggest challenge?" question140- Test calendar embed vs. form submission141142**Lead Capture Forms**143- Email-only vs. email + name144- Test value proposition messaging above form145- Gated vs. ungated content strategies146- Post-submission enrichment questions147148**Contact Forms**149- Add department/topic routing dropdown150- Test with/without message field requirement151- Show alternative contact methods (chat, phone)152- Expected response time messaging153154---155156### Mobile & UX Experiments157158- Larger touch targets for mobile159- Test appropriate keyboard types by field160- Sticky submit button on mobile161- Auto-focus first field on page load162- Test form container styling (card vs. minimal)163164---165166## Task-Specific Questions1671681. What's your current form completion rate?1692. Do you have field-level analytics?1703. What happens with the data after submission?1714. Which fields are actually used in follow-up?1725. Are there compliance/legal requirements?1736. What's the mobile vs. desktop split?174175---176177## Related Skills178179- **signup-flow-cro** — WHEN: the form being optimized is an account creation or trial registration form specifically. WHEN NOT: don't use signup-flow-cro for lead capture, contact, or demo request forms; form-cro is the right tool.180- **popup-cro** — WHEN: the form lives inside a modal, exit-intent popup, or slide-in widget rather than embedded on a page. WHEN NOT: don't use popup-cro for standalone page-embedded forms.181- **page-cro** — WHEN: the page containing the form is itself underperforming — poor value prop, weak headline, or mismatched traffic source. Fix the page context before or alongside the form. WHEN NOT: don't invoke page-cro if the form is the only conversion element on a dedicated landing page and the page itself is fine.182- **ab-test-setup** — WHEN: specific form hypotheses are ready to test (field count, button copy, multi-step vs. single-step). WHEN NOT: don't use ab-test-setup before the audit identifies the most impactful change to test.183- **analytics-tracking** — WHEN: field-level drop-off data doesn't exist yet and the team needs to instrument form analytics before any optimization can happen. WHEN NOT: skip if analytics are already in place.184- **marketing-context** — WHEN: check `.claude/product-marketing-context.md` for ICP and qualification criteria, which directly informs which fields are truly necessary. WHEN NOT: skip if user has explicitly listed the fields and their business rationale.185186---187188## Communication189190All form CRO output follows this quality standard:191- Every field recommendation is justified — never just "remove fields" without explaining which and why192- Audit output uses the **Issue / Impact / Fix / Priority** structure consistently193- Multi-step vs. single-step recommendation always includes the qualifying criteria for the choice194- Mobile optimization is addressed separately from desktop — never conflate the two195- Submit button copy alternatives are always provided (minimum 3 options with reasoning)196- Error message rewrites are included when error handling is flagged as an issue197198---199200## Proactive Triggers201202Automatically surface form-cro when:2032041. **"Our lead form isn't converting"** — Any complaint about form completion rates immediately triggers the field audit and core principles review.2052. **Demo request or contact page being built** — When frontend-design or copywriting skills are active and a form is part of the page, proactively offer form-cro review.2063. **"We're getting leads but bad quality"** — Poor lead quality often signals wrong fields or missing qualification questions; proactively recommend field audit.2074. **Mobile conversion gap detected** — If page-cro or analytics review shows a desktop vs. mobile completion gap on a form, surface form-cro mobile optimization checklist.2085. **Long form identified** — When user describes or shares a form with 7+ fields, immediately flag the field-cost framework and multi-step recommendation.209210---211212## Output Artifacts213214| Artifact | Format | Description |215|----------|--------|-------------|216| Form Audit | Issue/Impact/Fix/Priority table | Per-field and per-pattern analysis with actionable fixes |217| Recommended Field Set | Justified list | Required vs. optional fields with rationale for each |218| Field Order & Layout Spec | Annotated outline | Recommended sequence, grouping, column layout, and mobile considerations |219| Submit Button Copy Options | 3-option table | Action-oriented button copy variants with reasoning |220| A/B Test Hypotheses | Table | Hypothesis × variant × success metric × priority for top 3-5 test ideas |