Prospect research decision surface
Prospect research breaks pipeline speed when teams keep researching after the route is already clear.
Use a minimum research packet to decide enough, not enough, enrich, or skip in minutes so each prospect moves to a real next action.
The research leak
Long research notes do not help if they do not change route.
Prospect research should answer one operational question: is there enough verified context to route this lead and write the first useful message?
When research becomes a profile-completion project, teams lose throughput, hide uncertainty, and create decorative notes that cannot support a route decision.
Central action object
Minimum research packet builder
Paste the company, role, signals, and channels. Return a packet that decides if research is enough for route or still unknown.
Copy-ready prompt
You are a prospect research assistant for sales routing.
Input:
PROSPECT_INPUT:
[PASTE COMPANY, CONTACT ROLE, PUBLIC SIGNALS, KNOWN PROBLEM CLUES, AVAILABLE CHANNELS, AND CRM NOTES]
ROUTE_GOAL:
[WRITE THE NEEDED DECISION: PURSUE, NURTURE, ENRICH, OR SKIP]
Task:
Build one minimum research packet and decide whether research is enough.
Return this exact output format:
- company and role snapshot
- visible fit signal
- probable pain area
- reachable channel
- confidence level
- unknowns that block route
- decision (enough, not enough, enrich, skip)
- routing-ready next action
Decision criteria:
Prioritize route readiness, evidence quality, and risk of fake personalization.
Rules:
- keep unknown fields visible instead of inventing context;
- cite source evidence for each signal;
- if one missing fact blocks route, choose enrich and name the fact;
- if fit is weak or unreachable, choose skip;
- keep output operational and short.
QA loop:
Flag any claim with no source and rewrite as Unknown.
Decision rule
Use enough / not enough / enrich / skip before writing outreach.
| Decision | Use when | Route action |
|---|---|---|
| enough | Fit, pain clue, and reachable channel are explicit. | Create routing-ready record and move to scoring or outreach. |
| not enough | Signal exists but core evidence is thin. | Collect one missing field fast, then re-run decision. |
| enrich | Unknown company/role/channel blocks safe route. | Enrich minimum fields only, then score and route. |
| skip | Weak fit, no reachable channel, or irrelevant signal. | Mark skip with reason code and remove from active queue. |
Example input
Turn company notes into a routing-ready research packet.
- Company
- Northstar Operations Group
- Role
- Head of Revenue Operations
- Visible signal
- Hiring SDRs and documenting handoff ownership in job listings.
- Probable pain
- Lead follow-up leakage and inconsistent routing.
- Channel
- Email and LinkedIn available.
- Unknown
- Account status and current CRM process maturity.
Example output
Company → research notes → routing-ready record.
decision
enough for scoring and route initialization; enrichment can run in parallel for account status.
confidence
Medium-high. Fit signal and pain are explicit, unknowns are acknowledged.
routing-ready record
Assign to sales-ops workflow queue with reason: revenue operations role plus handoff pain signal.
unknown handling
Mark account status Unknown and request enrichment before final owner handoff.
next action
Run lead scoring, then prepare first-message angle tied to routing leakage.
Quality boundary
Minimum research is valid only when uncertainty is explicit.
Evidence over polish
One real signal beats long speculative notes.
Unknown is allowed
Unknown fields should trigger enrich or review, not fake detail.
Route first
Stop research once you can safely choose the next route action.
Reuse packet
Research packet should feed scoring and outreach angle without rework.