Build a Target List of Prospects

A prospect list is not a pile of names. It is an evidence system for deciding whom to contact, why the conversation is relevant, who can approve a small test, and when to stop pursuing an unqualified lead. A small list of well-documented buyers is more useful than a purchased list of thousands of strangers.

The segment exercise produced a rough list. This chapter turns that list into a working pipeline that protects privacy, respects contact rules, and supports a real sales conversation.

Begin With the Segment Card

The list inherits its rules from the chosen segment:

• Buyer situation.
• Trigger and recurring job.
• Approver role.
• Relevant evidence.
• Access route.
• Trust requirement.
• Delivery fit.
• Cash timing.

Do not add a name because the person seems interesting. Every entry should explain the match. If the explanation depends on a stereotype, an unverified personal detail, or a guess about someone's finances, leave the person out.

Define Inclusion and Exclusion Rules

Write the rules before collecting names:

Include an organization or buyer when:

• There is public or permitted evidence of the triggering situation.
• The work could plausibly fit the offer.
• A legitimate contact route exists.
• The decision role can be identified without prying.
• The buyer appears able to pay for a small test within the runway.

Exclude a buyer when:

• The available evidence does not match the segment.
• Contact would violate a platform rule, do-not-contact request, or local law.
• The buyer only gives access to sensitive data you cannot handle.
• The opportunity requires a license, insurance, or expertise you do not have.
• The procurement path or timeline cannot affect the current cash problem.
• The relationship would create a conflict or ethical risk.

Inclusion rules should be specific enough that another person could review the list and remove a poor fit.

Use Lawful Sources

Possible sources include:

• Referrals from people who know both you and the buyer.
• The buyer's public business website.
• Trade directories and association lists.
• Public events and speaker pages.
• Public procurement records.
• Job postings that describe the recurring workflow.
• Your own prior work and professional relationships.
• Communities where self-promotion and direct contact are permitted.

Check the source date and purpose. A public directory listing does not automatically authorize an unsolicited marketing message. Privacy, electronic marketing, telephone, and anti-spam rules vary by jurisdiction and channel. Record the basis for contact and the opt-out path.

Do not collect sensitive personal data merely because it is visible. A business email address and public role may be enough. Avoid health, financial, family, or identity details that do not change the usefulness of the conversation.

Map the Buying Roles

For each prospect, record the likely roles:

• User.
• Champion.
• Budget owner.
• Technical or compliance gatekeeper.
• Final approver.

Use the buyer's public role and information the buyer has voluntarily shared. Do not assume that a founder approves every purchase at a larger company or that a manager controls a budget they have never mentioned. Write "likely" or "unknown" when that is the truth.

The first conversation may begin with a user, but a useful list shows how to reach the approver or request a referral. A list of twenty-five users who cannot influence a purchase is not a sales pipeline.

Build an Evidence Field

Each row should contain a short evidence note:

• The buyer announced a new workshop series.
• A recent job posting mentions weekly reporting.
• A public case study describes a manual onboarding process.
• A referral said the owner was looking for help after an event.

Evidence may support a hypothesis, not prove the problem. Separate what you observed from what you inferred. This protects you from opening a message with a false claim.

Do not fabricate personalization. An AI tool can generate a sentence that sounds researched while mixing up a company's services. Verify the source and keep the wording modest.

Record a Contact Route

The route should be practical and permitted:

• Warm introduction through a named person.
• A public business contact form.
• A professional email published for inquiries.
• An event follow-up where contact was expected.
• A platform's permitted direct-message feature.
• A phone call to a business number where local rules allow it.

Store the minimum information needed. Do not build a dossier on an individual. If someone asks not to be contacted, record the request and suppress the record from future outreach.

Score Fit Without Hiding the Gates

Use a simple score:

• Evidence of trigger.
• Reachability.
• Decision access.
• Urgency.
• Trust fit.
• Delivery fit.
• Ability to pay within the runway.

Do not let a high total override a hard exclusion. A score of 28 on 35 is irrelevant if the work requires a license you do not have. Gates come first; scores help prioritize what remains.

Keep a short note on why each score was assigned. A future review should be able to challenge the reasoning rather than trust an unexplained number.

Aim for Thirty, Then Prioritize Ten

Thirty qualified entries provide enough variety to test a message and see patterns without pretending the sample is a market study. The number is a practical starting point, not a quota that justifies adding poor contacts.

