A prospect list is useful when each row answers the operating questions for an account, a person, and the next action. Build the schema around those jobs, keeping account facts, contact facts, relationship context, and action status distinct. Keep the boundary clear between a researched prospect and a worked prospect. A record becomes a contacted prospect only after it has at least one campaign send.1 This lets you measure list work without counting a populated row as outreach.
Start with record grain
Row grain
- If row represents a contact, attach it
- If it represents an account, keep person-level details
Decide what each row represents and how it connects to the rest of the list before choosing columns or importing anything. That keeps account details, person details, and activity from collapsing into one hard-to-use record.
Call lists can include leads, accounts, person accounts, and contacts.2 An account is the organization a contact belongs to.3 A contact is a person who works at an account.4 A prospect can link to more than one employee, and an employee can relate to multiple prospects or leads.5
Set the row grain before importing anything. If the row represents a contact, attach it to an account. If it represents an account, keep person-level details in related contact records. Preserve the relationship when several people belong to the same organization.
Account fields
Account fields describe the organization and give the team enough context to decide where the record belongs. Keep them stable when several contacts share the same account.
Start with the account name and a related contact list containing name, title, email, and last interaction.6 Capture industry, revenue, employee count, and location so the prospect can be assigned with enough context.7
Keep the associated account populated when your workflow uses local time. The account associated with a prospect is used to calculate and populate the prospect's local time.8
The account record should tell the team which organization it is, what kind of organization it is, where it operates, which contacts belong to it, and which interaction the owner should see first.
Put qualification notes that belong to the person on the contact record. Keep account-wide facts on the account record. That separation prevents a change for one person from rewriting the organization for everyone else.
Contact fields
Contact fields should let a rep identify, reach, and take ownership of a person without opening another document. Keep the record focused on the person and the relationship to the account.
Include first name, last name, job title, email, phone number, and contact owner.9 For a targeting record, include the target's name, title, company, and LinkedIn profile.10
Add a short rationale field for the seller's belief about the prospect's problem. Use this question as the field prompt:
Why do I believe this prospect has this problem?11
That note gives the next rep a reason for the row's inclusion and checks against empty personalization. Ask the owner to write a specific reason, then move on when the record explains why this person belongs in the list.
Context and status fields
Context fields explain why the record is present, how it entered the list, and where it sits in the working process. Keep them separate from identity so the same contact can move through different campaigns without becoming a different person in the database.
Capture relationship, acquisition or consent path, segment, lifecycle stage, organization type, list age, and sender maturity.12 For lead rows, retain source, campaign, created timestamp, first-touch timestamp, lifecycle stages, rejection reason, and pipeline value.13
Use an account or contact indicator or type for prospect and customer designation. Keep lead stage available for upsells.14 This gives the record a commercial designation without forcing the next action into the same field.
Treat campaign history as activity and the next action as status. A person can remain the same contact while the owner changes what should happen next.
Compliance and suppression
Keep suppression fields separate because sending eligibility can change independently from account fit or sales status. Make the rule visible to anyone who exports or routes the list.
Store an Opted Out field on prospect records.15 Keep that field separate from Do Not Email.16 The suppression list status shows whether the list is active or inactive. Lead status can change after client interactions or campaign changes.17
Before a row reaches an outbound workflow, check both the relationship context and the suppression state. A complete contact record can still be ineligible for outreach.
Validate the record layout
Run a schema check before the list enters rotation. Catch missing relationships, unusable fields, and ambiguous status values while the list is still easy to repair.
Review the Record Layout to ensure the data meets your requirements.18 Then test representative rows against the questions the owner will ask:
- Can the row resolve to the correct account?
- Can the owner identify and reach the person?
- Can the row explain why the prospect belongs in the list?
- Can the owner tell how the record entered the list?
- Can the workflow distinguish permission to send from sales progress?
If an answer depends on a value stored in free text, create a field for that value or remove the dependency. If two fields appear to describe the same decision, define which one controls the workflow before importing more records.
What not to do
- Use Lead Status to show the sales representative what to do next with a contact; it should not identify the contact or record website activity.19
- Keep Opted Out and Do Not Email as separate fields on prospect records.16
- Do not duplicate a contact just to place that contact in another list. A contact can belong to multiple lists without being duplicated in the account.20