Track results and decide what to do next.
7 workflows
A product person connects Claude Code to PostHog and a folder of company context and interview transcripts, then asks it to explain a revenue dip, a funnel drop and user segments.
A shared n8n template pulls last week's Stripe revenue, Notion deal pipeline and a Sheets row of support numbers, has Claude write a three-paragraph summary, and emails and posts it to Slack.
A founder connects five MCP servers to Claude Code, each acting as an SEO analyst, market researcher, technical auditor or product analyst, with the prompts he uses, including a weekly rage-click report.
A newsletter writer has Google Analytics and Search Console email six CSV reports each Monday, and a Claude skill compares the week to the last and saves a visual report and the raw data to a dated folder.
A public repo documents a content site's SEO system: scripts that split human from machine search queries, judge rewrites against untouched control pages, and guard against traffic drops.
A step-by-step build that tags each open-text survey response with themes, sentiment and a churn signal using a cheap Claude model, alerts on risky ones, and emails a weekly summary of themes.
A product founder describes an AI-assisted SEO process for a static site: Search Console data feeds Claude audit skills that decide whether to improve, create or reject each page, with a release check before deploy.