Match a prospect to approved customer references

Why use this

1. A seller preparing a reference request may default to familiar customer names even when the prospect has a different operating context. A long approved list is difficult to use if relevant similarities are buried in notes.

2. A reasoned shortlist could expose both the fit and the gaps before anyone approaches a reference customer. The reviewer would still need to check current consent and whether the proposed introduction is appropriate.

Why an agent / simpler alternative

Useful judgment

Compare several fit dimensions and explain trade-offs rather than selecting a recognizable logo.

Simpler alternative

Use filters when matching depends only on a few clean, agreed categories.

Unsuitable when

Reference permissions or prospect requirements are absent or unreliable.

Proposed inputs

1. Name

   Prospect brief

   Owner

   Account owner

   Minimum scope

   Use case, relevant constraints and desired reference discussion

   Quality check

   Distinguish stated needs from seller assumptions.

2. Name

   Approved reference snapshot

   Owner

   Reference-program owner

   Minimum scope

   Approved customer profiles and current permission limits

   Quality check

   Check consent status and allowed disclosure fields.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only, field-limited prospect and approved-reference exports.

Compatibility unknowns

1. Unknown: exact runtime, CRM connectivity and reference-database availability.

External actions requiring approval

1. Contacting reference customers, disclosing identities or arranging introductions.

Expected deliverable and review checks

Proposed artifact

Ranked candidate shortlist with fit evidence, mismatches and consent questions.

Critical checks

1. Reasons cite supplied profile fields.

2. Unapproved or expired entries are excluded; weak matches remain labelled.

Missing output evidence

No actual shortlist quality, consent check or completed reference introduction is established.

Failure signals and proposed responses

1. Signal

   A strong fit has expired participation approval.

   Why it matters

   Commercial relevance cannot substitute for consent.

   Proposed response

   Exclude the candidate and request a program-owner review.

2. Signal

   Industry similarity hides a different use case.

   Why it matters

   The reference conversation may not answer the prospect’s concerns.

   Proposed response

   Lower the ranking and expose the mismatch instead of concealing it.

Effort and cost — unknown

Setup work

1. Agree fit dimensions and normalize permission labels.

Ongoing review

1. Refresh availability and review reasons with the seller.

Unknowns

1. Unknown: database completeness, ranking effort and connector charges.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Three fictional references: same industry but wrong use case, matching use case with expired consent, and partial approved fit.

Acceptance checks

1. Expired consent excludes the strongest apparent match.

2. Partial fit includes its limitation.

Stop conditions

1. A recommendation requires private facts outside the approved snapshot.

Limits

1. Editorial recommendation check; rankings do not establish willingness or permission to participate.