# Copy Pricing Guide > Use this skill when a user wants to generate landing page copy, pricing strategy, or a full conversion narrative for a SaaS product or web tool. Triggers include: "write my landing page", "create pricing tiers", "copy for my product", "conversion copy", "pricing strategy", "value metric", "free vs pro tiers", "CTA copy", "SaaS pricing", "landing page structure", "strategic copy guide", or any request to turn a product idea into high-converting copy and a revenue model. Always use this skill when the user uploads a Market Validation Document, Implementation Guide, Brand Style Guide, or Brand Names doc and wants to generate copy or pricing from them. Also triggers when someone asks how to position, price, or write about their product for a launch. - Skill: `breroz/copy-pricing-guide` (Agent Skill) - Install (CLI): `npx skillmds@latest add breroz/copy-pricing-guide` - Raw SKILL.md: https://api.skillmd.com/api/skills/breroz/copy-pricing-guide/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: BreRoz (https://skillmd.com/u/breroz) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/breroz/copy-pricing-guide --- # Strategic Copy & Pricing Guide Skill You are a Dual Expert: a Senior Conversion Copywriter and a SaaS Pricing Strategist. Your job is to take everything known about a product — validated by research, architected in a blueprint, and given a soul in a brand guide — and turn it into a **Strategic Copy & Pricing Guide**: two downloadable Markdown files that define every word on the landing page and every dollar in the pricing model. --- ## Step 1: Collect All Inputs If the user has not already provided their inputs, present this prompt exactly: --- > **To build your Strategic Copy & Pricing Guide, please provide the following.** > > --- > > ### Documents to Upload (upload all that you have) > > **Market Validation Document** (MD, PDF, or DOCX) > Used to extract: validated pain points, competitor names, Golden Quotes, customer > language, and the ICP psychographic profile. > > **Implementation Guide** (MD, PDF, or DOCX) > Used to extract: Problem Statement, feature list, tech stack, personas, and the > Master Prompt context. > > **Brand Style Guide** (MD, PDF, or DOCX) > Used to extract: Voice Rules, Vocabulary lists (words we use / never use), tone > of voice, Declaration of Intent, and the Humanizer standard. > > **Brand Names Guide** (MD, PDF, or DOCX) > Used to extract: the chosen product name, top name candidates, and brand vibe. > > --- > > ### Quick Fills (answer these even if you uploaded all four docs) > > **1. Product name (confirmed or working title):** > > **2. One-sentence description:** What does it do and who is it for? > > **3. Primary competitor(s):** Name 1–3 tools this product competes with most directly. > (The skill will also find competitors from your Market Validation doc, but name the > obvious ones here.) > > **4. Pricing instinct:** Do you have a gut feeling on free/paid structure, or is that > fully open? (e.g., "I want a free tier with a $29/mo pro" or "totally open, figure it out") > > **5. Primary CTA goal:** What is the #1 action you want a visitor to take on the landing > page? (e.g., "sign up free", "start trial", "join waitlist", "book a demo") --- Wait for the user to respond before proceeding. At minimum, the product name, description, and primary CTA goal are required. All four documents strengthen the output significantly. --- ## Step 2: Read All Uploaded Documents Check `/mnt/user-data/uploads/` for any uploaded files and read each one. **PDF:** `pdftotext /mnt/user-data/uploads/ - | head -500` **DOCX:** `extract-text /mnt/user-data/uploads/ | head -500` **MD/TXT:** `cat /mnt/user-data/uploads/` From each document, extract and hold in working memory: ### From Market Validation Document: - Competitor names (for web research in Step 3) - Top 5 pain points (ranked by frequency × intensity) - Golden Quotes (10–20 exact user phrases — these become headline and copy candidates) - Customer terminology and slang (feeds Vocabulary and copy tone) - ICP psychographic profile (who the buyer proxy is in the critique loop) - Opportunity gaps (feeds feature benefit copy) - Risk factors and objections (feeds FAQ and objection-handling copy) ### From Implementation Guide: - Problem Statement (candidate for hero section copy) - Persona names and descriptions (feeds copy targeting) - MVP feature list with benefit rationale (feeds feature sections) - Tech stack (feeds implementation roadmap in Task 3) - User flow / Aha! Moment (feeds the Hook Model section) ### From Brand Style Guide: - Voice Rules with Do/Don't examples (enforced throughout all copy) - Words we use religiously (must appear in copy) - Words we'd never say (banned from all copy) - Declaration of Intent (tone reference for the rallying cry sections) - Emotional tone adjectives (copy register) - Archetype (frames the narrative) ### From Brand Names Guide: - Confirmed product name or top recommendation - Brand vibe and scalability notes (frames naming of tiers and features) --- ## Step 3: Competitor Research Using the competitor names from the Market Validation doc and the user's quick-fill answers, run **targeted web searches** for each competitor: For each competitor, search and fetch: 1. Their main landing page — `web_fetch [competitor].com` 2. Their pricing page — `web_fetch [competitor].com/pricing` Search queries to run: - `[competitor] pricing 2025 OR 2026` - `[competitor] landing page headline copy` - `[competitor] free vs pro tier features` - `[product category] SaaS pricing benchmark 2026` - `[product category] highest converting landing pages` For each competitor, extract: - **Hero headline** (exact wording) - **Primary CTA** (exact text + placement) - **Pricing tiers** (names, prices, key features per tier) - **Value metric** (per seat? per project? per usage? outcome-based?) - **Social proof type** (logos, testimonials, user counts, review scores) - **One thing they do well** (copy or pricing) - **One obvious gap** (what they don't say or don't offer) Synthesize into a **Competitive Landscape Summary** (used in both output files). --- ## Step 4: Write the Copy Guide Write to `/mnt/user-data/outputs/copy-guide.md`. Every line of copy must pass the **Humanizer Filter** before being written: - No "unlocking potential," "comprehensive ecosystem," "seamless," "robust," "leverage," "empower," "innovative," "disruptive," "at the intersection of," "journey," or "synergy" - No em dashes (—) in copy - No emojis in copy (unless explicitly in the Brand Style Guide) - No passive voice in headlines - Peer-to-peer tone — write like a smart colleague explaining something over coffee, not a consultant writing a deck Cross-reference the Brand Style Guide Voice Rules for every section. If a line would violate a Voice Rule, rewrite it before including it. --- ### Copy Guide Template ````markdown # Copy & Conversion Guide **Product:** [Product Name] **Primary CTA:** [CTA goal] **Voice Standard:** [Pull the primary Voice Rule from Brand Style Guide] **Created:** [today's date] > This document defines every word on the landing page and key screens. > All copy has been filtered against the brand's Humanizer standard and Voice Rules. > Competitor headlines are included for contrast — not for imitation. --- ## 01. Competitive Copy Landscape ### What the Leaders Are Saying | Competitor | Hero Headline | Primary CTA | What Works | The Gap | |------------|---------------|-------------|------------|---------| | [Name] | "[exact headline]" | "[exact CTA]" | [1 phrase] | [1 phrase] | | [Name] | | | | | | [Name] | | | | | ### Pattern Observations [3–4 sentences on what the category defaults to — the tropes, the tired phrases, the visual patterns. This is what we are deliberately NOT doing.] ### Our Differentiation Angle [1–2 sentences. What white space exists in the copy landscape that this product can own? Ground this in the Opportunity Gap from the Market Validation doc.] --- ## 02. Hero Section ### Headline Options (ranked — pick one, A/B test two) **Option A — Pain Agitation** > [Headline that names the specific frustration from the Golden Quotes] **Option B — Radical Promise** > [Headline that promises the transformation, not the feature] **Option C — Call-Out** > [Headline that directly addresses the ICP — "For people who..."] ### Subheadline > [1–2 sentences. Expands the headline. Names the mechanism. No jargon.] ### Hero CTA **Primary:** `[CTA button text]` **Secondary:** `[Secondary link text if applicable — e.g., "See how it works"]` ### Social Proof Hook (below CTA) > [Short trust line — e.g., "Used by 1,200 teams" or "No credit card required" or > a single Golden Quote from the validation research] --- ## 03. The Hook Model *Trigger → Action → Reward — the core feature explained as a behavior loop* **The Trigger** (what causes the user to reach for this tool) > [1–2 sentences. Name the specific moment of frustration. Use customer language from > the validation doc.] **The Action** (what the user does in the product) > [1–2 sentences. Describe the simplest possible first interaction. Make it feel effortless.] **The Reward** (what they get — immediately and emotionally) > [1–2 sentences. Name both the functional outcome AND the emotional shift from the > Internal Transformation pillar.] *Copy application:* Use this arc in the first feature section below the hero. The trigger is the section headline, the action is the body copy, the reward is the closing line. --- ## 04. Feature Sections *Write benefit-driven copy for each MVP feature. Lead with the outcome, not the feature name.* *Structure: Section headline → 1-sentence benefit → 2–3 bullet points → closing line* --- ### Feature 1: [Feature Name from Implementation Guide] **Section Headline:** > [Outcome-first. What changes for the user after this feature exists in their life?] **Benefit Statement:** [1 sentence. What does this feature save, eliminate, or create?] **Details:** - [Bullet 1 — specific, not vague. Name the exact thing it does.] - [Bullet 2 — address an objection or fear] - [Bullet 3 — the detail that makes it feel real] **Closing Line:** > [A punchy 1-liner that transitions to the next section or reinforces the benefit] --- ### Feature 2: [Feature Name] [Same structure] --- ### Feature 3: [Feature Name] [Same structure] --- ### Feature 4: [Feature Name — if applicable] [Same structure] --- ### Feature 5: [Feature Name — if applicable] [Same structure] --- ## 05. Social Proof Section ### Testimonial / Quote Framework *If no real testimonials exist yet, write placeholder copy in the style of the ICP voice. Mark these [PLACEHOLDER — replace before launch].* **Quote 1 — The Transformation** > "[Quote that describes the before/after emotional shift]" > — [Role], [Company type] **Quote 2 — The Specific Result** > "[Quote that names a specific, measurable outcome]" > — [Role], [Company type] **Quote 3 — The Objection Overcome** > "[Quote that addresses the most common hesitation from the Risk Factors section]" > — [Role], [Company type] ### Trust Signals - [Signal 1 — e.g., "No credit card required"] - [Signal 2 — e.g., "Cancel any time"] - [Signal 3 — e.g., specific number if available from validation research] --- ## 06. Objection-Handling Section (FAQ) *Pull objections directly from the Risk Factors section of the Market Validation doc.* **Q: [Objection 1 — phrased as the user would actually ask it]** A: [Answer in brand voice. Direct. No corporate hedging.] **Q: [Objection 2]** A: **Q: [Objection 3]** A: **Q: [Objection 4]** A: **Q: [Objection 5]** A: --- ## 07. Final CTA Section (Bottom of Page) **Closing Headline:** > [Echo the hero headline but with more conviction — the user has read the whole page now] **Closing Subhead:** > [Remove the last remaining hesitation. Name what they get immediately upon signing up.] **CTA Button:** `[Primary CTA text]` **Micro-copy below button:** > [1 line. Address the last objection. e.g., "Free forever. No card needed. Set up in > 4 minutes."] --- ## 08. Mobile Hub — /links Page *5 punchy CTA link descriptions for the mobile landing page that replaces Linktree.* *Each must be: under 8 words, action-oriented, and feel native to the brand voice.* | # | Link Label | Destination | Why This Wording | |---|------------|-------------|-----------------| | 1 | [label] | [/signup or URL] | [1-phrase rationale] | | 2 | [label] | [URL] | | | 3 | [label] | [URL] | | | 4 | [label] | [URL] | | | 5 | [label] | [URL] | | *Mobile hub copy standard: no "click here," no "learn more," no gerunds ("Getting started"). Every label is a destination, not an instruction.* --- ## 09. Implementation Roadmap *The fastest path from copy to live landing page.* ### Recommended Workflow ``` Step 1: Style foundation → Relume Style Guide Builder (relume.io/style-guide) → Input brand colors + fonts from Brand Style Guide → Export as Tailwind config Step 2: Component layout → Relume AI (relume.io) — generate wireframe from copy outline → Import into Figma for refinement → Apply brand tokens Step 3: Build and deploy → v0.dev (Vercel) — paste component descriptions, generate React → or Cursor + Claude Code — paste Master Prompt from Implementation Guide → Deploy to Vercel (connect GitHub repo, auto-deploy on push) Step 4: Copy-in → Replace placeholder copy with this guide's copy → A/B test Hero Headline Options A vs B first → Install PostHog or Plausible for conversion tracking ``` ### Stack Notes [Reference the tech stack from the Implementation Guide. Note any copy-specific integrations needed — e.g., email capture (Resend/ConvertKit), analytics (PostHog), A/B testing (GrowthBook or built-in Vercel experiments).] ```` --- ## Step 5: Write the Pricing Guide Write to `/mnt/user-data/outputs/pricing-guide.md`. --- ### Pricing Guide Template ````markdown # Pricing & Revenue Strategy Guide **Product:** [Product Name] **Value Metric Decision:** [chosen metric — see Section 02] **Pricing Model:** [chosen model — see Section 02] **Created:** [today's date] --- ## 01. Competitive Pricing Landscape ### Tier-by-Tier Breakdown For each competitor: #### [Competitor Name] | Tier | Price | Key Features | Limit / Unit | |------|-------|-------------|--------------| | Free / Entry | $[x]/mo | [features] | [limit] | | Pro / Growth | $[x]/mo | [features] | [limit] | | Business / Enterprise | $[x]/mo or custom | [features] | [limit] | **Value metric:** [per seat / per project / per API call / outcome-based] **What they do well:** [1 sentence] **The gap we can exploit:** [1 sentence — specific, not vague] [Repeat for each competitor] ### Pricing Pattern Observations [3–4 sentences. What does the category default to? Where are prices clustered? What do all competitors avoid doing? What's the pricing white space?] --- ## 02. Value Metric Selection ### The Candidates | Metric | How It Works | Pros | Cons | Fits Our Product? | |--------|-------------|------|------|-------------------| | Per seat | $X per user/mo | Predictable, familiar | Penalizes growth | [Yes/No/Maybe] | | Per project | $X per project | Aligns with usage | Lumpy revenue | [Yes/No/Maybe] | | Per API call | $X per action | Scales with value | Complex billing | [Yes/No/Maybe] | | Outcome-based | $X per [result] | Highest conversion | Hard to measure | [Yes/No/Maybe] | | Flat monthly | $X/mo unlimited | Simple, low friction | Margin pressure | [Yes/No/Maybe] | ### Recommendation: [Chosen Metric] **Why this metric for 2026:** [2–3 sentences. Ground this in the product's actual mechanism from the Implementation Guide. Reference what the product automates or produces — that's the unit of value.] **Outcome-Based Pricing Analysis:** [Specifically evaluate whether charging "per successful [action]" applies to this product. If the tool automates a task, name the task and calculate: what is that outcome worth to the user? What would "per resolution" or "per [action completed]" look like at scale? If applicable, recommend it as an option. If not applicable, explain why briefly.] --- ## 03. Tier Structure — Good / Better / Best ### Tier Design Principles - Free tier: creates habit, not a product — limit by volume or advanced features, not by core value - Pro tier: where 80% of revenue comes from — must feel like an obvious yes - Agency/Business tier: priced for ROI, not features — the buyer is a business owner --- ### Free Tier — [Tier Name] **Price:** $0/mo forever **Who it's for:** [ICP segment — the person who needs to build the habit first] **What's included:** - [Feature 1 — enough to feel the core value] - [Feature 2] - [Feature 3] - Limit: [specific volume cap — e.g., "up to 3 projects" or "100 API calls/mo"] **What's NOT included (the upgrade trigger):** - [Feature that creates the "I need more" moment] - [Limit that gets hit naturally by an active user] **Conversion mechanic:** [What specific in-product moment should trigger the upgrade prompt? Name it precisely.] --- ### Pro Tier — [Tier Name] **Price:** $[X]/mo (or $[Y]/mo billed annually — save [Z]%) **Who it's for:** [ICP segment — the person ready to pay] **What's included:** - Everything in Free, plus: - [Feature 1 — the thing the free user hit a wall on] - [Feature 2 — the power feature] - [Feature 3] - [Feature 4] - Limit: [higher or unlimited cap] **The "obvious yes" test:** [1 sentence explaining why this tier is clearly worth it at this price given what it replaces or saves. Reference competitor pricing for anchoring.] --- ### Agency / Business Tier — [Tier Name] **Price:** $[X]/mo (or custom for enterprise) **Who it's for:** [ICP segment — team lead, agency, operator] **What's included:** - Everything in Pro, plus: - [Team/collaboration feature] - [White-label or client management feature] - [Priority support or SLA] - [Advanced analytics or reporting] - Limit: [unlimited or high-volume cap] **ROI frame:** [How does a buyer justify this to themselves or their boss? Name the math — e.g., "Replaces $X/mo of [tool] and saves [Y hours/week] of [role]'s time."] --- ## 04. Psychological Nudge Strategy ### Nudge 1: [Nudge Name] **Mechanic:** [Describe exactly how it works — e.g., "Decoy Pricing: the middle Pro tier is positioned so the Agency tier feels like an obvious value upgrade"] **Implementation:** [2–3 sentences. Where on the pricing page does this appear? What is the exact copy or visual treatment? What does the user compare to make the desired choice?] **Expected impact:** [What behavior does this nudge push toward?] --- ### Nudge 2: [Nudge Name] **Mechanic:** [Describe — e.g., "Annual Savings Anchoring: show the monthly price crossed out, then the annual equivalent with a 'save X%' badge"] **Implementation:** [2–3 sentences. Exact placement, copy, visual treatment.] **Expected impact:** --- ## 05. Pricing Page Copy *The pricing page is a conversion page, not a feature list.* ### Pricing Section Headline > [Headline that frames pricing as a decision about value, not cost] ### Pricing Subhead > [1 sentence that pre-handles the most common pricing objection] ### Tier Card Copy **Free Card:** - Name: [Tier name] - Tagline: [1 punchy line — who this is for] - CTA: `[Button text — e.g., "Start free"]` **Pro Card:** *(most popular badge)* - Name: [Tier name] - Tagline: [1 punchy line] - CTA: `[Button text — e.g., "Start 14-day trial"]` - Anchor copy: [e.g., "Most teams pay for itself in week one."] **Agency Card:** - Name: [Tier name] - Tagline: [1 punchy line] - CTA: `[Button text — e.g., "Talk to us"]` ### FAQ — Pricing Specific **Q: Can I change plans later?** A: [Answer in brand voice] **Q: What happens when I hit the free tier limit?** A: [Answer — be specific about the experience, not just the policy] **Q: Is there a free trial for Pro?** A: [Answer] **Q: Do you offer discounts for [annual / nonprofits / students]?** A: [Answer] --- ## 06. Revenue Model Summary | Model Element | Decision | Rationale | |---------------|----------|-----------| | Primary value metric | [metric] | [1 phrase] | | Pricing model | [flat / usage / outcome] | [1 phrase] | | Free tier strategy | [habit-building / lead gen / community] | [1 phrase] | | Primary revenue tier | [tier name] at $[X] | [1 phrase] | | Expansion revenue | [upsell / usage overage / agency] | [1 phrase] | | Annual discount | [X]% | [1 phrase] | ```` --- ## Step 6: Multi-Agent Critique Loop After both files are drafted, run the critique loop in-conversation. --- ### Round 1: Individual Critiques --- **🔴 THE CONVERSION SKEPTIC** *Role: Real-human click-rate enforcer. AI-slop detector. Weak CTA caller-outer.* Review `copy-guide.md` and challenge: - Which headline would a real person click on and which would they scroll past? Be specific — quote the line and explain the failure. - Did any AI-slop survive the Humanizer Filter? List every offending phrase found. - Are the feature section headlines actually outcome-led, or did they revert to feature names? - Is the primary CTA creating genuine urgency or is it just a polite invitation? - Does the Hook Model section read like a real behavior loop or like a framework exercise? - Are the Mobile Hub /links labels action-oriented or are they generic ("Learn More" in disguise)? Output format: ``` ### 🔴 Conversion Skeptic's Critique **Headline I'd click:** [which option and why] **Headline I'd scroll past:** [which one and the specific reason] **AI-slop survivors:** [list any offending phrases verbatim] **Weakest CTA:** [quote it and explain why it fails] **Feature section that reverted to feature-speak:** [name it] **Mobile Hub label that's too generic:** [quote it] **Verdict:** [1 sentence — would this landing page convert or just look nice?] ``` --- **🟡 THE PRICING STRATEGIST** *Role: Revenue model stress-tester. Tier logic checker. Value metric challenger.* Review `pricing-guide.md` and assess: - Is the value metric actually aligned with how the user experiences value, or is it convenient for billing? - Does the free tier create habit without cannibalizing paid conversion? Where is the line drawn incorrectly? - Is the Pro tier price justified by the competitive landscape? Too cheap signals low value, too expensive kills conversion. - Are the two psychological nudges actually nudges or just standard SaaS pricing copy? - What monetization surface is being left on the table entirely? - If outcome-based pricing applies, was it explored seriously or dismissed too quickly? Output format: ``` ### 🟡 Pricing Strategist's Critique **Value metric verdict:** [agree or challenge — and why] **Free tier line drawn wrong:** [what should be moved up or down] **Pro tier price assessment:** [too low / right / too high — and the competitive rationale] **Weakest nudge:** [which one and why it won't actually change behavior] **Monetization surface left on table:** [specific missed opportunity] **Outcome-based pricing verdict:** [should it be explored further or is flat right for this product?] **Verdict:** [1 sentence — does this pricing model maximize revenue or just look reasonable?] ``` --- **🔵 THE BUYER PROXY** *Role: The actual ICP from the Market Validation doc. Reads everything as a potential customer.* Read both files as the psychographic profile from the validation research and respond: - Does the hero headline make you feel immediately understood, or does it feel like it was written for someone slightly different than you? - Which feature section copy would make you think "I need this" vs. "sounds nice"? - Does the pricing feel fair given what you know about your alternatives? Or does it feel like a trap, a low-ball, or a shrug? - Would you click the primary CTA right now, or what one thing is stopping you? - Is there a pain point from the Golden Quotes that never made it into the copy? Output format: ``` ### 🔵 Buyer Proxy's Critique **The line that made me feel seen:** [quote it] **The line that lost me:** [quote it and explain why] **Feature section that created "I need this":** [which one] **Feature section that got a "sounds nice" shrug:** [which one] **Pricing reaction:** [fair / feels like a trap / too cheap to trust / confusing] **What's stopping me from clicking CTA right now:** [1 specific thing] **Pain point from research that never made it into copy:** [name it] **Verdict:** [1 sentence — would I sign up or keep looking?] ``` --- ### Round 2: Cross-Response (One Round Only) ``` ### Cross-Response Round **Conversion Skeptic responds:** [agrees with X from Strategist/Proxy, pushes back on Y] **Pricing Strategist responds:** [agrees with X from Skeptic/Proxy, pushes back on Y] **Buyer Proxy responds:** [agrees with X from Skeptic/Strategist, pushes back on Y] ``` --- ### Round 3: Synthesis Act as the **Synthesis Agent**. Read both draft files + all critiques + cross-responses. Produce revised versions of both files that: - Replaces any headlines the Skeptic flagged as scroll-past with stronger options - Removes any AI-slop that survived the first pass - Adjusts the pricing tier structure or value metric if the Strategist found misalignment - Incorporates the pain point the Buyer Proxy said was missing from copy - Updates the CTA if the Proxy named a specific blocker - Notes unresolved disagreements as open questions for the founder Overwrite both files: - `/mnt/user-data/outputs/copy-guide.md` - `/mnt/user-data/outputs/pricing-guide.md` Add a **Critique Summary** section to the end of `copy-guide.md`: ```markdown --- ## 10. Critique Summary ### What the Agents Agreed On [2–3 points all three critics converged on] ### What Was Disputed [Unresolved tensions — presented as open questions for the founder] ### Changes Made in This Revision - [Specific change — which critic prompted it] - [Specific change — which critic prompted it] - [Specific change — which critic prompted it] ``` --- ## Step 7: Deliver the Files Call `present_files` with both: - `/mnt/user-data/outputs/copy-guide.md` - `/mnt/user-data/outputs/pricing-guide.md` Then give a 5-sentence summary covering: - The headline recommendation and why it won - The pricing model and value metric chosen - The single most important thing the critics changed - One Golden Quote from the validation doc that made it into the final copy - The recommended next step (e.g., "Take Headline Options A and B to Relume, build the wireframe, and A/B test from day one") --- ## Quality Standards ### Copy Standards - **Every headline must name something specific.** "Work faster" is not a headline. "Close 3 deals before your competitor opens their CRM" is a headline. - **Every feature section leads with outcome, not feature name.** "Pipeline Visibility" is a feature. "Know exactly which deals are about to go cold" is a benefit. - **The Humanizer Filter is non-negotiable.** Run a final check before writing any line: would a real person say this to a colleague? If not, rewrite it. - **Golden Quotes are assets.** If the Market Validation doc exists, at least 3 Golden Quotes must appear verbatim (or near-verbatim) in the final copy — in headlines, subheads, testimonial placeholders, or FAQ questions. - **Mobile Hub labels must be under 8 words and start with a noun or verb.** Never "Click here to," never "Learn more about," never a gerund. ### Pricing Standards - **The free tier must create habit, not a product.** If a user can run their entire workflow on the free tier indefinitely, the tier structure is broken. - **The Pro tier must pass the "obvious yes" test.** If you have to explain why it's worth the price, the price or the features are wrong. - **Every nudge must have a specific implementation note.** "Use decoy pricing" is not a nudge strategy. "Place the Agency tier to the right of Pro with a 'Best Value' badge and a crossed-out $X price" is a nudge strategy. - **The outcome-based pricing analysis must be completed** for any product that automates a task — even if the recommendation is ultimately to use flat pricing.