Marketing Sales Letter Framework

Workflow Pack v2.0

Marketing Sales Letter Framework

conversioncopywritingmarketingPersuasionsalesworkflow pack
ChatGPTClaudeGemini⚠ Human review required🌐 Needs web access📁 Needs project context🔌 MCP-ready⚡ Automation-ready
Health 100/100 18 📋 116 copies

Trigger Phrase

Start workflow: Marketing Sales Letter Framework

Prompt

297 words
# WORKFLOW: Marketing Sales Letter Framework

**Goal:** You are a conversion copywriter.
**Before you start:** Have your inputs ready. Work through each step in order.
**Time estimate:** 20–40 minutes.

---

## Inputs Required
- **Context**: [describe your project, goal, or situation]

---

## Step 1: Define & Frame
**Purpose:** Establish the goal, audience, and constraints before generating anything.
**Prompt:**
> Define the goal for: Marketing Sales Letter Framework
> Input: [paste your context from the inputs above]
> Return: clear goal statement, target audience, 3 success criteria, and key constraints.

**Before moving on:** Confirm the goal statement is accurate.

---

## Step 2: Generate Draft
**Purpose:** Produce the core output based on the framing from Step 1.
**Prompt:**
You are a conversion copywriter.

Inputs:
- Product/service: [product/service]
- Customer segment: [customer segment]

Write a persuasive sales letter (max 250 words): 1) relatable opening 2) agitate the pain point 3) introduce the solution 4) 3 features-as-benefits 5) one testimonial slot 6) a clear CTA.

Constraints:
- Use a [placeholder] for the testimonial and any stat - don't invent quotes or numbers.
- Natural, non-spammy tone; respect the word limit.

Output: a ready-to-edit sales letter.

**Before moving on:** Review for gaps, invented facts, or missing sections.

---

## Step 3: Refine & Quality Check
**Purpose:** Improve and verify the output before use.
**Prompt:**
> Review this output:
> [paste Step 2 output]
>
> Check: Is it specific to the inputs? Are all sections complete? Are there any invented facts or vague generics? Return an improved version with issues flagged.

**Before moving on:** Output should be ready to use with light editing.

---

## Step 4: Final Output
**Purpose:** Format for use.
**Prompt:**
> Format the final output from Step 3 for [channel/format — e.g. document, email, slide deck].
> Keep all content; improve structure and readability only.

---

## Quality Gate
Before using: confirm no placeholder text remains, no invented data, and the output matches your original goal from Step 1.

Before & After

❌ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

✅ With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Read the full workflow before starting. Install any skills listed as prerequisites. Work through steps in order — do not skip. Fill in all bracketed inputs before running each step. Use a quality gate at the end if one is linked.

Test It

Test command:
Run Step 1 of the Marketing Sales Letter Framework with a simple, real example. Confirm output matches the expected format before continuing.
Expected output:
Ever lose an evening to [pain]? ... Meet [product]: [benefit]. "[testimonial placeholder]" -
Try it today: [CTA].
Pass criteria:
  • Each step produces a usable output before moving to the next. Final output is complete and matches the stated goal. No invented data, prices, or statistics.

⚠️ Guardrails

  • Follow step order. Do not skip or merge steps. Do not start a step until the previous step's output is confirmed. Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result — ask for clarification.

📁 Context File Tip

Brand Brief context file

⚠️ Common Failure Modes

  • May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.

🔧 Fix Prompt

Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.

🎛 Available Modes

Quick Detailed Critic Final

🔌 Compatibility & Requirements

🌐 Needs web access
📎 Needs uploaded files
📁 Needs project context
👤 Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools: Web researchFile analysisConnected appsAutomation builder

🔗 Connector required — check MCP or integration docs.

⚡ Automation

n8n | Make | Zapier

📋 Upgrade Notes

Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.

💡 Suggest an improvement

Install Wizard

Choose your platform to get step-by-step install instructions: