What comes in, and what goes out.
Two halves of one system. Research arrives from the places your customers actually talk, gets filed against what you already know, and leaves as a draft in a tool your team already opens. Nothing publishes itself.
Research · what comes in
Where it listens.
Swept nightly. Not all of these apply to every brand, and the ones that do not stay switched off rather than padding a report.
spot-mitt.png1024 × 1024| Source | What it gives us | Where it stops |
|---|---|---|
| Google SERP | What people type, and how the results page answers it | Volume is modelled, not metered |
| Google Trends | Relative interest over time, and what is rising underneath a term | Relative, so it never gives you an absolute count |
| How people talk when they are not talking to a brand | Thin in categories with no active subreddit | |
| TikTok | Posts snapshotted daily, ranked by how fast they are moving | Public posts only |
| The same daily snapshots, plus comments on your own posts | Public posts only | |
| How a category talks about itself in public | Useful for B2B, quiet for most consumer brands | |
| Yelp | Reviews with the complaint attached to the thing complained about | Local businesses only |
| Tripadvisor | The same, for anywhere people travel to | Hospitality and travel only |
| Amazon reviews | What buyers say after the purchase, per product | Only where you actually sell |
| Your own site | What you already claim, so nothing contradicts it | Needs to be crawlable |
Delivery · what goes out
Where it publishes.
Always as a draft, in that channel's native format, so the last edit and the publish button both stay with a person. If a channel is not here, the API is, and it returns the same work as plain JSON.
spot-throw.png1024 × 1024| Channel | What it gives us | Where it stops |
|---|---|---|
| WordPress | A draft post, with your formatting and media library | Needs an application password |
| Shopify | A draft blog article or a product description | Draft only, never published live |
| Any website | Clean HTML, or the raw fields, through the API | You wire the last step |
| A ready-to-send campaign, formatted for the inbox | A person still presses send | |
| Mailchimp | A draft campaign in your account | Draft only |
| Substack | A draft post | Draft only |
| A caption and the asset, staged for review | Scheduling is on you | |
| TikTok | The same | Scheduling is on you |
| API and webhooks | Everything above, as JSON, on your own schedule | Nothing, this is the escape hatch |
Reading your own data from the Claude app you already use is a separate thing. That is the MCP server.
Request access