Ask Claude. WhyUser tests, fixes and saves the work.
WhyUser in Claude is WhyUser’s MCP server and skill. Marketers ask Claude to test, fix and ship campaigns, and every run is saved in WhyUser.
Start with WhyUser: Name the page, and the committee or persona. WhyUser tests it, then revises it from the fixes.
WhyUser’s MCP server and skill for Claude Code, the Claude desktop app and claude.ai. Marketers ask Claude to test, fix and ship campaigns, and every run is saved in WhyUser.
Test a page, ad or email sequence, then have WhyUser revise the page or sequence from the fixes. It also writes persona messaging and finds patterns across runs. One request does it all, such as “WhyUser: test example.com/pricing with the Platform committee, then revise it from the fixes”.
No. Start the request with WhyUser, so Claude uses the WhyUser skill. Name the page and the committee or persona. For Audience Discovery, name the page and its industry.
Yes, through Claude’s own connectors and your own access. Claude reads your guidelines and writes tickets, audiences, sequences and briefs. WhyUser never needs those logins, and facts from your tools are flagged for review.
Yes. An admin sets each person to off, read only, or read and run, with a credit cap. Claude shows the price before every run, and no key can delete anything.
Create a key in WhyUser under Settings → AI assistant access. In Claude Code, run /plugin marketplace add WhyUserLabs/skills, then /plugin install whyuser@whyuser. For the desktop app and claude.ai, follow the setup guide.
/plugin marketplace add WhyUserLabs/skills
/plugin install whyuser@whyuser