Find relevant contacts for a potential collaboration
Research a target organization and its public team profiles to prepare a focused collaboration approach. The practitioner described using this to identify a suitable research contact.
How this works
Research a target organization and its public team profiles to prepare a focused collaboration approach. The practitioner described using this to identify a suitable research contact.
Find an organizational contact whose current responsibilities align with a specific collaboration proposal. Prioritize evidence of relevant work and a credible reason to approach, not a broad list of impressive titles.
Before you start
Defined operating scope
A collaboration proposal needs a relevant professional contact inside a target organization.
Required source material
Obtain Target organization; Your expertise and proposed collaboration. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
The relevant person has left the organization. Mark the role stale and research the current responsible team.
Prepare the inputs
- target_organization
- Required
Official entity and domain
Resolve labs, divisions or subsidiaries.
- collaboration_brief
- Required
Proposed work and mutual relevance
State a bounded idea and available expertise.
- public_profiles
- Required
Professional roles and work references
Record dates and source reliability.
- contact_constraints
- Required
Permitted business channels and exclusions
Respect stated contact preferences.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check target_organization, collaboration_brief, public_profiles, contact_constraints before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected target_organization and any missing required fields.
Review the organization and relevant public team profiles
- Review the organization’s current work and the public teams most connected to the collaboration brief.
- Verify current role and project relevance for every shortlisted contact.
Checkpoint: A saved intermediate result for: Review the organization and relevant public team profiles.
Prepare short evidence-backed contact briefs
- Prepare short contact notes identifying relevant projects, current role evidence and unresolved identity details.
- Check every claim about the sender’s expertise against the provided brief.
Checkpoint: A saved intermediate result for: Prepare short evidence-backed contact briefs.
Compare potential contacts against the collaboration goal
- Compare contacts by role relevance and plausible ownership of the proposed collaboration, preserving alternatives.
- Verify current role and project relevance for every shortlisted contact.
Checkpoint: A saved intermediate result for: Compare potential contacts against the collaboration goal.
Draft a tailored introduction for the selected person
- Draft a concise introduction grounded in actual shared subject matter and a modest next step, without implying a prior relationship.
- Check every claim about the sender’s expertise against the provided brief.
Checkpoint: A saved intermediate result for: Draft a tailored introduction for the selected person.
Package the result and unresolved work
- Verify current roles and source facts before writing. A person sends the message; the reported reply does not establish a general response rate.
- Use public professional information and permitted business contact paths.
Checkpoint: A contact shortlist and an introduction draft. Unresolved items remain visible in the review record.
Decisions along the way
The relevant person has left the organization.
Mark the role stale and research the current responsible team.
Only a broad executive title is available.
Keep the contact tentative and seek evidence of relevant responsibility.
The proposal claims expertise unsupported by the user’s brief.
Remove the claim and ask for factual supporting material.
What you will produce
research-partnership-entry-points-result.json
JSONA contact shortlist and an introduction draft. Label proposed and completed states separately.
Include: contact_reference · role_evidence · relevant_work · collaboration_fit · uncertainties · introduction_draft · status · evidence_reference · review_note
research-partnership-entry-points-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving contact_constraints.
Include: source_reference · question · owner · next_action
Check the result
- Verify current role and project relevance for every shortlisted contact.
- Check every claim about the sender’s expertise against the provided brief.
- Inspect target_organization and collaboration_brief in both the original and output; confirm that record identity and interpretation survived the transformation.
- Verify current roles and source facts before writing. A person sends the message; the reported reply does not establish a general response rate.
When something goes wrong
The relevant person has left the organization.
Mark the role stale and research the current responsible team. Retain the affected evidence and recovery status.
Only a broad executive title is available.
Keep the contact tentative and seek evidence of relevant responsibility. Retain the affected evidence and recovery status.
The proposal claims expertise unsupported by the user’s brief.
Remove the claim and ask for factual supporting material. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Find relevant contacts for a potential collaboration for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Proposal concerns evaluation methods. Public profile P-3 leads infrastructure, while P-4 authors current evaluation work for the target team.
Expected result
Synthetic expected result: Shortlist P-4 for stronger topic alignment, noting current-role verification. Draft asks whether a short exchange about evaluation methods would be useful; no prior meeting is implied.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure contact relevance confirmed by the owner; substantive replies per approved approach.
Stop or revise
The proposal claims expertise unsupported by the user’s brief. Pause affected records and apply this recovery: Remove the claim and ask for factual supporting material.
Keep the scope clear
- Use public professional information and permitted business contact paths.
- Prepare an introduction draft; sending and relationship claims remain under the user’s control.
Check before using
Verify current roles and source facts before writing. A person sends the message; the reported reply does not establish a general response rate.
Business activities
- Find and approach prospects
- Research customers and markets
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Target organization · Your expertise and proposed collaboration
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow