version: "1.0.0" name: "cold-email-doctrine" description: "Draft concise, evidence-based cold outreach using the target project's current buyer, approved offer and campaign boundaries. No embedded sender state, platform benchmark or legacy product scope." license: MIT metadata: version: 2.0.0 author: Build n Bloom category: sales domain: cold-outreach updated: 2026-09-27

Cold outreach drafting method

Read the target project's current offer, buyer definition, approved claims and campaign instructions first. The earlier NDIS Referral Agent doctrine, benchmark numbers, n8n instructions and fixed cadence are preserved in the archive. They are historical context, not current sending rules.

Required context

Record the intended audience, recipient-specific evidence, reason the problem may matter, approved next step, and any existing relationship or exclusion. Missing evidence stays unknown. Do not invent a compliment, result, mutual relationship, first-hand experience or urgency.

Draft

• Use the buyer's own operational language and one concrete observation.
• Connect the observation to a plausible problem; label a hypothesis as a question.
• Explain the relevant offer without adding a price, guarantee or unsupported result.
• Use one clear, low-burden next step appropriate to the relationship.
• Keep the message concise, plain and specific. Follow the project's actual voice rules.

Return the draft alongside source references for each factual claim, assumptions and any unresolved campaign input. Example copy is never evidence of a client result.

Review and operation

The campaign owner supplies the permitted recipient list, contact basis, suppression/opt-out handling, actual sender account, platform settings, cadence and approval scope. Check these against the current project and provider before activation. This skill authorises drafting only; it does not authorise sending, enrollment, CRM mutation or changes to sender infrastructure.

Measure replies, qualified conversations and downstream outcomes using dated provider records and clear denominators. Do not inherit numeric performance expectations from an old example or present an observed result as a guarantee.