PlaysbyMoat8
Back to the library
The workflow guideFinance

Draft investor outreach with a specific reason to connect

Prepare a short introduction around an investor’s stated interests and a verifiable company proof point. Produce drafts for review, including a forwardable introduction or a follow-up when relevant.

5 implementation stepsSimple

How this works

Prepare a short introduction around an investor’s stated interests and a verifiable company proof point. Produce drafts for review, including a forwardable introduction or a follow-up when relevant. Use this to prepare a concise introduction based on a recipient's stated investment interests and one verified company proof point. Personalization should explain a real fit rather than imply a relationship or interest that does not exist.

Research current professional investment focus from primary public material or permitted records, match it to approved company facts, and draft one clear request. Keep forwardable introductions and follow-ups tied to actual context and new information. All messages remain drafts until sending is explicitly authorized.

Before you start

Approved company facts

Select verified traction or product evidence that may be shared.

Recipient context

Use current stated focus, stage and relevant prior interaction.

Outreach purpose

Confirm the requested meeting, introduction or follow-up and available materials.

Prepare the inputs

recipient
Required

verified professional identity and contact source

Do not guess email addresses or conflate similarly named people.

investment_focus
Required

source-backed stage, sector and geography

Record source date and unknown criteria.

company_proof
Required

claim, metric definition, period and evidence

Use only approved, substantiated statements.

relationship_history
Required

prior contact and promised follow-ups

Do not invent familiarity or prior agreement.

Implementation, step by step

  1. Verify recipient fit

    • Read relevant current professional sources and identify the stated investment criteria.
    • Separate known focus from inferred possible interest.

    Checkpoint: A short fit note cites its evidence.

  2. Choose the proof point

    • Select one company fact that directly relates to the recipient's focus.
    • Check its definition and sharing approval rather than using the largest unsupported number.

    Checkpoint: The message has a defensible reason to connect.

  3. Draft the introduction

    • Write a short context sentence, proof point and one specific request.
    • Use natural language and avoid fabricated praise or implied endorsements.

    Checkpoint: A concise draft fits the requested channel.

  4. Adapt the format

    • Prepare a forwardable introduction or follow-up only when the relationship context supports it.
    • For follow-ups, add new information or answer a promised question rather than manufacture urgency.

    Checkpoint: Each variant has a clear purpose.

  5. Review facts and state

    • Check recipient details, claims, attachments and the proposed ask.
    • Record draft status and send only if that exact action is authorized.

    Checkpoint: The owner can review a concrete message.

Decisions along the way

Investment criteria are unclear

Use a modest exploratory draft or flag insufficient fit evidence.

No new follow-up information

Avoid pretending there is an update; draft a simple check-in only if requested.

Proof point is confidential

Choose an approved alternative or leave it out.

What you will produce

investor-outreach-drafts.md

Markdown

Reviewable messages grounded in approved facts.

Include: recipient · fit_reason · subject · body · ask · status

outreach-evidence.csv

CSV

A small provenance record supporting personalization.

Include: recipient · focus_source · proof_source · unknowns

Check the result

  • Verify recipient identity and current professional role.
  • Trace the fit claim and proof point to evidence.
  • Confirm no prior relationship or endorsement was invented.
  • Check there is one clear request and no unauthorized attachment.

When something goes wrong

Public focus information is stale

Mark uncertainty and seek a current source before asserting fit.

Company metric changes

Refresh the proof point and all dependent drafts.

Delivery status is unknown after authorized sending

Check message history before retrying.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: draft an introduction to a seed investor.

Inputs

Public focus states B2B workflow software at seed stage. Approved company fact: ten paying teams as of 30 June. There has been no prior contact.

Expected result

Synthetic result: mention the shared B2B workflow focus and ten paying teams with the correct period, then ask for a short introductory call. Do not claim the recipient already expressed interest.

Run a small pilot

Start small

Prepare a small reviewed set for recipients with explicit public criteria.

Record the baseline

Record research time and factual or fit corrections.

Agree success criteria

Agree personalization quality and claim accuracy before preparing a larger set.

Stop or revise

Stop drafting when recipient identity or approved proof points cannot be verified.

Keep the scope clear

  • Researching professional fit does not authorize sending messages.
  • The workflow cannot establish investor interest, endorsement or likelihood of funding.

Check before using

Verify recipient details and claims. Approve each message before sending; the workflow does not establish investor interest.

Business activities

  • Raise capital or evaluate investments

Editorially adapted workflow; not independently tested.

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: Investor interests and relevant public work · Verified company facts and the desired next step

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