> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rippit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Marketing Insights

> Build messaging on your buyers' pains, not your feature list.

**B2C** · Marketing · For Product marketing managers · Also for [B2B companies](https://docs.rippit.com/use-cases/product-marketing-insights-b2b.md)

This agent captures the words customers use for their pains, goals and the value they get, across reviews, social posts, support chats and calls. It sorts them by customer segment, compares them with your messaging docs, and drafts the updates and copy to match.

## What it reads

Sales and CS calls from tools like Gong, support conversations from tools like Zendesk or Intercom, web research tables on reviews, forums and communities, and your messaging docs, personas and launch briefs uploaded as files. Anything else can come in through a CSV or the Bulk API.

## How it works

1. **Ingest.** Every buyer conversation next to your messaging.
2. **Analyze.** Where buyers say it differently than you do.
3. **Act.** Messaging that stays current, with copy drafted.

## What you get

Messaging updates and copy, sorted by persona.

* **Messaging docs** (Notion or Google Docs): 6 updates across 3 segments, led by a new pain for busy parents.
* **Copy drafts** (Notion or Google Docs): Email and landing page copy, built on the new pains.
* **Any tool you connect through MCP:** Post new proof points to the sales channel in Slack, or send them to any tool you connect through MCP.

## Build it

Tell Rippit chat to "set up messaging updates by persona, built from the words buyers use for their pains and goals," or ask your own AI assistant with Rippit connected. Rippit drafts it as a [pipeline](https://docs.rippit.com/pipelines/overview.md), tests it on a sample, and puts it live when you confirm. You can change what it reads, how it scores, who it notifies, and how often it runs at any time.

## Questions

> [accordion] How does it tell pains, goals and value apart?
>
> It reads each conversation in full and tags what customers say: a pain is a problem they want gone, a goal is what they're trying to achieve, and value is the result they got or expect. You can add your own categories, like objections or use cases.

> [accordion] Does it work with our messaging framework?
>
> Yes. It uses the messaging docs, segments and positioning in your knowledge base as the baseline, and suggests updates in the same structure.

> [accordion] Will it change our docs on its own?
>
> You decide. It can update your docs directly or suggest changes for your review, with the quotes behind each one.

> [accordion] Where do the results go?
>
> Your messaging docs and copy drafts go to Notion or Google Docs, with a summary in Slack or email and anything else sent to a tool you connect through MCP. It runs weekly by default, and can run daily or hourly.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.