Marketing collateral

Based on this meeting transcript, produce a capability brief that
translates what the product does into the outcomes customers gain.

Be faithful to the source — only describe capabilities that were
actually shown or described. If a capability was mentioned but not
detailed, note "Detail needed from product team."

Use customer language where the meeting captured it (verbatim quotes
from customers, user-side framings). Avoid internal jargon, product
code names, and feature-list framing unless the audience is internal.

Do not use vague qualifiers — "seamless," "intuitive," "industry-leading."
Use specific, evidence-grounded language.

Audience: {Specify — internal sales, prospects, existing customers}

Format:

# {Capability / Feature / Product Module Name}
**Audience:** {from above}
**Source:** {Meeting name — date}
**Owner:** {Name}

## The customer problem this solves
Two to three sentences in customer language. What were they doing
before? What was painful about it? Use verbatim phrasing if it came up
in the source meeting.

## What it is (in one line)
A single sentence describing the capability. Outcome-led, not
feature-led. The sentence sales reps will memorize.

## What it does
Three to five bullets grouped by user-visible outcome, not by
technical feature. For each:
- **{Outcome the customer experiences}:** what specifically the
  capability does to deliver it.

## Why this matters
- {Strategic benefit}
- {Operational benefit}
- {Outcome they can measure}

## How it works (when audience needs it)
For technical or evaluation-stage audiences:
- Brief technical context
- Architecture, integration, requirements

## Who it's for
- **Primary persona:** {role / use case}
- **Secondary personas:** {list}
- **Not for:** explicit exclusions — situations where this isn't the
  right fit

## Common objections and responses
For sales-facing briefs:
- **Objection:** "{language reps actually hear}"
  **Response:** {grounded answer with evidence}

## Proof points
- {Specific outcome with metric where possible}
- Customer quote: "..." (if from a captured meeting)

## Competitive context
- **vs. {Alternative}:** {differentiator}
- **vs. status quo:** {why act now}

## Sales talking points (for internal briefs)
Three to five phrases sales reps can take verbatim into customer
conversations.
- "{phrase}"
- "{phrase}"
- "{phrase}"

## Resources
- {Demo link if applicable}
- {Documentation}
- {Customer references}

Based on this meeting transcript, produce customer-facing marketing
copy. Audience is prospects or customers; the copy needs to capture
attention, communicate value, and prompt action — in that order.

Use the customer's own language wherever the source meeting captured
it. If you're tempted to use a buzzword, find what the customer
actually said instead.

Be specific. "Save time" doesn't sell; "stop spending two hours every
Monday reconciling reports" does.

No emojis unless brand voice specifically calls for them. No
superlatives without evidence ("the best," "the leading" — cut unless
quantifiably true).

Audience: {TOFU prospect, MOFU evaluator, existing customer, specific
persona}

Format:

# {Asset name — what this copy is for}
**Audience:** {from above}
**Channel:** {Landing page | Email | Ad | Blog}
**Goal:** {Primary action you want the reader to take}
**Source:** {Meeting(s)}

## Headline
The single line that has to earn the rest of the read. Use the
customer's framing of the pain or outcome. Test it against: would the
customer recognize themselves in this headline?

**Headline option 1:** "..."
**Headline option 2:** "..."
**Headline option 3:** "..."

## Subhead
One to two sentences that follow the headline. Makes the headline's
promise concrete enough that the reader keeps reading.

## Body — the case

### What's broken (the problem)
Two to three sentences. The customer's pain in their language. Use
verbatim quotes from the source meeting where they captured the pain.

### What's different (the offer)
Two to three sentences. What this product or feature does that solves
the pain. Outcome-led; not feature-listed.

### Why it works (the proof)
One to three specific proof points:
- A specific outcome customers have achieved
- A way the product mechanically addresses the pain
- A quote from a real customer (with attribution if shareable)

### What it costs / what's required
If commercial details are relevant.

## Call to action
What you want the reader to do. Verb-led, specific.
- **Primary CTA:** "{verb-led action}"
- **Secondary CTA (if applicable):** "{lighter action}"

## Frequently asked
Three to five questions the audience would have at this stage.

## Customer voice
If the source meeting had quotable customer language:
> "{verbatim quote}"
> — {attribution if shareable}

## What this is NOT
For artifacts where misalignment risks are real: clarify what this
isn't, who it isn't for, when this isn't the right fit. Counter-
intuitively strengthens credibility.

## SEO and metadata (for web artifacts)
- **Title tag:** {variant of headline}
- **Meta description:** {under 160 chars}
- **Primary keyword:** {based on source customer language}

Based on this meeting transcript (a launch planning meeting, exec
strategy discussion, or product review for an upcoming launch),
produce a launch announcement. The artifact answers: what changed,
why now, what does it mean for {audience}, what should they do.

For press releases specifically: standard PR format. Lead with the
news. Quote the founder/CEO with the strategic narrative.

