A qualified lead can be valuable and still be wrong for your agency. The budget may be below your delivery model, the geography may sit outside your coverage, the requested service may belong to another specialist, or the timing may not justify an active opportunity. The responsible response is a documented routing decision, not an automatic sale or an indefinite CRM limbo.
This guide is a decision framework. It does not claim that every non-fit lead should enter a marketplace, and it does not publish an invented transfer-success rate. Use your consent, privacy, contract, and customer-experience rules before moving any record between organizations.
First separate “not now” from “not us”
“Not now” means the need may fit your agency, but the buying window is not active. “Not us” means another provider is structurally better suited. Combining these reasons damages both follow-up and transfer decisions.
- Not now: budget cycle, internal project, leadership change, procurement delay, or a future renewal window.
- Not us: service mismatch, geography, company size, industry restriction, delivery capacity, required certification, or commercial model.
- Not qualified: no verified need, authority, basic fit, or usable contact path. Do not relabel weak data as qualified inventory.
Record the reason at the time of disposition. A later operator should not have to infer it from free-form notes or from the absence of a meeting.
Use a four-way decision table
| Path | Use when | Required control |
|---|---|---|
| Nurture | The agency fits, but timing or readiness does not. | Named owner, next review date, appropriate communication basis. |
| Direct referral | One known partner clearly fits and a contextual introduction helps. | Prospect expectation, partner acceptance, ownership handoff. |
| Marketplace transfer | Several verified partners may fit and a structured matching process is useful. | Eligibility, masking, buyer rules, audit trail, dispute path. |
| Close | The record is not appropriate, current, authorized, or useful to transfer. | Reason code, suppression or retention action, no silent recycling. |
The decision should optimize for the prospect’s next useful outcome, not merely for recovering acquisition cost.
Define “qualified” independently of “fits us”
Before a transfer, write the qualification rule in terms another partner can audit. Useful evidence can include a stated need, verified company context, role relevance, timing information, and the source and date of each fact. “Sales accepted it” is a workflow state, not proof.
Separate three evidence types:
- Observed fact: a public company attribute, completed form field, or dated CRM event.
- Prospect statement: what the person said, with date and context.
- Seller inference: a judgment about fit or urgency that the buyer must be able to challenge.
This separation prevents a sales opinion from becoming a universal truth as the record moves between teams.
Preserve the prospect’s experience
A lead handoff is also a trust handoff. The recipient should not be surprised by a new organization using details they did not expect to travel. Decide what explanation, permission, or notice is appropriate for the actual jurisdiction, list source, relationship, and channel.
Use the smallest useful packet. Remove internal commentary, sensitive attributes, unrelated personal data, speculative intent, and information the receiving partner does not need to evaluate the opportunity. The UK ICO describes data minimisation as keeping personal data adequate, relevant, and limited to what is necessary.
A qualified record is not a license to expose everything the first seller knows.
Protect ownership during transfer
Ambiguous ownership creates duplicate outreach and disputes. Define these states before listing:
- who may view masked information;
- whether a reservation blocks other buyers and for how long;
- when full details become available;
- whether the seller may continue outreach;
- which reply, objection, refund, or conflict event changes ownership;
- who resolves stale or contradictory CRM records.
A transfer is complete only when the receiving owner can act and the previous owner knows what must stop.
Measure quality after the handoff
Do not treat a listing, reservation, or purchase as the final outcome. Follow the record through acceptance, usable-data confirmation, first contact, meeting decision, qualified commercial outcome, and any dispute or refund. Keep operational metrics separate from causal claims: a marketplace can record what happened without proving it caused the outcome.
Review rejection reasons as evidence about the handoff process. Repeated “wrong geography” decisions may indicate a mapping failure; repeated “no current need” may indicate qualification drift; repeated “already contacted” decisions may reveal an ownership conflict.
Transfer-readiness checklist
- The record is qualified under a written rule.
- The non-fit reason is specific, current, and separable from qualification.
- The prospect’s expectation and applicable transfer rules were reviewed.
- Only necessary fields enter the preview and acceptance packet.
- Facts, statements, and seller inferences are labelled.
- Seller and buyer ownership states are defined.
- Suppression, objection, and dispute events have owners.
- The team will measure outcomes beyond the transaction.
Sources and next step
The privacy principle in this guide is grounded in the UK ICO’s guidance on data minimisation and the NIST Privacy Framework. Legal duties depend on the real parties, data, purpose, and jurisdiction.
Next, use the partner-ready lead record to package the evidence a buyer needs without exposing unrelated context.