AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

form-cro

Use when a lead, contact, demo or checkout form is underperforming or being designed, before changing fields. Scores field friction with form_field_analyzer.py. Signup forms: signup-flow-cro.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--form-cro at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 2

references/form-cro-playbook.md

form-cro reference

Core Principles

1. Every Field Has a Cost

Each field reduces completion rate. Rule of thumb:

  • 3 fields: Baseline
  • 4-6 fields: 10-25% reduction
  • 7+ fields: 25-50%+ reduction

For each field, ask:

  • Is this absolutely necessary before we can help them?
  • Can we get this information another way?
  • Can we ask this later?

2. Value Must Exceed Effort

  • Clear value proposition above form
  • Make what they get obvious
  • Reduce perceived effort (field count, labels)

3. Reduce Cognitive Load

  • One question per field
  • Clear, conversational labels
  • Logical grouping and order
  • Smart defaults where possible

Field-by-Field Optimization

Email Field

  • Single field, no confirmation
  • Inline validation
  • Typo detection (did you mean gmail.com?)
  • Proper mobile keyboard

Name Fields

  • Single "Name" vs. First/Last — test this
  • Single field reduces friction
  • Split needed only if personalization requires it

Phone Number

  • Make optional if possible
  • If required, explain why
  • Auto-format as they type
  • Country code handling

Company/Organization

  • Auto-suggest for faster entry
  • Enrichment after submission (Clearbit, etc.)
  • Consider inferring from email domain

Job Title/Role

  • Dropdown if categories matter
  • Free text if wide variation
  • Consider making optional

Message/Comments (Free Text)

  • Make optional
  • Reasonable character guidance
  • Expand on focus

Dropdown Selects

  • "Select one..." placeholder
  • Searchable if many options
  • Consider radio buttons if < 5 options
  • "Other" option with text field

Checkboxes (Multi-select)

  • Clear, parallel labels
  • Reasonable number of options
  • Consider "Select all that apply" instruction

Form Layout Optimization

Field Order

  1. Start with easiest fields (name, email)
  2. Build commitment before asking more
  3. Sensitive fields last (phone, company size)
  4. Logical grouping if many fields

Labels and Placeholders

  • Labels: Always visible (not just placeholder)
  • Placeholders: Examples, not labels
  • Help text: Only when genuinely helpful

Good:

Email
[[email protected]]

Bad:

[Enter your email address]  ← Disappears on focus

Visual Design

  • Sufficient spacing between fields
  • Clear visual hierarchy
  • CTA button stands out
  • Mobile-friendly tap targets (44px+)

Single Column vs. Multi-Column

  • Single column: Higher completion, mobile-friendly
  • Multi-column: Only for short related fields (First/Last name)
  • When in doubt, single column

Multi-Step Forms

When to Use Multi-Step

  • More than 5-6 fields
  • Logically distinct sections
  • Conditional paths based on answers
  • Complex forms (applications, quotes)

Multi-Step Best Practices

  • Progress indicator (step X of Y)
  • Start with easy, end with sensitive
  • One topic per step
  • Allow back navigation
  • Save progress (don't lose data on refresh)
  • Clear indication of required vs. optional

Progressive Commitment Pattern

  1. Low-friction start (just email)
  2. More detail (name, company)
  3. Qualifying questions
  4. Contact preferences

Error Handling

Inline Validation

  • Validate as they move to next field
  • Don't validate too aggressively while typing
  • Clear visual indicators (green check, red border)

Error Messages

  • Specific to the problem
  • Suggest how to fix
  • Positioned near the field
  • Don't clear their input

Good: "Please enter a valid email address (e.g., [email protected])" Bad: "Invalid input"

On Submit

  • Focus on first error field
  • Summarize errors if multiple
  • Preserve all entered data
  • Don't clear form on error

Submit Button Optimization

Button Copy

Weak: "Submit" | "Send" Strong: "[Action] + [What they get]"

Examples:

  • "Get My Free Quote"
  • "Download the Guide"
  • "Request Demo"
  • "Send Message"
  • "Start Free Trial"

Button Placement

  • Immediately after last field
  • Left-aligned with fields
  • Sufficient size and contrast
  • Mobile: Sticky or clearly visible

Post-Submit States

  • Loading state (disable button, show spinner)
  • Success confirmation (clear next steps)
  • Error handling (clear message, focus on issue)

Trust and Friction Reduction

Near the Form

  • Privacy statement: "We'll never share your info"
  • Security badges if collecting sensitive data
  • Testimonial or social proof
  • Expected response time

Reducing Perceived Effort

  • "Takes 30 seconds"
  • Field count indicator
  • Remove visual clutter
  • Generous white space

Addressing Objections

  • "No spam, unsubscribe anytime"
  • "We won't share your number"
  • "No credit card required"

Form Types: Specific Guidance

Lead Capture (Gated Content)

  • Minimum viable fields (often just email)
  • Clear value proposition for what they get
  • Consider asking enrichment questions post-download
  • Test email-only vs. email + name

Contact Form

  • Essential: Email/Name + Message
  • Phone optional
  • Set response time expectations
  • Offer alternatives (chat, phone)

Demo Request

  • Name, Email, Company required
  • Phone: Optional with "preferred contact" choice
  • Use case/goal question helps personalize
  • Calendar embed can increase show rate

Quote/Estimate Request

  • Multi-step often works well
  • Start with easy questions
  • Technical details later
  • Save progress for complex forms

Survey Forms

  • Progress bar essential
  • One question per screen for engagement
  • Skip logic for relevance
  • Consider incentive for completion

Mobile Optimization

  • Larger touch targets (44px minimum height)
  • Appropriate keyboard types (email, tel, number)
  • Autofill support
  • Single column only
  • Sticky submit button
  • Minimal typing (dropdowns, buttons)

Measurement

Key Metrics

  • Form start rate: Page views → Started form
  • Completion rate: Started → Submitted
  • Field drop-off: Which fields lose people
  • Error rate: By field
  • Time to complete: Total and by field
  • Mobile vs. desktop: Completion by device

What to Track

  • Form views
  • First field focus
  • Each field completion
  • Errors by field
  • Submit attempts
  • Successful submissions