---
name: outreach-composer
description: "Prepare personalized outreach and follow-up drafts. Use for this workflow with supplied business information."
---

# Outreach composer

## Inputs and purpose

Use this workflow to prepare: Personalized outreach and follow-up drafts.

Start with: Writing samples, supplied prospect facts and offer.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Read the supplied writing samples, prospect facts and offer. Identify tone patterns that can be reused without copying private details.

2. Choose an evidence-backed reason for contact and a clear, low-friction requested response.

3. Draft the initial message and follow-up variants that add useful information rather than pressure.

4. Return copy and factual review notes. Never invent a prior relationship, personal event or customer result to create personalization.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).