QUALIFIED PROSPECT RECORD · EXAMPLE
A useful prospect record connects company fit, buyer relevance, source evidence, verification state and the reason it was accepted. This worked record is an illustrative fixture example, not a historic client result.
Illustrative fixture: fields, scoring and acceptance logic vary by project.
The record is designed to let your team understand what was found, why it matched the brief and what still needs attention before outreach. Fields vary with the agreed project scope.
A prospect only makes sense when the company fits the agreed market. Company evidence supports the qualification reason and makes the inclusion decision inspectable.
The buyer is selected against the campaign's agreed role hierarchy. The record keeps the person's role and supporting source context together rather than treating any contact as interchangeable.
Where a professional email is found, the record can show the verification status, provider and date. A verification state is evidence about that step, not a guarantee of delivery, reply or commercial outcome.
Before delivery, the record is checked against the agreed qualification criteria, duplicate handling, exclusions and suppression controls. Records with insufficient or conflicting evidence can be rejected or held for review.
This example demonstrates the shape of a finished record. The names, address and contact route are fixture-safe example data. Scores and fields are shown for illustration and are not universal project rules.
Manchester, UK
UK geography; active website supplied; matched target evidence: outbound agency, appointment setting, outbound; Companies House identity; 3 opportunity signal(s); buyer: Founder
Relevant company and role sources are retained where useful, alongside collection dates or the available evidence state.
The record explains why the company and buyer fit the agreed brief instead of hiding the decision behind a score alone.
Contact verification is represented as a status with provider and date where applicable, with unknowns kept visible.
Acceptance, rejection or hold status shows what happened at the review boundary before a record reaches delivery.
The fixture shows four components: fit, opportunity, buyer confidence and data confidence. Together they produce an illustrative total and tier for this example. A score is useful when its inputs and reason are visible, but the scale, weighting and thresholds can vary by project and must not be presented as a universal Keystone standard.
A company and buyer match the agreed criteria, source context is attached, the relevant contact step has a recorded status, and the record has passed the required duplicate, suppression and human-review checks.
An unsuitable company, conflicting identity, suppressed contact, weak buyer evidence or unresolved verification state can be rejected or held until the issue is resolved. No invented score is needed.
The accepted and rejected examples describe decision logic, not a universal numeric threshold. Project-specific criteria are agreed before research begins.
Approved records can be prepared for the agreed handover route, with the relevant fields, evidence and review state retained. Current standard delivery routes are a review-ready CSV or an agreed HubSpot delivery; other destinations must be scoped separately.
A record can include the matched company, website and location, the relevant decision-maker and job title, contact-discovery and verification status, source evidence, collection dates, match reasons and review state. The exact field set is agreed for the project.
The illustrative fixture shows fit, opportunity, buyer-confidence and data-confidence components, a total and a tier. These values explain this example record; they are not universal thresholds or a promise that every project uses the same scoring scale.
No. Verification reports the result and status returned by the verification step. It does not guarantee mailbox acceptance, delivery, a reply or a meeting.
Records are checked against the agreed company and buyer criteria, duplicate rules, exclusions and suppression controls. Accepted records pass the relevant checks and human review; insufficient, risky or unresolved records can be rejected or held rather than presented as finished prospects.
No. Prospect research and delivery are separate from sending, mailbox management, copywriting and automated replies. Outreach requires its own scope and approval, suppression and responsible-use controls.
INSPECT THE WORK BEFORE YOU SCALE IT