From the thirty, choose ten first contacts based on:

• Strength of trigger evidence.
• Ease of lawful access.
• Likelihood of reaching the approver.
• Fit with your current capacity.
• Urgency before the next event or deadline.

The remaining twenty stay in the queue. This prevents a burst of generic messages and lets you improve after real replies and objections.

Separate Research From Outreach

Use two states:

1. Research: You have evidence and a possible route but have not contacted anyone.
2. Active: You have a permitted contact, a date, and a clear next step.

Do not mark a person active because you found a name. Do not mark a conversation qualified because someone was polite. Qualification requires a problem, a plausible result, a decision path, and a next step.

Track:

• Source and date.
• Contact route and permission basis.
• Role and likely approver.
• Message date.
• Reply or no reply.
• Referral to another role.
• Opt-out.
• Next action and date.

Keep a Data-Minimization Rule

Ask three questions before adding information:

1. Does this help me decide whether the buyer fits?
2. Is the information accurate and lawfully obtained?
3. Will I still need it after the next contact?

If the answer to the first or second is no, do not store it. If the answer to the third is no, set a deletion date.

Spreadsheets can be appropriate for a small list, but they still need access control, backups, and sharing rules. Do not put sensitive prospect information in a public document or an unapproved AI service.

A Worked Target List

The following records are illustrative composites. They are not real people or endorsements, and the contact routes would still need verification under local rules.

• Workshop company A. A public event page shows a new four-part series. The operations lead is the likely person to help, the owner is the likely approver, and a warm referral is available from a past participant. Four events in one quarter make the transcript workflow a plausible repeat.
• Workshop company B. A job post mentions post-event follow-up. The marketing coordinator is the likely person to help, the founder is the likely approver, and the business inquiry form is the proposed route. The fit note says faster follow-up may matter, but no data owner is known.
• Training consultant C. A recent workshop recording was published, but its reuse permission is unknown. The consultant is both user and approver, and an existing professional relationship provides access. Reachability is strong, but rights and data use must be confirmed.
• Small agency D. A public page advertises live cohort programs. The program manager is the likely person to help, the agency owner is the likely approver, and the event follow-up route is available. The workflow is similar, but the approval path is longer.
• Training company E. A job posting says the team is hiring an operations assistant. The operations manager is the likely person to help, the founder is the likely approver, and a mutual contact can provide a referral. A backlog may be relevant, but more evidence is needed before making a direct claim.

The list is useful because it shows what is unknown. Nina does not claim that company B needs her service. She asks about the workflow described in the public job post. She marks company C's published recording as "permission unknown" and does not use the content in an offer.

Nina verifies each route, records the date, and removes one prospect whose public profile belongs to a person who has asked not to receive marketing messages. The remaining list is smaller but more responsible.

Your Chapter Exercise

1. Copy the inclusion and exclusion rules from the segment card.
2. Choose three lawful source types for the first research pass.
3. Build thirty prospect records using the fields in this chapter.
4. Add one evidence note and one unknown to every qualified record.
5. Identify the likely approver for the first ten.
6. Verify the contact route for those ten.
7. Remove anyone with a hard legal, privacy, competence, or timeline exclusion.
8. Prioritize ten first contacts and leave twenty in the queue.
9. Set a permission or suppression field and a deletion date.
10. Ask someone outside the project to challenge five fit claims.

Chapter Deliverable

Maintain a private target-list workbook with:

• Segment rules.
• Thirty prospect records or a documented smaller lawful list.
• Public or permitted source and date.
• Trigger evidence and inference.
• Buying roles and likely approver.
• Contact route and permission basis.
• Fit score and hard exclusions.
• Priority, next action, opt-out, and retention fields.

Source and Decision Caution

Contact and marketing rules vary by jurisdiction, channel, and recipient type. A public profile or business email is not a universal permission to send repeated commercial messages. Verify current rules and platform policies, keep records of consent or another lawful basis where required, and honor opt-outs promptly.

Business directories can be stale, and AI-generated lists can produce nonexistent people, wrong companies, or sensitive inferences. Verify every identity and evidence field before contacting anyone.

Do not use protected characteristics or unnecessary personal data to infer need, creditworthiness, or decision authority. The purpose of this list is a relevant, respectful business conversation, not surveillance.

The next chapter writes outreach that earns attention with specific evidence and asks for one low-friction next step.