Format:

# {Launch name}
**Type:** Press release | Blog post | Customer email | All-hands
**Audience:** Press | Customers | Employees | Prospects
**Publish date:** {date}
**Source:** {Meeting(s)}

## Headline
**Headline:** "{news headline}"
**Subhead:** "{strategic context in one sentence}"

## Lead paragraph
For press releases: who, what, when, where, why — standard inverted
pyramid. Two to three sentences. If a reader stops here, they have
the news.

For blog posts: an engaging opening that earns the rest of the read.

## The news (what's launching)
One to two paragraphs. What's actually launching, in the language the
audience cares about.

## Strategic narrative
Why this matters. The big-picture frame the founder or exec articulated
in the source meeting. Use verbatim phrasing where it landed well.

> "Quote from founder or CEO — extracted from source meeting,
>  attributed correctly, captures the strategic message in their voice."

## What this means for {primary audience}
The "so what" layered on top of the news.

## Detail / supporting points
Three to five supporting points:
- {Capability or change}
- {Customer or partner context if applicable}

## Voices in the announcement
Quotes that round out the announcement — founder/CEO for strategic
narrative; product lead for what's launching; customer if willing to
be quoted; partner/investor where relevant.

## Availability and next steps
- **Available when:** {date}
- **Available to whom:** {customers / segments / tiers}
- **How to access:** {URL, sign-up, contact sales}

## Boilerplate (for press releases)
- **About {Company}:** {standard boilerplate}
- **Media contact:** {name, email}

## Distribution plan
- Primary publication
- Secondary distribution (email, social, partner co-marketing)
- Press outreach if applicable
- Internal communication
- Customer communication

Based on this meeting transcript (a strategy discussion, positioning
workshop, or exec narrative session), produce a messaging pillars
document. This artifact governs how the company talks about {topic}
across all channels.

Be faithful to the source. If the meeting articulated specific
phrasings or framings, preserve them.

Format:

# Messaging Framework: {Topic / Product / Category}
**Status:** Draft v1.0
**Source discussions:** {Meeting names — dates}
**Approved by:** {Required approvers}
**Owner:** {Name}
**Review cadence:** Quarterly | Annual

## The market context
Two to three sentences. What's true about the market we're operating
in. What's shifting. Why this messaging matters now.

## The customer we serve
- **Primary persona / segment:** who
- **What they care about:** their stated priorities
- **What they're worried about:** their stated concerns
- **What they don't yet realize:** the insight we're bringing

## The category we're in (or creating)
- **Established category name:** if existing
- **How we describe our position in it:** language
- **If creating a new category:** name, definition, why this category
  needs to exist

## Our core message
The single sentence that everything else supports.

> "{The core message, in one sentence}"

## Messaging pillars
Three to five pillars that support the core message.

### Pillar 1: {Pillar name}
- **Pillar message:** "{one-sentence framing}"
- **What we say:** language we use to express this pillar
- **Evidence:** specific proof points, customer outcomes, capabilities
- **What this counters:** common alternative views or competitor
  positioning this pillar argues against
- **Sample applications:** how this pillar shows up in specific
  artifacts (web copy, sales talk tracks)

### Pillar 2: {Name}
[Same structure]

[Repeat for three to five pillars]

## Anti-messaging
What we explicitly do NOT say. Phrasings and positions to avoid.
- {Anti-phrasing} — why we avoid it
- {Anti-phrasing} — why we avoid it

## Competitive positioning
For each material competitor or alternative:
- **vs. {Competitor}:** how we differentiate; language we use; language
  we avoid
- **vs. status quo:** why act on this rather than not

## Customer voice
Three to five verbatim quotes from real customer conversations
(extracted from source meetings) that exemplify how customers describe
the value or the pain in their own language.

> "{Quote}" — {Persona / segment}

These quotes are the corpus that downstream marketing copy should
draw from. Match the voice; don't invent new framings.

## Specific language guidance
- **Preferred terms:** use these
- **Avoided terms:** don't use these

## Application across the GTM motion
- **Web copy:** implications
- **Sales enablement:** implications
- **Content marketing:** implications
- **Internal communications:** implications

## What this doesn't cover
Topics or audiences that need their own framework.

## Change log
[Version table]

Across the customer interviews provided, identify the most common
ways customers describe {pain / outcome / use case}. For each pattern:

- The phrasing customers use (with verbatim quotes)
- How many calls it came up in
- Which customer segments use it
- Adjacent phrasings that mean similar things

The output is a customer-language corpus that downstream marketing
copy should draw from.

The messaging pillar is: "{pillar message}"

Across the customer conversations provided, identify:
- Moments where customers expressed something aligned with this
  pillar (with quotes)
- Moments where customers expressed something orthogonal or
  contradictory
- Specific phrasings the pillar might adopt to land better with
  customers