A lead vendor deserves a test when you can define what you are buying, verify how it reaches you, agree on acceptance terms, and track the result through to a customer. “High quality” is too vague to settle any of those questions.

Before discussing volume, ask the vendor to walk one sample lead from the original inquiry through delivery and reporting. That conversation gives you something concrete to evaluate: the information collected, the promises made to the person inquiring, the time between inquiry and delivery, and the responsibilities on each side.

Define a usable lead before comparing prices

Start with your own requirements. Which product, service area, customer characteristics, and contact details must be present? What makes a lead outside your buying criteria? Write the answers down before the first invoice arrives.

Keep three separate questions in view: Did the lead meet the agreed delivery specification? Could your team reach the person? Did that person become a customer? These outcomes belong in different fields. An unsuccessful sale does not, by itself, tell you whether the vendor delivered what you purchased.

If you are comparing different products, review the basic differences between data leads, calls, and other lead formats. A completed form and a transferred conversation require different preparation from the buyer.

Use these questions to inspect the offer

What to check	Question for the vendor	Evidence to request
Product fit	Which fields determine whether an inquiry matches our order?	A field list, allowed values, and a sample record.
Inquiry origin	What did the person see and request before becoming a lead?	The relevant page or form and its version or capture date.
Timing	When was the inquiry created, and when will we receive it?	Creation and delivery timestamps with time zones.
Distribution	Who else can receive this inquiry, and when?	Written sharing, exclusivity, and resale terms.
Duplicates	Which identifier and time window define a duplicate?	The matching rule and a worked example.
Delivery	What happens when our system rejects a record or our team cannot accept a call?	A delivery test and the retry or overflow rules.
Credits	Which failures qualify, what evidence is required, and by when?	The credit policy and submission process.
Reporting	Can we reconcile delivery, billing, and customer outcomes by lead ID?	A sample export with stable identifiers.

You do not need a perfect answer to every operational question on the first call. You do need a named owner and a clear answer before spending against an unresolved assumption.

Look past the source label

Paid search, organic search, social advertising, and affiliate traffic describe acquisition channels. They do not explain the entire offer. Ask what the person was trying to accomplish and whether the experience they saw matches the conversation your team intends to have.

For a vendor using multiple sources, ask whether those sources have identifiers your reporting can preserve. You want to know whether a result came from the same product you tested or from a later change in the traffic mix. Agree on how changes to sourcing, qualification, or distribution will be communicated.

Ask your internal compliance team which supporting records it needs and how those records should be supplied. Include those requirements in the vendor setup, with a named owner for unresolved questions. Keep that review separate from the commercial acceptance checklist.

Test delivery before testing performance

Send a clearly marked test record through the actual delivery route. Check that the source ID, lead ID, timestamps, qualification fields, and assigned owner arrive intact. Confirm what your system sends back when it accepts or rejects the record.

For calls, test the handoff, opening information, operating hours, and overflow path. Ask exactly when billing starts. For data leads, check field formatting, duplicate handling, and failed-delivery notifications. A successful email notification is not enough if the lead never reaches the person expected to work it.

Review your lead management process alongside the vendor setup. Assign responsibility for exceptions before they accumulate.

Agree on the test and the credit process in writing

Your test plan can fit on one page. Include the product and filters, delivery hours, daily cap, spending limit, responsible sales team, follow-up procedure, reporting fields, and review date. Give the test enough time for the outcome you are measuring; an appointment and a completed sale may happen on different schedules.

Write down a stop condition for operational failures. For example, pause delivery if records stop reaching the CRM or calls arrive outside agreed hours. That is different from ending a source test because its sales performance disappoints.

Before launch, submit a fictional rejection example to the vendor: “This record is outside our agreed service area. Which field and supporting evidence do you need?” Establish the submission deadline, review timing, and whether an approved claim produces a refund, account credit, or replacement. Track requested and approved credits separately.

Decide what the results actually support

At review, reconcile leads delivered, leads accepted, attempts made, people reached, qualified opportunities, and customers acquired. Record missing follow-up and routing failures alongside vendor issues. Otherwise, you can mistake a process problem for a source problem.

Compare cost per acquired customer, including the costs of working leads that did not convert. Keep the time window and customer definition consistent. A small test can reveal delivery problems and suggest what to test next; it does not establish a dependable conversion rate by itself.

If sourcing leads is part of your job, review the qualifications and apply for LGW’s $395 Lead Buyer Pass. The application page explains eligibility and access to the Lead Buyer Summit. Applications are reviewed; submitting one does not guarantee a discounted pass.