Files of Conversion optimization artifact templates
wondelai/
Show the full text200 lines
conversion-optimization artifact templates
Skeletons for every docs/ file this journey writes. Read the file before writing: if it is missing, create it from the full skeleton below (all section headings), then fill only the sections your phase names; if it exists, extend it — add or update your sections and preserve everyone else's. Creating a file from a partial set of headings is the drift these skeletons exist to prevent.
Tracker: docs/CONVERSION-OPTIMIZATION-PLAN.md
Created on the first run (Intake). Never shared with another journey.
# Conversion Optimization Plan
## Context
Intake answers, date started, the flow and its ONE action, project specifics.
Mode: skills-installed | fallback (Briefs + references/methods.md) — set at the first phase, so a
resumed session knows whether earlier artifacts are skill-grade or Brief-grade.
## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1 | lean-analytics | pending | METRICS.md | |
| 2 | cro-methodology | pending | FUNNEL.md, EXPERIMENTS.md | |
| 3 | storybrand-messaging | pending | POSITIONING.md, FUNNEL.md, EXPERIMENTS.md | |
| 4 | hundred-million-offers | pending | OFFER.md, EXPERIMENTS.md | |
| 5 | influence-psychology | pending | FUNNEL.md, EXPERIMENTS.md | |
| 6 | design-everyday-things | pending | FUNNEL.md, DESIGN.md, EXPERIMENTS.md | |
| 7 | cro-methodology | pending | EXPERIMENTS.md, METRICS.md | |
Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>
A phase parked at `awaiting-evidence` carries a Next Actions row naming the evidence owed, its owner,
and the date — otherwise the next session cannot tell what it is waiting for.
## Key Decisions
| Date | Phase | Decision | Rationale |
|---|---|---|---|
## Next Actions
- [ ] action (owner, due)
docs/FUNNEL.md
One conversion flow end to end — its steps, why people drop, and what answers each doubt. Creates: conversion-optimization.
# Conversion Flow
## Flow Map & ONE Action
Flow scope (entry → conversion), the single action each step drives, competing CTAs cut.
| Step | ONE action | Current message/CTA | Proposed message/CTA | Notes |
|---|---|---|---|---|
## Leak Diagnosis
Why each step loses people. METRICS.md `## Funnel` stays canonical for the conversion numbers; this
table adds the researched reason and severity, and cites those numbers rather than restating them.
| Stage | Baseline | Benchmark | Evidence for why | Severity |
|---|---|---|---|---|
## Objections & Counters (O/CO)
| Objection (Big 5) | Evidence (customer words) | Counter | Placement | Status |
|---|---|---|---|---|
## Proof Inventory
| Asset | Type | Placement | Status |
|---|---|---|---|
## Flow Friction Audit
| Step | Issue | Severity (0-4) | Fix | Status |
|---|---|---|---|---|
docs/METRICS.md
What we measure and current baselines.
# Metrics
## Stage & One Metric That Matters
OMTM · counter-metric · why now.
## KPI Definitions
| Metric | Definition | Actionable ratio? | Owner |
|---|---|---|---|
## Baselines & Targets
| Metric | Baseline (date) | Target | Line in the sand (miss response) |
|---|---|---|---|
## Funnel
| Stage | Conversion | Benchmark | Bottleneck? |
|---|---|---|---|
## Cohort Notes
docs/EXPERIMENTS.md
Every test we run, with pre-committed criteria.
# Experiments
## Experiment Cards
### EXP-001 — [name]
- Hypothesis: We believe [outcome] if [who] [does what] because [reason]
- Type: sprint / smoke test / concierge / painted door / A-B
- Primary metric & threshold (pre-committed):
- Guardrail metric:
- Decision rule (pivot / persevere / iterate):
- Result & verdict:
## Experiment Backlog
| Idea | ICE (impact/confidence/ease) | Status |
|---|---|---|
docs/POSITIONING.md
How the market should understand us — positioning canvas and messaging in one file.
# Positioning & Messaging
## Competitive Alternatives
## Unique Attributes → Value Themes
| Attribute | Value ("so what") | Proof |
|---|---|---|
## Best-Fit Customer
## Market Category
Choice (existing / subcategory / new) and rationale.
## One-Liner
## Brand Script (StoryBrand)
Character · Problem (external/internal/philosophical) · Guide · Plan · Call to action · Failure · Success.
## Key Messages
| Surface | Message | Status |
|---|---|---|
docs/OFFER.md
What we sell and at what price.
# Offer & Pricing
## Offer Stack
| Element | Description | Honest value | Objection it kills |
|---|---|---|---|
Core offer · Bonuses · Guarantee · Scarcity/urgency (real only) · Name.
"Honest value" is what someone would pay for that element standalone; for per-seat software an
element that has no standalone price is recorded as `n/a — bundled`, never an invented figure.
## Willingness-to-Pay Evidence
| Segment | Acceptable | Expensive | Prohibitive | Source |
|---|---|---|---|---|
## Leader / Filler / Killer Features
| Feature | Class | Tier placement |
|---|---|---|
## Tiers (Good / Better / Best)
## Price Metric
What we charge per, and why.
docs/DESIGN.md
Visual and interaction system.
# Design System
## Design Direction
Signature moment, personality, references.
## Typography
Typefaces, scale, measure, line height, loading strategy.
## Tokens
Spacing scale · color palette (shades, tinted grays) · shadows.
## Components
| Component | Decision | Status |
|---|---|---|
## UX Audit Findings
| Issue | Heuristic | Severity (0-4) | Fix | Status |
|---|---|---|---|---|
## Microinteraction Inventory
| Interaction | Trigger/Rules/Feedback/Loops | Fix | Status |
|---|---|---|---|
| 1 | # conversion-optimization artifact templates |
| 2 | |
| 3 | Skeletons for every docs/ file this journey writes. Read the file before writing: if it is missing, create it from the full skeleton below (all section headings), then fill only the sections your phase names; if it exists, extend it — add or update your sections and preserve everyone else's. Creating a file from a partial set of headings is the drift these skeletons exist to prevent. |
| 4 | |
| 5 | ## Tracker: docs/CONVERSION-OPTIMIZATION-PLAN.md |
| 6 | |
| 7 | Created on the first run (Intake). Never shared with another journey. |
| 8 | |
| 9 | |
| 10 | # Conversion Optimization Plan |
| 11 | |
| 12 | ## Context |
| 13 | Intake answers, date started, the flow and its ONE action, project specifics. |
| 14 | Mode: skills-installed | fallback (Briefs + references/methods.md) — set at the first phase, so a |
| 15 | resumed session knows whether earlier artifacts are skill-grade or Brief-grade. |
| 16 | |
| 17 | ## Phase Status |
| 18 | | Phase | Skill | Status | Artifact | Date | |
| 19 | |---|---|---|---|---| |
| 20 | | 1 | lean-analytics | pending | METRICS.md | | |
| 21 | | 2 | cro-methodology | pending | FUNNEL.md, EXPERIMENTS.md | | |
| 22 | | 3 | storybrand-messaging | pending | POSITIONING.md, FUNNEL.md, EXPERIMENTS.md | | |
| 23 | | 4 | hundred-million-offers | pending | OFFER.md, EXPERIMENTS.md | | |
| 24 | | 5 | influence-psychology | pending | FUNNEL.md, EXPERIMENTS.md | | |
| 25 | | 6 | design-everyday-things | pending | FUNNEL.md, DESIGN.md, EXPERIMENTS.md | | |
| 26 | | 7 | cro-methodology | pending | EXPERIMENTS.md, METRICS.md | | |
| 27 | Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason> |
| 28 | A phase parked at `awaiting-evidence` carries a Next Actions row naming the evidence owed, its owner, |
| 29 | and the date — otherwise the next session cannot tell what it is waiting for. |
| 30 | |
| 31 | ## Key Decisions |
| 32 | | Date | Phase | Decision | Rationale | |
| 33 | |---|---|---|---| |
| 34 | |
| 35 | ## Next Actions |
| 36 | - [ ] action (owner, due) |
| 37 | |
| 38 | |
| 39 | ## docs/FUNNEL.md |
| 40 | |
| 41 | One conversion flow end to end — its steps, why people drop, and what answers each doubt. Creates: conversion-optimization. |
| 42 | |
| 43 | |
| 44 | # Conversion Flow |
| 45 | |
| 46 | ## Flow Map & ONE Action |
| 47 | Flow scope (entry → conversion), the single action each step drives, competing CTAs cut. |
| 48 | | Step | ONE action | Current message/CTA | Proposed message/CTA | Notes | |
| 49 | |---|---|---|---|---| |
| 50 | |
| 51 | ## Leak Diagnosis |
| 52 | Why each step loses people. METRICS.md `## Funnel` stays canonical for the conversion numbers; this |
| 53 | table adds the researched reason and severity, and cites those numbers rather than restating them. |
| 54 | | Stage | Baseline | Benchmark | Evidence for why | Severity | |
| 55 | |---|---|---|---|---| |
| 56 | |
| 57 | ## Objections & Counters (O/CO) |
| 58 | | Objection (Big 5) | Evidence (customer words) | Counter | Placement | Status | |
| 59 | |---|---|---|---|---| |
| 60 | |
| 61 | ## Proof Inventory |
| 62 | | Asset | Type | Placement | Status | |
| 63 | |---|---|---|---| |
| 64 | |
| 65 | ## Flow Friction Audit |
| 66 | | Step | Issue | Severity (0-4) | Fix | Status | |
| 67 | |---|---|---|---|---| |
| 68 | |
| 69 | |
| 70 | ## docs/METRICS.md |
| 71 | |
| 72 | What we measure and current baselines. |
| 73 | |
| 74 | |
| 75 | # Metrics |
| 76 | |
| 77 | ## Stage & One Metric That Matters |
| 78 | OMTM · counter-metric · why now. |
| 79 | |
| 80 | ## KPI Definitions |
| 81 | | Metric | Definition | Actionable ratio? | Owner | |
| 82 | |---|---|---|---| |
| 83 | |
| 84 | ## Baselines & Targets |
| 85 | | Metric | Baseline (date) | Target | Line in the sand (miss response) | |
| 86 | |---|---|---|---| |
| 87 | |
| 88 | ## Funnel |
| 89 | | Stage | Conversion | Benchmark | Bottleneck? | |
| 90 | |---|---|---|---| |
| 91 | |
| 92 | ## Cohort Notes |
| 93 | |
| 94 | |
| 95 | ## docs/EXPERIMENTS.md |
| 96 | |
| 97 | Every test we run, with pre-committed criteria. |
| 98 | |
| 99 | |
| 100 | # Experiments |
| 101 | |
| 102 | ## Experiment Cards |
| 103 | ### EXP-001 — [name] |
| 104 | - Hypothesis: We believe [outcome] if [who] [does what] because [reason] |
| 105 | - Type: sprint / smoke test / concierge / painted door / A-B |
| 106 | - Primary metric & threshold (pre-committed): |
| 107 | - Guardrail metric: |
| 108 | - Decision rule (pivot / persevere / iterate): |
| 109 | - Result & verdict: |
| 110 | |
| 111 | ## Experiment Backlog |
| 112 | | Idea | ICE (impact/confidence/ease) | Status | |
| 113 | |---|---|---| |
| 114 | |
| 115 | |
| 116 | ## docs/POSITIONING.md |
| 117 | |
| 118 | How the market should understand us — positioning canvas and messaging in one file. |
| 119 | |
| 120 | |
| 121 | # Positioning & Messaging |
| 122 | |
| 123 | ## Competitive Alternatives |
| 124 | |
| 125 | ## Unique Attributes → Value Themes |
| 126 | | Attribute | Value ("so what") | Proof | |
| 127 | |---|---|---| |
| 128 | |
| 129 | ## Best-Fit Customer |
| 130 | |
| 131 | ## Market Category |
| 132 | Choice (existing / subcategory / new) and rationale. |
| 133 | |
| 134 | ## One-Liner |
| 135 | |
| 136 | ## Brand Script (StoryBrand) |
| 137 | Character · Problem (external/internal/philosophical) · Guide · Plan · Call to action · Failure · Success. |
| 138 | |
| 139 | ## Key Messages |
| 140 | | Surface | Message | Status | |
| 141 | |---|---|---| |
| 142 | |
| 143 | |
| 144 | ## docs/OFFER.md |
| 145 | |
| 146 | What we sell and at what price. |
| 147 | |
| 148 | |
| 149 | # Offer & Pricing |
| 150 | |
| 151 | ## Offer Stack |
| 152 | | Element | Description | Honest value | Objection it kills | |
| 153 | |---|---|---|---| |
| 154 | Core offer · Bonuses · Guarantee · Scarcity/urgency (real only) · Name. |
| 155 | "Honest value" is what someone would pay for that element standalone; for per-seat software an |
| 156 | element that has no standalone price is recorded as `n/a — bundled`, never an invented figure. |
| 157 | |
| 158 | ## Willingness-to-Pay Evidence |
| 159 | | Segment | Acceptable | Expensive | Prohibitive | Source | |
| 160 | |---|---|---|---|---| |
| 161 | |
| 162 | ## Leader / Filler / Killer Features |
| 163 | | Feature | Class | Tier placement | |
| 164 | |---|---|---| |
| 165 | |
| 166 | ## Tiers (Good / Better / Best) |
| 167 | |
| 168 | ## Price Metric |
| 169 | What we charge per, and why. |
| 170 | |
| 171 | |
| 172 | ## docs/DESIGN.md |
| 173 | |
| 174 | Visual and interaction system. |
| 175 | |
| 176 | |
| 177 | # Design System |
| 178 | |
| 179 | ## Design Direction |
| 180 | Signature moment, personality, references. |
| 181 | |
| 182 | ## Typography |
| 183 | Typefaces, scale, measure, line height, loading strategy. |
| 184 | |
| 185 | ## Tokens |
| 186 | Spacing scale · color palette (shades, tinted grays) · shadows. |
| 187 | |
| 188 | ## Components |
| 189 | | Component | Decision | Status | |
| 190 | |---|---|---| |
| 191 | |
| 192 | ## UX Audit Findings |
| 193 | | Issue | Heuristic | Severity (0-4) | Fix | Status | |
| 194 | |---|---|---|---|---| |
| 195 | |
| 196 | ## Microinteraction Inventory |
| 197 | | Interaction | Trigger/Rules/Feedback/Loops | Fix | Status | |
| 198 | |---|---|---|---| |
| 199 | |
| 200 |
Discussion
Browse more free Claude skills.