Lead Research

Prospect research is useful when a sales team has a clear customer profile but cannot trust its list. The service documents why an organization fits, where each public fact came from, and whether the record should be suppressed. It does not decide whether an outreach message is lawful, invent a relationship, or sell scraped personal data as a substitute for consent.

This guide applies the general Starter Library method to lead research. Use G01 for opportunity selection, G03 for AI verification, G04 for demand evidence, G05 for setup, G06 and G07 for customer contact and selling, G08 for pricing, G09 for service recovery, G10 for cash discipline, G12 for workflows, and G13 for contracts and privacy. Those guides carry the shared method; the sections below cover the operating decisions that change when this specific service is delivered.

Opportunity and Customer

The buyer group is Business-to-business service providers with a defined ideal customer, lawful contact basis, and a human who owns outreach decisions and suppression requests.

The recurring problem is Sales lists are inconsistent, sources are unverified, duplicates cause repeated contact, and outreach is sent without checking consent or exclusion rules.

The paid result is A source-verified prospect list with fit notes, contact basis, duplicate and suppression checks, and a documented handoff for approved outreach. Progress must remain inspectable, and consequential changes require the buyer's named approver.

The operating boundary is You research and organize prospects. The client decides whether and how to contact someone under applicable law and remains responsible for the message.

Demand evidence

Ask the sales owner to define an ideal customer, a clear exclusion, and the last known list-quality problem. Strong evidence includes duplicate outreach, outdated roles, costly manual verification, a suppression backlog, or a segment where generic lists produce poor conversations. Confirm that the client already has a lawful outreach process and a named person who handles suppression. A request for thousands of emails is not a valid starting signal. The paid sample should measure accepted and rejected records, not reward the seller for inflating volume. Review one current row to confirm that the organization, role, and source can be verified independently.

Fit and Skills

The fit assessment is Fits a careful researcher who values source quality, privacy, anti-spam rules, and precise notes over list volume.

The minimum skill set is Learn public-source research, entity disambiguation, role relevance, contact-basis documentation, suppression management, and data-quality sampling.

Use G04 to test buyer demand for lead research after building this guide's artifact; capability alone is not proof.

Capability artifact

Create a fictional 25-organization research sample for commercial-cleaning prospects. Include one similar-name collision, one outdated role, one duplicate domain, one suppressed contact, and one generic address that should not be treated as a person. Produce a source log, acceptance rules, quality sample, and handoff report with accepted, rejected, and unresolved counts.

Startup Budget

These lead research USD ranges are planning inputs; confirm each cost with current local quotes and keep first-test loss affordable.

• Spreadsheet and source log: 0 USD.
• Browser research and citation tools: 0 to 20 USD monthly.
• Customer-relationship or contact system: 0 to 80 USD monthly.
• Data-protection or marketing-law learning: 50 to 250 USD.
• Professional review allowance: 100 to 400 USD.
• Contingency for re-verification and duplicate cleanup: 50 to 200 USD.

Skill Acquisition

Operating sequence

Start with written inclusion, exclusion, source, field, and retention rules. Build a source log before collecting contacts, resolve organizations and roles, record the public contact route and fit evidence, compare against the client's suppression list, and sample uncertain entities. Output rejected and unresolved records with reasons instead of padding the count. The client's authorized team decides whether and how to contact anyone.

Acceptance test

Sample accepted records against the sources and check that the organization, person, role, and contact route refer to the same entity. Verify that duplicate and suppression checks use the current list. Test a name collision, an outdated role, a generic company address, and a person who requested no contact. A record without a documented basis, purpose, and review status is not accepted.

Setup

Define the buyer profile, allowed sources, contact purpose, legal basis to document, prohibited data, suppression rules, list owner, and retention period.

Launch controls

Use minimum fields for the stated business purpose and keep the client's suppression and consent data in an approved system. Record permitted source, access date, uncertainty, and retention date. Do not bypass access controls, scrape private groups, infer sensitive traits, or send test outreach from the client's account without explicit authorization.

Use G05 and G13 for jurisdiction-specific setup, privacy, and legal questions.

Concrete Offer

A two-hundred-prospect research sprint for one defined segment. Includes inclusion and exclusion criteria, public-source citations, role fit, duplicate checks, suppression matching, quality sample, and a handoff report.

First acceptance evidence

The proof is an auditable batch rather than a maximum record count. It shows requested records, accepted records, rejections by reason, duplicates, suppressed matches, source coverage, and a reviewed sample. The client can trace why each accepted record belongs and can update suppression before any outreach decision.

Use G07, G08, and G13 to write the scope, payment, approval, and stop condition.

Outreach

Do not use the service itself as a reason to mass-email researched contacts. Approach the hiring business through an authorized channel and discuss its current list-quality problem.

Work with small B2B firms that have a clear customer and an existing lawful outreach process but no reliable research system.

Acquisition test

