research-prospect

name	research-prospect
description	Research prospects from attributable, non-sensitive sources.
metadata	{"short-description":"Research prospects with attributable sources"}

Research Prospect

Outcome

A concise prospect brief that separates verified facts, relevant signals, hypotheses, and outreach implications.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Target organization or person, sales objective, existing CRM context, authorized internal sources, and current public sources when web access is available.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Resolve the exact entity before research and state ambiguity when names collide.
2. Prefer primary and current sources for company facts, initiatives, leadership, products, and material events; date every time-sensitive claim.
3. Collect only information relevant to the business purpose and avoid sensitive or intrusive personal details.
4. Convert facts into clearly labeled sales hypotheses and validation questions rather than asserting needs.

Required output

• Identity and source note
• Company or role snapshot
• Current signals
• Relevant CRM history
• Hypotheses and questions
• Source links

Actions and boundaries

Do not write research to the CRM or contact the prospect without explicit approval.