Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Optimizes lead capture, contact, demo request, and checkout forms (non-signup) to maximize completion rates.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
SKILL.md
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," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.4metadata:5version: 1.1.06---78# Form CRO910You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.1112## Initial Assessment1314**Check for product marketing context first:**15If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.1617Before providing recommendations, identify:18191. **Form Type**20- Lead capture (gated content, newsletter)21- Contact form22- Demo/sales request23- Application form24- Survey/feedback25- Checkout form26- Quote request27282. **Current State**29- How many fields?30- What's the current completion rate?31- Mobile vs. desktop split?32- Where do users abandon?33343. **Business Context**35- What happens with form submissions?36- Which fields are actually used in follow-up?37- Are there compliance/legal requirements?3839---4041## Core Principles4243### 1. Every Field Has a Cost44Each field reduces completion rate. Rule of thumb:45- 3 fields: Baseline46- 4-6 fields: 10-25% reduction47- 7+ fields: 25-50%+ reduction4849For each field, ask:50- Is this absolutely necessary before we can help them?51- Can we get this information another way?52- Can we ask this later?5354### 2. Value Must Exceed Effort55- Clear value proposition above form56- Make what they get obvious57- Reduce perceived effort (field count, labels)5859### 3. Reduce Cognitive Load60- One question per field61- Clear, conversational labels62- Logical grouping and order63- Smart defaults where possible6465---6667## Field-by-Field Optimization6869### Email Field70- Single field, no confirmation71- Inline validation72- Typo detection (did you mean gmail.com?)73- Proper mobile keyboard7475### Name Fields76- Single "Name" vs. First/Last — test this77- Single field reduces friction78- Split needed only if personalization requires it7980### Phone Number81- Make optional if possible82- If required, explain why83- Auto-format as they type84- Country code handling8586### Company/Organization87- Auto-suggest for faster entry88- Enrichment after submission (Clearbit, etc.)89- Consider inferring from email domain9091### Job Title/Role92- Dropdown if categories matter93- Free text if wide variation94- Consider making optional9596### Message/Comments (Free Text)97- Make optional98- Reasonable character guidance99- Expand on focus100101### Dropdown Selects102- "Select one..." placeholder103- Searchable if many options104- Consider radio buttons if < 5 options105- "Other" option with text field106107### Checkboxes (Multi-select)108- Clear, parallel labels109- Reasonable number of options110- Consider "Select all that apply" instruction111112---113114## Form Layout Optimization115116### Field Order1171. Start with easiest fields (name, email)1182. Build commitment before asking more1193. Sensitive fields last (phone, company size)1204. Logical grouping if many fields121122### Labels and Placeholders123- Labels: Keep visible (not just placeholder) — placeholders disappear when typing, leaving users unsure what they're filling in124- Placeholders: Examples, not labels125- Help text: Only when genuinely helpful126127**Good:**128```129130[[email protected]]131```132133**Bad:**134```135[Enter your email address] ← Disappears on focus136```137138### Visual Design139- Sufficient spacing between fields140- Clear visual hierarchy141- CTA button stands out142- Mobile-friendly tap targets (44px+)143144### Single Column vs. Multi-Column145- Single column: Higher completion, mobile-friendly146- Multi-column: Only for short related fields (First/Last name)147- When in doubt, single column148149---150151## Multi-Step Forms152153### When to Use Multi-Step154- More than 5-6 fields155- Logically distinct sections156- Conditional paths based on answers157- Complex forms (applications, quotes)158159### Multi-Step Best Practices160- Progress indicator (step X of Y)161- Start with easy, end with sensitive162- One topic per step163- Allow back navigation164- Save progress (don't lose data on refresh)165- Clear indication of required vs. optional166167### Progressive Commitment Pattern1681. Low-friction start (just email)1692. More detail (name, company)1703. Qualifying questions1714. Contact preferences172173---174175## Error Handling176177### Inline Validation178- Validate as they move to next field179- Don't validate too aggressively while typing180- Clear visual indicators (green check, red border)181182### Error Messages183- Specific to the problem184- Suggest how to fix185- Positioned near the field186- Don't clear their input187188**Good:** "Please enter a valid email address (e.g., [email protected])"189**Bad:** "Invalid input"190191### On Submit192- Focus on first error field193- Summarize errors if multiple194- Preserve all entered data195- Don't clear form on error196197---198199## Submit Button Optimization200201### Button Copy202Weak: "Submit" | "Send"203Strong: "[Action] + [What they get]"204205Examples:206- "Get My Free Quote"207- "Download the Guide"208- "Request Demo"209- "Send Message"210- "Start Free Trial"211212### Button Placement213- Immediately after last field214- Left-aligned with fields215- Sufficient size and contrast216- Mobile: Sticky or clearly visible217218### Post-Submit States219- Loading state (disable button, show spinner)220- Success confirmation (clear next steps)221- Error handling (clear message, focus on issue)222223---224225## Trust and Friction Reduction226227### Near the Form228- Privacy statement: "We'll never share your info"229- Security badges if collecting sensitive data230- Testimonial or social proof231- Expected response time232233### Reducing Perceived Effort234- "Takes 30 seconds"235- Field count indicator236- Remove visual clutter237- Generous white space238239### Addressing Objections240- "No spam, unsubscribe anytime"241- "We won't share your number"242- "No credit card required"243244---245246## Form Types: Specific Guidance247248### Lead Capture (Gated Content)249- Minimum viable fields (often just email)250- Clear value proposition for what they get251- Consider asking enrichment questions post-download252- Test email-only vs. email + name253254### Contact Form255- Essential: Email/Name + Message256- Phone optional257- Set response time expectations258- Offer alternatives (chat, phone)259260### Demo Request261- Name, Email, Company required262- Phone: Optional with "preferred contact" choice263- Use case/goal question helps personalize264- Calendar embed can increase show rate265266### Quote/Estimate Request267- Multi-step often works well268- Start with easy questions269- Technical details later270- Save progress for complex forms271272### Survey Forms273- Progress bar essential274- One question per screen for engagement275- Skip logic for relevance276- Consider incentive for completion277278---279280## Mobile Optimization281282- Larger touch targets (44px minimum height)283- Appropriate keyboard types (email, tel, number)284- Autofill support285- Single column only286- Sticky submit button287- Minimal typing (dropdowns, buttons)288289---290291## Measurement292293### Key Metrics294- **Form start rate**: Page views → Started form295- **Completion rate**: Started → Submitted296- **Field drop-off**: Which fields lose people297- **Error rate**: By field298- **Time to complete**: Total and by field299- **Mobile vs. desktop**: Completion by device300301### What to Track302- Form views303- First field focus304- Each field completion305- Errors by field306- Submit attempts307- Successful submissions308309---310311## Output Format312313### Form Audit314For each issue:315- **Issue**: What's wrong316- **Impact**: Estimated effect on conversions317- **Fix**: Specific recommendation318- **Priority**: High/Medium/Low319320### Recommended Form Design321- **Required fields**: Justified list322- **Optional fields**: With rationale323- **Field order**: Recommended sequence324- **Copy**: Labels, placeholders, button325- **Error messages**: For each field326- **Layout**: Visual guidance327328### Test Hypotheses329Ideas to A/B test with expected outcomes330331---332333## Experiment Ideas334335### Form Structure Experiments336337**Layout & Flow**338- Single-step form vs. multi-step with progress bar339- 1-column vs. 2-column field layout340- Form embedded on page vs. separate page341- Vertical vs. horizontal field alignment342- Form above fold vs. after content343344**Field Optimization**345- Reduce to minimum viable fields346- Add or remove phone number field347- Add or remove company/organization field348- Test required vs. optional field balance349- Use field enrichment to auto-fill known data350- Hide fields for returning/known visitors351352**Smart Forms**353- Add real-time validation for emails and phone numbers354- Progressive profiling (ask more over time)355- Conditional fields based on earlier answers356- Auto-suggest for company names357358---359360### Copy & Design Experiments361362**Labels & Microcopy**363- Test field label clarity and length364- Placeholder text optimization365- Help text: show vs. hide vs. on-hover366- Error message tone (friendly vs. direct)367368**CTAs & Buttons**369- Button text variations ("Submit" vs. "Get My Quote" vs. specific action)370- Button color and size testing371- Button placement relative to fields372373**Trust Elements**374- Add privacy assurance near form375- Show trust badges next to submit376- Add testimonial near form377- Display expected response time378379---380381### Form Type-Specific Experiments382383**Demo Request Forms**384- Test with/without phone number requirement385- Add "preferred contact method" choice386- Include "What's your biggest challenge?" question387- Test calendar embed vs. form submission388389**Lead Capture Forms**390- Email-only vs. email + name391- Test value proposition messaging above form392- Gated vs. ungated content strategies393- Post-submission enrichment questions394395**Contact Forms**396- Add department/topic routing dropdown397- Test with/without message field requirement398- Show alternative contact methods (chat, phone)399- Expected response time messaging400401---402403### Mobile & UX Experiments404405- Larger touch targets for mobile406- Test appropriate keyboard types by field407- Sticky submit button on mobile408- Auto-focus first field on page load409- Test form container styling (card vs. minimal)410411---412413## Task-Specific Questions4144151. What's your current form completion rate?4162. Do you have field-level analytics?4173. What happens with the data after submission?4184. Which fields are actually used in follow-up?4195. Are there compliance/legal requirements?4206. What's the mobile vs. desktop split?421422---423424## Related Skills425426- **signup-flow-cro**: For account creation forms427- **popup-cro**: For forms inside popups/modals428- **page-cro**: For the page containing the form429- **ab-test-setup**: For testing form changes430