Forms & Leads
Contact forms, lead capture, CRM integration — the mechanics of converting visitors.
Form Types & Use Cases
Forms serve different purposes and require different designs:
Visitor reaches out to you. Simple (name, email, message) or detailed (company, phone, subject). Requires moderate spam protection.
Just email address, maybe name. Single-field is best (25%+ lower abandonment than two fields). High volume, minimal data.
Sales needs details: company size, budget, timeline, use case. 8-15 fields. Higher abandonment but qualified leads. Multi-step forms perform better here.
Name, email, company, phone, preferred time. 5-7 fields. High-intent visitor. Lower abandonment than generic leads.
Resume upload, cover letter, portfolio link. Requires file handling and ATS integration.
Multiple questions with different types (multiple choice, rating, open-ended). Can be lengthy but requires engaging design.
Form Design Principles
Two-column layouts confuse the eye. Single column converts better, especially on mobile.
Every field you add reduces completion by 3-5%. If you don't absolutely need it, remove it.
Labels should be outside fields (not inside as placeholder). Error messages should be specific ("Phone must be 10 digits" not "Invalid").
Pre-fill country, state, or common values when possible. Autocomplete for email and address fields.
Button text should say what happens ("Send Message" not "Submit"). Make it prominent and obviously clickable.
The Spam Problem
Without protection, forms fill with spam—both automated bot submissions and human spam. This wastes your time processing junk and pollutes your CRM.
Spam Prevention Options:
Industry standard. reCAPTCHA v3 (invisible) vs v2 (user interaction). Free. Slightly annoying to users but very effective. Privacy: Google collects data.
Privacy-first alternative to reCAPTCHA. Free. Fewer user interactions needed. Growing adoption.
Hidden form field. Bots fill it; humans don't see it. If filled, reject the submission. Zero UX friction. Can be combined with other methods.
Catch typos (name@example.c0m). Verify domain exists. Prevents obvious spam but doesn't stop sophisticated bots.
Allow only X submissions per IP per hour. Stops brute-force spam. Can block real users from slow connections.
Regex patterns for common spam keywords. Requires maintenance as spammers change tactics.
Best approach: honeypot + email validation + one CAPTCHA option for repeat submitters. Balances UX and spam prevention.
CRM Integration Methods
Form data is useless unless it flows into your CRM where sales can follow up. Integration can happen via:
Platform supports direct CRM connection (Webflow → Salesforce, HubSpot). No setup. Automatic data sync. Limited flexibility.
No-code automation platform. Connect form to CRM with visual workflow builder. Cost: $15-50/month depending on task volume. Flexible, easy to modify.
Custom code makes HTTP request to CRM API when form submits. Full control. Requires developer. Fragile if APIs change.
Form service sends HTTP POST to your backend when submission received. Your server processes and pushes to CRM. Most flexible. Requires backend.
Platform Form Capabilities
| Platform | Native Forms | SPAM Protection | CRM Integration | Conditional Logic |
|---|---|---|---|---|
| Wix | Built-in | Limited | HubSpot native | No |
| Webflow | Built-in | reCAPTCHA | Limited | Yes |
| WordPress | With plugin | Plugin-dependent | Full | With plugin |
| Typeform | Specialized | Built-in | Zapier | Yes |
| Custom | Build yourself | Your choice | Full | Full |