# Lead capture form specification > Define a form's offer, fields, consent, routing and delivery as one complete customer interaction. Use the editable worksheet, example and review steps to turn it into a working document. Source: https://saas-marketing.net/templates/lead-capture-form-spec/ Topic: SaaS Lead Generation Type: template Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/templates/lead-capture-form-spec/ ## Short answer Lead capture form specification helps a SaaS team define a form's offer, fields, consent, routing and delivery as one complete customer interaction. The fields below define the required decisions and evidence. Download a CSV working copy, assign owners and replace the illustrative example with your own approved information. ## Key takeaways - Define a form's offer, fields, consent, routing and delivery as one complete customer interaction. - A database write is not resource delivery. Test the promised outcome after the form succeeds. - Every field needs a useful answer, supporting evidence or an explicit unresolved question. - The download is an editable CSV file that opens in spreadsheet applications. --- Define a form's offer, fields, consent, routing and delivery as one complete customer interaction. This worksheet supports the broader [saas lead generation plan](/saas-lead-generation/). ## The working template | Field | What to enter | Your answer | Owner | | --- | --- | --- | --- | | Offer | State exactly what the visitor receives. | | | | Required fields | Justify each mandatory input. | | | | Optional fields | Explain how extra detail changes the response. | | | | Validation | Specify length, format and useful error messages. | | | | Consent | Separate the requested service from optional marketing. | | | | Routing | Assign the destination and accountable owner. | | | | Delivery | Define the success screen and real download or response. | | | | Failure recovery | Keep entered data available after a recoverable error. | | | ## A worked example A template form needs an email and a clear download result. A consultation form may also need the website and problem so a reviewer can prepare. The example is illustrative. It does not describe a measured customer result or create a promise about your own outcomes. Use it to understand the level of specificity the document needs. ## How to complete the worksheet 1. Choose one project, account segment or decision. A document that attempts to cover the whole company usually hides important differences. 2. Gather the evidence required by the fields above. Use approved customer research, current product information and the relevant business records. 3. Draft the answers with the person responsible for doing the work. Keep unresolved questions visible and assign a next action to each one. 4. Review the document with the people who depend on it. Confirm scope, responsibilities and any constraints before treating it as an operating agreement. 5. Save the version and review date. Update it when the underlying offer, process or customer evidence changes. ## Review before sharing A database write is not resource delivery. Test the promised outcome after the form succeeds. A useful working document makes disagreements visible while there is still time to resolve them. Ask a colleague to explain the intended decision from the filled-in version without additional narration. If they cannot identify the next step or the evidence behind it, revise the relevant field. Remove confidential customer details from any public copy. Keep names, prices and results only when you have permission and can explain their context. An empty evidence field is a signal to investigate, not an invitation to supply a plausible-sounding number. ## Continue the work - [B2B SaaS lead generation](/guides/b2b-saas-lead-generation/) - [The B2B SaaS lead generation funnel](/guides/saas-lead-generation-funnel/) - [Lead generation by company stage](/guides/lead-generation-for-saas-companies/) - [Lead generation playbooks by ACV band](/playbooks/b2b-saas-lead-generation-by-acv/) - [Lead generation for a SaaS startup](/guides/saas-startup-lead-generation/) Find more [templates](/templates/) and [checklists](/checklists/) for adjacent tasks. {/* expanded-practice-2026-09 */} ## Apply lead capture form specification in a working review Make a copy of the working file and complete one representative row before filling the entire document. Replace example values with evidence from the actual project. Add an owner and a review condition where the template calls for a decision. A blank marked unknown is more useful than an invented number that makes the file look finished. For this topic, involve the conversion-path owner and the person reviewing saved requests and work from the form promise, stored record and actual delivered resource. The relevant unit is a valid consented request with a defined purpose. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence. ### Evidence to prepare Test the entire path from a suitable visitor’s action to verified storage and useful delivery. A success animation is not evidence that a record was saved. Keep the requested resource accessible after completion and make error recovery clear without exposing private submissions. | Review field | What to record | | --- | --- | | Topic | Lead capture form specification | | Decision | The specific action this explanation should help you choose | | Working evidence | the form promise, stored record and actual delivered resource | | Unit and scope | a valid consented request with a defined purpose | | Responsible people | conversion-path owner and the person reviewing saved requests | | Remaining uncertainty | The missing fact that could change the decision | ### Two situations that can change the interpretation #### When form fields reduce useful submissions A file download may need only email and consent, while a tailored audit request can justify a small amount of business context. Use this check: Review each field's operational purpose and inspect valid incomplete attempts without collecting unnecessary private data. A shorter form can reduce context, so review downstream quality as well as volume. The [focused diagnostic guide](/guides/form-fields-reduce-useful-submissions/) provides the correction process and a working evidence sheet. #### When saved leads have no operational owner A working Firestore write is a storage success; a useful customer response requires a separate human or automated operating workflow. Use this check: Trace a recent synthetic request from storage to the person responsible for review. Do not claim notifications or email routing are configured when only storage exists. The [focused diagnostic guide](/guides/lead-follow-up-has-no-owner/) provides the correction process and a working evidence sheet. ### Record the decision and the limit A synthetic test request can confirm that the form validates, the database accepts the intended fields and the advertised file exists. The test should be isolated from real leads and cleaned up by an authorized process. Operational review of genuine requests remains a separate responsibility. Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required. Use the [complete topic collection](/topics/saas-lead-generation/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied. ## Frequently asked questions ### What format is the downloadable template? The working copy is a CSV file. Open it in your spreadsheet application, add owners and dates, and keep a separate copy of the original for reference. ### How should I fill in this template? Define a form's offer, fields, consent, routing and delivery as one complete customer interaction. Start with one real project so that the decisions remain specific. ### What mistake should I avoid? A database write is not resource delivery. Test the promised outcome after the form succeeds. ### Do I need to complete every field before starting? Identify the fields that change the decision or block safe execution. Mark unknowns with an owner and a review date rather than inventing an answer.