Approach ten B2B service providers that already have a lawful sales process and a narrow ideal-customer statement. Ask how they prevent duplicate contact and verify current roles. Offer a paid 25-record quality sample. Do not use the prospect's email list, harvested addresses, or the contact targets themselves as the sales channel.

Use G06 for the lawful contact method and record each reply and next action.

Pricing and Unit Economics

An illustrative 200-record sprint is 500 to 2,000 USD depending on verification depth. Price by accepted records and quality rules, not raw records delivered.

Count criteria design, source research, entity matching, duplicates, suppression checks, verification, rejection, and sample review. Cheap list volume creates expensive legal and brand risk.

Illustrative floor calculation

For 200 records, plan 3 units for inclusion and source rules, 16 for research, 4 for duplicate and suppression checks, 3 for quality sampling, and 2 for the handoff report. At 35 USD per direct unit, planned labor is 980 USD before data tools and administration. A 900 USD sprint is realistic only if records are high quality and the segment is relatively easy to verify; rejected records are work, not billable padding.

Use G08 and G10 to set a local floor; contribution is not owner pay.

Delivery Example

The example below is an illustrative composite, not a real customer record or income promise.

A commercial cleaning company wants property-management contacts. You research 200 organizations with public contact routes, record why each fits, remove duplicates and opted-out addresses, and flag uncertain entities for human review. The illustrative fee is 900 USD. The client sends any outreach.

Delivery trace

In the cleaning-company example, the batch removes a duplicate domain, flags a similar-name organization, and matches two contacts against the suppression list. The accepted row cites the public source and the reason for fit. The client receives no copied private lists and remains responsible for deciding whether and how to make contact.

Growth

Add recurring re-verification and suppression maintenance. Build sector playbooks. Never sell scraped personal data or contacts whose source and permitted use cannot be explained.

Scale boundary

Add a market only after the first segment has stable source and rejection rules. Recurring maintenance should re-verify roles, remove suppressed records, and report source age. Do not scale by reducing verification until the audit becomes meaningless; cheap list volume creates legal, brand, and sales-quality costs that sit outside the line-item fee.

Use G14 before expanding lead research capacity, a customer segment, or a service line; protect delivery quality first.

Risks

• Sending unlawful or unwanted outreach.
• Mixing people with similar names or roles.
• Collecting sensitive personal data without a need.
• Keeping stale or suppressed contacts active.

The controls above are the early-warning route. Jurisdiction-specific professional review still applies.

Privacy and AI Verification

Research only what the defined purpose requires, cite public sources, document restrictions, and remove suppressed contacts. AI can assist entity matching, but a human must verify identity, role, contact basis, and current suppression status.

Apply the authorization, minimization, verification, and deletion process in G03, G12, and G13.

30-Day Action Plan

• Days 1-4: choose one B2B segment and define strict inclusion and exclusion rules.
• Days 5-9: build a 25-prospect sample from public sources and document every field.
• Days 10-13: create source, duplicate, suppression, quality, and retention templates.
• Days 14-20: contact ten potential business clients with the bounded research offer.
• Days 21-26: deliver a sample or paid sprint and check a random quality sample.
• Days 27-30: review rejection rate, verification time, legal friction, and contribution.

At day 30, continue, revise one variable, or stop.

Day-30 decision record

At day 30, record paid lead research tests, costs, delivery time, rework, exceptions, one objection, and one approval delay.

Templates

Template 1

Research brief: Segment, must-have criteria, exclusions, permitted sources, fields, verification standard, suppression source, owner, and retention date.

Template 2

Prospect row: Organization, source, role, fit reason, public contact route, duplicate status, suppression status, uncertainty, and reviewer.

Template 3

Quality report: Records requested, accepted, rejected, duplicates, unresolved entities, source coverage, sample error rate, and handoff date.

Adapt contract language through G13 and local professional review.

Related General Guides

• G01, Finding a Business Opportunity That Fits
• G03, AI Assistant Basics
• G04, Validating Demand
• G06, Finding Customers
• G07, Selling Services
• G09, Customer Service
• G13, Contracts and Privacy

Read the linked general guides for shared definitions, customer acquisition, pricing method, service recovery, cash discipline, workflow design, and legal and privacy controls. This specialized guide intentionally stays focused on lead research operations.

Key Takeaways

• The proof is an auditable batch rather than a maximum record count.
• Sample accepted records against the sources and check that the organization, person, role, and contact route refer to the same entity.
• For 200 records, plan 3 units for inclusion and source rules, 16 for research, 4 for duplicate and suppression checks, 3 for quality sampling, and 2 for the handoff report.
• Approach ten B2B service providers that already have a lawful sales process and a narrow ideal-customer statement.
• Add a market only after the first segment has stable source and rejection rules.
• Keep the service boundary, named approver, and stop condition in every offer.
• At day 30, decide from paid delivery evidence and actual contribution.