Prospecting

Find accounts that fit the motion you actually sell.

Prospecting starts with a clear ideal customer profile and a shared reason for why an account belongs on the list.

Prospecting example using approved fictional Pursenda sample data.
Fictional sample data. Example workflow, not customer proof.

ICP filters

Shape lists around segment, region, size, buying journey, and agreed account criteria.

Source and freshness

Keep source category and last-reviewed date visible so stale lists do not become hidden truth.

Saved ownership

Attach owner, research notes, and next action before outreach begins.

Know why every account is on the list

Know why every account is on the list

Each account carries a source category, last-reviewed date, owner, confidence note, and next action. Account-level discovery is the published baseline; named-person contact coverage is scoped only when the implementation supports it.

From list to workflow

From list to workflow

A list is useful only when it connects to priority, sequence tasks, relationship history, and pipeline reporting.

Account and contact boundary

Prospecting starts at the account level.

Pursenda can show configured account discovery now. Named-person contact coverage, enrichment providers, guaranteed contact accuracy, exports, and person-level attribution are scoped only when the implementation supports them.

Search result evidence

A focused list is not finished until every row explains itself.

The example rows use the approved fictional fixture and show why each account is on the list before anyone starts outreach.

AccountWhy includedNext action
Northstar ComponentsMidwest manufacturing supplier, target revenue band, operations-growth signal observed July 27, source category: account news.Maya Lee reviews operations buyer roles and assigns intro sequence.
Keystone SupplyMatches segment and territory; freshness medium; duplicate candidate resolved against prior CRM record.Assign owner before enrollment.
Harbor AnalyticsTarget industry and first-party content visit; confidence low until company fit is confirmed.Research and either suppress or open account.

Supported filters

Search uses buyer-approved criteria.

  1. FirmographicIndustry, region, size band, account type, and configured segment.
  2. FitIdeal customer profile, territory, buyer motion, disqualifiers, and source category.
  3. WorkflowOwner, saved segment, source category, freshness, confidence, and next-action status.
  4. QualityDuplicate review, stale-record marker, correction note, and suppression status.
  5. PeopleContact roles are planned only when the scoped source supports them; account discovery remains the public baseline.
  6. LimitsNo universal data coverage, named vendor claim, guaranteed enrichment accuracy, or automated list generation claim.

Source and freshness

A prospect row shows where the account came from and when it was last reviewed.

Source category, observed date, last-reviewed date, freshness status, duplicate check, owner, and suppression state keep stale data from becoming hidden truth.

Source

Configured implementations label account news, first-party activity, CRM history, list import, human research, or other approved source categories.

Freshness

Rows can show observed date, review date, age, and expiry rules by signal type.

Corrections

Duplicates, bad-fit accounts, stale records, and suppression requests create visible review states.

Actions

The end of prospecting is a decision: research, assign owner, start sequence, open opportunity, suppress, or export within the scoped terms.

Start to finish

The list becomes work only when it reaches the next action.

  1. Define ICPAgree target segment, disqualifiers, region, size band, buying motion, and source types.
  2. Build listCreate account rows with source, freshness, owner, duplicate status, and confidence notes.
  3. Review qualityResolve duplicates, stale records, unclear fit, and suppression states before enrollment.
  4. Route actionAssign research, sequence, opportunity creation, suppression, or export according to the scoped workflow.

Next step

Start with the workflow before configuration starts.

Use the working session to decide what belongs in the first configured version and what stays out of scope.