46 lines
1.5 KiB
Markdown
46 lines
1.5 KiB
Markdown
|
# Marketing Content
|
||
|
|
|
||
|
|
## Purpose
|
||
|
|
|
||
|
|
Create external-facing content that explains, promotes, or launches product capabilities in a way that is accurate, audience-aware, and compelling.
|
||
|
|
|
||
|
|
## When to use
|
||
|
|
|
||
|
|
- Drafting launch posts, emails, feature pages, announcements, or social content
|
||
|
|
- Turning product or engineering work into outward-facing communication
|
||
|
|
- Adapting one core message into multiple channels
|
||
|
|
- Creating content tied to a release or campaign
|
||
|
|
|
||
|
|
## Inputs to gather
|
||
|
|
|
||
|
|
- Audience, channel, and desired action
|
||
|
|
- The actual product change or offer being communicated
|
||
|
|
- Supporting proof points, examples, and differentiators
|
||
|
|
- Voice, tone, and length constraints
|
||
|
|
|
||
|
|
## How to work
|
||
|
|
|
||
|
|
- Lead with why the audience should care.
|
||
|
|
- Ground claims in the real product and its benefits.
|
||
|
|
- Structure content so it is easy to scan and repurpose.
|
||
|
|
- Tailor tone and density to the channel instead of reusing the same draft everywhere.
|
||
|
|
- Keep technical explanations accurate while translating them into audience-relevant outcomes.
|
||
|
|
|
||
|
|
## Output expectations
|
||
|
|
|
||
|
|
- A polished draft for the requested channel
|
||
|
|
- Supporting variations or headline options when useful
|
||
|
|
- Clear call to action where appropriate
|
||
|
|
|
||
|
|
## Quality checklist
|
||
|
|
|
||
|
|
- The content is audience-centered, not feature-dump centered.
|
||
|
|
- Claims are specific and defensible.
|
||
|
|
- The narrative is easy to scan and follow.
|
||
|
|
- The output matches the requested medium and length.
|
||
|
|
|
||
|
|
## Handoff notes
|
||
|
|
|
||
|
|
- State which audience and channel the draft targets.
|
||
|
|
- Pair with messaging/positioning when the strategic framing is not yet settled.
|