When to Use
User wants to improve conversion rates for websites, landing pages, SaaS products, or eCommerce. Agent runs funnel audits, designs A/B tests, interprets statistical results, and implements winning variants while maintaining legal compliance.
Quick Reference
| Topic |
File |
| A/B testing methodology |
testing.md |
| Conversion audits |
audits.md |
| Legal compliance |
legal.md |
| Tools and integrations |
tools.md |
Core Rules
1. Statistical Rigor First
- 95% confidence minimum before calling any test
- Calculate sample size before starting — underpowered tests waste time
- Run tests to full duration — early peeking inflates false positives
- Document hypothesis before running — post-hoc rationalization is not science
2. Funnel Analysis Before Optimization
- Map entire journey: awareness, consideration, decision, retention
- Quantify drop-off at each step with specific numbers
- Revenue impact per improvement — prioritize by dollars, not percentages
- Segment by traffic source, device, user type — aggregates hide insights
3. One Variable Per Test
- Isolate changes to attribute results correctly
- Multivariate testing requires massive traffic most don't have
- If you change two things and conversion improves, you learned nothing
4. Mobile-First Testing
- Test mobile variants explicitly — desktop assumptions fail on phones
- Majority of traffic is mobile, often worst conversion
- Touch targets, page speed, form friction all differ
5. Legal Compliance Non-Negotiable
- Cookie consent required in EU before tracking
- GDPR: personal data in experiments needs legal basis
- Dark patterns are illegal — fake urgency, confirm-shaming, hidden costs
- Accessibility (WCAG) is both legal requirement and conversion opportunity
6. Document Everything
- Hypothesis, variants, results, learnings in permanent record
- Losing tests are learning — document why hypothesis was wrong
- Share results across teams — wins in one funnel inform others
7. Revenue Connection
- Revenue targets tie to conversion targets — make the math explicit
- Signups mean nothing if they never convert to revenue
- Prioritize by ICE: Impact, Confidence, Ease
Common Traps
- Calling tests early because results look good — false positives waste resources
- "We changed everything and revenue went up" — no control group proves nothing
- Copy-pasting competitor tactics without context — what works for them may fail for you
- Optimizing for vanity metrics — engagement without revenue is vanity
- Testing without proper tracking setup — retroactive data is unreliable
Related Skills
Install with clawhub install <slug> if user confirms:
ceo — strategic leadershipcfo — financial planningcmo — marketing strategyanalytics — data analysis
Feedback
- If useful:
clawhub star cro
- Stay updated:
clawhub sync
1---2name: cro-chief-revenue-officer3description: Optimize conversion rates with funnel analysis, A/B testing, statistical significance, and compliance-safe experiments.4---56## When to Use78User wants to improve conversion rates for websites, landing pages, SaaS products, or eCommerce. Agent runs funnel audits, designs A/B tests, interprets statistical results, and implements winning variants while maintaining legal compliance.910## Quick Reference1112| Topic | File |13|-------|------|14| A/B testing methodology | `testing.md` |15| Conversion audits | `audits.md` |16| Legal compliance | `legal.md` |17| Tools and integrations | `tools.md` |1819## Core Rules2021### 1. Statistical Rigor First22- 95% confidence minimum before calling any test23- Calculate sample size before starting — underpowered tests waste time24- Run tests to full duration — early peeking inflates false positives25- Document hypothesis before running — post-hoc rationalization is not science2627### 2. Funnel Analysis Before Optimization28- Map entire journey: awareness, consideration, decision, retention29- Quantify drop-off at each step with specific numbers30- Revenue impact per improvement — prioritize by dollars, not percentages31- Segment by traffic source, device, user type — aggregates hide insights3233### 3. One Variable Per Test34- Isolate changes to attribute results correctly35- Multivariate testing requires massive traffic most don't have36- If you change two things and conversion improves, you learned nothing3738### 4. Mobile-First Testing39- Test mobile variants explicitly — desktop assumptions fail on phones40- Majority of traffic is mobile, often worst conversion41- Touch targets, page speed, form friction all differ4243### 5. Legal Compliance Non-Negotiable44- Cookie consent required in EU before tracking45- GDPR: personal data in experiments needs legal basis46- Dark patterns are illegal — fake urgency, confirm-shaming, hidden costs47- Accessibility (WCAG) is both legal requirement and conversion opportunity4849### 6. Document Everything50- Hypothesis, variants, results, learnings in permanent record51- Losing tests are learning — document why hypothesis was wrong52- Share results across teams — wins in one funnel inform others5354### 7. Revenue Connection55- Revenue targets tie to conversion targets — make the math explicit56- Signups mean nothing if they never convert to revenue57- Prioritize by ICE: Impact, Confidence, Ease5859## Common Traps6061- Calling tests early because results look good — false positives waste resources62- "We changed everything and revenue went up" — no control group proves nothing63- Copy-pasting competitor tactics without context — what works for them may fail for you64- Optimizing for vanity metrics — engagement without revenue is vanity65- Testing without proper tracking setup — retroactive data is unreliable6667## Related Skills68Install with `clawhub install <slug>` if user confirms:69- `ceo` — strategic leadership70- `cfo` — financial planning71- `cmo` — marketing strategy72- `analytics` — data analysis7374## Feedback7576- If useful: `clawhub star cro`77- Stay updated: `clawhub sync`
johnalbertini14-glitch