Lead Generation Form Template

Capture and qualify in one lean pass. Five short questions turn page visitors into named, sourced, consented leads a salesperson can act on.

Free · copies into your editor in one click
Live preview — try it, nothing is saved

Tell us a little about yourself and what you want to achieve. It takes under a minute, and a real person reads every answer.

press Enter ↵
Question 1. Your name

A lead generation form is a trade. The visitor gives you contact details and a sliver of context, and you give back a reason to believe the follow-up will be worth it. Every choice in this template guards that trade from its two failure modes: ask so little that sales cannot prioritize, or ask so much that nobody finishes.

The two fields that make a lead. Name and work email are the irreducible pair; without them you hold a pageview, not a lead. The company website stays optional on purpose. It costs the visitor five seconds and saves your team a research trip before the first call, and because it never blocks a submission, it can only help. The single qualifying question, "what are you hoping to improve?", is the highest-leverage field on the page: one tap sorts every lead into a lane your team already thinks in, which is what makes tomorrow's follow-up list sortable. The consent question stands on its own with two honest options instead of a buried checkbox. Leads who pick "yes, keep me posted" become a mailing audience you can defend, and the ones who decline still get their reply.

How the hidden fields earn their keep. Two hidden fields, utm_source and utm_campaign, ride along with every submission. Share the form as yourlink?utm_source=linkedin&utm_campaign=spring and each response arrives stamped with where it came from. No respondent ever sees these, yet your CSV export gains two columns that settle every "which channel is working" argument with data instead of vibes. Create one link per placement and the form becomes its own attribution system.

What stays off the form. Phone numbers lead the exclusions, because asking for a number before you have earned it is the single biggest completion killer in lead capture. Budget questions come off too, premature at this stage and easy to sandbag. Long message boxes belong on contact forms, where they earn their place; here they would bleed the momentum the focus layout builds.

Where teams reach for it. Agencies gate their "get a proposal" buttons with it, SaaS teams run it behind mid-funnel content, and consultants link it from their speaking-gig bios. Because every response carries its own source stamp, one form serves every channel at once.

Tuning it to your pipeline. Rewrite the qualifying options in the vocabulary your sales team already uses for its pipeline stages, and the closer the match, the less translation between form and CRM. Wire a webhook in Settings so each lead reaches your tools the second it arrives, signed so you can verify the payload. Keep Focus mode on, since one question per screen keeps the exchange feeling like a conversation, and let the built-in spam stack of honeypot, timing checks, and invisible proof-of-work keep bot "leads" out of your pipeline without a CAPTCHA in sight.

Frequently asked questions

How do the hidden UTM fields get filled in?

Append parameters that match the hidden field labels to your share link, for example ?utm_source=newsletter&utm_campaign=launch. Each response captures the values silently, and they surface as columns in your responses view and CSV export.

Can leads flow straight into my CRM?

Add a webhook in Settings and every submission POSTs to your endpoint in real time with an HMAC signature, retrying on its own if your endpoint is briefly down. For the batch route, CSV export has it covered.

Will bots pollute my lead list?

The form ships with layered protection: a honeypot field, submission-timing analysis, and an invisible proof-of-work challenge that escalates only when abuse patterns appear. Humans never see a puzzle.

Should I add more qualifying questions?

Only if sales acts on the answer. Each added required field lowers completion, so promote a question only when it changes who calls the lead or what they say.