A practical prospect-fit scorecard for specialist B2B firms

1. Problem relevance

• 0: No visible connection to the problem.
• 1: The company could experience the problem, but the evidence is generic.
• 2: Public information shows an operating condition that makes the problem materially relevant.

2. Offer fit

• 0: The service would require a different buyer, delivery model, or capability.
• 1: Part of the offer could help.
• 2: The approved offer closely matches the likely need.

3. Company readiness

• 0: The company is structurally unable to use the service.
• 1: Readiness is unknown.
• 2: Size, market, systems, or operating maturity make engagement plausible.

4. Buyer clarity

• 0: No credible owner for the problem.
• 1: A function is clear, but the role is uncertain.
• 2: A role with plausible responsibility is identifiable.

5. Evidence quality

• 0: The reason is inferred from a generic category label.
• 1: One current public source supports part of the case.
• 2: Multiple current sources or a strong first-party source support the case.

Apply the score to a real prospect hypothesis

Consider a consultancy that helps software vendors prepare security evidence for enterprise customers. A vendor has announced a regulated-market offering and published a vendor-review process. Problem relevance might score 2: the operating context is specific. Offer fit might score 2 if the consultancy has an approved service for that work. Company readiness might score 1 because no public source shows capacity or timing. Buyer clarity might score 1 until a responsible security or operations role is identified. Evidence quality might score 2 if both observations come from current first-party pages. Total: 8.

An 8 is a reason to complete buyer research, not a reason to claim the vendor has a security problem. If the only “signal” were an industry tag, problem relevance and evidence quality would drop. The score is useful precisely because it exposes where the case is thin.

Read the total carefully

• 0–3: Do not contact. The case is too weak.
• 4–6: Research further or wait for stronger evidence.
• 7–8: Reasonable candidate for human review.
• 9–10: Strong fit, but still not proof of intent.

Add hard stops before the total

A numerical total should not compensate for a disqualifier. If the company is outside the service geography, the offer cannot be delivered, the contact is suppressed, or the only way to write the email is to make an unsupported claim, stop regardless of score. Likewise, a company should not pass on “evidence quality” merely because many low-quality directory pages repeat the same old fact.

Use the score to make the team’s reasoning consistent, then keep the actual source and decision beside the account. Apollo’s account-search documentation describes account qualification and explicit disqualifiers; the broader principle is that a score is most useful when it can be inspected, challenged, and updated.

Research: Apollo company search and account qualification

Write the fit reason before the email

For every approved prospect, write one internal sentence: “[Company] may fit because [current, sourced operating context] makes [problem] relevant, and [role] is a plausible owner.” If that sentence requires unsupported assumptions, the prospect is not ready for a draft.

Calibrate the rubric with outcomes, not wishful thinking

After a small set of campaigns, compare high-scoring accounts with the conversations that actually resulted. Do not treat silence as proof that an account had no need; timing, deliverability, and message quality also affect response. Instead, review whether the original evidence was current, whether the chosen role owned the workflow, and whether the message stated the fit reason accurately.

If the team repeatedly disagrees on a criterion, rewrite the definition with a concrete positive and negative example. A scorecard should make better decisions easier; it should not turn judgment into a decorative number.