Lead scoring model worksheet

Separate account fit from buying signals so a lead’s activity does not conceal poor suitability. This worksheet supports the broader saas lead generation plan.

The working template

A worked example

A relevant company requesting implementation help may deserve faster follow-up than an unrelated account downloading several introductory guides.

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

Do not make a score appear scientific by adding many arbitrary weights. Start with a small model the sales team can explain.

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
• The B2B SaaS lead generation funnel
• Lead generation by company stage
• Lead generation playbooks by ACV band
• Lead generation for a SaaS startup

Find more templates and checklists for adjacent tasks.

Apply lead scoring model worksheet 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.

Two situations that can change the interpretation

When duplicate submissions inflate lead reporting

A visitor downloading three related worksheets creates three interactions, not necessarily three independent sales opportunities.

Use this check: Compare normalized identifiers and submission purposes within an explicit deduplication window. Do not merge different people merely because they share an organization or domain.

The focused diagnostic guide 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 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 for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.