# Vibegrow Full LLM Context This file concatenates public, machine-readable Vibegrow pages for AI agents. --- Source: https://vibegrow.io/index.md Canonical: https://vibegrow.io/ # Vibegrow Canonical: https://vibegrow.io/ Markdown: https://vibegrow.io/index.md Vibegrow is the marketing department your AI agent has been missing. ## What Vibegrow Is - 42 marketing skills for AI coding agents. - Built as Agent Skills spec compatible SKILL.md files. - Covers CRO, copywriting, SEO, AI search optimization, paid ads, lifecycle, pricing, research, and growth workflows. - Works with Claude Code, Cursor, Codex, Windsurf, Cline, Continue, Aider, Amp, Antigravity, CodeBuddy, OpenClaw, IBM Bob, and other agents that load Agent Skills. - Sold as a one-time USD 99.99 purchase with lifetime updates. ## Who It Is For - Solo founders and indie hackers who own marketing themselves. - Technical marketers and growth engineers who want reusable agent playbooks. - Small startup teams that need better marketing output before hiring a full marketing team. ## How It Works 1. Install once: One command drops 40 marketing skills into your project's .agents/skills/ folder. Works with Claude Code, Cursor, Codex, Windsurf - anything that reads the Agent Skills spec. (60 seconds) 2. Set your product context once: Fill in .agents/product-marketing-context.md (15 minutes). Every skill reads it before doing anything, so you stop re-explaining your ICP, positioning, and tone in every chat. (15 minutes) 3. Ask your agent to do marketing: Skills auto-trigger on phrases like "optimize this page," "write a welcome sequence," or "audit my SEO." No more 800-word prompts. Your agent picks the right framework and applies it. (Whenever you ship) 4. Lifetime updates via git pull: We add and refine skills continuously. Every new skill is yours forever - no re-purchase, no upgrade tier. One git pull and your agent gets smarter. (Forever) ## Main Skill Categories - Acquisition: 9 skills - Conversion: 7 skills - Lifecycle: 5 skills - Content: 7 skills - Pricing: 0 skills - Research: 14 skills ## Core Pages - [Homepage](https://vibegrow.io/index.md): Product positioning, ICP, core use cases, and page map. - [Pricing](https://vibegrow.io/pricing.md): Structured price, license, refund, delivery, and included features. - [Skills](https://vibegrow.io/skills.md): Index of every marketing skill. - [Instagrow](https://vibegrow.io/instagrow.md): Chrome extension overview for Instagram creator workflows. - [Docs](https://vibegrow.io/docs.md): Documentation entry points. ## Machine-Readable Files - [llms.txt](https://vibegrow.io/llms.txt): Primary LLM navigation file. - [llms-full.txt](https://vibegrow.io/llms-full.txt): Expanded plain-text context bundle. - [Markdown sitemap entries](https://vibegrow.io/sitemap.xml): XML sitemap includes canonical pages and Markdown variants. - [Robots](https://vibegrow.io/robots.txt): Crawler rules for public pages, search bots, and AI agents. --- Source: https://vibegrow.io/pricing.md Canonical: https://vibegrow.io/pricing # Vibegrow Pricing Canonical: https://vibegrow.io/pricing Markdown: https://vibegrow.io/pricing.md ## Product - Name: Vibegrow marketing skills pack. - Price: USD 99.99 one-time purchase. - Included: 42 marketing skills for AI coding agents. - Updates: lifetime updates via git pull. - License: single-user commercial license; no redistribution. - Refund policy shown on the page: 14-day money-back guarantee. - Delivery: buyer signs in after purchase and gets access to the private skills repository. ## Included - CRO, copywriting, SEO, paid ads, lifecycle, pricing, research, and content frameworks. - Cross-agent compatibility with agents that load the Agent Skills spec. - Auto-triggering skill descriptions so the agent can choose the right framework. - Composable skills that reference each other for connected workflows. - Shared product context through .agents/product-marketing-context.md. ## Pricing FAQ - One-time price: yes, USD 99.99 once. - Subscription: no. - Future updates: included. - Team license: not the default; contact Vibegrow for team needs. - Checkout: Stripe. --- Source: https://vibegrow.io/skills.md Canonical: https://vibegrow.io/skills # All 42 Vibegrow Marketing Skills Canonical: https://vibegrow.io/skills Markdown: https://vibegrow.io/skills.md Every skill is a markdown SKILL.md file built for AI coding agents. ## Acquisition - [Ad Creative](https://vibegrow.io/skills/ad-creative.md): Generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. - [AI SEO](https://vibegrow.io/skills/ai-seo.md): Optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. - [Community Marketing](https://vibegrow.io/skills/community-marketing.md): Build and leverage online communities to drive product growth and brand loyalty. - [Competitor & Alternative Pages](https://vibegrow.io/skills/competitor-alternatives.md): Create competitor comparison or alternative pages for SEO and sales enablement. - [Free Tool Strategy (Engineering as Marketing)](https://vibegrow.io/skills/free-tool-strategy.md): Plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. - [Launch Strategy](https://vibegrow.io/skills/launch-strategy.md): Plan a product launch, feature announcement, or release strategy. - [Paid Ads](https://vibegrow.io/skills/paid-ads.md): Paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. - [Programmatic SEO](https://vibegrow.io/skills/programmatic-seo.md): Create SEO-driven pages at scale using templates and data. - [SEO Audit](https://vibegrow.io/skills/seo-audit.md): Audit, review, or diagnose SEO issues on their site. ## Conversion - [A/B Test Setup](https://vibegrow.io/skills/ab-test-setup.md): Plan, design, or implement an A/B test or experiment, or build a growth experimentation program. - [Form CRO](https://vibegrow.io/skills/form-cro.md): Optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or… - [Onboarding CRO](https://vibegrow.io/skills/onboarding-cro.md): Optimize post-signup onboarding, user activation, first-run experience, or time-to-value. - [Page Conversion Rate Optimization (CRO)](https://vibegrow.io/skills/page-cro.md): Optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. - [Paywall and Upgrade Screen CRO](https://vibegrow.io/skills/paywall-upgrade-cro.md): Create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. - [Popup CRO](https://vibegrow.io/skills/popup-cro.md): Create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. - [Signup Flow CRO](https://vibegrow.io/skills/signup-flow-cro.md): Optimize signup, registration, account creation, or trial activation flows. ## Lifecycle - [Churn Prevention](https://vibegrow.io/skills/churn-prevention.md): Reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. - [Cold Email Writing](https://vibegrow.io/skills/cold-email.md): Write B2B cold emails and follow-up sequences that get replies. - [Email Sequence Design](https://vibegrow.io/skills/email-sequence.md): Create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. - [Lead Magnets](https://vibegrow.io/skills/lead-magnets.md): Create, plan, or optimize a lead magnet for email capture or lead generation. - [RevOps](https://vibegrow.io/skills/revops.md): Revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. ## Content - [Content Strategy](https://vibegrow.io/skills/content-strategy.md): Plan a content strategy, decide what content to create, or figure out what topics to cover. - [Copy Editing](https://vibegrow.io/skills/copy-editing.md): Edit, review, or improve existing marketing copy, or refresh outdated content. - [Copywriting](https://vibegrow.io/skills/copywriting.md): Write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. - [Image](https://vibegrow.io/skills/image.md): Create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets. - [Social Content](https://vibegrow.io/skills/social-content.md): Creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. - [Video](https://vibegrow.io/skills/video.md): Create, generate, or produce video content using AI tools or programmatic frameworks. - [Video Cut Editor](https://vibegrow.io/skills/video-cut-editor.md): Use when the user wants to cut, tighten, clean up, or rough-cut video/audio footage. ## Research - [Analytics Tracking](https://vibegrow.io/skills/analytics-tracking.md): Set up, improve, or audit analytics tracking and measurement. - [ASO Audit](https://vibegrow.io/skills/aso-audit.md): Audit or optimize an App Store or Google Play listing. - [Competitor Profiling](https://vibegrow.io/skills/competitor-profiling.md): Research, profile, or analyze competitors from their URLs. - [Customer Research](https://vibegrow.io/skills/customer-research.md): Conduct, analyze, or synthesize customer research. - [Directory Submissions](https://vibegrow.io/skills/directory-submissions.md): Submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. - [Instagrow Instagram Scheduling](https://vibegrow.io/skills/instagrow.md): Use when scheduling, publishing, drafting, or verifying Instagram posts with the Vibegrow Instagrow Chrome extension and Pi Chrome. - [Marketing Ideas for SaaS](https://vibegrow.io/skills/marketing-ideas.md): Marketing ideas, inspiration, or strategies for their SaaS or software product. - [Marketing Psychology & Mental Models](https://vibegrow.io/skills/marketing-psychology.md): Apply psychological principles, mental models, or behavioral science to marketing. - [Pricing Strategy](https://vibegrow.io/skills/pricing-strategy.md): Pricing decisions, packaging, or monetization strategy. - [Product Marketing Context](https://vibegrow.io/skills/product-marketing-context.md): Create or update their product marketing context document. - [Referral & Affiliate Programs](https://vibegrow.io/skills/referral-program.md): Create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. - [Sales Enablement](https://vibegrow.io/skills/sales-enablement.md): Create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. - [Schema Markup](https://vibegrow.io/skills/schema-markup.md): Add, fix, or optimize schema markup and structured data on their site. - [Site Architecture](https://vibegrow.io/skills/site-architecture.md): Plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. --- Source: https://vibegrow.io/instagrow.md Canonical: https://vibegrow.io/instagrow # Instagrow Canonical: https://vibegrow.io/instagrow Markdown: https://vibegrow.io/instagrow.md Instagrow is the desktop command center for Instagram creators. ## Product Facts - Product: Chrome extension for Instagram creator workflows. - Current public release: instagrow-chrome-v1.0.0.zip. - Install path: Chrome developer mode, load unpacked extension. - Affiliation: independent extension, not affiliated with Instagram or Meta. ## Capabilities - Publish from desktop. - Music-aware story workflow. - Plan and schedule creator work. - Download and archive media. - DM and account workflows. - Growth operations that pair with Vibegrow skills. ## Install Steps 1. Download instagrow-chrome-v1.0.0.zip. 2. Unzip the release folder. 3. Open chrome://extensions and enable Developer mode. 4. Choose Load unpacked and select the unzipped folder. 5. Open Instagram in the same Chrome profile. --- Source: https://vibegrow.io/instagrow/support.md Canonical: https://vibegrow.io/instagrow/support # Instagrow Support Canonical: https://vibegrow.io/instagrow/support Markdown: https://vibegrow.io/instagrow/support.md ## Support Paths - Download the current Chrome dev-mode ZIP. - Use /contact?product=instagrow&topic=support to talk to a human. - Use /contact?product=instagrow&topic=bug to report a bug. - Read the privacy and terms pages for extension data and acceptable-use details. ## Common Questions ### How do I install the extension? Download the ZIP, unzip it, open chrome://extensions, enable Developer mode, click Load unpacked, and select the unzipped folder. ### Does Instagrow send my data anywhere? The extension is documented as local-only by design and uses the browser session for Instagram requests. --- Source: https://vibegrow.io/docs.md Canonical: https://vibegrow.io/docs # Vibegrow Docs Canonical: https://vibegrow.io/docs Markdown: https://vibegrow.io/docs.md The docs page points users and agents to the current install, compatibility, skill reference, support, and repository surfaces. ## Documentation Sections - [Quickstart](https://vibegrow.io/get-started.md): Install Vibegrow, set product context, and run the first skill. - [Skill Reference](https://vibegrow.io/skills.md): Browse every public skill entry and its markdown equivalent. - [FAQ](https://vibegrow.io/faq.md): Common buyer and implementation questions. - [Changelog](https://vibegrow.io/changelog.md): Recent skill and product updates. --- Source: https://vibegrow.io/get-started.md Canonical: https://vibegrow.io/get-started # Get Started With Vibegrow Canonical: https://vibegrow.io/get-started Markdown: https://vibegrow.io/get-started.md ## Current Flow Complete checkout first. Vibegrow provisions GitHub access to the private skills repository from the purchase email. ## Setup Steps - Install once: drop the skills into your project's .agents/skills/ folder. - Set product context: fill .agents/product-marketing-context.md. - Ask your agent: skills auto-trigger from natural-language requests. ## Example Commands ```sh npx skills add vibegrow/marketing-skills $EDITOR .agents/product-marketing-context.md ``` --- Source: https://vibegrow.io/faq.md Canonical: https://vibegrow.io/faq # Vibegrow FAQ Canonical: https://vibegrow.io/faq Markdown: https://vibegrow.io/faq.md ## Which AI agents does this work with? Anything that loads skills following the Agent Skills spec. Today that includes Claude Code, Cursor, Codex, Windsurf, Cline, Continue, Aider, Amp, Antigravity, CodeBuddy, OpenClaw, and IBM Bob. The spec is open at agentskills.io - new agents adopting it inherit support automatically. ## How is this different from claudekit.cc? Claudekit is engineering-first and Claude-Code-only (slash commands). Vibegrow is marketing-first, runs on the open Agent Skills spec (so it works in Cursor, Codex, Windsurf, etc.), and the skills compose with each other. Different audience, different format, different category. ## Do I get future updates? Yes - lifetime updates included. Every new skill we publish and every refinement to existing ones is yours via git pull. No re-purchase, no upgrade tier. ## Do I need to know marketing to use this? No. The whole point is that the marketing knowledge is encoded in the skills. You describe what you want ("draft a welcome email sequence"), the agent picks the right skill, and the skill walks the agent through the framework. You review the output, just like you'd review code from your agent. ## How does delivery work? After purchase you sign in (Google or GitHub OAuth) and get added as a collaborator on the private skills repo. You clone it once, drop the skills folder into your project's .agents/skills/, and you're set. Every future update is a git pull. ## What if it's not the right fit? Email us within 14 days for a full refund - no friction, no questions. We can't take the source files back, so this is on the honor system. Browse every SKILL.md before you buy if you want to see exactly what you're getting. ## Is this really one-time pricing? Yes. USD 99.99 once. No subscription. Lifetime updates included via git pull. ## What is the license? Single-user, commercial use, no redistribution. You can use the skills in projects you own or work on, but cannot resell them or share the private repo. --- Source: https://vibegrow.io/about.md Canonical: https://vibegrow.io/about # About Vibegrow Canonical: https://vibegrow.io/about Markdown: https://vibegrow.io/about.md AI coding agents are excellent at code. They are mediocre at marketing until marketing expertise is encoded into reusable skills. ## Positioning Vibegrow is the marketing department your AI agent has been missing. ## Convictions - Marketing knowledge belongs in skills, not prompts. - Open spec beats vendor lock-in. - Indie hackers should not pay agency rates to test ideas. ## Format 42 markdown skills for AI coding agents, built on the open Agent Skills spec and designed to work across compatible agents. --- Source: https://vibegrow.io/changelog.md Canonical: https://vibegrow.io/changelog # Vibegrow Changelog Canonical: https://vibegrow.io/changelog Markdown: https://vibegrow.io/changelog.md - Total skills detected: 42 - Latest update: not available in local checkout - Updates are included with lifetime access via git pull. ## Recent Changes No changelog entries were available from the local marketing-skills checkout. --- Source: https://vibegrow.io/contact.md Canonical: https://vibegrow.io/contact # Contact Vibegrow Canonical: https://vibegrow.io/contact Markdown: https://vibegrow.io/contact.md ## Contact Paths - Email: hello@vibegrow.io - X: https://x.com/vibegrow - GitHub issues: https://github.com/OutSightAI/vibegrow-platform/issues - Typical response time shown on site: within 24 hours on weekdays. --- Source: https://vibegrow.io/services.md Canonical: https://vibegrow.io/services # Vibegrow Implementation Partners Canonical: https://vibegrow.io/services Markdown: https://vibegrow.io/services.md Vibegrow is the product. This page is a secondary implementation channel for teams that want an approved operator, freelancer, or forward deployed growth engineer to help apply Vibegrow in their business. ## Positioning - The core offer remains the Vibegrow skills product. - Partner work is optional and qualified manually. - Approved partners may say they work with Vibegrow, but they are not Vibegrow employees. - Partner attribution is preserved through query parameters such as /services?partner=outsight-ai. ## Common Implementation Projects ### Vibegrow Workflow Audit A focused review of your offer, funnel, analytics, and where Vibegrow skills should be applied first. Deliverables: - Website and funnel review - Analytics and tracking check - Prioritized 30-day action plan ### Partner Landing Page Sprint A partner helps turn Vibegrow-generated strategy into a clearer conversion page. Deliverables: - Messaging and offer pass - Landing page copy - Design or build support ### Vibegrow Setup Sprint Install Vibegrow skills, define product context, and set up repeatable agent workflows. Deliverables: - Product context file - Skill installation support - Reusable growth workflows ### SEO + Content Operating System Use Vibegrow workflows to build the research, briefs, and publishing system behind search-driven growth. Deliverables: - Keyword and topic map - Content briefs - AI-search optimization plan ### Lifecycle Workflow Setup Map the customer journey and implement the email workflows that move people to the next step. Deliverables: - Lifecycle map - Welcome or nurture sequence - Conversion copy review ### Paid Readiness Review Pressure-test the offer, landing path, tracking, and creative brief before spend scales. Deliverables: - Offer and funnel review - Tracking plan - Campaign and creative brief ### Creator Workflow Setup Turn scattered ideas into a Vibegrow-powered content system with pillars, scripts, hooks, and publishing flow. Deliverables: - Content pillars - Short-form scripts - Publishing workflow ### Instagrow Creator Ops Set up Instagrow and the operating checklist around Instagram creator work. Deliverables: - Instagrow setup - Creator workflow training - Operations checklist ## Partner Types ### Implementation partner Uses Vibegrow to help teams install workflows, improve pages, and ship growth assets. ### Forward deployed engineer Works alongside a customer for a focused sprint to make Vibegrow useful inside their real stack. ### Reseller or agency partner Introduces Vibegrow to an existing customer base and can support implementation after review. ### Sponsor or co-marketing partner Bundles, promotes, or co-sells a campaign where Vibegrow remains the product being adopted. --- Source: https://vibegrow.io/privacy.md Canonical: https://vibegrow.io/privacy # Vibegrow Privacy Policy Canonical: https://vibegrow.io/privacy Markdown: https://vibegrow.io/privacy.md Last updated: November 21, 2025. ## Summary Vibegrow collects information users provide directly, account and payment-related information, usage data, and analytics. Vibegrow states that it does not sell personal information and shares information only with consent, service providers, legal obligations, or fraud and rights protection needs. ## Contact privacy@vibegrow.ai --- Source: https://vibegrow.io/terms.md Canonical: https://vibegrow.io/terms # Vibegrow Terms of Service Canonical: https://vibegrow.io/terms Markdown: https://vibegrow.io/terms.md Last updated: November 21, 2025. ## Summary - Using Vibegrow means accepting the terms. - Vibegrow is sold as a one-time USD 99.99 purchase per user. - The terms describe a single-user commercial license for the marketing-skills repository including lifetime updates. - The service is provided as-is with limitations of liability. ## Contact legal@vibegrow.ai --- Source: https://vibegrow.io/skills/ab-test-setup.md Canonical: https://vibegrow.io/skills/ab-test-setup # A/B Test Setup Canonical: https://vibegrow.io/skills/ab-test-setup Markdown: https://vibegrow.io/skills/ab-test-setup.md Plan, design, or implement an A/B test or experiment, or build a growth experimentation program. ## Skill Metadata - Slug: ab-test-setup - Category: Conversion - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - plan, design, or implement an A/B test or experiment, or build a growth experime ## Full Skill Source # A/B Test Setup You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before designing a test, understand: 1. **Test Context** - What are you trying to improve? What change are you considering? 2. **Current State** - Baseline conversion rate? Current traffic volume? 3. **Constraints** - Technical complexity? Timeline? Tools available? --- ## Core Principles ### 1. Start with a Hypothesis - Not just "let's see what happens" - Specific prediction of outcome - Based on reasoning or data ### 2. Test One Thing - Single variable per test - Otherwise you don't know what worked ### 3. Statistical Rigor - Pre-determine sample size - Don't peek and stop early - Commit to the methodology ### 4. Measure What Matters - Primary metric tied to business value - Secondary metrics for context - Guardrail metrics to prevent harm --- ## Hypothesis Framework ### Structure ``` Because [observation/data], we believe [change] will cause [expected outcome] for [audience]. We'll know this is true when [metrics]. ``` ### Example **Weak**: "Changing the button color might increase clicks." **Strong**: "Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button larger and using contrasting color will increase CTA clicks by 15%+ for new visitors. We'll measure click-through rate from page view to signup start." --- ## Test Types | Type | Description | Traffic Needed | |------|-------------|----------------| | A/B | Two versions, single change | Moderate | | A/B/n | Multiple variants | Higher | | MVT | Multiple changes in combinations | Very high | | Split URL | Different URLs for variants | Moderate | --- ## Sample Size ### Quick Reference | Baseline | 10% Lift | 20% Lift | 50% Lift | |----------|----------|----------|----------| | 1% | 150k/variant | 39k/variant | 6k/variant | | 3% | 47k/variant | 12k/variant | 2k/variant | | 5% | 27k/variant | 7k/variant | 1.2k/variant | | 10% | 12k/variant | 3k/variant | 550/variant | **Calculators:** - [Evan Miller's](https://www.evanmiller.org/ab-testing/sample-size.html) - [Optimizely's](https://www.optimizely.com/sample-size-calculator/) **For detailed sample size tables and duration calculations**: See [references/sample-size-guide.md](references/sample-size-guide.md) --- ## Metrics Selection ### Primary Metric - Single metric that matters most - Directly tied to hypothesis - What you'll use to call the test ### Secondary Metrics - Support primary metric interpretation - Explain why/how the change worked ### Guardrail Metrics - Things that shouldn't get worse - Stop test if significantly negative ### Example: Pricing Page Test - **Primary**: Plan selection rate - **Secondary**: Time on page, plan distribution - **Guardrail**: Support tickets, refund rate --- ## Designing Variants ### What to Vary | Category | Examples | |----------|----------| | Headlines/Copy | Message angle, value prop, specificity, tone | | Visual Design | Layout, color, images, hierarchy | | CTA | Button copy, size, placement, number | | Content | Information included, order, amount, social proof | ### Best Practices - Single, meaningful change - Bold enough to make a difference - True to the hypothesis --- ## Traffic Allocation | Approach | Split | When to Use | |----------|-------|-------------| | Standard | 50/50 | Default for A/B | | Conservative | 90/10, 80/20 | Limit risk of bad variant | | Ramping | Start small, increase | Technical risk mitigation | **Considerations:** - Consistency: Users see same variant on return - Balanced exposure across time of day/week --- ## Implementation ### Client-Side - JavaScript modifies page after load - Quick to implement, can cause flicker - Tools: PostHog, Optimizely, VWO ### Server-Side - Variant determined before render - No flicker, requires dev work - Tools: PostHog, LaunchDarkly, Split --- ## Running the Test ### Pre-Launch Checklist - [ ] Hypothesis documented - [ ] Primary metric defined - [ ] Sample size calculated - [ ] Variants implemented correctly - [ ] Tracking verified - [ ] QA completed on all variants ### During the Test **DO:** - Monitor for technical issues - Check segment quality - Document external factors **Avoid:** - Peek at results and stop early - Make changes to variants - Add traffic from new sources ### The Peeking Problem Looking at results before reaching sample size and stopping early leads to false positives and wrong decisions. Pre-commit to sample size and trust the process. --- ## Analyzing Results ### Statistical Significance - 95% confidence = p-value < 0.05 - Means <5% chance result is random - Not a guarantee—just a threshold ### Analysis Checklist 1. **Reach sample size?** If not, result is preliminary 2. **Statistically significant?** Check confidence intervals 3. **Effect size meaningful?** Compare to MDE, project impact 4. **Secondary metrics consistent?** Support the primary? 5. **Guardrail concerns?** Anything get worse? 6. **Segment differences?** Mobile vs. desktop? New vs. returning? ### Interpreting Results | Result | Conclusion | |--------|------------| | Significant winner | Implement variant | | Significant loser | Keep control, learn why | | No significant difference | Need more traffic or bolder test | | Mixed signals | Dig deeper, maybe segment | --- ## Documentation Document every test with: - Hypothesis - Variants (with screenshots) - Results (sample, metrics, significance) - Decision and learnings **For templates**: See [references/test-templates.md](references/test-templates.md) --- ## Growth Experimentation Program Individual tests are valuable. A continuous experimentation program is a compounding asset. This section covers how to run experiments as an ongoing growth engine, not just one-off tests. ### The Experiment Loop ``` 1. Generate hypotheses (from data, research, competitors, customer feedback) 2. Prioritize with ICE scoring 3. Design and run the test 4. Analyze results with statistical rigor 5. Promote winners to a playbook 6. Generate new hypotheses from learnings → Repeat ``` ### Hypothesis Generation Feed your experiment backlog from multiple sources: | Source | What to Look For | |--------|-----------------| | Analytics | Drop-off points, low-converting pages, underperforming segments | | Customer research | Pain points, confusion, unmet expectations | | Competitor analysis | Features, messaging, or UX patterns they use that you don't | | Support tickets | Recurring questions or complaints about conversion flows | | Heatmaps/recordings | Where users hesitate, rage-click, or abandon | | Past experiments | "Significant loser" tests often reveal new angles to try | ### ICE Prioritization Score each hypothesis 1-10 on three dimensions: | Dimension | Question | |-----------|----------| | **Impact** | If this works, how much will it move the primary metric? | | **Confidence** | How sure are we this will work? (Based on data, not gut.) | | **Ease** | How fast and cheap can we ship and measure this? | **ICE Score** = (Impact + Confidence + Ease) / 3 Run highest-scoring experiments first. Re-score monthly as context changes. ### Experiment Velocity Track your experimentation rate as a leading indicator of growth: | Metric | Target | |--------|--------| | Experiments launched per month | 4-8 for most teams | | Win rate | 20-30% is common for mature programs (sustained higher rates may indicate conservative hypotheses) | | Average test duration | 2-4 weeks | | Backlog depth | 20+ hypotheses queued | | Cumulative lift | Compound gains from all winners | ### The Experiment Playbook When a test wins, don't just implement it — document the pattern: ``` ## [Experiment Name] **Date**: [date] **Hypothesis**: [the hypothesis] **Sample size**: [n per variant] **Result**: [winner/loser/inconclusive] — [primary metric] changed by [X%] (95% CI: [range], p=[value]) **Guardrails**: [any guardrail metrics and their outcomes] **Segment deltas**: [notable differences by device, segment, or cohort] **Why it worked/failed**: [analysis] **Pattern**: [the reusable insight — e.g., "social proof near pricing CTAs increases plan selection"] **Apply to**: [other pages/flows where this pattern might work] **Status**: [implemented / parked / needs follow-up test] ``` Over time, your playbook becomes a library of proven growth patterns specific to your product and audience. ### Experiment Cadence **Weekly (30 min)**: Review running experiments for technical issues and guardrail metrics. Don't call winners early — but do stop tests where guardrails are significantly negative. **Bi-weekly**: Conclude completed experiments. Analyze results, update playbook, launch next experiment from backlog. **Monthly (1 hour)**: Review experiment velocity, win rate, cumulative lift. Replenish hypothesis backlog. Re-prioritize with ICE. **Quarterly**: Audit the playbook. Which patterns have been applied broadly? Which winning patterns haven't been scaled yet? What areas of the funnel are under-tested? --- ## Common Mistakes ### Test Design - Testing too small a change (undetectable) - Testing too many things (can't isolate) - No clear hypothesis ### Execution - Stopping early - Changing things mid-test - Not checking implementation ### Analysis - Ignoring confidence intervals - Cherry-picking segments - Over-interpreting inconclusive results --- ## Task-Specific Questions 1. What's your current conversion rate? 2. How much traffic does this page get? 3. What change are you considering and why? 4. What's the smallest improvement worth detecting? 5. What tools do you have for testing? 6. Have you tested this area before? --- ## Related Skills - **page-cro**: For generating test ideas based on CRO principles - **analytics-tracking**: For setting up test measurement - **copywriting**: For creating variant copy --- Source: https://vibegrow.io/skills/ad-creative.md Canonical: https://vibegrow.io/skills/ad-creative # Ad Creative Canonical: https://vibegrow.io/skills/ad-creative Markdown: https://vibegrow.io/skills/ad-creative.md Generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. ## Skill Metadata - Slug: ad-creative - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - generate, iterate, or scale ad creative — headlines, descriptions, primary text, ## Full Skill Source # Ad Creative You are an expert performance creative strategist. Your goal is to generate high-performing ad creative at scale — headlines, descriptions, and primary text that drive clicks and conversions — and iterate based on real performance data. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Platform & Format - What platform? (Google Ads, Meta, LinkedIn, TikTok, Twitter/X) - What ad format? (Search RSAs, display, social feed, stories, video) - Are there existing ads to iterate on, or starting from scratch? ### 2. Product & Offer - What are you promoting? (Product, feature, free trial, demo, lead magnet) - What's the core value proposition? - What makes this different from competitors? ### 3. Audience & Intent - Who is the target audience? - What stage of awareness? (Problem-aware, solution-aware, product-aware) - What pain points or desires drive them? ### 4. Performance Data (if iterating) - What creative is currently running? - Which headlines/descriptions are performing best? (CTR, conversion rate, ROAS) - Which are underperforming? - What angles or themes have been tested? ### 5. Constraints - Brand voice guidelines or words to avoid? - Compliance requirements? (Industry regulations, platform policies) - Any mandatory elements? (Brand name, trademark symbols, disclaimers) --- ## How This Skill Works This skill supports two modes: ### Mode 1: Generate from Scratch When starting fresh, you generate a full set of ad creative based on product context, audience insights, and platform best practices. ### Mode 2: Iterate from Performance Data When the user provides performance data (CSV, paste, or API output), you analyze what's working, identify patterns in top performers, and generate new variations that build on winning themes while exploring new angles. The core loop: ``` Pull performance data → Identify winning patterns → Generate new variations → Validate specs → Deliver ``` --- ## Platform Specs Platforms reject or truncate creative that exceeds these limits, so verify every piece of copy fits before delivering. ### Google Ads (Responsive Search Ads) | Element | Limit | Quantity | |---------|-------|----------| | Headline | 30 characters | Up to 15 | | Description | 90 characters | Up to 4 | | Display URL path | 15 characters each | 2 paths | **RSA rules:** - Headlines must make sense independently and in any combination - Pin headlines to positions only when necessary (reduces optimization) - Include at least one keyword-focused headline - Include at least one benefit-focused headline - Include at least one CTA headline ### Meta Ads (Facebook/Instagram) | Element | Limit | Notes | |---------|-------|-------| | Primary text | 125 chars visible (up to 2,200) | Front-load the hook | | Headline | 40 characters recommended | Below the image | | Description | 30 characters recommended | Below headline | | URL display link | 40 characters | Optional | ### LinkedIn Ads | Element | Limit | Notes | |---------|-------|-------| | Intro text | 150 chars recommended (600 max) | Above the image | | Headline | 70 chars recommended (200 max) | Below the image | | Description | 100 chars recommended (300 max) | Appears in some placements | ### TikTok Ads | Element | Limit | Notes | |---------|-------|-------| | Ad text | 80 chars recommended (100 max) | Above the video | | Display name | 40 characters | Brand name | ### Twitter/X Ads | Element | Limit | Notes | |---------|-------|-------| | Tweet text | 280 characters | The ad copy | | Headline | 70 characters | Card headline | | Description | 200 characters | Card description | For detailed specs and format variations, see [references/platform-specs.md](references/platform-specs.md). --- ## Generating Ad Visuals For image and video ad creative, use generative AI tools and code-based video rendering. See [references/generative-tools.md](references/generative-tools.md) for the complete guide covering: - **Image generation** — Nano Banana Pro (Gemini), Flux, Ideogram for static ad images - **Video generation** — Veo, Kling, Runway, Sora, Seedance, Higgsfield for video ads - **Voice & audio** — ElevenLabs, OpenAI TTS, Cartesia for voiceovers, cloning, multilingual - **Code-based video** — Remotion for templated, data-driven video at scale - **Platform image specs** — Correct dimensions for every ad placement - **Cost comparison** — Pricing for 100+ ad variations across tools **Recommended workflow for scaled production:** 1. Generate hero creative with AI tools (exploratory, high-quality) 2. Build Remotion templates based on winning patterns 3. Batch produce variations with Remotion using data feeds 4. Iterate — AI for new angles, Remotion for scale --- ## Generating Ad Copy ### Step 1: Define Your Angles Before writing individual headlines, establish 3-5 distinct **angles** — different reasons someone would click. Each angle should tap into a different motivation. **Common angle categories:** | Category | Example Angle | |----------|---------------| | Pain point | "Stop wasting time on X" | | Outcome | "Achieve Y in Z days" | | Social proof | "Join 10,000+ teams who..." | | Curiosity | "The X secret top companies use" | | Comparison | "Unlike X, we do Y" | | Urgency | "Limited time: get X free" | | Identity | "Built for [specific role/type]" | | Contrarian | "Why [common practice] doesn't work" | ### Step 2: Generate Variations per Angle For each angle, generate multiple variations. Vary: - **Word choice** — synonyms, active vs. passive - **Specificity** — numbers vs. general claims - **Tone** — direct vs. question vs. command - **Structure** — short punch vs. full benefit statement ### Step 3: Validate Against Specs Before delivering, check every piece of creative against the platform's character limits. Flag anything that's over and provide a trimmed alternative. ### Step 4: Organize for Upload Present creative in a structured format that maps to the ad platform's upload requirements. --- ## Iterating from Performance Data When the user provides performance data, follow this process: ### Step 1: Analyze Winners Look at the top-performing creative (by CTR, conversion rate, or ROAS — ask which metric matters most) and identify: - **Winning themes** — What topics or pain points appear in top performers? - **Winning structures** — Questions? Statements? Commands? Numbers? - **Winning word patterns** — Specific words or phrases that recur? - **Character utilization** — Are top performers shorter or longer? ### Step 2: Analyze Losers Look at the worst performers and identify: - **Themes that fall flat** — What angles aren't resonating? - **Common patterns in low performers** — Too generic? Too long? Wrong tone? ### Step 3: Generate New Variations Create new creative that: - **Doubles down** on winning themes with fresh phrasing - **Extends** winning angles into new variations - **Tests** 1-2 new angles not yet explored - **Avoids** patterns found in underperformers ### Step 4: Document the Iteration Track what was learned and what's being tested: ``` ## Iteration Log - Round: [number] - Date: [date] - Top performers: [list with metrics] - Winning patterns: [summary] - New variations: [count] headlines, [count] descriptions - New angles being tested: [list] - Angles retired: [list] ``` --- ## Writing Quality Standards ### Headlines That Click **Strong headlines:** - Specific ("Cut reporting time 75%") over vague ("Save time") - Benefits ("Ship code faster") over features ("CI/CD pipeline") - Active voice ("Automate your reports") over passive ("Reports are automated") - Include numbers when possible ("3x faster," "in 5 minutes," "10,000+ teams") **Avoid:** - Jargon the audience won't recognize - Claims without specificity ("Best," "Leading," "Top") - All caps or excessive punctuation - Clickbait that the landing page can't deliver on ### Descriptions That Convert Descriptions should complement headlines, not repeat them. Use descriptions to: - Add proof points (numbers, testimonials, awards) - Handle objections ("No credit card required," "Free forever for small teams") - Reinforce CTAs ("Start your free trial today") - Add urgency when genuine ("Limited to first 500 signups") --- ## Output Formats ### Standard Output Organize by angle, with character counts: ``` ## Angle: [Pain Point — Manual Reporting] ### Headlines (30 char max) 1. "Stop Building Reports by Hand" (29) 2. "Automate Your Weekly Reports" (28) 3. "Reports Done in 5 Min, Not 5 Hr" (31) <- OVER LIMIT, trimmed below -> "Reports in 5 Min, Not 5 Hrs" (27) ### Descriptions (90 char max) 1. "Marketing teams save 10+ hours/week with automated reporting. Start free." (73) 2. "Connect your data sources once. Get automated reports forever. No code required." (80) ``` ### Bulk CSV Output When generating at scale (10+ variations), offer CSV format for direct upload: ```csv headline_1,headline_2,headline_3,description_1,description_2,platform "Stop Manual Reporting","Automate in 5 Minutes","Join 10K+ Teams","Save 10+ hrs/week on reports. Start free.","Connect data sources once. Reports forever.","google_ads" ``` ### Iteration Report When iterating, include a summary: ``` ## Performance Summary - Analyzed: [X] headlines, [Y] descriptions - Top performer: "[headline]" — [metric]: [value] - Worst performer: "[headline]" — [metric]: [value] - Pattern: [observation] ## New Creative [organized variations] ## Recommendations - [What to pause, what to scale, what to test next] ``` --- ## Batch Generation Workflow For large-scale creative production (Anthropic's growth team generates 100+ variations per cycle): ### 1. Break into sub-tasks - **Headline generation** — Focused on click-through - **Description generation** — Focused on conversion - **Primary text generation** — Focused on engagement (Meta/LinkedIn) ### 2. Generate in waves - Wave 1: Core angles (3-5 angles, 5 variations each) - Wave 2: Extended variations on top 2 angles - Wave 3: Wild card angles (contrarian, emotional, specific) ### 3. Quality filter - Remove anything over character limit - Remove duplicates or near-duplicates - Flag anything that might violate platform policies - Ensure headline/description combinations make sense together --- ## Common Mistakes - **Writing headlines that only work together** — RSA headlines get combined randomly - **Ignoring character limits** — Platforms truncate without warning - **All variations sound the same** — Vary angles, not just word choice - **No CTA headlines** — RSAs need action-oriented headlines to drive clicks; include at least 2-3 - **Generic descriptions** — "Learn more about our solution" wastes the slot - **Iterating without data** — Gut feelings are less reliable than metrics - **Testing too many things at once** — Change one variable per test cycle - **Retiring creative too early** — Allow 1,000+ impressions before judging --- ## Tool Integrations For pulling performance data and managing campaigns, see the [tools registry](../../tools/REGISTRY.md). | Platform | Pull Performance Data | Manage Campaigns | Guide | |----------|:---------------------:|:----------------:|-------| | **Google Ads** | `google-ads campaigns list`, `google-ads reports get` | `google-ads campaigns create` | [google-ads.md](../../tools/integrations/google-ads.md) | | **Meta Ads** | `meta-ads insights get` | `meta-ads campaigns list` | [meta-ads.md](../../tools/integrations/meta-ads.md) | | **LinkedIn Ads** | `linkedin-ads analytics get` | `linkedin-ads campaigns list` | [linkedin-ads.md](../../tools/integrations/linkedin-ads.md) | | **TikTok Ads** | `tiktok-ads reports get` | `tiktok-ads campaigns list` | [tiktok-ads.md](../../tools/integrations/tiktok-ads.md) | ### Workflow: Pull Data, Analyze, Generate ```bash # 1. Pull recent ad performance node tools/clis/google-ads.js reports get --type ad_performance --date-range last_30_days # 2. Analyze output (identify top/bottom performers) # 3. Feed winning patterns into this skill # 4. Generate new variations # 5. Upload to platform ``` --- ## Related Skills - **paid-ads**: For campaign strategy, targeting, budgets, and optimization - **copywriting**: For landing page copy (where ad traffic lands) - **ab-test-setup**: For structuring creative tests with statistical rigor - **marketing-psychology**: For psychological principles behind high-performing creative - **copy-editing**: For polishing ad copy before launch --- Source: https://vibegrow.io/skills/ai-seo.md Canonical: https://vibegrow.io/skills/ai-seo # AI SEO Canonical: https://vibegrow.io/skills/ai-seo Markdown: https://vibegrow.io/skills/ai-seo.md Optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. ## Skill Metadata - Slug: ai-seo - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - optimize content for AI search engines, get cited by LLMs, or appear in AI-gener ## Full Skill Source # AI SEO You are an expert in AI search optimization — the practice of making content discoverable, extractable, and citable by AI systems including Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, and Copilot. Your goal is to help users get their content cited as a source in AI-generated answers. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Current AI Visibility - Do you know if your brand appears in AI-generated answers today? - Have you checked ChatGPT, Perplexity, or Google AI Overviews for your key queries? - What queries matter most to your business? ### 2. Content & Domain - What type of content do you produce? (Blog, docs, comparisons, product pages) - What's your domain authority / traditional SEO strength? - Do you have existing structured data (schema markup)? ### 3. Goals - Get cited as a source in AI answers? - Appear in Google AI Overviews for specific queries? - Compete with specific brands already getting cited? - Optimize existing content or create new AI-optimized content? ### 4. Competitive Landscape - Who are your top competitors in AI search results? - Are they being cited where you're not? --- ## How AI Search Works ### The AI Search Landscape | Platform | How It Works | Source Selection | |----------|-------------|----------------| | **Google AI Overviews** | Summarizes top-ranking pages | Strong correlation with traditional rankings | | **ChatGPT (with search)** | Searches web, cites sources | Draws from wider range, not just top-ranked | | **Perplexity** | Always cites sources with links | Favors authoritative, recent, well-structured content | | **Gemini** | Google's AI assistant | Pulls from Google index + Knowledge Graph | | **Copilot** | Bing-powered AI search | Bing index + authoritative sources | | **Claude** | Brave Search (when enabled) | Training data + Brave search results | For a deep dive on how each platform selects sources and what to optimize per platform, see [references/platform-ranking-factors.md](references/platform-ranking-factors.md). ### Key Difference from Traditional SEO Traditional SEO gets you ranked. AI SEO gets you **cited**. In traditional search, you need to rank on page 1. In AI search, a well-structured page can get cited even if it ranks on page 2 or 3 — AI systems select sources based on content quality, structure, and relevance, not just rank position. **Critical stats:** - AI Overviews appear in ~45% of Google searches - AI Overviews reduce clicks to websites by up to 58% - Brands are 6.5x more likely to be cited via third-party sources than their own domains - Optimized content gets cited 3x more often than non-optimized - Statistics and citations boost visibility by 40%+ across queries --- ## AI Visibility Audit Before optimizing, assess your current AI search presence. ### Step 1: Check AI Answers for Your Key Queries Test 10-20 of your most important queries across platforms: | Query | Google AI Overview | ChatGPT | Perplexity | You Cited? | Competitors Cited? | |-------|:-----------------:|:-------:|:----------:|:----------:|:-----------------:| | [query 1] | Yes/No | Yes/No | Yes/No | Yes/No | [who] | | [query 2] | Yes/No | Yes/No | Yes/No | Yes/No | [who] | **Query types to test:** - "What is [your product category]?" - "Best [product category] for [use case]" - "[Your brand] vs [competitor]" - "How to [problem your product solves]" - "[Your product category] pricing" ### Step 2: Analyze Citation Patterns When your competitors get cited and you don't, examine: - **Content structure** — Is their content more extractable? - **Authority signals** — Do they have more citations, stats, expert quotes? - **Freshness** — Is their content more recently updated? - **Schema markup** — Do they have structured data you're missing? - **Third-party presence** — Are they cited via Wikipedia, Reddit, review sites? ### Step 3: Content Extractability Check For each priority page, verify: | Check | Pass/Fail | |-------|-----------| | Clear definition in first paragraph? | | | Self-contained answer blocks (work without surrounding context)? | | | Statistics with sources cited? | | | Comparison tables for "[X] vs [Y]" queries? | | | FAQ section with natural-language questions? | | | Schema markup (FAQ, HowTo, Article, Product)? | | | Expert attribution (author name, credentials)? | | | Recently updated (within 6 months)? | | | Heading structure matches query patterns? | | | AI bots allowed in robots.txt? | | ### Step 4: AI Bot Access Check Verify your robots.txt allows AI crawlers. Each AI platform has its own bot, and blocking it means that platform can't cite you: - **GPTBot** and **ChatGPT-User** — OpenAI (ChatGPT) - **PerplexityBot** — Perplexity - **ClaudeBot** and **anthropic-ai** — Anthropic (Claude) - **Google-Extended** — Google Gemini and AI Overviews - **Bingbot** — Microsoft Copilot (via Bing) Check your robots.txt for `Disallow` rules targeting any of these. If you find them blocked, you have a business decision to make: blocking prevents AI training on your content but also prevents citation. One middle ground is blocking training-only crawlers (like **CCBot** from Common Crawl) while allowing the search bots listed above. See [references/platform-ranking-factors.md](references/platform-ranking-factors.md) for the full robots.txt configuration. --- ## Optimization Strategy ### The Three Pillars ``` 1. Structure (make it extractable) 2. Authority (make it citable) 3. Presence (be where AI looks) ``` ### Pillar 1: Structure — Make Content Extractable AI systems extract passages, not pages. Every key claim should work as a standalone statement. **Content block patterns:** - **Definition blocks** for "What is X?" queries - **Step-by-step blocks** for "How to X" queries - **Comparison tables** for "X vs Y" queries - **Pros/cons blocks** for evaluation queries - **FAQ blocks** for common questions - **Statistic blocks** with cited sources For detailed templates for each block type, see [references/content-patterns.md](references/content-patterns.md). **Structural rules:** - Lead every section with a direct answer (don't bury it) - Keep key answer passages to 40-60 words (optimal for snippet extraction) - Use H2/H3 headings that match how people phrase queries - Tables beat prose for comparison content - Numbered lists beat paragraphs for process content - Each paragraph should convey one clear idea ### Pillar 2: Authority — Make Content Citable AI systems prefer sources they can trust. Build citation-worthiness. **The Princeton GEO research** (KDD 2024, studied across Perplexity.ai) ranked 9 optimization methods: | Method | Visibility Boost | How to Apply | |--------|:---------------:|--------------| | **Cite sources** | +40% | Add authoritative references with links | | **Add statistics** | +37% | Include specific numbers with sources | | **Add quotations** | +30% | Expert quotes with name and title | | **Authoritative tone** | +25% | Write with demonstrated expertise | | **Improve clarity** | +20% | Simplify complex concepts | | **Technical terms** | +18% | Use domain-specific terminology | | **Unique vocabulary** | +15% | Increase word diversity | | **Fluency optimization** | +15-30% | Improve readability and flow | | ~~Keyword stuffing~~ | **-10%** | **Actively hurts AI visibility** | **Best combination:** Fluency + Statistics = maximum boost. Low-ranking sites benefit even more — up to 115% visibility increase with citations. **Statistics and data** (+37-40% citation boost) - Include specific numbers with sources - Cite original research, not summaries of research - Add dates to all statistics - Original data beats aggregated data **Expert attribution** (+25-30% citation boost) - Named authors with credentials - Expert quotes with titles and organizations - "According to [Source]" framing for claims - Author bios with relevant expertise **Freshness signals** - "Last updated: [date]" prominently displayed - Regular content refreshes (quarterly minimum for competitive topics) - Current year references and recent statistics - Remove or update outdated information **E-E-A-T alignment** - First-hand experience demonstrated - Specific, detailed information (not generic) - Transparent sourcing and methodology - Clear author expertise for the topic ### Pillar 3: Presence — Be Where AI Looks AI systems don't just cite your website — they cite where you appear. **Third-party sources matter more than your own site:** - Wikipedia mentions (7.8% of all ChatGPT citations) - Reddit discussions (1.8% of ChatGPT citations) - Industry publications and guest posts - Review sites (G2, Capterra, TrustRadius for B2B SaaS) - YouTube (frequently cited by Google AI Overviews) - Quora answers **Actions:** - Ensure your Wikipedia page is accurate and current - Participate authentically in Reddit communities - Get featured in industry roundups and comparison articles - Maintain updated profiles on relevant review platforms - Create YouTube content for key how-to queries - Answer relevant Quora questions with depth ### Machine-Readable Files for AI Agents AI agents aren't just answering questions — they're becoming buyers. When an AI agent evaluates tools on behalf of a user, it needs structured, parseable information. If your pricing is locked in a JavaScript-rendered page or a "contact sales" wall, agents will skip you and recommend competitors whose information they can actually read. Add these machine-readable files to your site root: **`/pricing.md` or `/pricing.txt`** — Structured pricing data for AI agents ```markdown # Pricing — [Your Product Name] ## Free - Price: $0/month - Limits: 100 emails/month, 1 user - Features: Basic templates, API access ## Pro - Price: $29/month (billed annually) | $35/month (billed monthly) - Limits: 10,000 emails/month, 5 users - Features: Custom domains, analytics, priority support ## Enterprise - Price: Custom — contact sales@example.com - Limits: Unlimited emails, unlimited users - Features: SSO, SLA, dedicated account manager ``` **Why this matters now:** - AI agents increasingly compare products programmatically before a human ever visits your site - Opaque pricing gets filtered out of AI-mediated buying journeys - A simple markdown file is trivially parseable by any LLM — no rendering, no JavaScript, no login walls - Same principle as `robots.txt` (for crawlers), `llms.txt` (for AI context), and `AGENTS.md` (for agent capabilities) **Best practices:** - Use consistent units (monthly vs. annual, per-seat vs. flat) - Include specific limits and thresholds, not just feature names - List what's included at each tier, not just what's different - Keep it updated — stale pricing is worse than no file - Link to it from your sitemap and main pricing page **`/llms.txt`** — Context file for AI systems (see [llmstxt.org](https://llmstxt.org)) If you don't have one yet, add an `llms.txt` that gives AI systems a quick overview of what your product does, who it's for, and links to key pages (including your pricing). ### Schema Markup for AI Structured data helps AI systems understand your content. Key schemas: | Content Type | Schema | Why It Helps | |-------------|--------|-------------| | Articles/Blog posts | `Article`, `BlogPosting` | Author, date, topic identification | | How-to content | `HowTo` | Step extraction for process queries | | FAQs | `FAQPage` | Direct Q&A extraction | | Products | `Product` | Pricing, features, reviews | | Comparisons | `ItemList` | Structured comparison data | | Reviews | `Review`, `AggregateRating` | Trust signals | | Organization | `Organization` | Entity recognition | Content with proper schema shows 30-40% higher AI visibility. For implementation, use the **schema-markup** skill. --- ## Content Types That Get Cited Most Not all content is equally citable. Prioritize these formats: | Content Type | Citation Share | Why AI Cites It | |-------------|:------------:|----------------| | **Comparison articles** | ~33% | Structured, balanced, high-intent | | **Definitive guides** | ~15% | Comprehensive, authoritative | | **Original research/data** | ~12% | Unique, citable statistics | | **Best-of/listicles** | ~10% | Clear structure, entity-rich | | **Product pages** | ~10% | Specific details AI can extract | | **How-to guides** | ~8% | Step-by-step structure | | **Opinion/analysis** | ~10% | Expert perspective, quotable | **Underperformers for AI citation:** - Generic blog posts without structure - Thin product pages with marketing fluff - Gated content (AI can't access it) - Content without dates or author attribution - PDF-only content (harder for AI to parse) --- ## Monitoring AI Visibility ### What to Track | Metric | What It Measures | How to Check | |--------|-----------------|-------------| | AI Overview presence | Do AI Overviews appear for your queries? | Manual check or Semrush/Ahrefs | | Brand citation rate | How often you're cited in AI answers | AI visibility tools (see below) | | Share of AI voice | Your citations vs. competitors | Peec AI, Otterly, ZipTie | | Citation sentiment | How AI describes your brand | Manual review + monitoring tools | | Source attribution | Which of your pages get cited | Track referral traffic from AI sources | ### AI Visibility Monitoring Tools | Tool | Coverage | Best For | |------|----------|----------| | **Otterly AI** | ChatGPT, Perplexity, Google AI Overviews | Share of AI voice tracking | | **Peec AI** | ChatGPT, Gemini, Perplexity, Claude, Copilot+ | Multi-platform monitoring at scale | | **ZipTie** | Google AI Overviews, ChatGPT, Perplexity | Brand mention + sentiment tracking | | **LLMrefs** | ChatGPT, Perplexity, AI Overviews, Gemini | SEO keyword → AI visibility mapping | ### DIY Monitoring (No Tools) Monthly manual check: 1. Pick your top 20 queries 2. Run each through ChatGPT, Perplexity, and Google 3. Record: Are you cited? Who is? What page? 4. Log in a spreadsheet, track month-over-month --- ## AI SEO for Different Content Types ### SaaS Product Pages **Goal:** Get cited in "What is [category]?" and "Best [category]" queries. **Optimize:** - Clear product description in first paragraph (what it does, who it's for) - Feature comparison tables (you vs. category, not just competitors) - Specific metrics ("processes 10,000 transactions/sec" not "blazing fast") - Customer count or social proof with numbers - Pricing transparency (AI cites pages with visible pricing) — add a `/pricing.md` file so AI agents can parse your plans without rendering your page (see "Machine-Readable Files" above) - FAQ section addressing common buyer questions ### Blog Content **Goal:** Get cited as an authoritative source on topics in your space. **Optimize:** - One clear target query per post (match heading to query) - Definition in first paragraph for "What is" queries - Original data, research, or expert quotes - "Last updated" date visible - Author bio with relevant credentials - Internal links to related product/feature pages ### Comparison/Alternative Pages **Goal:** Get cited in "[X] vs [Y]" and "Best [X] alternatives" queries. **Optimize:** - Structured comparison tables (not just prose) - Fair and balanced (AI penalizes obviously biased comparisons) - Specific criteria with ratings or scores - Updated pricing and feature data - Cite the competitor-alternatives skill for building these pages ### Documentation / Help Content **Goal:** Get cited in "How to [X] with [your product]" queries. **Optimize:** - Step-by-step format with numbered lists - Code examples where relevant - HowTo schema markup - Screenshots with descriptive alt text - Clear prerequisites and expected outcomes --- ## Common Mistakes - **Ignoring AI search entirely** — ~45% of Google searches now show AI Overviews, and ChatGPT/Perplexity are growing fast - **Treating AI SEO as separate from SEO** — Good traditional SEO is the foundation; AI SEO adds structure and authority on top - **Writing for AI, not humans** — If content reads like it was written to game an algorithm, it won't get cited or convert - **No freshness signals** — Undated content loses to dated content because AI systems weight recency heavily. Show when content was last updated - **Gating all content** — AI can't access gated content. Keep your most authoritative content open - **Ignoring third-party presence** — You may get more AI citations from a Wikipedia mention than from your own blog - **No structured data** — Schema markup gives AI systems structured context about your content - **Keyword stuffing** — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study) - **Hiding pricing behind "contact sales" or JS-rendered pages** — AI agents evaluating your product on behalf of buyers can't parse what they can't read. Add a `/pricing.md` file - **Blocking AI bots** — If GPTBot, PerplexityBot, or ClaudeBot are blocked in robots.txt, those platforms can't cite you - **Generic content without data** — "We're the best" won't get cited. "Our customers see 3x improvement in [metric]" will - **Forgetting to monitor** — You can't improve what you don't measure. Check AI visibility monthly at minimum --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). | Tool | Use For | |------|---------| | `semrush` | AI Overview tracking, keyword research, content gap analysis | | `ahrefs` | Backlink analysis, content explorer, AI Overview data | | `gsc` | Search Console performance data, query tracking | | `ga4` | Referral traffic from AI sources | --- ## Task-Specific Questions 1. What are your top 10-20 most important queries? 2. Have you checked if AI answers exist for those queries today? 3. Do you have structured data (schema markup) on your site? 4. What content types do you publish? (Blog, docs, comparisons, etc.) 5. Are competitors being cited by AI where you're not? 6. Do you have a Wikipedia page or presence on review sites? --- ## Related Skills - **seo-audit**: For traditional technical and on-page SEO audits - **schema-markup**: For implementing structured data that helps AI understand your content - **content-strategy**: For planning what content to create - **competitor-alternatives**: For building comparison pages that get cited - **programmatic-seo**: For building SEO pages at scale - **copywriting**: For writing content that's both human-readable and AI-extractable --- Source: https://vibegrow.io/skills/analytics-tracking.md Canonical: https://vibegrow.io/skills/analytics-tracking # Analytics Tracking Canonical: https://vibegrow.io/skills/analytics-tracking Markdown: https://vibegrow.io/skills/analytics-tracking.md Set up, improve, or audit analytics tracking and measurement. ## Skill Metadata - Slug: analytics-tracking - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - set up, improve, or audit analytics tracking and measurement ## Full Skill Source # Analytics Tracking You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before implementing tracking, understand: 1. **Business Context** - What decisions will this data inform? What are key conversions? 2. **Current State** - What tracking exists? What tools are in use? 3. **Technical Context** - What's the tech stack? Any privacy/compliance requirements? --- ## Core Principles ### 1. Track for Decisions, Not Data - Every event should inform a decision - Avoid vanity metrics - Quality > quantity of events ### 2. Start with the Questions - What do you need to know? - What actions will you take based on this data? - Work backwards to what you need to track ### 3. Name Things Consistently - Naming conventions matter - Establish patterns before implementing - Document everything ### 4. Maintain Data Quality - Validate implementation - Monitor for issues - Clean data > more data --- ## Tracking Plan Framework ### Structure ``` Event Name | Category | Properties | Trigger | Notes ---------- | -------- | ---------- | ------- | ----- ``` ### Event Types | Type | Examples | |------|----------| | Pageviews | Automatic, enhanced with metadata | | User Actions | Button clicks, form submissions, feature usage | | System Events | Signup completed, purchase, subscription changed | | Custom Conversions | Goal completions, funnel stages | **For comprehensive event lists**: See [references/event-library.md](references/event-library.md) --- ## Event Naming Conventions ### Recommended Format: Object-Action ``` signup_completed button_clicked form_submitted article_read checkout_payment_completed ``` ### Best Practices - Lowercase with underscores - Be specific: `cta_hero_clicked` vs. `button_clicked` - Include context in properties, not event name - Avoid spaces and special characters - Document decisions --- ## Essential Events ### Marketing Site | Event | Properties | |-------|------------| | cta_clicked | button_text, location | | form_submitted | form_type | | signup_completed | method, source | | demo_requested | - | ### Product/App | Event | Properties | |-------|------------| | onboarding_step_completed | step_number, step_name | | feature_used | feature_name | | purchase_completed | plan, value | | subscription_cancelled | reason | **For full event library by business type**: See [references/event-library.md](references/event-library.md) --- ## Event Properties ### Standard Properties | Category | Properties | |----------|------------| | Page | page_title, page_location, page_referrer | | User | user_id, user_type, account_id, plan_type | | Campaign | source, medium, campaign, content, term | | Product | product_id, product_name, category, price | ### Best Practices - Use consistent property names - Include relevant context - Don't duplicate automatic properties - Avoid PII in properties --- ## GA4 Implementation ### Quick Setup 1. Create GA4 property and data stream 2. Install gtag.js or GTM 3. Enable enhanced measurement 4. Configure custom events 5. Mark conversions in Admin ### Custom Event Example ```javascript gtag('event', 'signup_completed', { 'method': 'email', 'plan': 'free' }); ``` **For detailed GA4 implementation**: See [references/ga4-implementation.md](references/ga4-implementation.md) --- ## Google Tag Manager ### Container Structure | Component | Purpose | |-----------|---------| | Tags | Code that executes (GA4, pixels) | | Triggers | When tags fire (page view, click) | | Variables | Dynamic values (click text, data layer) | ### Data Layer Pattern ```javascript dataLayer.push({ 'event': 'form_submitted', 'form_name': 'contact', 'form_location': 'footer' }); ``` **For detailed GTM implementation**: See [references/gtm-implementation.md](references/gtm-implementation.md) --- ## UTM Parameter Strategy ### Standard Parameters | Parameter | Purpose | Example | |-----------|---------|---------| | utm_source | Traffic source | google, newsletter | | utm_medium | Marketing medium | cpc, email, social | | utm_campaign | Campaign name | spring_sale | | utm_content | Differentiate versions | hero_cta | | utm_term | Paid search keywords | running+shoes | ### Naming Conventions - Lowercase everything - Use underscores or hyphens consistently - Be specific but concise: `blog_footer_cta`, not `cta1` - Document all UTMs in a spreadsheet --- ## Debugging and Validation ### Testing Tools | Tool | Use For | |------|---------| | GA4 DebugView | Real-time event monitoring | | GTM Preview Mode | Test triggers before publish | | Browser Extensions | Tag Assistant, dataLayer Inspector | ### Validation Checklist - [ ] Events firing on correct triggers - [ ] Property values populating correctly - [ ] No duplicate events - [ ] Works across browsers and mobile - [ ] Conversions recorded correctly - [ ] No PII leaking ### Common Issues | Issue | Check | |-------|-------| | Events not firing | Trigger config, GTM loaded | | Wrong values | Variable path, data layer structure | | Duplicate events | Multiple containers, trigger firing twice | --- ## Privacy and Compliance ### Considerations - Cookie consent required in EU/UK/CA - No PII in analytics properties - Data retention settings - User deletion capabilities ### Implementation - Use consent mode (wait for consent) - IP anonymization - Only collect what you need - Integrate with consent management platform --- ## Output Format ### Tracking Plan Document ```markdown # [Site/Product] Tracking Plan ## Overview - Tools: GA4, GTM - Last updated: [Date] ## Events | Event Name | Description | Properties | Trigger | |------------|-------------|------------|---------| | signup_completed | User completes signup | method, plan | Success page | ## Custom Dimensions | Name | Scope | Parameter | |------|-------|-----------| | user_type | User | user_type | ## Conversions | Conversion | Event | Counting | |------------|-------|----------| | Signup | signup_completed | Once per session | ``` --- ## Task-Specific Questions 1. What tools are you using (GA4, Mixpanel, etc.)? 2. What key actions do you want to track? 3. What decisions will this data inform? 4. Who implements - dev team or marketing? 5. Are there privacy/consent requirements? 6. What's already tracked? --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analytics tools: | Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](../../tools/integrations/ga4.md) | | **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](../../tools/integrations/mixpanel.md) | | **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](../../tools/integrations/amplitude.md) | | **PostHog** | Open-source analytics, session replay | - | [posthog.md](../../tools/integrations/posthog.md) | | **Segment** | Customer data platform, routing | - | [segment.md](../../tools/integrations/segment.md) | --- ## Related Skills - **ab-test-setup**: For experiment tracking - **seo-audit**: For organic traffic analysis - **page-cro**: For conversion optimization (uses this data) - **revops**: For pipeline metrics, CRM tracking, and revenue attribution --- Source: https://vibegrow.io/skills/aso-audit.md Canonical: https://vibegrow.io/skills/aso-audit # ASO Audit Canonical: https://vibegrow.io/skills/aso-audit Markdown: https://vibegrow.io/skills/aso-audit.md Audit or optimize an App Store or Google Play listing. ## Skill Metadata - Slug: aso-audit - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - audit or optimize an App Store or Google Play listing ## Full Skill Source # ASO Audit Analyze App Store and Google Play listings against ASO best practices. Fetches live listing data, scores metadata, visuals, and ratings, then produces a prioritized action plan. ## When to Use - User shares an App Store or Google Play URL - User asks to audit or optimize an app listing - User wants to compare their app against competitors - User asks about app store ranking, visibility, or download conversion ## Before Auditing **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. ## Phase 1 — Identify Store & Fetch ### Detect store type from URL ``` Apple: apps.apple.com/{country}/app/{name}/id{digits} Google: play.google.com/store/apps/details?id={package} ``` If the user gives an app name instead of a URL, search the web for: `site:apps.apple.com "{app name}"` or `site:play.google.com "{app name}"` ### Fetch the listing Use WebFetch to retrieve the listing page. Extract every available field: **Apple App Store fields:** - App name (title) — 30 char limit - Subtitle — 30 char limit - Description (long) — not indexed for search, but matters for conversion - Promotional text — 170 chars, updatable without new release - Category (primary + secondary) - Screenshots (count, order, caption text) - Preview video (presence, duration) - Rating (average + count) - Recent reviews (visible ones) - Price / in-app purchases - Developer name - Last updated date - Version history notes - Age rating - Size - Languages / localizations listed - In-app events (if any visible) **Google Play fields:** - App name (title) — 30 char limit - Short description — 80 char limit - Full description — 4,000 char limit, IS indexed for search - Category + tags - Feature graphic (presence) - Screenshots (count, order) - Preview video (presence) - Rating (average + count) - Recent reviews (visible ones) - Price / in-app purchases - Developer name - Last updated date - What's new text - Downloads range - Content rating - Data safety section - Languages listed If WebFetch returns incomplete data (stores render client-side), note gaps and work with what's available. Ask the user to paste missing fields if critical. ### Visual asset assessment WebFetch cannot extract screenshot images or caption text. **Take a screenshot of the listing page** to get visual data: 1. Navigate to the listing URL and capture a full-page screenshot 2. Assess the screenshot for: icon quality, screenshot count, caption text, messaging quality, preview video presence, feature graphic (Google Play) 3. If browser tools are unavailable, ask the user to share a screenshot of the listing page **Promotional text (Apple):** This 170-char field appears above the description but is often indistinguishable from it in scraped HTML. If you cannot confirm its presence, note this and recommend the user check App Store Connect. --- ## Phase 1.5 — Assess Brand Maturity Before scoring, classify the app into one of three tiers. This determines how you interpret "textbook ASO" deviations — a deliberate brand choice by a household name is not the same as a missed opportunity by an unknown app. ### Tier definitions | Tier | Signals | Examples | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- | | **Dominant** | Household name, 1M+ ratings, top-10 in category, near-universal brand recognition. Users search by brand name, not generic keywords. | Instagram, Uber, Spotify, WhatsApp, Netflix | | **Established** | Well-known in their category, 100K+ ratings, strong organic installs, recognized brand but not universally known. | Strava, Notion, Duolingo, Cash App, Calm | | **Challenger** | Building awareness, <100K ratings, needs discovery through keywords and ASO tactics. Most apps fall here. | Your app, most indie/startup apps | ### How tier affects scoring **Dominant apps** get adjusted scoring in these areas: - **Title:** Brand-only or brand-first titles are valid (score 8+ if brand is the keyword). These apps don't need generic keyword discovery. - **Description:** Score purely on conversion quality, not keyword presence. If the app is a household name, a well-crafted brand description beats a keyword-stuffed one. - **Visual Assets:** Lifestyle/brand photography instead of UI demos is a legitimate conversion strategy. No video is acceptable if the product is hard to demo in 30s or brand awareness is near-universal. - **What's New:** Generic release notes at weekly+ cadence are acceptable (score 8+). At scale, detailed changelogs have minimal ROI and risk backlash. - **In-app events:** Missing events for utility apps with massive install bases (Uber, WhatsApp) is not a penalty. These apps don't need discovery help. - **Localization:** Score relative to actual market, not absolute count. A US-only fintech with 2 languages (English + Spanish) is appropriately localized. **Established apps** get partial adjustment: - Brand-first titles are fine but should still include 1-2 keywords - Strategic description choices get benefit of the doubt - Other dimensions scored normally **Challenger apps** are scored strictly against textbook ASO best practices — every character, screenshot, and keyword matters. **Key principle:** Before docking points, ask: "Is this a mistake or a deliberate choice by a team that has data I don't?" If the app has 1M+ ratings and a dedicated ASO team, assume their choices are data-informed unless clearly wrong. --- ## Phase 2 — Score Each Dimension Score each dimension 0-10 using the criteria in `references/scoring-criteria.md`. Apply the brand maturity tier adjustments from Phase 1.5. Reference files for platform specs and benchmarks: - `references/apple-specs.md` — Official Apple character limits, screenshot/video specs, CPP/PPO rules, rejection triggers - `references/google-play-specs.md` — Official Google Play limits, screenshot specs, Android Vitals thresholds, policies - `references/benchmarks.md` — Conversion data, rating impact, video lift, screenshot behavior, CPP/event benchmarks ### Dimensions and Weights | # | Dimension | Weight | What It Covers | | --- | -------------------- | ------ | ------------------------------------------------------------------------- | | 1 | Title & Subtitle | 20% | Character usage, keyword presence, clarity, brand + keyword balance | | 2 | Description | 15% | First 3 lines, keyword density (Google), CTA, structure, promotional text | | 3 | Visual Assets | 25% | Screenshot count/quality/messaging, video, icon, feature graphic | | 4 | Ratings & Reviews | 20% | Average rating, volume, recency, developer responses | | 5 | Metadata & Freshness | 10% | Category choice, update recency, localization count, data safety | | 6 | Conversion Signals | 10% | Price positioning, IAP transparency, social proof, download range | **Final score** = weighted sum, out of 100. ### Score interpretation | Score | Grade | Meaning | | ------ | ----- | --------------------------------------------------------- | | 85-100 | A | Well-optimized; focus on A/B testing and iteration | | 70-84 | B | Good foundation; clear opportunities to improve | | 50-69 | C | Significant gaps; prioritized fixes will have high impact | | 30-49 | D | Major optimization needed across multiple dimensions | | 0-29 | F | Listing needs a complete overhaul | --- ## Phase 3 — Competitor Comparison (Optional) If the user provides competitor URLs or asks for comparison: 1. Fetch 2-3 top competitors in the same category 2. Run the same scoring on each 3. Build a comparison table highlighting where the user's app is weaker/stronger 4. Identify keyword gaps — terms competitors rank for that the user's app doesn't target If no competitors are specified, suggest the user provide 2-3 or offer to search for top apps in their category. --- ## Phase 4 — Generate Report Use the template in `references/report-template.md` to structure the output. The report must include: 1. **Score card** — table with all 6 dimensions, scores, and grade 2. **Top 3 quick wins** — changes that take <1 hour and have highest impact 3. **Detailed findings** — per-dimension breakdown with specific issues and fixes 4. **Keyword suggestions** — based on title/description analysis and competitor gaps 5. **Visual asset recommendations** — specific screenshot/video improvements 6. **Priority action plan** — ordered list of changes by impact vs effort ### Report rules - Every recommendation must be **specific and actionable** ("Change subtitle from X to Y" not "Improve subtitle") - Include character counts for all text recommendations - Flag platform-specific differences (Apple vs Google) when relevant - Note what CANNOT be assessed without paid tools (search volume, exact rankings) - When suggesting keyword changes, explain WHY each keyword matters --- ## Platform-Specific Rules ### Apple App Store — Key Facts - Title (30 chars) + Subtitle (30 chars) + Keyword field (100 **bytes**, hidden) = indexed text - Keywords field is bytes not chars — Arabic/CJK use 2-3 bytes per char - Long description is NOT indexed for search — optimize for conversion only - Promotional text (170 chars) does NOT affect search (Apple confirmed) - Never repeat words across title/subtitle/keyword field (Apple indexes each word once) - Keyword field: commas, no spaces ("photo,editor,filter" not "photo, editor, filter") - Screenshots: up to 10 per device. First 3 visible in search — 90% never scroll past 3rd - Screenshot captions indexed since June 2025 (AI extraction) - In-app events: max 10 published at once, max 31 days each. Indexed and appear in search - Custom Product Pages (up to 70) in organic search since July 2025. +5.9% avg conversion lift - App preview video: up to 3, 15-30s each. Autoplays muted — +20-40% conversion lift - SKStoreReviewController: max 3 prompts per 365 days - Apple has human editorial curation — quality and design matter more - See `references/apple-specs.md` for full specs, dimensions, and rejection triggers ### Google Play — Key Facts - Title (30 chars) + Short description (80 chars) + Full description (4,000 chars) = indexed text - Full description IS indexed — target 2-3% keyword density naturally - No hidden keyword field — all keywords must be in visible text - Google NLP/semantic understanding — keyword stuffing detected and penalized - Prohibited in title: emojis, ALL CAPS, "best"/"#1"/"free", CTAs (enforced since 2021) - Screenshots: min 2, **max 8** per device (not 10 like Apple) - Feature graphic (1024x500, exact) required for featured placements - Video does NOT autoplay — only ~6% of users tap play (low ROI vs iOS) - Android Vitals directly affect ranking: crash >1.09% or ANR >0.47% = reduced visibility - Promotional Content: submit 14 days early for featuring. Apps see 2x explore acquisitions - Custom Store Listings: up to 50 (can target churned users, specific countries, ad campaigns) - Store Listing Experiments: test up to 3 variants, run 7+ days, 1 experiment at a time - See `references/google-play-specs.md` for full specs and policy details ### What Apple Indexes vs What Google Indexes | Field | Apple Indexed? | Google Indexed? | | --------------------- | ---------------- | ---------------------- | | Title | Yes | Yes (strongest signal) | | Subtitle / Short desc | Yes | Yes | | Keyword field | Yes (hidden) | Does not exist | | Long description | No | Yes (heavily) | | Screenshot captions | Yes (since 2025) | No | | In-app events | Yes | N/A (LiveOps instead) | | Developer name | No | Partial | | IAP names | Yes | Yes | --- ## Common Issues Checklist Flag these if found. Items marked _(tier-dependent)_ should be evaluated against the app's brand maturity tier — they may be deliberate choices for Dominant apps. **Always flag (all tiers):** - [ ] Rating below 4.0 - [ ] Last update > 3 months ago - [ ] Google Play description has no keyword strategy (under 1% density) - [ ] Google Play missing feature graphic - [ ] Apple keyword field likely has repeated words (inferred from title+subtitle) - [ ] Category mismatch — app would face less competition in a different category - [ ] Fewer than 5 screenshots **Flag for Challenger/Established only** _(not mistakes for Dominant apps):_ - [ ] Title wastes characters on brand name only (no keywords) _(Dominant: brand IS the keyword)_ - [ ] Subtitle/short description duplicates title keywords - [ ] Description first 3 lines are generic _(Dominant: may be brand-voice choice)_ - [ ] No preview video _(Dominant: may be rational if product is hard to demo)_ - [ ] Screenshots are just UI dumps with no messaging/captions _(Dominant: lifestyle/brand shots may convert better)_ - [ ] Only 1-2 localizations _(score relative to actual market, not absolute count)_ - [ ] No in-app events or promotional content _(Dominant utility apps may not need discovery help)_ **Flag for all tiers but note context:** - [ ] No developer responses to negative reviews _(note volume — responding at 10M+ reviews is a different challenge than at 1K)_ - [ ] Generic "What's New" text _(acceptable at weekly+ release cadence for Established/Dominant)_ --- ## Task-Specific Questions 1. What is the App Store or Google Play URL? 2. Is this your app or a competitor's? 3. What category does the app compete in? 4. Do you have competitor URLs to compare against? 5. Are you focused on search visibility, conversion rate, or both? 6. Do you have access to App Store Connect or Google Play Console data? --- ## Related Skills - **page-cro**: For optimizing the conversion of web-based landing pages that drive app installs - **ad-creative**: For creating App Store and Google Play ad creatives - **analytics-tracking**: For setting up install attribution and in-app event tracking - **customer-research**: For understanding user needs and language to inform listing copy --- Source: https://vibegrow.io/skills/churn-prevention.md Canonical: https://vibegrow.io/skills/churn-prevention # Churn Prevention Canonical: https://vibegrow.io/skills/churn-prevention Markdown: https://vibegrow.io/skills/churn-prevention.md Reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. ## Skill Metadata - Slug: churn-prevention - Category: Lifecycle - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - reduce churn, build cancellation flows, set up save offers, recover failed payme ## Full Skill Source # Churn Prevention You are an expert in SaaS retention and churn prevention. Your goal is to help reduce both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments) through well-designed cancel flows, dynamic save offers, proactive retention, and dunning strategies. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Current Churn Situation - What's your monthly churn rate? (Voluntary vs. involuntary if known) - How many active subscribers? - What's the average MRR per customer? - Do you have a cancel flow today, or does cancel happen instantly? ### 2. Billing & Platform - What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree) - Monthly, annual, or both billing intervals? - Do you support plan pausing or downgrades? - Any existing retention tooling? (Churnkey, ProsperStack, Raaft) ### 3. Product & Usage Data - Do you track feature usage per user? - Can you identify engagement drop-offs? - Do you have cancellation reason data from past churns? - What's your activation metric? (What do retained users do that churned users don't?) ### 4. Constraints - B2B or B2C? (Affects flow design) - Self-serve cancellation required? (Some regulations mandate easy cancel) - Brand tone for offboarding? (Empathetic, direct, playful) --- ## How This Skill Works Churn has two types requiring different strategies: | Type | Cause | Solution | |------|-------|----------| | **Voluntary** | Customer chooses to cancel | Cancel flows, save offers, exit surveys | | **Involuntary** | Payment fails | Dunning emails, smart retries, card updaters | Voluntary churn is typically 50-70% of total churn. Involuntary churn is 30-50% but is often easier to fix. This skill supports three modes: 1. **Build a cancel flow** — Design from scratch with survey, save offers, and confirmation 2. **Optimize an existing flow** — Analyze cancel data and improve save rates 3. **Set up dunning** — Failed payment recovery with retries and email sequences --- ## Cancel Flow Design ### The Cancel Flow Structure Every cancel flow follows this sequence: ``` Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel ``` **Step 1: Trigger** Customer clicks "Cancel subscription" in account settings. **Step 2: Exit Survey** Ask why they're cancelling. This determines which save offer to show. **Step 3: Dynamic Save Offer** Present a targeted offer based on their reason (discount, pause, downgrade, etc.) **Step 4: Confirmation** If they still want to cancel, confirm clearly with end-of-billing-period messaging. **Step 5: Post-Cancel** Set expectations, offer easy reactivation path, trigger win-back sequence. ### Exit Survey Design The exit survey is the foundation. Good reason categories: | Reason | What It Tells You | |--------|-------------------| | Too expensive | Price sensitivity, may respond to discount or downgrade | | Not using it enough | Low engagement, may respond to pause or onboarding help | | Missing a feature | Product gap, show roadmap or workaround | | Switching to competitor | Competitive pressure, understand what they offer | | Technical issues / bugs | Product quality, escalate to support | | Temporary / seasonal need | Usage pattern, offer pause | | Business closed / changed | Unavoidable, learn and let go gracefully | | Other | Catch-all, include free text field | **Survey best practices:** - 1 question, single-select with optional free text - 5-8 reason options max (avoid decision fatigue) - Put most common reasons first (review data quarterly) - Don't make it feel like a guilt trip - "Help us improve" framing works better than "Why are you leaving?" ### Dynamic Save Offers The key insight: **match the offer to the reason.** A discount won't save someone who isn't using the product. A feature roadmap won't save someone who can't afford it. **Offer-to-reason mapping:** | Cancel Reason | Primary Offer | Fallback Offer | |---------------|---------------|----------------| | Too expensive | Discount (20-30% for 2-3 months) | Downgrade to lower plan | | Not using it enough | Pause (1-3 months) | Free onboarding session | | Missing feature | Roadmap preview + timeline | Workaround guide | | Switching to competitor | Competitive comparison + discount | Feedback session | | Technical issues | Escalate to support immediately | Credit + priority fix | | Temporary / seasonal | Pause subscription | Downgrade temporarily | | Business closed | Skip offer (respect the situation) | — | ### Save Offer Types **Discount** - 20-30% off for 2-3 months is the sweet spot - Avoid 50%+ discounts (trains customers to cancel for deals) - Time-limit the offer ("This offer expires when you leave this page") - Show the dollar amount saved, not just the percentage **Pause subscription** - 1-3 month pause maximum (longer pauses rarely reactivate) - 60-80% of pausers eventually return to active - Auto-reactivation with advance notice email - Keep their data and settings intact **Plan downgrade** - Offer a lower tier instead of full cancellation - Show what they keep vs. what they lose - Position as "right-size your plan" not "downgrade" - Easy path back up when ready **Feature unlock / extension** - Unlock a premium feature they haven't tried - Extend trial of a higher tier - Works best for "not getting enough value" reasons **Personal outreach** - For high-value accounts (top 10-20% by MRR) - Route to customer success for a call - Personal email from founder for smaller companies ### Cancel Flow UI Patterns ``` ┌─────────────────────────────────────┐ │ We're sorry to see you go │ │ │ │ What's the main reason you're │ │ cancelling? │ │ │ │ ○ Too expensive │ │ ○ Not using it enough │ │ ○ Missing a feature I need │ │ ○ Switching to another tool │ │ ○ Technical issues │ │ ○ Temporary / don't need right now │ │ ○ Other: [____________] │ │ │ │ [Continue] │ │ [Never mind, keep my subscription] │ └─────────────────────────────────────┘ ↓ (selects "Too expensive") ┌─────────────────────────────────────┐ │ What if we could help? │ │ │ │ We'd love to keep you. Here's a │ │ special offer: │ │ │ │ ┌───────────────────────────────┐ │ │ │ 25% off for the next 3 months│ │ │ │ Save $XX/month │ │ │ │ │ │ │ │ [Accept Offer] │ │ │ └───────────────────────────────┘ │ │ │ │ Or switch to [Basic Plan] at │ │ $X/month → │ │ │ │ [No thanks, continue cancelling] │ └─────────────────────────────────────┘ ``` **UI principles:** - Keep the "continue cancelling" option visible (no dark patterns) - One primary offer + one fallback, not a wall of options - Show specific dollar savings, not abstract percentages - Use the customer's name and account data when possible - Mobile-friendly (many cancellations happen on mobile) For detailed cancel flow patterns by industry and billing provider, see [references/cancel-flow-patterns.md](references/cancel-flow-patterns.md). --- ## Churn Prediction & Proactive Retention The best save happens before the customer ever clicks "Cancel." ### Risk Signals Track these leading indicators of churn: | Signal | Risk Level | Timeframe | |--------|-----------|-----------| | Login frequency drops 50%+ | High | 2-4 weeks before cancel | | Key feature usage stops | High | 1-3 weeks before cancel | | Support tickets spike then stop | High | 1-2 weeks before cancel | | Email open rates decline | Medium | 2-6 weeks before cancel | | Billing page visits increase | High | Days before cancel | | Team seats removed | High | 1-2 weeks before cancel | | Data export initiated | Critical | Days before cancel | | NPS score drops below 6 | Medium | 1-3 months before cancel | ### Health Score Model Build a simple health score (0-100) from weighted signals: ``` Health Score = ( Login frequency score × 0.30 + Feature usage score × 0.25 + Support sentiment × 0.15 + Billing health × 0.15 + Engagement score × 0.15 ) ``` | Score | Status | Action | |-------|--------|--------| | 80-100 | Healthy | Upsell opportunities | | 60-79 | Needs attention | Proactive check-in | | 40-59 | At risk | Intervention campaign | | 0-39 | Critical | Personal outreach | ### Proactive Interventions **Before they think about cancelling:** | Trigger | Intervention | |---------|-------------| | Usage drop >50% for 2 weeks | "We noticed you haven't used [feature]. Need help?" email | | Approaching plan limit | Upgrade nudge (not a wall — paywall-upgrade-cro handles this) | | No login for 14 days | Re-engagement email with recent product updates | | NPS detractor (0-6) | Personal follow-up within 24 hours | | Support ticket unresolved >48h | Escalation + proactive status update | | Annual renewal in 30 days | Value recap email + renewal confirmation | --- ## Involuntary Churn: Payment Recovery Failed payments cause 30-50% of all churn but are the most recoverable. ### The Dunning Stack ``` Pre-dunning → Smart retry → Dunning emails → Grace period → Hard cancel ``` ### Pre-Dunning (Prevent Failures) - **Card expiry alerts**: Email 30, 15, and 7 days before card expires - **Backup payment method**: Prompt for a second payment method at signup - **Card updater services**: Visa/Mastercard auto-update programs (reduces hard declines 30-50%) - **Pre-billing notification**: Email 3-5 days before charge for annual plans ### Smart Retry Logic Not all failures are the same. Retry strategy by decline type: | Decline Type | Examples | Retry Strategy | |-------------|----------|----------------| | Soft decline (temporary) | Insufficient funds, processor timeout | Retry 3-5 times over 7-10 days | | Hard decline (permanent) | Card stolen, account closed | Don't retry — ask for new card | | Authentication required | 3D Secure, SCA | Send customer to update payment | **Retry timing best practices:** - Retry 1: 24 hours after failure - Retry 2: 3 days after failure - Retry 3: 5 days after failure - Retry 4: 7 days after failure (with dunning email escalation) - After 4 retries: Hard cancel with reactivation path **Smart retry tip:** Retry on the day of the month the payment originally succeeded (if Day 1 worked before, retry on Day 1). Stripe Smart Retries handles this automatically. ### Dunning Email Sequence | Email | Timing | Tone | Content | |-------|--------|------|---------| | 1 | Day 0 (failure) | Friendly alert | "Your payment didn't go through. Update your card." | | 2 | Day 3 | Helpful reminder | "Quick reminder — update your payment to keep access." | | 3 | Day 7 | Urgency | "Your account will be paused in 3 days. Update now." | | 4 | Day 10 | Final warning | "Last chance to keep your account active." | **Dunning email best practices:** - Direct link to payment update page (no login required if possible) - Show what they'll lose (their data, their team's access) - Don't blame ("your payment failed" not "you failed to pay") - Include support contact for help - Plain text performs better than designed emails for dunning ### Recovery Benchmarks | Metric | Poor | Average | Good | |--------|------|---------|------| | Soft decline recovery | <40% | 50-60% | 70%+ | | Hard decline recovery | <10% | 20-30% | 40%+ | | Overall payment recovery | <30% | 40-50% | 60%+ | | Pre-dunning prevention | None | 10-15% | 20-30% | For the complete dunning playbook with provider-specific setup, see [references/dunning-playbook.md](references/dunning-playbook.md). --- ## Metrics & Measurement ### Key Churn Metrics | Metric | Formula | Target | |--------|---------|--------| | Monthly churn rate | Churned customers / Start-of-month customers | <5% B2C, <2% B2B | | Revenue churn (net) | (Lost MRR - Expansion MRR) / Start MRR | Negative (net expansion) | | Cancel flow save rate | Saved / Total cancel sessions | 25-35% | | Offer acceptance rate | Accepted offers / Shown offers | 15-25% | | Pause reactivation rate | Reactivated / Total paused | 60-80% | | Dunning recovery rate | Recovered / Total failed payments | 50-60% | | Time to cancel | Days from first churn signal to cancel | Track trend | ### Cohort Analysis Segment churn by: - **Acquisition channel** — Which channels bring stickier customers? - **Plan type** — Which plans churn most? - **Tenure** — When do most cancellations happen? (30, 60, 90 days?) - **Cancel reason** — Which reasons are growing? - **Save offer type** — Which offers work best for which segments? ### Cancel Flow A/B Tests Test one variable at a time: | Test | Hypothesis | Metric | |------|-----------|--------| | Discount % (20% vs 30%) | Higher discount saves more | Save rate, LTV impact | | Pause duration (1 vs 3 months) | Longer pause increases return rate | Reactivation rate | | Survey placement (before vs after offer) | Survey-first personalizes offers | Save rate | | Offer presentation (modal vs full page) | Full page gets more attention | Save rate | | Copy tone (empathetic vs direct) | Empathetic reduces friction | Save rate | **How to run cancel flow experiments:** Use the **ab-test-setup** skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the [PostHog integration guide](../../tools/integrations/posthog.md) for setup. --- ## Common Mistakes - **No cancel flow at all** — Instant cancel leaves money on the table. Even a simple survey + one offer saves 10-15% - **Making cancellation hard to find** — Hidden cancel buttons breed resentment and bad reviews. Many jurisdictions require easy cancellation (FTC Click-to-Cancel rule) - **Same offer for every reason** — A blanket discount doesn't address "missing feature" or "not using it" - **Discounts too deep** — 50%+ discounts train customers to cancel-and-return for deals - **Ignoring involuntary churn** — Often 30-50% of total churn and the easiest to fix - **No dunning emails** — Letting payment failures silently cancel accounts - **Guilt-trip copy** — "Are you sure you want to abandon us?" damages brand trust - **Not tracking save offer LTV** — A "saved" customer who churns 30 days later wasn't really saved - **Pausing too long** — Pauses beyond 3 months rarely reactivate. Set limits. - **No post-cancel path** — Make reactivation easy and trigger win-back emails, because some churned users will want to come back --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). ### Retention Platforms | Tool | Best For | Key Feature | |------|----------|-------------| | **Churnkey** | Full cancel flow + dunning | AI-powered adaptive offers, 34% avg save rate | | **ProsperStack** | Cancel flows with analytics | Advanced rules engine, Stripe/Chargebee integration | | **Raaft** | Simple cancel flow builder | Easy setup, good for early-stage | | **Chargebee Retention** | Chargebee customers | Native integration, was Brightback | ### Billing Providers (Dunning) | Provider | Smart Retries | Dunning Emails | Card Updater | |----------|:------------:|:--------------:|:------------:| | **Stripe** | Built-in (Smart Retries) | Built-in | Automatic | | **Chargebee** | Built-in | Built-in | Via gateway | | **Paddle** | Built-in | Built-in | Managed | | **Recurly** | Built-in | Built-in | Built-in | | **Braintree** | Manual config | Manual | Via gateway | ### Related CLI Tools | Tool | Use For | |------|---------| | `stripe` | Subscription management, dunning config, payment retries | | `customer-io` | Dunning email sequences, retention campaigns | | `posthog` | Cancel flow A/B tests via feature flags, funnel analytics | | `mixpanel` / `ga4` | Usage tracking, churn signal analysis | | `segment` | Event routing for health scoring | --- ## Related Skills - **email-sequence**: For win-back email sequences after cancellation - **paywall-upgrade-cro**: For in-app upgrade moments and trial expiration - **pricing-strategy**: For plan structure and annual discount strategy - **onboarding-cro**: For activation to prevent early churn - **analytics-tracking**: For setting up churn signal events - **ab-test-setup**: For testing cancel flow variations with statistical rigor --- Source: https://vibegrow.io/skills/cold-email.md Canonical: https://vibegrow.io/skills/cold-email # Cold Email Writing Canonical: https://vibegrow.io/skills/cold-email Markdown: https://vibegrow.io/skills/cold-email.md Write B2B cold emails and follow-up sequences that get replies. ## Skill Metadata - Slug: cold-email - Category: Lifecycle - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - write cold outreach emails, prospecting emails, cold email campaigns, sales deve ## Full Skill Source # Cold Email Writing You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template. ## Before Writing **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Understand the situation (ask if not provided): 1. **Who are you writing to?** — Role, company, why them specifically 2. **What do you want?** — The outcome (meeting, reply, intro, demo) 3. **What's the value?** — The specific problem you solve for people like them 4. **What's your proof?** — A result, case study, or credibility signal 5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger. --- ## Writing Principles ### Write like a peer, not a vendor The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it. ### Every sentence must earn its place Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer. ### Personalization must connect to the problem If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out. See [personalization.md](references/personalization.md) for the 4-level system and research signals. ### Lead with their world, not yours The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does. ### One ask, low friction Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply. --- ## Voice & Tone **The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy. **Calibrate to the audience:** - C-suite: ultra-brief, peer-level, understated - Mid-level: more specific value, slightly more detail - Technical: precise, no fluff, respect their intelligence **What it should NOT sound like:** - A template with fields swapped in - A pitch deck compressed into paragraph form - A LinkedIn DM from someone you've never met - An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class") --- ## Structure There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one. **Common shapes that work:** - **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested? - **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look? - **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious? - **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you? For the full catalog of frameworks with examples, see [frameworks.md](references/frameworks.md). --- ## Subject Lines Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell. - 2-4 words, lowercase, no punctuation tricks - Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast") - No product pitches, no urgency, no emojis, no prospect's first name See [subject-lines.md](references/subject-lines.md) for the full data. --- ## Follow-Up Sequences Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond. - 3-5 total emails, increasing gaps between them - Each email should stand alone (they may not have read the previous ones) - The breakup email is your last touch — honor it See [follow-up-sequences.md](references/follow-up-sequences.md) for cadence, angle rotation, and breakup email templates. --- ## Quality Check Before presenting, gut-check: - Does it sound like a human wrote it? (Read it aloud) - Would YOU reply to this if you received it? - Does every sentence serve the reader, not the sender? - Is the personalization connected to the problem? - Is there one clear, low-friction ask? --- ## What to Avoid - Opening with "I hope this email finds you well" or "My name is X and I work at Y" - Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider" - Feature dumps — one proof point beats ten features - HTML, images, or multiple links - Fake "Re:" or "Fwd:" subject lines - Identical templates with only {{FirstName}} swapped - Asking for 30-minute calls in first touch - "Just checking in" follow-ups --- ## Data & Benchmarks The references contain performance data if you need to make informed choices: - [benchmarks.md](references/benchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes - [personalization.md](references/personalization.md) — 4-level personalization system, research signals - [subject-lines.md](references/subject-lines.md) — Subject line data and optimization - [follow-up-sequences.md](references/follow-up-sequences.md) — Cadence, angles, breakup emails - [frameworks.md](references/frameworks.md) — All copywriting frameworks with examples Use this data to inform your writing — not as a checklist to satisfy. --- ## Related Skills - **copywriting**: For landing pages and web copy - **email-sequence**: For lifecycle/nurture email sequences (not cold outreach) - **social-content**: For LinkedIn and social posts - **product-marketing-context**: For establishing foundational positioning - **revops**: For lead scoring, routing, and pipeline management --- Source: https://vibegrow.io/skills/community-marketing.md Canonical: https://vibegrow.io/skills/community-marketing # Community Marketing Canonical: https://vibegrow.io/skills/community-marketing Markdown: https://vibegrow.io/skills/community-marketing.md Build and leverage online communities to drive product growth and brand loyalty. ## Skill Metadata - Slug: community-marketing - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create a community strategy, grow a Discord or Slack community, manage a forum o ## Full Skill Source # Community Marketing You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes. ## Before You Start **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered. Understand the situation (ask if not provided): 1. **What is the product or brand?** — What problem does it solve, who uses it 2. **What community platform(s) are in play?** — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc. 3. **What stage is the community at?** — Pre-launch, 0–100 members, 100–1k, scaling, or established 4. **What is the primary community goal?** — Retention, activation, word-of-mouth, support deflection, product feedback, revenue 5. **Who is the ideal community member?** — Role, motivation, what they hope to get from joining Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them. --- ## Community Strategy Principles ### Build around a shared identity, not just a product The strongest communities are built around who members *are* or aspire to be — not around your product. Members join because of the product but stay because of the people and identity. Examples: - Indie hackers (identity: bootstrapped founders) - r/homelab (identity: tinkerers who self-host) - Figma community (identity: designers who care about craft) Always define: **What identity does this community reinforce for its members?** ### Value must flow to members first Every community touchpoint should answer: *What does the member get from this?* - Exclusive knowledge or early access - Peer connections they can't get elsewhere - Recognition and status within a group they respect - Direct influence on the product roadmap - Career opportunities, visibility, or credibility ### The Community Flywheel Healthy communities compound over time: ``` Members join → get value → engage → create content/help others ↑ ↓ ←←←←← new members discover the community ←← ``` Design for the flywheel from day one. Every decision should ask: *Does this accelerate the loop or slow it down?* --- ## Playbooks by Goal ### Launching a Community from Zero 1. **Recruit 20–50 founding members manually** — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity. 2. **Set the culture explicitly** — Write community guidelines that describe the *vibe*, not just the rules. What does great participation look like here? 3. **Seed conversations before launch** — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources. 4. **Do things that don't scale at first** — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof. 5. **Define your core loop** — What action do you want members to take weekly? Make it easy and reward it publicly. ### Growing an Existing Community 1. **Audit where members drop off** — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage. 2. **Create a new member journey** — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear "start here" path. 3. **Surface member wins publicly** — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards. 4. **Run recurring community rituals** — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit. 5. **Identify and invest in power users** — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input. ### Building a Brand Ambassador / Advocate Program 1. **Identify candidates** — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts. 2. **Make the ask personal** — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically. 3. **Offer meaningful benefits** — Exclusive access, swag, revenue share, or public recognition — not just "early access to features." 4. **Give them tools and content** — Referral links, shareable assets, key talking points, a private Slack channel. 5. **Measure and iterate** — Track referral traffic, signups, and engagement driven by advocates. Double down on what works. ### Community-Led Support (Deflection + Retention) 1. **Create a searchable knowledge base** from top community questions 2. **Recognize members who help others** — "Community Expert" badges, leaderboards, shoutouts 3. **Close the loop with product** — When community feedback drives a change, announce it publicly and credit the members who raised it 4. **Monitor sentiment weekly** — Look for patterns in complaints or confusion before they become churn signals --- ## Platform Selection Guide | Platform | Best For | Watch Out For | |----------|----------|---------------| | Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction | | Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work | | Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic | | Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard | | Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent | | Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post | --- ## Community Health Metrics Track these signals weekly: - **DAU/MAU ratio** — Stickiness. Above 20% is healthy for most communities. - **New member post rate** — % of new members who post within 7 days of joining - **Thread reply rate** — % of posts that receive at least one reply - **Churn / lurker ratio** — Members who joined but haven't posted in 30+ days - **Content created by non-staff** — % of posts not written by the company team **Warning signs:** - Most posts are from the company team, not members - Questions go unanswered for >24 hours - The same 5 people account for 80%+ of engagement - New members stop posting after their intro message --- ## Output Formats Depending on what the user needs, produce one of: - **Community Strategy Doc** — Platform choice, identity definition, core loop, 90-day launch plan - **Channel Architecture** — Recommended channels/categories with purpose and posting guidelines for each - **New Member Journey** — Welcome sequence: pinned post, DM template, first-week prompts - **Community Ritual Calendar** — Weekly/monthly recurring events and threads - **Ambassador Program Brief** — Criteria, benefits, outreach template, tracking plan - **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today. --- ## Task-Specific Questions 1. What platform are you building on (or considering)? 2. What stage is the community at? (Pre-launch, early, growing, established) 3. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection) 4. Who is the ideal community member and what motivates them? 5. Do you have existing users or customers to seed from? 6. How much time can you dedicate to community management weekly? --- ## Related Skills - **referral-program**: For structured referral and ambassador incentive programs - **churn-prevention**: For retention strategies that complement community engagement - **social-content**: For content creation across social platforms - **customer-research**: For understanding your community members' needs and language --- Source: https://vibegrow.io/skills/competitor-alternatives.md Canonical: https://vibegrow.io/skills/competitor-alternatives # Competitor & Alternative Pages Canonical: https://vibegrow.io/skills/competitor-alternatives Markdown: https://vibegrow.io/skills/competitor-alternatives.md Create competitor comparison or alternative pages for SEO and sales enablement. ## Skill Metadata - Slug: competitor-alternatives - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create competitor comparison or alternative pages for SEO and sales enablement ## Full Skill Source # Competitor & Alternative Pages You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before creating competitor pages, understand: 1. **Your Product** - Core value proposition - Key differentiators - Ideal customer profile - Pricing model - Strengths and honest weaknesses 2. **Competitive Landscape** - Direct competitors - Indirect/adjacent competitors - Market positioning of each - Search volume for competitor terms 3. **Goals** - SEO traffic capture - Sales enablement - Conversion from competitor users - Brand positioning --- ## Core Principles ### 1. Honesty Builds Trust - Acknowledge competitor strengths - Be accurate about your limitations - Don't misrepresent competitor features - Readers are comparing—they'll verify claims ### 2. Depth Over Surface - Go beyond feature checklists - Explain *why* differences matter - Include use cases and scenarios - Show, don't just tell ### 3. Help Them Decide - Different tools fit different needs - Be clear about who you're best for - Be clear about who competitor is best for - Reduce evaluation friction ### 4. Modular Content Architecture - Competitor data should be centralized - Updates propagate to all pages - Single source of truth per competitor --- ## Page Formats ### Format 1: [Competitor] Alternative (Singular) **Search intent**: User is actively looking to switch from a specific competitor **URL pattern**: `/alternatives/[competitor]` or `/[competitor]-alternative` **Target keywords**: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]" **Page structure**: 1. Why people look for alternatives (validate their pain) 2. Summary: You as the alternative (quick positioning) 3. Detailed comparison (features, service, pricing) 4. Who should switch (and who shouldn't) 5. Migration path 6. Social proof from switchers 7. CTA --- ### Format 2: [Competitor] Alternatives (Plural) **Search intent**: User is researching options, earlier in journey **URL pattern**: `/alternatives/[competitor]-alternatives` **Target keywords**: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]" **Page structure**: 1. Why people look for alternatives (common pain points) 2. What to look for in an alternative (criteria framework) 3. List of alternatives (you first, but include real options) 4. Comparison table (summary) 5. Detailed breakdown of each alternative 6. Recommendation by use case 7. CTA **Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better. --- ### Format 3: You vs [Competitor] **Search intent**: User is directly comparing you to a specific competitor **URL pattern**: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]` **Target keywords**: "[You] vs [Competitor]", "[Competitor] vs [You]" **Page structure**: 1. TL;DR summary (key differences in 2-3 sentences) 2. At-a-glance comparison table 3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations) 4. Who [You] is best for 5. Who [Competitor] is best for (be honest) 6. What customers say (testimonials from switchers) 7. Migration support 8. CTA --- ### Format 4: [Competitor A] vs [Competitor B] **Search intent**: User comparing two competitors (not you directly) **URL pattern**: `/compare/[competitor-a]-vs-[competitor-b]` **Page structure**: 1. Overview of both products 2. Comparison by category 3. Who each is best for 4. The third option (introduce yourself) 5. Comparison table (all three) 6. CTA **Why this works**: Captures search traffic for competitor terms, positions you as knowledgeable. --- ## Essential Sections ### TL;DR Summary Start every page with a quick summary for scanners—key differences in 2-3 sentences. ### Paragraph Comparisons Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters. ### Feature Comparison For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation. ### Pricing Comparison Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size. ### Who It's For Be explicit about ideal customer for each option. Honest recommendations build trust. ### Migration Section Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched. **For detailed templates**: See [references/templates.md](references/templates.md) --- ## Content Architecture ### Centralized Competitor Data Create a single source of truth for each competitor with: - Positioning and target audience - Pricing (all tiers) - Feature ratings - Strengths and weaknesses - Best for / not ideal for - Common complaints (from reviews) - Migration notes **For data structure and examples**: See [references/content-architecture.md](references/content-architecture.md) --- ## Research Process ### Deep Competitor Research For each competitor, gather: 1. **Product research**: Sign up, use it, document features/UX/limitations 2. **Pricing research**: Current pricing, what's included, hidden costs 3. **Review mining**: G2, Capterra, TrustRadius for common praise/complaint themes 4. **Customer feedback**: Talk to customers who switched (both directions) 5. **Content research**: Their positioning, their comparison pages, their changelog ### Ongoing Updates - **Quarterly**: Verify pricing, check for major feature changes - **When notified**: Customer mentions competitor change - **Annually**: Full refresh of all competitor data --- ## SEO Considerations ### Keyword Targeting | Format | Primary Keywords | |--------|-----------------| | Alternative (singular) | [Competitor] alternative, alternative to [Competitor] | | Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives | | You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] | | Competitor vs Competitor | [A] vs [B], [B] vs [A] | ### Internal Linking - Link between related competitor pages - Link from feature pages to relevant comparisons - Create hub page linking to all competitor content ### Schema Markup Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?" --- ## Output Format ### Competitor Data File Complete competitor profile in YAML format for use across all comparison pages. ### Page Content For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs. ### Page Set Plan Recommended pages to create with priority order based on search volume. --- ## Task-Specific Questions 1. What are common reasons people switch to you? 2. Do you have customer quotes about switching? 3. What's your pricing vs. competitors? 4. Do you offer migration support? --- ## Related Skills - **programmatic-seo**: For building competitor pages at scale - **copywriting**: For writing compelling comparison copy - **seo-audit**: For optimizing competitor pages - **schema-markup**: For FAQ and comparison schema - **sales-enablement**: For internal sales collateral, decks, and objection docs --- Source: https://vibegrow.io/skills/competitor-profiling.md Canonical: https://vibegrow.io/skills/competitor-profiling # Competitor Profiling Canonical: https://vibegrow.io/skills/competitor-profiling Markdown: https://vibegrow.io/skills/competitor-profiling.md Research, profile, or analyze competitors from their URLs. ## Skill Metadata - Slug: competitor-profiling - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - research, profile, or analyze competitors from their URLs ## Full Skill Source # Competitor Profiling You are an expert competitive intelligence analyst. Your goal is to take a list of competitor URLs and produce comprehensive, structured competitor profile documents by combining live site scraping with SEO and market data. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered. Before profiling, confirm: 1. **Competitor URLs** — the list of competitor website URLs to profile 2. **Your product** — what you do (if not in product marketing context) 3. **Depth level** — quick scan (key facts only) or deep profile (full research) 4. **Focus areas** — any specific dimensions to prioritize (e.g., pricing, positioning, SEO strength, content strategy) If the user provides URLs and context is available, proceed without asking. --- ## Core Principles ### 1. Facts Over Opinions Every claim in a profile should be traceable to a source — scraped page content, review data, or SEO metrics. Label inferences clearly. ### 2. Structured and Comparable All profiles follow the same template so they can be compared side by side. Consistency matters more than completeness on any single profile. ### 3. Current Data Profiles are snapshots. Always include the date generated. Flag anything that looks stale (e.g., "pricing page last updated 2023"). ### 4. Honest Assessment Don't exaggerate competitor weaknesses or downplay their strengths. Accurate profiles are useful profiles. --- ## Saving Raw Data Before synthesizing the profile, persist all raw scrape, SEO, and review data to disk so it can be re-read, audited, or re-used later without re-running expensive API calls. **Directory layout** (relative to project root): ``` competitor-profiles/ ├── raw/ │ └── / │ └── / │ ├── scrapes/ # one .md file per scraped page (homepage.md, pricing.md, ...) │ ├── seo/ # one .json file per DataForSEO call (backlinks-summary.json, ranked-keywords.json, ...) │ └── reviews/ # one .md or .json file per review source (g2.md, capterra.md, ...) ├── .md # final synthesized profile └── _summary.md # cross-competitor summary ``` Rules: - `` is lowercase, hyphenated (e.g. `responsehub`, `safe-base`) - `` is the date the data was pulled — supports re-running and diffing snapshots over time - Save each Firecrawl scrape as raw markdown to `scrapes/.md` - Save each DataForSEO response as raw JSON to `seo/.json` - Save each review source to `reviews/.md` (cleaned text) or `.json` (raw) - Always create the date folder fresh on a new run; never overwrite a prior date's data The synthesized profile (`.md`) should reference the raw data folder it was built from in its `## Raw Data Sources` section. --- ## Research Process ### Phase 1: Site Scraping (Firecrawl) For each competitor URL, scrape key pages to extract positioning, features, pricing, and messaging. #### Step 1: Map the site Use **Firecrawl Map** to discover the competitor's site structure and identify key pages: ``` firecrawl_map → competitor URL ``` From the map, identify and prioritize these page types: - Homepage - Pricing page - Features / product pages - About / company page - Blog (top-level, for content strategy signals) - Customers / case studies page - Integrations page - Changelog / what's new (if exists) #### Step 2: Scrape key pages Use **Firecrawl Scrape** on each identified page: ``` firecrawl_scrape → each key page URL ``` Save each result to `competitor-profiles/raw///scrapes/.md` before extracting fields. Extract from each page: | Page | What to Extract | |------|----------------| | **Homepage** | Headline, subheadline, value proposition, primary CTA, social proof claims, target audience signals | | **Pricing** | Tiers, prices, feature breakdown per tier, billing options, free tier/trial details, enterprise pricing signals | | **Features** | Feature categories, key capabilities, how they describe each feature, screenshots/demo signals | | **About** | Founding story, team size, funding, mission statement, headquarters | | **Customers** | Named customers, logos, industries served, case study themes | | **Integrations** | Integration count, key integrations, categories | | **Changelog** | Release velocity, recent focus areas, product direction signals | #### Step 3: Scrape competitor reviews (optional but high-value) Use **Firecrawl Scrape** or **Firecrawl Search** to find: - G2 reviews page for the competitor - Capterra reviews page - Product Hunt launch page - TrustRadius profile Save each scraped review page to `competitor-profiles/raw///reviews/.md`. Then extract: overall rating, review count, common praise themes, common complaint themes, and 3-5 representative quotes. --- ### Phase 2: SEO & Market Data (DataForSEO) Use DataForSEO MCP tools to gather quantitative competitive intelligence. Save each raw response as JSON to `competitor-profiles/raw///seo/.json` before parsing it into the profile. For the full list of MCP tools used in this skill (Firecrawl + DataForSEO) and example calls, see [references/tool-reference.md](references/tool-reference.md). #### Domain Authority & Backlinks Use **backlinks_summary** to get: - Domain rank / authority score - Total backlinks - Referring domains count - Spam score Use **backlinks_referring_domains** for: - Top referring domains (quality signals) - Link acquisition patterns #### Keyword & Traffic Intelligence Use **dataforseo_labs_google_ranked_keywords** to get: - Total organic keywords ranking - Keywords in top 3, top 10, top 100 - Estimated organic traffic Use **dataforseo_labs_google_domain_rank_overview** for: - Domain-level organic metrics - Estimated traffic value - Top keywords by traffic Use **dataforseo_labs_google_keywords_for_site** to discover: - What keywords they target - Content gaps vs. your site #### Competitive Positioning Data Use **dataforseo_labs_google_competitors_domain** to find: - Their closest organic competitors (may reveal competitors you haven't considered) - Market overlap data Use **dataforseo_labs_google_relevant_pages** to find: - Their highest-traffic pages - Content that drives the most organic value --- ### Phase 3: Synthesis Combine scraped content with SEO data to build the profile. Cross-reference claims (e.g., if they claim "10,000 customers" on site, check if their traffic/backlink profile supports that scale). --- ## Output Format ### Profile Document Structure Generate one markdown file per competitor, saved to a `competitor-profiles/` directory in the project root. **Filename**: `competitor-profiles/[competitor-name].md` **For the full profile and summary templates**: See [references/templates.md](references/templates.md) Each profile follows this structure: ```markdown # [Competitor Name] — Competitor Profile **URL**: [website] **Generated**: [date] **Depth**: [quick scan / deep profile] --- ## At a Glance | Metric | Value | |--------|-------| | Tagline | [from homepage] | | Founded | [year] | | Headquarters | [location] | | Team size | [estimate] | | Funding | [if known] | | Domain rank | [from DataForSEO] | | Est. organic traffic | [monthly] | | Referring domains | [count] | | Organic keywords | [count] | --- ## Positioning & Messaging **Primary value proposition**: [headline + subheadline from homepage] **Target audience**: [who they're speaking to, based on copy analysis] **Positioning angle**: [how they position — e.g., "simplicity-first," "enterprise-grade," "all-in-one"] **Key messaging themes**: - [theme 1 — with source page] - [theme 2] - [theme 3] --- ## Product & Features ### Core capabilities - [capability 1] — [brief description from their site] - [capability 2] - ... ### Notable differentiators - [what they emphasize as unique] ### Integrations - [count] integrations - Key: [list top 5-10] ### Product direction signals - [based on changelog / recent feature releases] --- ## Pricing | Tier | Price | Key Inclusions | |------|-------|---------------| | [Free/Starter] | [price] | [what's included] | | [Pro/Growth] | [price] | [what's included] | | [Enterprise] | [price] | [what's included] | **Billing**: [monthly/annual, discount for annual] **Free trial**: [yes/no, duration] **Notable**: [any pricing quirks — per-seat, usage-based, hidden costs] --- ## Customers & Social Proof **Named customers**: [list notable logos] **Industries**: [primary industries served] **Case study themes**: [what outcomes they highlight] **Review ratings**: - G2: [rating] ([count] reviews) - Capterra: [rating] ([count] reviews) --- ## SEO & Content Strategy **Organic strength**: - Estimated monthly organic traffic: [number] - Organic keywords (top 10): [count] - Organic traffic value: $[estimated] **Top organic pages** (by estimated traffic): 1. [page URL] — [keyword] — [est. traffic] 2. [page URL] — [keyword] — [est. traffic] 3. [page URL] — [keyword] — [est. traffic] **Content strategy signals**: - Blog post frequency: [estimate] - Primary content types: [guides, comparisons, templates, etc.] - Content focus areas: [topics they invest in] **Backlink profile**: - Referring domains: [count] - Top referring sites: [list 5] - Link acquisition pattern: [growing/stable/declining] --- ## Strengths & Weaknesses ### Strengths - [strength 1 — with evidence source] - [strength 2] - [strength 3] ### Weaknesses - [weakness 1 — with evidence source] - [weakness 2] - [weakness 3] --- ## Competitive Implications for [Your Product] **Where they're strong vs. us**: [areas where this competitor has an advantage] **Where we're strong vs. them**: [areas where you have an advantage] **Opportunities**: [gaps in their offering or positioning we can exploit] **Threats**: [areas where they're improving or gaining ground] --- ## Raw Data Sources - Homepage scraped: [date] - Pricing page scraped: [date] - SEO data pulled: [date] - Review data pulled: [date, sources] ``` --- ### Summary Document After profiling all competitors, generate a `competitor-profiles/_summary.md` that includes: 1. **Competitor landscape overview** — one paragraph summarizing the competitive field 2. **Comparison table** — key metrics side by side for all profiled competitors 3. **Positioning map** — where each competitor sits (e.g., simple↔complex, cheap↔premium) 4. **Key takeaways** — 3-5 strategic observations from the research 5. **Gaps and opportunities** — where the market is underserved --- ## Quick Scan vs. Deep Profile ### Quick Scan (faster, lower cost) - Scrape: homepage + pricing page only - SEO: domain rank overview + ranked keywords summary - Skip: reviews, technology stack, backlink details - Output: abbreviated profile (At a Glance + Positioning + Pricing + SEO summary) ### Deep Profile (comprehensive) - Scrape: all key pages + review sites - SEO: full backlink analysis + keyword intelligence + competitor discovery - Include: technology stack, content strategy analysis, review mining - Output: full profile template Default to **quick scan** unless the user requests deep profiling or specifies a small number of competitors (3 or fewer). --- ## Handling Multiple Competitors When profiling more than one competitor: 1. **Parallelize scraping** — scrape all competitors' homepages simultaneously, then pricing pages, etc. 2. **Use consistent metrics** — pull the same DataForSEO metrics for every competitor so profiles are comparable 3. **Build the summary last** — after all individual profiles are complete 4. **Prioritize by relevance** — if the user has 10+ competitors, suggest profiling the top 5 first based on domain overlap or market similarity --- ## Updating Profiles Profiles are snapshots. When updating: - Check pricing pages first (most volatile) - Re-pull SEO metrics (traffic and rankings shift monthly) - Scan changelog for product changes - Update the "Generated" date - Note what changed since last profile in a `## Change Log` section at the bottom --- ## Task-Specific Questions Only ask if not answered by context or input: 1. What competitor URLs should I profile? 2. Quick scan or deep profile? 3. Any specific dimensions to focus on (pricing, SEO, positioning)? 4. Should I compare findings against your product? --- ## Related Skills - **competitor-alternatives**: For creating comparison/alternative pages from these profiles - **customer-research**: For mining reviews and community sentiment in depth - **content-strategy**: For using competitor content gaps to plan your own content - **seo-audit**: For auditing your own site relative to competitors - **sales-enablement**: For turning profiles into battle cards and sales collateral - **paid-ads**: For analyzing competitor ad strategies - **pricing-strategy**: For deeper pricing analysis informed by competitor profiles --- Source: https://vibegrow.io/skills/content-strategy.md Canonical: https://vibegrow.io/skills/content-strategy # Content Strategy Canonical: https://vibegrow.io/skills/content-strategy Markdown: https://vibegrow.io/skills/content-strategy.md Plan a content strategy, decide what content to create, or figure out what topics to cover. ## Skill Metadata - Slug: content-strategy - Category: Content - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - plan a content strategy, decide what content to create, or figure out what topic ## Full Skill Source # Content Strategy You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both. ## Before Planning **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Business Context - What does the company do? - Who is the ideal customer? - What's the primary goal for content? (traffic, leads, brand awareness, thought leadership) - What problems does your product solve? ### 2. Customer Research - What questions do customers ask before buying? - What objections come up in sales calls? - What topics appear repeatedly in support tickets? - What language do customers use to describe their problems? ### 3. Current State - Do you have existing content? What's working? - What resources do you have? (writers, budget, time) - What content formats can you produce? (written, video, audio) ### 4. Competitive Landscape - Who are your main competitors? - What content gaps exist in your market? --- ## Searchable vs Shareable Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation. **Searchable content** captures existing demand. Optimized for people actively looking for answers. **Shareable content** creates demand. Spreads ideas and gets people talking. ### When Writing Searchable Content - Target a specific keyword or question - Match search intent exactly—answer what the searcher wants - Use clear titles that match search queries - Structure with headings that mirror search patterns - Place keywords in title, headings, first paragraph, URL - Provide comprehensive coverage (don't leave questions unanswered) - Include data, examples, and links to authoritative sources - Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web ### When Writing Shareable Content - Lead with a novel insight, original data, or counterintuitive take - Challenge conventional wisdom with well-reasoned arguments - Tell stories that make people feel something - Create content people want to share to look smart or help others - Connect to current trends or emerging problems - Share vulnerable, honest experiences others can learn from --- ## Content Types ### Searchable Content Types **Use-Case Content** Formula: [persona] + [use-case]. Targets long-tail keywords. - "Project management for designers" - "Task tracking for developers" - "Client collaboration for freelancers" **Hub and Spoke** Hub = comprehensive overview. Spokes = related subtopics. ``` /topic (hub) ├── /topic/subtopic-1 (spoke) ├── /topic/subtopic-2 (spoke) └── /topic/subtopic-3 (spoke) ``` Create hub first, then build spokes. Interlink strategically. **Note:** Most content works fine under `/blog`. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's `/agile` guide). For typical blog posts, `/blog/post-title` is sufficient. **Template Libraries** High-intent keywords + product adoption. - Target searches like "marketing plan template" - Provide immediate standalone value - Show how product enhances the template ### Shareable Content Types **Thought Leadership** - Articulate concepts everyone feels but hasn't named - Challenge conventional wisdom with evidence - Share vulnerable, honest experiences **Data-Driven Content** - Product data analysis (anonymized insights) - Public data analysis (uncover patterns) - Original research (run experiments, share results) **Expert Roundups** 15-30 experts answering one specific question. Built-in distribution. **Case Studies** Structure: Challenge → Solution → Results → Key learnings **Meta Content** Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC." For programmatic content at scale, see **programmatic-seo** skill. --- ## Content Pillars and Topic Clusters Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content. Most of the time, all content can live under `/blog` with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like `/guides/topic`) are only needed when you're building comprehensive resources with multiple layers of depth. ### How to Identify Pillars 1. **Product-led**: What problems does your product solve? 2. **Audience-led**: What does your ICP need to learn? 3. **Search-led**: What topics have volume in your space? 4. **Competitor-led**: What are competitors ranking for? ### Pillar Structure ``` Pillar Topic (Hub) ├── Subtopic Cluster 1 │ ├── Article A │ ├── Article B │ └── Article C ├── Subtopic Cluster 2 │ ├── Article D │ ├── Article E │ └── Article F └── Subtopic Cluster 3 ├── Article G ├── Article H └── Article I ``` ### Pillar Criteria Good pillars should: - Align with your product/service - Match what your audience cares about - Have search volume and/or social interest - Be broad enough for many subtopics --- ## Keyword Research by Buyer Stage Map topics to the buyer's journey using proven keyword modifiers: ### Awareness Stage Modifiers: "what is," "how to," "guide to," "introduction to" Example: If customers ask about project management basics: - "What is Agile Project Management" - "Guide to Sprint Planning" - "How to Run a Standup Meeting" ### Consideration Stage Modifiers: "best," "top," "vs," "alternatives," "comparison" Example: If customers evaluate multiple tools: - "Best Project Management Tools for Remote Teams" - "Asana vs Trello vs Monday" - "Basecamp Alternatives" ### Decision Stage Modifiers: "pricing," "reviews," "demo," "trial," "buy" Example: If pricing comes up in sales calls: - "Project Management Tool Pricing Comparison" - "How to Choose the Right Plan" - "[Product] Reviews" ### Implementation Stage Modifiers: "templates," "examples," "tutorial," "how to use," "setup" Example: If support tickets show implementation struggles: - "Project Template Library" - "Step-by-Step Setup Tutorial" - "How to Use [Feature]" --- ## Content Ideation Sources ### 1. Keyword Data If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for: - Topic clusters (group related keywords) - Buyer stage (awareness/consideration/decision/implementation) - Search intent (informational, commercial, transactional) - Quick wins (low competition + decent volume + high relevance) - Content gaps (keywords competitors rank for that you don't) Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority | ### 2. Call Transcripts If user provides sales or customer call transcripts, extract: - Questions asked → FAQ content or blog posts - Pain points → problems in their own words - Objections → content to address proactively - Language patterns → exact phrases to use (voice of customer) - Competitor mentions → what they compared you to Output content ideas with supporting quotes. ### 3. Survey Responses If user provides survey data, mine for: - Open-ended responses (topics and language) - Common themes (30%+ mention = high priority) - Resource requests (what they wish existed) - Content preferences (formats they want) ### 4. Forum Research Use web search to find content ideas: **Reddit:** `site:reddit.com [topic]` - Top posts in relevant subreddits - Questions and frustrations in comments - Upvoted answers (validates what resonates) **Quora:** `site:quora.com [topic]` - Most-followed questions - Highly upvoted answers **Other:** Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord Extract: FAQs, misconceptions, debates, problems being solved, terminology used. ### 5. Competitor Analysis Use web search to analyze competitor content: **Find their content:** `site:competitor.com/blog` **Analyze:** - Top-performing posts (comments, shares) - Topics covered repeatedly - Gaps they haven't covered - Case studies (customer problems, use cases, results) - Content structure (pillars, categories, formats) **Identify opportunities:** - Topics you can cover better - Angles they're missing - Outdated content to improve on ### 6. Sales and Support Input Extract from customer-facing teams: - Common objections - Repeated questions - Support ticket patterns - Success stories - Feature requests and underlying problems --- ## Prioritizing Content Ideas Score each idea on four factors: ### 1. Customer Impact (40%) - How frequently did this topic come up in research? - What percentage of customers face this challenge? - How emotionally charged was this pain point? - What's the potential LTV of customers with this need? ### 2. Content-Market Fit (30%) - Does this align with problems your product solves? - Can you offer unique insights from customer research? - Do you have customer stories to support this? - Will this naturally lead to product interest? ### 3. Search Potential (20%) - What's the monthly search volume? - How competitive is this topic? - Are there related long-tail opportunities? - Is search interest growing or declining? ### 4. Resource Requirements (10%) - Do you have expertise to create authoritative content? - What additional research is needed? - What assets (graphics, data, examples) will you need? ### Scoring Template | Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total | |------|----------------------|-------------------------|----------------------|-----------------|-------| | Topic A | 8 | 9 | 7 | 6 | 8.0 | | Topic B | 6 | 7 | 9 | 8 | 7.1 | --- ## Output Format When creating a content strategy, provide: ### 1. Content Pillars - 3-5 pillars with rationale - Subtopic clusters for each pillar - How pillars connect to product ### 2. Priority Topics For each recommended piece: - Topic/title - Searchable, shareable, or both - Content type (use-case, hub/spoke, thought leadership, etc.) - Target keyword and buyer stage - Why this topic (customer research backing) ### 3. Topic Cluster Map Visual or structured representation of how content interconnects. --- ## Task-Specific Questions 1. What patterns emerge from your last 10 customer conversations? 2. What questions keep coming up in sales calls? 3. Where are competitors' content efforts falling short? 4. What unique insights from customer research aren't being shared elsewhere? 5. Which existing content drives the most conversions, and why? --- ## References - **[Headless CMS Guide](references/headless-cms.md)**: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi) --- ## Related Skills - **copywriting**: For writing individual content pieces - **seo-audit**: For technical SEO and on-page optimization - **ai-seo**: For optimizing content for AI search engines and getting cited by LLMs - **programmatic-seo**: For scaled content generation - **site-architecture**: For page hierarchy, navigation design, and URL structure - **email-sequence**: For email-based content - **social-content**: For social media content --- Source: https://vibegrow.io/skills/copy-editing.md Canonical: https://vibegrow.io/skills/copy-editing # Copy Editing Canonical: https://vibegrow.io/skills/copy-editing Markdown: https://vibegrow.io/skills/copy-editing.md Edit, review, or improve existing marketing copy, or refresh outdated content. ## Skill Metadata - Slug: copy-editing - Category: Content - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - edit, review, or improve existing marketing copy, or refresh outdated content ## Full Skill Source # Copy Editing You are an expert copy editor specializing in marketing and conversion copy. Your goal is to systematically improve existing copy through focused editing passes while preserving the core message. ## Core Philosophy **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before editing. Use brand voice and customer language from that context to guide your edits. Good copy editing isn't about rewriting—it's about enhancing. Each pass focuses on one dimension, catching issues that get missed when you try to fix everything at once. **Key principles:** - Don't change the core message; focus on enhancing it - Multiple focused passes beat one unfocused review - Each edit should have a clear reason - Preserve the author's voice while improving clarity --- ## The Seven Sweeps Framework Edit copy through seven sequential passes, each focusing on one dimension. After each sweep, loop back to check previous sweeps aren't compromised. ### Sweep 1: Clarity **Focus:** Can the reader understand what you're saying? **What to check:** - Confusing sentence structures - Unclear pronoun references - Jargon or insider language - Ambiguous statements - Missing context **Common clarity killers:** - Sentences trying to say too much - Abstract language instead of concrete - Assuming reader knowledge they don't have - Burying the point in qualifications **Process:** 1. Read through quickly, highlighting unclear parts 2. Don't correct yet—just note problem areas 3. After marking issues, recommend specific edits 4. Verify edits maintain the original intent **After this sweep:** Confirm the "Rule of One" (one main idea per section) and "You Rule" (copy speaks to the reader) are intact. --- ### Sweep 2: Voice and Tone **Focus:** Is the copy consistent in how it sounds? **What to check:** - Shifts between formal and casual - Inconsistent brand personality - Mood changes that feel jarring - Word choices that don't match the brand **Common voice issues:** - Starting casual, becoming corporate - Mixing "we" and "the company" references - Humor in some places, serious in others (unintentionally) - Technical language appearing randomly **Process:** 1. Read aloud to hear inconsistencies 2. Mark where tone shifts unexpectedly 3. Recommend edits that smooth transitions 4. Ensure personality remains throughout **After this sweep:** Return to Clarity Sweep to ensure voice edits didn't introduce confusion. --- ### Sweep 3: So What **Focus:** Does every claim answer "why should I care?" **What to check:** - Features without benefits - Claims without consequences - Statements that don't connect to reader's life - Missing "which means..." bridges **The So What test:** For every statement, ask "Okay, so what?" If the copy doesn't answer that question with a deeper benefit, it needs work. ❌ "Our platform uses AI-powered analytics" *So what?* ✅ "Our AI-powered analytics surface insights you'd miss manually—so you can make better decisions in half the time" **Common So What failures:** - Feature lists without benefit connections - Impressive-sounding claims that don't land - Technical capabilities without outcomes - Company achievements that don't help the reader **Process:** 1. Read each claim and literally ask "so what?" 2. Highlight claims missing the answer 3. Add the benefit bridge or deeper meaning 4. Ensure benefits connect to real reader desires **After this sweep:** Return to Voice and Tone, then Clarity. --- ### Sweep 4: Prove It **Focus:** Is every claim supported with evidence? **What to check:** - Unsubstantiated claims - Missing social proof - Assertions without backup - "Best" or "leading" without evidence **Types of proof to look for:** - Testimonials with names and specifics - Case study references - Statistics and data - Third-party validation - Guarantees and risk reversals - Customer logos - Review scores **Common proof gaps:** - "Trusted by thousands" (which thousands?) - "Industry-leading" (according to whom?) - "Customers love us" (show them saying it) - Results claims without specifics **Process:** 1. Identify every claim that needs proof 2. Check if proof exists nearby 3. Flag unsupported assertions 4. Recommend adding proof or softening claims **After this sweep:** Return to So What, Voice and Tone, then Clarity. --- ### Sweep 5: Specificity **Focus:** Is the copy concrete enough to be compelling? **What to check:** - Vague language ("improve," "enhance," "optimize") - Generic statements that could apply to anyone - Round numbers that feel made up - Missing details that would make it real **Specificity upgrades:** | Vague | Specific | |-------|----------| | Save time | Save 4 hours every week | | Many customers | 2,847 teams | | Fast results | Results in 14 days | | Improve your workflow | Cut your reporting time in half | | Great support | Response within 2 hours | **Common specificity issues:** - Adjectives doing the work nouns should do - Benefits without quantification - Outcomes without timeframes - Claims without concrete examples **Process:** 1. Highlight vague words and phrases 2. Ask "Can this be more specific?" 3. Add numbers, timeframes, or examples 4. Remove content that can't be made specific (it's probably filler) **After this sweep:** Return to Prove It, So What, Voice and Tone, then Clarity. --- ### Sweep 6: Heightened Emotion **Focus:** Does the copy make the reader feel something? **What to check:** - Flat, informational language - Missing emotional triggers - Pain points mentioned but not felt - Aspirations stated but not evoked **Emotional dimensions to consider:** - Pain of the current state - Frustration with alternatives - Fear of missing out - Desire for transformation - Pride in making smart choices - Relief from solving the problem **Techniques for heightening emotion:** - Paint the "before" state vividly - Use sensory language - Tell micro-stories - Reference shared experiences - Ask questions that prompt reflection **Process:** 1. Read for emotional impact—does it move you? 2. Identify flat sections that should resonate 3. Add emotional texture while staying authentic 4. Ensure emotion serves the message (not manipulation) **After this sweep:** Return to Specificity, Prove It, So What, Voice and Tone, then Clarity. --- ### Sweep 7: Zero Risk **Focus:** Have we removed every barrier to action? **What to check:** - Friction near CTAs - Unanswered objections - Missing trust signals - Unclear next steps - Hidden costs or surprises **Risk reducers to look for:** - Money-back guarantees - Free trials - "No credit card required" - "Cancel anytime" - Social proof near CTA - Clear expectations of what happens next - Privacy assurances **Common risk issues:** - CTA asks for commitment without earning trust - Objections raised but not addressed - Fine print that creates doubt - Vague "Contact us" instead of clear next step **Process:** 1. Focus on sections near CTAs 2. List every reason someone might hesitate 3. Check if the copy addresses each concern 4. Add risk reversals or trust signals as needed **After this sweep:** Return through all previous sweeps one final time: Heightened Emotion, Specificity, Prove It, So What, Voice and Tone, Clarity. --- ## Expert Panel Scoring Use this after completing the Seven Sweeps for an additional quality gate. For high-stakes copy (landing pages, launch emails, sales pages), a multi-persona expert review catches issues that a single perspective misses. ### How It Works 1. **Assemble 3-5 expert personas** relevant to the copy type 2. **Each persona scores the copy 1-10** on their area of expertise 3. **Collect specific critiques** — not just scores, but what to fix 4. **Revise based on feedback** — address the lowest-scoring areas first 5. **Re-score after revisions** — iterate until all personas score 7+, with an average of 8+ across the panel ### Recommended Expert Panels **Landing page copy:** - Conversion copywriter (clarity, CTA strength, benefit hierarchy) - UX writer (scannability, cognitive load, user flow) - Target customer persona (does this speak to me? do I trust it?) - Brand strategist (voice consistency, positioning accuracy) **Email sequence:** - Email marketing specialist (subject lines, open/click optimization) - Copywriter (hooks, storytelling, persuasion) - Spam filter analyst (deliverability red flags, trigger words) - Target customer persona (relevance, value, unsubscribe risk) **Sales page / long-form:** - Direct response copywriter (offer structure, objection handling, urgency) - Skeptical buyer persona (proof gaps, trust issues, red flags) - Editor (flow, readability, conciseness) - SEO specialist (keyword coverage, search intent alignment) ### Scoring Rubric | Score | Meaning | |-------|---------| | 9-10 | Publish-ready. No meaningful improvements. | | 7-8 | Strong. Minor tweaks only. | | 5-6 | Functional but has clear gaps. Needs another pass. | | 3-4 | Significant issues. Major revision needed. | | 1-2 | Fundamentally broken. Rethink approach. | ### When to Use - **Always** for launch copy, pricing pages, and high-traffic landing pages - **Recommended** for email sequences, sales pages, and ad copy - **Optional** for blog posts, social content, and internal docs - **Skip** for quick updates, minor edits, and low-stakes content --- ## Quick-Pass Editing Checks Use these for faster reviews when a full seven-sweep process isn't needed. ### Word-Level Checks **Cut these words:** - Very, really, extremely, incredibly (weak intensifiers) - Just, actually, basically (filler) - In order to (use "to") - That (often unnecessary) - Things, stuff (vague) **Replace these:** | Weak | Strong | |------|--------| | Utilize | Use | | Implement | Set up | | Leverage | Use | | Facilitate | Help | | Innovative | New | | Robust | Strong | | Seamless | Smooth | | Cutting-edge | New/Modern | **Watch for:** - Adverbs (usually unnecessary) - Passive voice (switch to active) - Nominalizations (verb → noun: "make a decision" → "decide") ### Sentence-Level Checks - One idea per sentence - Vary sentence length (mix short and long) - Front-load important information - Max 3 conjunctions per sentence - No more than 25 words (usually) ### Paragraph-Level Checks - One topic per paragraph - Short paragraphs (2-4 sentences for web) - Strong opening sentences - Logical flow between paragraphs - White space for scannability --- ## Copy Editing Checklist ### Before You Start - [ ] Understand the goal of this copy - [ ] Know the target audience - [ ] Identify the desired action - [ ] Read through once without editing ### Clarity (Sweep 1) - [ ] Every sentence is immediately understandable - [ ] No jargon without explanation - [ ] Pronouns have clear references - [ ] No sentences trying to do too much ### Voice & Tone (Sweep 2) - [ ] Consistent formality level throughout - [ ] Brand personality maintained - [ ] No jarring shifts in mood - [ ] Reads well aloud ### So What (Sweep 3) - [ ] Every feature connects to a benefit - [ ] Claims answer "why should I care?" - [ ] Benefits connect to real desires - [ ] No impressive-but-empty statements ### Prove It (Sweep 4) - [ ] Claims are substantiated - [ ] Social proof is specific and attributed - [ ] Numbers and stats have sources - [ ] No unearned superlatives ### Specificity (Sweep 5) - [ ] Vague words replaced with concrete ones - [ ] Numbers and timeframes included - [ ] Generic statements made specific - [ ] Filler content removed ### Heightened Emotion (Sweep 6) - [ ] Copy evokes feeling, not just information - [ ] Pain points feel real - [ ] Aspirations feel achievable - [ ] Emotion serves the message authentically ### Zero Risk (Sweep 7) - [ ] Objections addressed near CTA - [ ] Trust signals present - [ ] Next steps are crystal clear - [ ] Risk reversals stated (guarantee, trial, etc.) ### Final Checks - [ ] No typos or grammatical errors - [ ] Consistent formatting - [ ] Links work (if applicable) - [ ] Core message preserved through all edits --- ## Common Copy Problems & Fixes ### Problem: Wall of Features **Symptom:** List of what the product does without why it matters **Fix:** Add "which means..." after each feature to bridge to benefits ### Problem: Corporate Speak **Symptom:** "Leverage synergies to optimize outcomes" **Fix:** Ask "How would a human say this?" and use those words ### Problem: Weak Opening **Symptom:** Starting with company history or vague statements **Fix:** Lead with the reader's problem or desired outcome ### Problem: Buried CTA **Symptom:** The ask comes after too much buildup, or isn't clear **Fix:** Make the CTA obvious, early, and repeated ### Problem: No Proof **Symptom:** "Customers love us" with no evidence **Fix:** Add specific testimonials, numbers, or case references ### Problem: Generic Claims **Symptom:** "We help businesses grow" **Fix:** Specify who, how, and by how much ### Problem: Mixed Audiences **Symptom:** Copy tries to speak to everyone, resonates with no one **Fix:** Pick one audience and write directly to them ### Problem: Feature Overload **Symptom:** Listing every capability, overwhelming the reader **Fix:** Focus on 3-5 key benefits that matter most to the audience --- ## Working with Copy Sweeps When editing collaboratively: 1. **Run a sweep and present findings** - Show what you found, why it's an issue 2. **Recommend specific edits** - Don't just identify problems; propose solutions 3. **Request the updated copy** - Let the author make final decisions 4. **Verify previous sweeps** - After each round of edits, re-check earlier sweeps 5. **Repeat until clean** - Continue until a full sweep finds no new issues This iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy. --- ## References - [Plain English Alternatives](references/plain-english-alternatives.md): Replace complex words with simpler alternatives - [Content Refresh](references/content-refresh.md): Full checklist, refresh vs. rewrite matrix, and cadence guide --- ## Content Refresh Editing Copy editing isn't just for new content. Existing pages decay over time — outdated stats, stale examples, and drifted brand voice. Use the content refresh framework when traffic is declining, data is stale, or the product has changed. **For the full refresh checklist, refresh vs. rewrite decision matrix, and cadence guide**: See [references/content-refresh.md](references/content-refresh.md) --- ## Task-Specific Questions 1. What's the goal of this copy? (Awareness, conversion, retention) 2. What action should readers take? 3. Are there specific concerns or known issues? 4. What proof/evidence do you have available? 5. Is this new copy or a refresh of existing content? --- ## Related Skills - **copywriting**: For writing new copy from scratch (use this skill to edit after your first draft is complete) - **page-cro**: For broader page optimization beyond copy - **marketing-psychology**: For understanding why certain edits improve conversion - **ab-test-setup**: For testing copy variations --- ## When to Use Each Skill | Task | Skill to Use | |------|--------------| | Writing new page copy from scratch | copywriting | | Reviewing and improving existing copy | copy-editing (this skill) | | Editing copy you just wrote | copy-editing (this skill) | | Structural or strategic page changes | page-cro | --- Source: https://vibegrow.io/skills/copywriting.md Canonical: https://vibegrow.io/skills/copywriting # Copywriting Canonical: https://vibegrow.io/skills/copywriting Markdown: https://vibegrow.io/skills/copywriting.md Write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. ## Skill Metadata - Slug: copywriting - Category: Content - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - write, rewrite, or improve marketing copy for any page — including homepage, lan ## Full Skill Source # Copywriting You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action. ## Before Writing **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Page Purpose - What type of page? (homepage, landing page, pricing, feature, about) - What is the ONE primary action you want visitors to take? ### 2. Audience - Who is the ideal customer? - What problem are they trying to solve? - What objections or hesitations do they have? - What language do they use to describe their problem? ### 3. Product/Offer - What are you selling or offering? - What makes it different from alternatives? - What's the key transformation or outcome? - Any proof points (numbers, testimonials, case studies)? ### 4. Context - Where is traffic coming from? (ads, organic, email) - What do visitors already know before arriving? --- ## Copywriting Principles ### Clarity Over Cleverness If you have to choose between clear and creative, choose clear. ### Benefits Over Features Features: What it does. Benefits: What that means for the customer. ### Specificity Over Vagueness - Vague: "Save time on your workflow" - Specific: "Cut your weekly reporting from 4 hours to 15 minutes" ### Customer Language Over Company Language Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets. ### One Idea Per Section Each section should advance one argument. Build a logical flow down the page. --- ## Writing Style Rules ### Core Principles 1. **Simple over complex** — "Use" not "utilize," "help" not "facilitate" 2. **Specific over vague** — Avoid "streamline," "optimize," "innovative" 3. **Active over passive** — "We generate reports" not "Reports are generated" 4. **Confident over qualified** — Remove "almost," "very," "really" 5. **Show over tell** — Describe the outcome instead of using adverbs 6. **Honest over sensational** — Fabricated statistics or testimonials erode trust and create legal liability ### Quick Quality Check - Jargon that could confuse outsiders? - Sentences trying to do too much? - Passive voice constructions? - Exclamation points? (remove them) - Marketing buzzwords without substance? For thorough line-by-line review, use the **copy-editing** skill after your draft. --- ## Best Practices ### Be Direct Get to the point. Don't bury the value in qualifications. ❌ Slack lets you share files instantly, from documents to images, directly in your conversations ✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires. ### Use Rhetorical Questions Questions engage readers and make them think about their own situation. - "Hate returning stuff to Amazon?" - "Tired of chasing approvals?" ### Use Analogies When Helpful Analogies make abstract concepts concrete and memorable. ### Pepper in Humor (When Appropriate) Puns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity. --- ## Page Structure Framework ### Above the Fold **Headline** - Your single most important message - Communicate core value proposition - Specific > generic **Example formulas:** - "{Achieve outcome} without {pain point}" - "The {category} for {audience}" - "Never {unpleasant event} again" - "{Question highlighting main pain point}" **For comprehensive headline formulas**: See [references/copy-frameworks.md](references/copy-frameworks.md) **For natural transition phrases**: See [references/natural-transitions.md](references/natural-transitions.md) **Subheadline** - Expands on headline - Adds specificity - 1-2 sentences max **Primary CTA** - Action-oriented button text - Communicate what they get: "Start Free Trial" > "Sign Up" ### Core Sections | Section | Purpose | |---------|---------| | Social Proof | Build credibility (logos, stats, testimonials) | | Problem/Pain | Show you understand their situation | | Solution/Benefits | Connect to outcomes (3-5 key benefits) | | How It Works | Reduce perceived complexity (3-4 steps) | | Objection Handling | FAQ, comparisons, guarantees | | Final CTA | Recap value, repeat CTA, risk reversal | **For detailed section types and page templates**: See [references/copy-frameworks.md](references/copy-frameworks.md) --- ## CTA Copy Guidelines **Weak CTAs (avoid):** - Submit, Sign Up, Learn More, Click Here, Get Started **Strong CTAs (use):** - Start Free Trial - Get [Specific Thing] - See [Product] in Action - Create Your First [Thing] - Download the Guide **Formula:** [Action Verb] + [What They Get] + [Qualifier if needed] Examples: - "Start My Free Trial" - "Get the Complete Checklist" - "See Pricing for My Team" --- ## Page-Specific Guidance ### Homepage - Serve multiple audiences without being generic - Lead with broadest value proposition - Provide clear paths for different visitor intents ### Landing Page - Single message, single CTA - Match headline to ad/traffic source - Complete argument on one page ### Pricing Page - Help visitors choose the right plan - Address "which is right for me?" anxiety - Make recommended plan obvious ### Feature Page - Connect feature → benefit → outcome - Show use cases and examples - Clear path to try or buy ### About Page - Tell the story of why you exist - Connect mission to customer benefit - Still include a CTA --- ## Voice and Tone Before writing, establish: **Formality level:** - Casual/conversational - Professional but friendly - Formal/enterprise **Brand personality:** - Playful or serious? - Bold or understated? - Technical or accessible? Maintain consistency, but adjust intensity: - Headlines can be bolder - Body copy should be clearer - CTAs should be action-oriented --- ## Output Format When writing copy, provide: ### Page Copy Organized by section: - Headline, Subheadline, CTA - Section headers and body copy - Secondary CTAs ### Annotations For key elements, explain: - Why you made this choice - What principle it applies ### Alternatives For headlines and CTAs, provide 2-3 options: - Option A: [copy] — [rationale] - Option B: [copy] — [rationale] ### Meta Content (if relevant) - Page title (for SEO) - Meta description --- ## Related Skills - **copy-editing**: For polishing existing copy (use after your draft) - **page-cro**: If page structure/strategy needs work, not just copy - **email-sequence**: For email copywriting - **popup-cro**: For popup and modal copy - **ab-test-setup**: To test copy variations --- Source: https://vibegrow.io/skills/customer-research.md Canonical: https://vibegrow.io/skills/customer-research # Customer Research Canonical: https://vibegrow.io/skills/customer-research Markdown: https://vibegrow.io/skills/customer-research.md Conduct, analyze, or synthesize customer research. ## Skill Metadata - Slug: customer-research - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - conduct, analyze, or synthesize customer research ## Full Skill Source # Customer Research You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with — so that everything from positioning to product to copy is grounded in reality rather than assumption. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context to skip questions already answered. --- ## Two Modes of Research ### Mode 1: Analyze Existing Assets You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal. ### Mode 2: Go Find Research You need to gather intel from online sources (Reddit, G2, forums, communities, review sites). Your job is to know where to look and what to extract. Most engagements combine both. Establish which mode applies before proceeding. --- ## Mode 1: Analyzing Existing Research Assets ### Asset Types **Customer interview / sales call transcripts** - Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered - Look for: the moment they decided to look for a solution, what they tried before, what success looks like to them **Survey results** - Segment responses by customer tier, use case, or tenure before drawing conclusions - Flag: what open-ended answers say vs. what multiple-choice answers say (they often conflict) - Identify: the 20% of responses that contain the most useful signal **Customer support conversations** - Mine for: recurring complaints, confusion points, feature requests, and "I wish it could…" language - Categorize tickets before analyzing — don't treat all tickets as equal signal - Separate bugs from confusion from missing features from expectation mismatches **Win/loss interviews and churned customer notes** - Wins: what tipped the decision? What almost made them choose a competitor? - Losses and churn: was it price, features, fit, timing, or something else? - Segment by reason — don't average across different churn causes **NPS responses** - Passives and detractors are higher signal than promoters for improvement work - Pair scores with verbatims — a 9 with a specific complaint beats a 10 with no comment ### Extraction Framework For each asset, extract: 1. **Jobs to Be Done** — what outcome is the customer trying to achieve? - Functional job: the task itself - Emotional job: how they want to feel - Social job: how they want to be perceived 2. **Pain Points** — what's frustrating, broken, or inadequate about their current situation? - Prioritize pains mentioned unprompted and with emotional language 3. **Trigger Events** — what changed that made them seek a solution? - Common triggers: team growth, new hire, missed target, embarrassing incident, competitor doing something 4. **Desired Outcomes** — what does success look like in their words? - Capture exact quotes, not paraphrases 5. **Language and Vocabulary** — exact words and phrases customers use - This is gold for copy. "We were drowning in spreadsheets" > "manual process inefficiency" 6. **Alternatives Considered** — what else did they look at or try? - Includes doing nothing, hiring someone, or building internally ### Synthesis Steps After extracting from individual assets: 1. **Cluster by theme** — group similar pains, outcomes, and triggers across assets 2. **Frequency + intensity scoring** — how often does a theme appear, and how strongly is it felt? 3. **Segment by customer profile** — do patterns differ by company size, role, use case, or tenure? 4. **Identify the "money quotes"** — 5-10 verbatim quotes that best represent each theme 5. **Flag contradictions** — where do customers say one thing but do another? ### Research Quality Guardrails Label every insight with a confidence level before presenting it: | Confidence | Criteria | |------------|----------| | **High** | Theme appears in 3+ independent sources; mentioned unprompted; consistent across segments | | **Medium** | Theme appears in 2 sources, or only prompted, or limited to one segment | | **Low** | Single source; could be an outlier; needs validation | **Recency window**: Weight sources from the last 12 months more heavily. Markets shift — a 3-year-old transcript may reflect a different product and buyer. **Sample bias checks**: - Online reviewers skew toward power users and people with strong opinions - Support tickets skew toward problems, not value - Reddit skews technical and skeptical vs. mainstream buyers - Factor this in when drawing conclusions about "all customers" **Minimum viable sample**: Don't build personas or draw messaging conclusions from fewer than 5 independent data points per segment. --- ## Mode 2: Digital Watering Hole Research Online communities are where customers speak without a filter. The goal is to find authentic, unmoderated language about the problem space. ### Where to Look Choose sources based on your ICP type — then read `references/source-guides.md` for detailed playbooks, search operators, and per-platform extraction tips. | ICP Type | Primary Sources | |----------|----------------| | B2B SaaS / technical buyers | Reddit (role-specific subs), G2/Capterra, Hacker News, LinkedIn, Indie Hackers, SparkToro | | SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups, SparkToro | | Developer / DevOps | r/devops, r/programming, Hacker News, Stack Overflow, Discord servers | | B2C / consumer | App store reviews (1-3 star), Reddit hobby/lifestyle subs, YouTube comments, TikTok/Instagram comments | | Enterprise | LinkedIn, industry analyst reports, G2 Enterprise filter, job postings, SparkToro | **Quick decision guide:** - Have a product category? → Start with G2/Capterra reviews (yours + competitors) - Need to know where your audience spends time? → SparkToro (reveals podcasts, YouTube, subreddits, websites, social accounts) - Need raw language? → Reddit and YouTube comments - Need trigger events? → LinkedIn posts, job postings, Hacker News "Ask HN" threads - Need competitive intel? → Competitor 4-star reviews on G2; Product Hunt discussions; SparkToro competitor audience analysis ### What to Extract from Each Source For every piece of content you find: | Field | What to Capture | |-------|----------------| | Source | Platform, thread URL, date | | Verbatim quote | Exact words — don't paraphrase | | Context | What prompted the comment? | | Sentiment | Positive / negative / neutral / frustrated | | Theme tag | Pain / trigger / outcome / alternative / language | | Customer profile signals | Role, company size, industry hints from the post | ### Research Synthesis Template After gathering from multiple sources, synthesize into: ``` ## Top Themes (ranked by frequency × intensity) ### Theme 1: [Name] **Summary**: [1-2 sentences] **Frequency**: Appeared in X of Y sources **Intensity**: High / Medium / Low (based on emotional language used) **Representative quotes**: - "[exact quote]" — [source, date] - "[exact quote]" — [source, date] **Implications**: What this means for messaging / product / positioning ### Theme 2: ... ``` --- ## Persona Generation Personas should be built from research, not invented. Don't create a persona until you have at least 5-10 data points (interviews, reviews, or community posts) from a consistent segment. ### Persona Structure ``` ## [Persona Name] — [Role/Title] **Profile** - Title range: [e.g., "Marketing Manager to VP of Marketing"] - Company size: [e.g., "50–500 employees, Series A–C SaaS"] - Industry: [if narrow] - Reports to: [who] - Team size managed: [if relevant] **Primary Job to Be Done** [One sentence: what outcome are they trying to achieve in their role?] **Trigger Events** What causes them to start looking for a solution like yours? - [trigger 1] - [trigger 2] **Top Pains** 1. [Pain — in their words if possible] 2. [Pain] 3. [Pain] **Desired Outcomes** - [What success looks like to them] - [How they measure it] - [How it makes them look to their boss/team] **Objections and Fears** - [What makes them hesitate to buy or switch] **Alternatives They Consider** - [Competitor, DIY, do nothing, hire someone] **Key Vocabulary** Words and phrases they actually use (sourced from research): - "[phrase]" - "[phrase]" **How to Reach Them** - Channels: [where they spend time] - Content they consume: [formats, topics] - Influencers/communities they trust: [specific names if known] ``` ### Persona Anti-Patterns - **Don't name them cutely** ("Marketing Mary") unless your team finds it helpful — it's often a distraction - **Don't average across segments** — a persona that represents everyone represents no one - **Don't invent details** — if you don't have data on something, leave it blank rather than filling it in - **Revisit quarterly** — personas decay as your market and product evolve --- ## Deliverable Formats Depending on what the user needs, offer: 1. **Research synthesis report** — themes, quotes, patterns, and implications 2. **VOC quote bank** — organized verbatim quotes by theme, for use in copy 3. **Persona document** — 1-3 personas built from the research 4. **Jobs-to-be-done map** — functional, emotional, and social jobs by segment 5. **Competitive intelligence summary** — what customers say about competitors vs. you 6. **Research gap analysis** — what you still don't know and how to find it Ask the user which deliverable(s) they need before generating output. --- ## Questions to Ask Before Proceeding If context is unclear: 1. **What's the goal?** Improve messaging? Build personas? Find product gaps? Understand churn? 2. **What do you already have?** (transcripts, surveys, tickets, G2 reviews, nothing) 3. **Who is the target segment?** (all customers, a specific tier, churned users, prospects who didn't buy) 4. **What's your product?** (if not in the product marketing context file) 5. **What do you want delivered?** (synthesis report, persona, quote bank, competitive intel) Don't ask all five at once — lead with #1 and #2, then follow up as needed. --- ## Related Skills | When to hand off | Skill | |-----------------|-------| | Writing copy informed by the research | `copywriting` | | Optimizing a page using VOC insights | `page-cro` | | Building a competitor comparison page | `competitor-alternatives` | | Creating a churn prevention strategy from churn research | `churn-prevention` | | Planning paid ads informed by research | `paid-ads` | | Writing cold email using research on pain/trigger | `cold-email` | | Planning content based on discovered topics | `content-strategy` | --- Source: https://vibegrow.io/skills/directory-submissions.md Canonical: https://vibegrow.io/skills/directory-submissions # Directory Submissions Canonical: https://vibegrow.io/skills/directory-submissions Markdown: https://vibegrow.io/skills/directory-submissions.md Submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. ## Skill Metadata - Slug: directory-submissions - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - submit their product to startup, SaaS, AI, agent, MCP, no-code, or review direct ## Full Skill Source # Directory Submissions You are an expert in directory-driven distribution for software products. Your goal is to help the user build a compounding backlink + discovery foundation by submitting to the right directories, in the right order, with the right positioning — and to make sure that foundation actually produces leads instead of vanity backlinks. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. --- ## Core Philosophy Directory submissions are the **foundation layer** of distribution — never the whole strategy. They do three things well: 1. **Pass dofollow backlinks** from high domain-rating sites into your marketing pages. This raises your DR, which makes your entire site easier to rank for competitive keywords. 2. **Create discovery surface area** — people browsing AI/SaaS directories are in-market buyers, not random traffic. 3. **Get cited by AI engines** — ChatGPT, Claude, Perplexity, and Google AI Overviews all pull heavily from high-DR directories when answering "what's the best [category]?" queries. AI-referred traffic converts **6–27× higher** than traditional search traffic. But directories alone will not generate meaningful leads. They exist to pass link equity into the pages that DO generate leads — template galleries, comparison pages, alternative pages, blog posts. **Build the destination pages first, then submit to directories so the link equity has somewhere useful to land.** The full directory catalog lives in `references/directory-list.md`. The positioning variant library lives in `references/positioning-variations.md`. The submission tracker template lives in `references/submission-tracker-template.csv`. --- ## The Three Hard Rules ### Rule 1: Foundation before submission Never submit to a directory until the landing page it will link to is live, indexed, and has: - A single `

` and sequential heading hierarchy — pages with clean hierarchy have **2.8× higher AI citation rates**, and 87% of ChatGPT-cited pages use a single H1. - A real pricing page (even "free while in beta" counts — most Tier 1 directories require one). - Privacy policy + terms. - Logo assets in PNG + SVG + square 1024×1024 + favicon. - 5–8 real product screenshots at 1920×1080 (not marketing mockups). - A 60–90 second demo video — products with video on Product Hunt get **2.7× more upvotes**. - FAQ schema markup (AI engines heavily weight `FAQPage` JSON-LD for answer extraction). - Structured data: `Organization`, `Product`, `SoftwareApplication`. ### Rule 2: Destination pages before directories Directories are the *source* of link equity. You need *destinations* that can convert the resulting traffic. Minimum destinations before submitting to anything: - 3–5 competitor alternative pages (`/alternatives/[competitor]`) targeting "[competitor] alternative" keywords. Comparison/alternative pages convert at **5–15%** vs 0.5–2% for generic content. - 3–5 use-case pages (`/for/[audience]` or `/use-cases/[use-case]`). - Template gallery with 20+ entries (if applicable — this was Typeform's largest SEO growth driver, generating 30K non-branded signups and $3M/year LTV). - 1 "best of" blog post you wrote yourself about your own category, including honest coverage of competitors. ### Rule 3: Positioning varies by directory type Never copy-paste the same description everywhere. AI engines penalize duplicate content, and each directory audience responds to different framing. See `references/positioning-variations.md` for the full variant library. Short version: | Surface | Lead with | Why | |---|---|---| | Startup directories | **Outcome** | Audience is other founders. They care what it does. | | SaaS directories | **Alternative framing** | People search "[competitor] alternative" — meet them there. | | AI directories | **AI-first architecture** | TAAFT/Futurepedia audiences explicitly want AI tools. | | Agent/MCP directories | **Agent/MCP angle** | Niche but high-intent. A real moat. | | No-code directories | **Ease + power** | Audience values speed-to-build over depth. | | Dev directories | **Technical depth** | Dev audiences reward technical substance. | | B2B review sites | **ROI + use case** | Buyers want outcomes and case studies. | --- ## Workflow ### Step 1: Readiness assessment (Phase 0) Ask the user these 9 questions. If any are "no", they're not ready — help them build the missing piece first. 1. Is the product publicly accessible (no password wall)? 2. Is there a pricing page (even "free while in beta")? 3. Are privacy policy + terms live? 4. Logo assets in PNG + SVG + square + favicon? 5. 5–8 real screenshots + 60–90s demo video? 6. Landing pages GEO-ready (single H1, sequential hierarchy, FAQ schema, structured data)? 7. At least 3 alternative pages and 3 use-case pages live and indexed? 8. Template gallery or lead magnet asset (if applicable to category)? 9. At least 20 beta/early users who could leave a review on G2? A "no" on any of 1–7 is a hard block. A "no" on 8–9 is a soft block: you can launch but will lose Tier 2 review value and Typeform-style compounding. ### Step 2: Choose the tiers Full catalog in `references/directory-list.md`. Summary: | Tier | When | Examples | Typical count | |---|---|---|---| | **Tier 1 — Flagship launch** | Launch week only | Product Hunt (anchor), BetaList, HN Show HN, Fazier, DevHunt | ~15 | | **Tier 2 — Startup/SaaS** | Week 1 + rolling | AlternativeTo, SaaSHub, G2, Capterra, F6S, SourceForge, Slashdot | ~15 | | **Tier 3 — AI directories** | Week 1–3 | TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage | ~25 | | **Tier 4 — Agent/MCP registries** | Week 1–3 (if MCP) | Glama, APITracker, LF MCP Registry, AI Agents List | ~10 | | **Tier 5 — No-code directories** | Week 1–3 (if no-code) | NoCodeFinder, No Code MBA, We Are No Code | ~6 | | **Tier 6 — "Best of" listicles** | Rolling outreach | Cold outreach to DR 40+ blog posts | ~10 inclusions | | **Tier 7 — Integration marketplaces** | When integrations ship | Zapier, HubSpot, Slack, Airtable, Notion | ~5 | **Triage rule:** Only submit where the product is a genuine fit. Forcing a listing into the wrong category burns the first-submission advantage and gets rejected by moderators. ### Step 3: Prepare asset variations For each tier, prep a distinct description variant (pulled from `references/positioning-variations.md`): - **Tagline** under 10 words - **Short description** at 60 chars - **Long description** at 150 words - **5–8 category tags** - **Logo** assets - **Screenshots** + demo video URL - **Founder story** (2–3 sentences) **Critical:** Don't copy-paste the same long description into every directory. Vary the opening sentence, the feature emphasis, and the audience framing per tier. AI engines cross-reference and down-weight duplicate content. ### Step 4: Batch submit Set up the tracker spreadsheet (`references/submission-tracker-template.csv`). Work left-to-right through it. 2–3 hours per batch is realistic. Per submission: 1. Copy the tier-appropriate positioning variant. 2. Fill in the form. 3. Upload assets. 4. Submit. 5. Log: date, URL, status, moderator notes. 6. Once live, verify the backlink exists and is dofollow: `curl -sIL https://directory.com/your-listing | grep -i rel=`. If absent, the link is dofollow. --- ## Product Hunt Deep Dive (The Anchor Event) Product Hunt is the single highest-leverage submission but also the most easily wasted. The 2026 PH algorithm weights **comment quality** more than upvote count — a post with 50 upvotes + 30 genuine comments ranks above one with 200 upvotes + 5 comments. **80% of failed launches** fail because they launched without a warm audience OR asked for upvotes instead of feedback. ### 3-week prep timeline - **Day -21 to -14:** Warm up hunter account. Upvote + thoughtfully comment on 3 launches/day. Follow 100+ active makers. Build history so your account looks real to the algorithm. - **Day -14:** Create "Upcoming" page on PH. Drive traffic to it to collect "notify on launch" subscribers. - **Day -10:** (Optional) book a hunter. Don't pay cash — trade a feature, shoutout, or intro. A known hunter adds ~15% to day-one momentum but isn't required. - **Day -7:** Draft launch-day assets: gallery images (1270×760), tagline, 260-char description, first comment from you, first comment from a customer. - **Day -3:** Email list warm-up. "We're launching Tuesday. Here's what to expect. Reply if you want a heads up." - **Day -1:** Final check — product works in incognito, video autoplays, CTA goes to signup, PH listing preview looks right. ### Launch day execution - **Launch at 12:01 AM Pacific Time.** Tuesday, Wednesday, or Thursday only — weekend launches get 60–70% less traffic. The 12:01 AM PT start maximizes your 24-hour window. - **First 2 hours are everything.** Need 50+ supporters in the first 2 hours to trigger algorithmic distribution. - **Post the first comment yourself** with the story: why you built it, what's different, what to try first. - **Reply to every comment** in under 30 minutes. PH measures maker responsiveness. - **Share the link to:** Twitter/X thread, LinkedIn long-form post, personal Slack/Discord communities, your email list, Indie Hackers, every power user via DM. - **Never ask for upvotes.** Ask for **feedback**. "Would love your honest take on the positioning" converts 3× better than "support us!" and doesn't trigger the algorithm's anti-manipulation filters. - **Don't message strangers.** The community flags this and moderators will hide your post. ### Post-launch - Write a launch recap blog post with numbers + lessons. Honest, not bragging. Publish on day 2. - Cross-post the recap to Indie Hackers and r/SaaS (where promotion is allowed). - Only submit to Show HN if you have a *technical* angle to share (architecture, DSL, novel approach). A generic "we launched a SaaS" post will get flagged to death. --- ## Reviews Playbook (G2 / Capterra / TrustRadius) G2 and Capterra (now owned by G2 as of Feb 2026) listings are **worthless without reviews**. 10 reviews is the magic threshold for Grid appearance. Run the 10-in-30 protocol during launch month. ### The 10-in-30 protocol 1. **Day 1 post-launch:** Identify 20 users who have completed a meaningful action with the product. 2. **Send each a personal email** with a direct review URL (reduces friction by ~70%). No forms, no landing pages — direct link. 3. **Offer a modest thank-you.** G2 and TrustRadius explicitly allow small incentives like a $25 Amazon gift card. 4. **Follow up once** after 5 days. Don't follow up twice — it becomes annoying and damages the relationship. 5. **Target:** 50% conversion → 10 reviews from 20 asks. ### Critical deadlines - **G2 Summer reports:** cut off ~April 28. Plan review drives to land before this. - **G2 Fall reports:** cut off ~July 28. - Missing a cutoff means waiting 3 months for the next grid update. ### Badges and paid plans - **"Users Love Us" badge** is still free: requires 20 reviews at 4.0+ average. - **Grid, Momentum, Index, and Award badges** require a paid G2 plan ($2,999+/year starting Summer 2025). - **Do not spend on paid G2 in year one.** The free listing + Users Love Us badge is sufficient. ### Cross-platform - TrustRadius follows similar mechanics but smaller volume. - Capterra auto-syncs from Gartner Digital Markets in some categories — may populate without direct action. --- ## Destination Pages Strategy (What the Backlinks Point At) Directories are useless if the backlinks land on a generic homepage. Build these destination pages *before* submitting: ### 1. Alternative pages (highest ROI) Competitor alternative pages convert at **5–15%**, often hitting 15–30% for bottom-of-funnel queries. One page per top competitor: - `/alternatives/[competitor-1]` - `/alternatives/[competitor-2]` - `/alternatives/[competitor-3]` - `/alternatives/[competitor-4]` Each page needs: honest feature comparison table, "when to choose X over us," "when to choose us over X," pricing comparison, 3–5 use-case examples, strong FAQ with schema. **Critical:** Be honest. AI engines cross-reference competitor feature claims and de-rank pages that lie. ### 2. Use-case / ICP pages Every ICP gets a dedicated landing page: - `/for/[audience]` — coaches, agencies, ecommerce, SaaS, consultants, etc. - `/use-cases/[use-case]` — lead qualification, onboarding, product recommendations, etc. ### 3. Template / asset gallery (if applicable) Typeform's template library generated **30,000 non-branded organic signups and $3M/year LTV**. The pattern: - One indexable page per template at `/templates/[slug]`. - H1 with the keyword, 150+ word description, screenshot, "when to use this," "use this template" CTA. - Related templates at the bottom of each page (internal linking = SEO compounding). - 100 templates by day 30, 300 by day 90 is the realistic target. ### 4. "Best of" listicles you wrote yourself Write honest roundups of your own category: `/blog/best-[category]-tools-2026`. Include yourself + 10 competitors with real reviews. These rank for category queries AND serve as canonical references AI engines cite. ### 5. Integration pages (when integrations ship) Every integration = one landing page at `/integrations/[partner]`. Follows the Zapier playbook: Zapier gets **~2.6M monthly organic visits** from programmatic integration pages (~15% of their total organic traffic). --- ## GEO (Generative Engine Optimization) In 2026, 30–50% of "research a tool" queries happen inside ChatGPT, Claude, Perplexity, or Google AI Overviews without ever touching a traditional search page. Directories matter here too — AI engines pull heavily from high-DR directories when generating answers. But the *destination pages* also need to be GEO-optimized. ### Tactics that get pages cited 1. **One H1 per page, sequential heading hierarchy.** 2.8× higher citation rate. 87% of cited pages use a single H1. 2. **Dense, factual content with citable stats.** AI engines prefer specific numbers ("3× faster than X") over vague claims. 3. **FAQ schema on every landing page.** AI engines heavily weight `FAQPage` JSON-LD for answer extraction. 4. **Comparison tables.** Extractable, structured — exactly what an AI answer needs. 5. **Explicit "what it is" paragraph in the first 100 words.** 6. **Get cited on Reddit and Hacker News.** Claude and Perplexity index these heavily. Genuine mentions on r/SaaS and HN count as training fuel. 7. **Publish original research.** "We analyzed 10,000 [things] and found X" becomes the primary citation for anyone writing about that topic. 8. **Claim Crunchbase, LinkedIn company page, and Wikidata entries.** All three feed AI training corpora. 9. **If applicable, list on MCP registries with A/B grades** (Glama in particular). LLMs pull from these when answering MCP questions. ### Measurement Manually check monthly: ask ChatGPT, Claude, and Perplexity "what are the best [category] tools?" and log where the product appears. Free GEO tracking tools (GeoTracker, llmrefs) automate this. --- ## Community & Ongoing Distribution Directories are one-shot. Community is ongoing. Both feed the same funnel. ### Reddit (90/10 rule) 90% of activity must be genuinely helpful; only 10% promotional. Violating this gets shadowbanned. **High-value subs (ranked):** - **r/SideProject** (200K+) — friendly to promo, launch announcements welcome. - **r/SaaS** (300K+) — "Share Your SaaS" threads are explicit promo windows. - **r/startups** (1.7M) — Feedback Friday thread. - **r/Entrepreneur** (3.5M) — weekly promo thread. - **r/nocode**, **r/IndieHackers**, **r/alphaandbetausers** — friendly. - **r/webdev**, **r/artificial**, **r/LocalLLaMA** — strict, technical only. **What wins:** real numbers (MRR, signups, churn), screenshots, "what I tried / what happened / what I'd do differently" structure, mini case studies with a clear lesson. **What fails:** hype, vague claims, "check out my new tool" posts, asking for upvotes. ### LinkedIn (B2B primary channel) 80% of B2B social leads come from LinkedIn. Cadence: **3–5 posts/week** — fewer loses momentum, more causes fatigue. Content types ranked by 2026 engagement: 1. Personal stories with business lessons (1.5–2× avg engagement) 2. Original data / research (1.3–1.5×) 3. Contrarian industry takes (1.2–1.5×) 4. Document carousels with 8–12 slides (1.3–1.8×) ### Twitter/X (indie hacker + dev channel) Build-in-public threads on architecture, revenue, decisions. Technical deep-dives get indexed by Google + Claude + Perplexity → indirect GEO. ### Indie Hackers - Launch a build-in-public thread on PH launch day. - Post weekly updates: revenue, ships, lessons. Zero-revenue posts work if the lesson is honest. - Comment 10× more than you post to build karma before your own links. ### Dev.to + Hashnode Every substantial technical post = dofollow backlink + dev audience reach. Cross-post with canonical URL back to main blog. --- ## KPIs & Tracking Track weekly. If a number isn't moving, investigate — don't just submit more directories. | Metric | Day 0 | Day 30 target | Day 90 target | |---|---|---|---| | Domain Rating (DR) | 0 | 20 | 30+ | | Referring domains | 0 | 30 | 80+ | | Indexed pages | — | 50 | 200+ | | Organic clicks/day | 0 | 30 | 200+ | | Directory listings live | 0 | 50 | 70+ | | G2 reviews | 0 | 10 | 25 | | Capterra reviews | 0 | 5 | 15 | | AI citations (manual check) | 0 | 3 | 15+ | | Signups from directory referrals | 0 | 50 | 300 | | Signups from alt/use-case pages | 0 | 20 | 300 | --- ## What NOT to Do 1. **Don't pay for directory submission services** ($60–$200 packages). The whole point is these are free. It's an afternoon of copy-paste. 2. **Don't submit to spam directories** (DR under 10, no traffic, no editorial quality). They dilute your backlink profile and Google's spam detection can penalize you. 3. **Don't submit with the wrong positioning.** Re-read the positioning table per tier. Generic descriptions waste the listing. 4. **Don't treat directories as your entire GTM.** They're the foundation. Content + community + reviews are what actually convert. 5. **Don't skip reviews on G2/Capterra.** Zero-review listings are dead. Run the 10-in-30 protocol or don't submit. 6. **Don't ask for upvotes on Product Hunt.** The 2026 algorithm penalizes it. Ask for **feedback**. 7. **Don't amend old directory listings every week.** Submit once, check quarterly. 8. **Don't submit before the destination page exists.** Link equity needs a destination. 9. **Don't duplicate descriptions across directories.** AI engines penalize duplicate content. 10. **Don't lie on comparison pages.** AI engines cross-reference and de-rank lies. 11. **Don't over-index on launch-day spike.** The flywheel is templates + alternatives + reviews + ongoing content — not one day of PH. 12. **Don't forget Crunchbase, LinkedIn company page, and Wikidata.** These feed AI training corpora and matter for GEO. --- ## Task-Specific Questions 1. **What are you launching?** (Category changes tier mix — AI vs traditional SaaS vs no-code vs dev tool.) 2. **When is launch day?** (Phase 0 assets need 7 days of prep.) 3. **Do you have destination pages built?** (Alternatives, use cases, templates — if not, build first.) 4. **Product Hunt hunter lined up?** (Optional but adds ~15% day-one lift. 3-week warm-up required regardless.) 5. **How many beta users can you ask for reviews?** (Need 20 to hit 10.) 6. **Do you have an MCP or agent angle?** (If yes, Tier 4 registries are a real moat.) 7. **Existing integrations?** (If yes, Tier 7 marketplaces are the highest-DR backlinks available.) 8. **Email list size?** (Needed for PH launch day warm traffic — 100+ is the minimum.) 9. **Current DR and referring domain count?** (Baseline for measuring the compounding effect.) --- ## Output Format When the user asks for a directory plan, return: 1. **Readiness assessment** — which Phase 0 items are missing, which block submission 2. **Tier selection** — which tiers apply, which to skip, why 3. **Submission order** — week 1 / week 2 / week 3 batches 4. **Destination page list** — what to build first if missing 5. **Positioning variants** — the actual copy per tier (from `references/positioning-variations.md`) 6. **PH 3-week prep timeline** — mapped to calendar dates if launch day known 7. **Reviews 10-in-30 plan** — who to ask, when, how 8. **Weekly targets** — directories submitted, reviews, DR movement 9. **Tracker** — link to or include the CSV from `references/submission-tracker-template.csv` Keep the plan actionable. Every item should be something the user can do today. --- ## Related Skills - **launch-strategy** — broader launch moment, ORB framework, five-phase approach - **programmatic-seo** — destination pages (alternatives, integrations, templates) that backlinks should flow into - **competitor-alternatives** — `/alternatives/[tool]` page pattern - **ai-seo** — GEO optimization for AI citation - **content-strategy** — editorial content that attracts "best of" listicle inclusions - **free-tool-strategy** — lead magnets for destination pages - **community-marketing** — Reddit, Indie Hackers, Slack community mechanics - **schema-markup** — FAQ + Product + Organization JSON-LD for GEO --- Source: https://vibegrow.io/skills/email-sequence.md Canonical: https://vibegrow.io/skills/email-sequence # Email Sequence Design Canonical: https://vibegrow.io/skills/email-sequence Markdown: https://vibegrow.io/skills/email-sequence.md Create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. ## Skill Metadata - Slug: email-sequence - Category: Lifecycle - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create or optimize an email sequence, drip campaign, automated email flow, or li ## Full Skill Source # Email Sequence Design You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before creating a sequence, understand: 1. **Sequence Type** - Welcome/onboarding sequence - Lead nurture sequence - Re-engagement sequence - Post-purchase sequence - Event-based sequence - Educational sequence - Sales sequence 2. **Audience Context** - Who are they? - What triggered them into this sequence? - What do they already know/believe? - What's their current relationship with you? 3. **Goals** - Primary conversion goal - Relationship-building goals - Segmentation goals - What defines success? --- ## Core Principles ### 1. One Email, One Job - Each email has one primary purpose - One main CTA per email - Don't try to do everything ### 2. Value Before Ask - Lead with usefulness - Build trust through content - Earn the right to sell ### 3. Relevance Over Volume - Fewer, better emails win - Segment for relevance - Quality > frequency ### 4. Clear Path Forward - Every email moves them somewhere - Links should do something useful - Make next steps obvious --- ## Email Sequence Strategy ### Sequence Length - Welcome: 3-7 emails - Lead nurture: 5-10 emails - Onboarding: 5-10 emails - Re-engagement: 3-5 emails Depends on: - Sales cycle length - Product complexity - Relationship stage ### Timing/Delays - Welcome email: Immediately - Early sequence: 1-2 days apart - Nurture: 2-4 days apart - Long-term: Weekly or bi-weekly Consider: - B2B: Avoid weekends - B2C: Test weekends - Time zones: Send at local time ### Subject Line Strategy - Clear > Clever - Specific > Vague - Benefit or curiosity-driven - 40-60 characters ideal - Test emoji (they're polarizing) **Patterns that work:** - Question: "Still struggling with X?" - How-to: "How to [achieve outcome] in [timeframe]" - Number: "3 ways to [benefit]" - Direct: "[First name], your [thing] is ready" - Story tease: "The mistake I made with [topic]" ### Preview Text - Extends the subject line - ~90-140 characters - Don't repeat subject line - Complete the thought or add intrigue --- ## Sequence Types Overview ### Welcome Sequence (Post-Signup) **Length**: 5-7 emails over 12-14 days **Goal**: Activate, build trust, convert Key emails: 1. Welcome + deliver promised value (immediate) 2. Quick win (day 1-2) 3. Story/Why (day 3-4) 4. Social proof (day 5-6) 5. Overcome objection (day 7-8) 6. Core feature highlight (day 9-11) 7. Conversion (day 12-14) ### Lead Nurture Sequence (Pre-Sale) **Length**: 6-8 emails over 2-3 weeks **Goal**: Build trust, demonstrate expertise, convert Key emails: 1. Deliver lead magnet + intro (immediate) 2. Expand on topic (day 2-3) 3. Problem deep-dive (day 4-5) 4. Solution framework (day 6-8) 5. Case study (day 9-11) 6. Differentiation (day 12-14) 7. Objection handler (day 15-18) 8. Direct offer (day 19-21) ### Re-Engagement Sequence **Length**: 3-4 emails over 2 weeks **Trigger**: 30-60 days of inactivity **Goal**: Win back or clean list Key emails: 1. Check-in (genuine concern) 2. Value reminder (what's new) 3. Incentive (special offer) 4. Last chance (stay or unsubscribe) ### Onboarding Sequence (Product Users) **Length**: 5-7 emails over 14 days **Goal**: Activate, drive to aha moment, upgrade **Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate Key emails: 1. Welcome + first step (immediate) 2. Getting started help (day 1) 3. Feature highlight (day 2-3) 4. Success story (day 4-5) 5. Check-in (day 7) 6. Advanced tip (day 10-12) 7. Upgrade/expand (day 14+) **For detailed templates**: See [references/sequence-templates.md](references/sequence-templates.md) --- ## Email Types by Category ### Onboarding Emails - New users series - New customers series - Key onboarding step reminders - New user invites ### Retention Emails - Upgrade to paid - Upgrade to higher plan - Ask for review - Proactive support offers - Product usage reports - NPS survey - Referral program ### Billing Emails - Switch to annual - Failed payment recovery - Cancellation survey - Upcoming renewal reminders ### Usage Emails - Daily/weekly/monthly summaries - Key event notifications - Milestone celebrations ### Win-Back Emails - Expired trials - Cancelled customers ### Campaign Emails - Monthly roundup / newsletter - Seasonal promotions - Product updates - Industry news roundup - Pricing updates **For detailed email type reference**: See [references/email-types.md](references/email-types.md) --- ## Email Copy Guidelines ### Structure 1. **Hook**: First line grabs attention 2. **Context**: Why this matters to them 3. **Value**: The useful content 4. **CTA**: What to do next 5. **Sign-off**: Human, warm close ### Formatting - Short paragraphs (1-3 sentences) - White space between sections - Bullet points for scanability - Bold for emphasis (sparingly) - Mobile-first (most read on phone) ### Tone - Conversational, not formal - First-person (I/we) and second-person (you) - Active voice - Read it out loud—does it sound human? ### Length - 50-125 words for transactional - 150-300 words for educational - 300-500 words for story-driven ### CTA Guidelines - Buttons for primary actions - Links for secondary actions - One clear primary CTA per email - Button text: Action + outcome **For detailed copy, personalization, and testing guidelines**: See [references/copy-guidelines.md](references/copy-guidelines.md) --- ## Output Format ### Sequence Overview ``` Sequence Name: [Name] Trigger: [What starts the sequence] Goal: [Primary conversion goal] Length: [Number of emails] Timing: [Delay between emails] Exit Conditions: [When they leave the sequence] ``` ### For Each Email ``` Email [#]: [Name/Purpose] Send: [Timing] Subject: [Subject line] Preview: [Preview text] Body: [Full copy] CTA: [Button text] → [Link destination] Segment/Conditions: [If applicable] ``` ### Metrics Plan What to measure and benchmarks --- ## Task-Specific Questions 1. What triggers entry to this sequence? 2. What's the primary goal/conversion action? 3. What do they already know about you? 4. What other emails are they receiving? 5. What's your current email performance? --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email tools: | Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) | | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) | | **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) | | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) | | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) | | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) | --- ## Related Skills - **lead-magnets**: For planning lead magnets that feed into nurture sequences - **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this) - **onboarding-cro**: For in-app onboarding (email supports this) - **copywriting**: For landing pages emails link to - **ab-test-setup**: For testing email elements - **popup-cro**: For email capture popups - **revops**: For lifecycle stages that trigger email sequences --- Source: https://vibegrow.io/skills/form-cro.md Canonical: https://vibegrow.io/skills/form-cro # Form CRO Canonical: https://vibegrow.io/skills/form-cro Markdown: https://vibegrow.io/skills/form-cro.md Optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or… ## Skill Metadata - Slug: form-cro - Category: Conversion - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - optimize any form that is NOT signup/registration — including lead capture forms ## Full Skill Source # Form CRO You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before providing recommendations, identify: 1. **Form Type** - Lead capture (gated content, newsletter) - Contact form - Demo/sales request - Application form - Survey/feedback - Checkout form - Quote request 2. **Current State** - How many fields? - What's the current completion rate? - Mobile vs. desktop split? - Where do users abandon? 3. **Business Context** - What happens with form submissions? - Which fields are actually used in follow-up? - Are there compliance/legal requirements? --- ## Core Principles ### 1. Every Field Has a Cost Each field reduces completion rate. Rule of thumb: - 3 fields: Baseline - 4-6 fields: 10-25% reduction - 7+ fields: 25-50%+ reduction For each field, ask: - Is this absolutely necessary before we can help them? - Can we get this information another way? - Can we ask this later? ### 2. Value Must Exceed Effort - Clear value proposition above form - Make what they get obvious - Reduce perceived effort (field count, labels) ### 3. Reduce Cognitive Load - One question per field - Clear, conversational labels - Logical grouping and order - Smart defaults where possible --- ## Field-by-Field Optimization ### Email Field - Single field, no confirmation - Inline validation - Typo detection (did you mean gmail.com?) - Proper mobile keyboard ### Name Fields - Single "Name" vs. First/Last — test this - Single field reduces friction - Split needed only if personalization requires it ### Phone Number - Make optional if possible - If required, explain why - Auto-format as they type - Country code handling ### Company/Organization - Auto-suggest for faster entry - Enrichment after submission (Clearbit, etc.) - Consider inferring from email domain ### Job Title/Role - Dropdown if categories matter - Free text if wide variation - Consider making optional ### Message/Comments (Free Text) - Make optional - Reasonable character guidance - Expand on focus ### Dropdown Selects - "Select one..." placeholder - Searchable if many options - Consider radio buttons if < 5 options - "Other" option with text field ### Checkboxes (Multi-select) - Clear, parallel labels - Reasonable number of options - Consider "Select all that apply" instruction --- ## Form Layout Optimization ### Field Order 1. Start with easiest fields (name, email) 2. Build commitment before asking more 3. Sensitive fields last (phone, company size) 4. Logical grouping if many fields ### Labels and Placeholders - Labels: Keep visible (not just placeholder) — placeholders disappear when typing, leaving users unsure what they're filling in - Placeholders: Examples, not labels - Help text: Only when genuinely helpful **Good:** ``` Email [name@company.com] ``` **Bad:** ``` [Enter your email address] ← Disappears on focus ``` ### Visual Design - Sufficient spacing between fields - Clear visual hierarchy - CTA button stands out - Mobile-friendly tap targets (44px+) ### Single Column vs. Multi-Column - Single column: Higher completion, mobile-friendly - Multi-column: Only for short related fields (First/Last name) - When in doubt, single column --- ## Multi-Step Forms ### When to Use Multi-Step - More than 5-6 fields - Logically distinct sections - Conditional paths based on answers - Complex forms (applications, quotes) ### Multi-Step Best Practices - Progress indicator (step X of Y) - Start with easy, end with sensitive - One topic per step - Allow back navigation - Save progress (don't lose data on refresh) - Clear indication of required vs. optional ### Progressive Commitment Pattern 1. Low-friction start (just email) 2. More detail (name, company) 3. Qualifying questions 4. Contact preferences --- ## Error Handling ### Inline Validation - Validate as they move to next field - Don't validate too aggressively while typing - Clear visual indicators (green check, red border) ### Error Messages - Specific to the problem - Suggest how to fix - Positioned near the field - Don't clear their input **Good:** "Please enter a valid email address (e.g., name@company.com)" **Bad:** "Invalid input" ### On Submit - Focus on first error field - Summarize errors if multiple - Preserve all entered data - Don't clear form on error --- ## Submit Button Optimization ### Button Copy Weak: "Submit" | "Send" Strong: "[Action] + [What they get]" Examples: - "Get My Free Quote" - "Download the Guide" - "Request Demo" - "Send Message" - "Start Free Trial" ### Button Placement - Immediately after last field - Left-aligned with fields - Sufficient size and contrast - Mobile: Sticky or clearly visible ### Post-Submit States - Loading state (disable button, show spinner) - Success confirmation (clear next steps) - Error handling (clear message, focus on issue) --- ## Trust and Friction Reduction ### Near the Form - Privacy statement: "We'll never share your info" - Security badges if collecting sensitive data - Testimonial or social proof - Expected response time ### Reducing Perceived Effort - "Takes 30 seconds" - Field count indicator - Remove visual clutter - Generous white space ### Addressing Objections - "No spam, unsubscribe anytime" - "We won't share your number" - "No credit card required" --- ## Form Types: Specific Guidance ### Lead Capture (Gated Content) - Minimum viable fields (often just email) - Clear value proposition for what they get - Consider asking enrichment questions post-download - Test email-only vs. email + name ### Contact Form - Essential: Email/Name + Message - Phone optional - Set response time expectations - Offer alternatives (chat, phone) ### Demo Request - Name, Email, Company required - Phone: Optional with "preferred contact" choice - Use case/goal question helps personalize - Calendar embed can increase show rate ### Quote/Estimate Request - Multi-step often works well - Start with easy questions - Technical details later - Save progress for complex forms ### Survey Forms - Progress bar essential - One question per screen for engagement - Skip logic for relevance - Consider incentive for completion --- ## Mobile Optimization - Larger touch targets (44px minimum height) - Appropriate keyboard types (email, tel, number) - Autofill support - Single column only - Sticky submit button - Minimal typing (dropdowns, buttons) --- ## Measurement ### Key Metrics - **Form start rate**: Page views → Started form - **Completion rate**: Started → Submitted - **Field drop-off**: Which fields lose people - **Error rate**: By field - **Time to complete**: Total and by field - **Mobile vs. desktop**: Completion by device ### What to Track - Form views - First field focus - Each field completion - Errors by field - Submit attempts - Successful submissions --- ## Output Format ### Form Audit For each issue: - **Issue**: What's wrong - **Impact**: Estimated effect on conversions - **Fix**: Specific recommendation - **Priority**: High/Medium/Low ### Recommended Form Design - **Required fields**: Justified list - **Optional fields**: With rationale - **Field order**: Recommended sequence - **Copy**: Labels, placeholders, button - **Error messages**: For each field - **Layout**: Visual guidance ### Test Hypotheses Ideas to A/B test with expected outcomes --- ## Experiment Ideas ### Form Structure Experiments **Layout & Flow** - Single-step form vs. multi-step with progress bar - 1-column vs. 2-column field layout - Form embedded on page vs. separate page - Vertical vs. horizontal field alignment - Form above fold vs. after content **Field Optimization** - Reduce to minimum viable fields - Add or remove phone number field - Add or remove company/organization field - Test required vs. optional field balance - Use field enrichment to auto-fill known data - Hide fields for returning/known visitors **Smart Forms** - Add real-time validation for emails and phone numbers - Progressive profiling (ask more over time) - Conditional fields based on earlier answers - Auto-suggest for company names --- ### Copy & Design Experiments **Labels & Microcopy** - Test field label clarity and length - Placeholder text optimization - Help text: show vs. hide vs. on-hover - Error message tone (friendly vs. direct) **CTAs & Buttons** - Button text variations ("Submit" vs. "Get My Quote" vs. specific action) - Button color and size testing - Button placement relative to fields **Trust Elements** - Add privacy assurance near form - Show trust badges next to submit - Add testimonial near form - Display expected response time --- ### Form Type-Specific Experiments **Demo Request Forms** - Test with/without phone number requirement - Add "preferred contact method" choice - Include "What's your biggest challenge?" question - Test calendar embed vs. form submission **Lead Capture Forms** - Email-only vs. email + name - Test value proposition messaging above form - Gated vs. ungated content strategies - Post-submission enrichment questions **Contact Forms** - Add department/topic routing dropdown - Test with/without message field requirement - Show alternative contact methods (chat, phone) - Expected response time messaging --- ### Mobile & UX Experiments - Larger touch targets for mobile - Test appropriate keyboard types by field - Sticky submit button on mobile - Auto-focus first field on page load - Test form container styling (card vs. minimal) --- ## Task-Specific Questions 1. What's your current form completion rate? 2. Do you have field-level analytics? 3. What happens with the data after submission? 4. Which fields are actually used in follow-up? 5. Are there compliance/legal requirements? 6. What's the mobile vs. desktop split? --- ## Related Skills - **signup-flow-cro**: For account creation forms - **popup-cro**: For forms inside popups/modals - **page-cro**: For the page containing the form - **ab-test-setup**: For testing form changes --- Source: https://vibegrow.io/skills/free-tool-strategy.md Canonical: https://vibegrow.io/skills/free-tool-strategy # Free Tool Strategy (Engineering as Marketing) Canonical: https://vibegrow.io/skills/free-tool-strategy Markdown: https://vibegrow.io/skills/free-tool-strategy.md Plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. ## Skill Metadata - Slug: free-tool-strategy - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - plan, evaluate, or build a free tool for marketing purposes — lead generation, S ## Full Skill Source # Free Tool Strategy (Engineering as Marketing) You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before designing a tool strategy, understand: 1. **Business Context** - What's the core product? Who is the target audience? What problems do they have? 2. **Goals** - Lead generation? SEO/traffic? Brand awareness? Product education? 3. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion? --- ## Core Principles ### 1. Solve a Real Problem - Tool must provide genuine value - Solves a problem your audience actually has - Useful even without your main product ### 2. Adjacent to Core Product - Related to what you sell - Natural path from tool to product - Educates on problem you solve ### 3. Simple and Focused - Does one thing well - Low friction to use - Immediate value ### 4. Worth the Investment - Lead value × expected leads > build cost + maintenance --- ## Tool Types Overview | Type | Examples | Best For | |------|----------|----------| | Calculators | ROI, savings, pricing estimators | Decisions involving numbers | | Generators | Templates, policies, names | Creating something quickly | | Analyzers | Website graders, SEO auditors | Evaluating existing work | | Testers | Meta tag preview, speed tests | Checking if something works | | Libraries | Icon sets, templates, snippets | Reference material | | Interactive | Tutorials, playgrounds, quizzes | Learning/understanding | **For detailed tool types and examples**: See [references/tool-types.md](references/tool-types.md) --- ## Ideation Framework ### Start with Pain Points 1. **What problems does your audience Google?** - Search query research, common questions 2. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations 3. **What do they need before buying your product?** - Assessments, planning, comparisons 4. **What information do they wish they had?** - Data they can't easily access, benchmarks ### Validate the Idea - **Search demand**: Is there search volume? How competitive? - **Uniqueness**: What exists? How can you be 10x better? - **Lead quality**: Does this audience match buyers? - **Build feasibility**: How complex? Can you scope an MVP? --- ## Lead Capture Strategy ### Gating Options | Approach | Pros | Cons | |----------|------|------| | Fully gated | Maximum capture | Lower usage | | Partially gated | Balance of both | Common pattern | | Ungated + optional | Maximum reach | Lower capture | | Ungated entirely | Pure SEO/brand | No direct leads | ### Lead Capture Best Practices - Value exchange clear: "Get your full report" - Minimal friction: Email only - Show preview of what they'll get - Optional: Segment by asking one qualifying question --- ## SEO Considerations ### Keyword Strategy **Tool landing page**: "[thing] calculator", "[thing] generator", "free [tool type]" **Supporting content**: "How to [use case]", "What is [concept]" ### Link Building Free tools attract links because: - Genuinely useful (people reference them) - Unique (can't link to just any page) - Shareable (social amplification) --- ## Build vs. Buy ### Build Custom When: Unique concept, core to brand, high strategic value, have dev capacity ### Use No-Code Tools Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow When: Speed to market, limited dev resources, testing concept ### Embed Existing When: Something good exists, white-label available, not core differentiator --- ## MVP Scope ### Minimum Viable Tool 1. Core functionality only—does the one thing, works reliably 2. Essential UX—clear input, obvious output, mobile works 3. Basic lead capture—email collection, leads go somewhere useful ### What to Skip Initially Account creation, saving results, advanced features, perfect design, every edge case --- ## Evaluation Scorecard Rate each factor 1-5: | Factor | Score | |--------|-------| | Search demand exists | ___ | | Audience match to buyers | ___ | | Uniqueness vs. existing | ___ | | Natural path to product | ___ | | Build feasibility | ___ | | Maintenance burden (inverse) | ___ | | Link-building potential | ___ | | Share-worthiness | ___ | **25+**: Strong candidate | **15-24**: Promising | **<15**: Reconsider --- ## Task-Specific Questions 1. What existing tools does your audience use for workarounds? 2. How do you currently generate leads? 3. What technical resources are available? 4. What's the timeline and budget? --- ## Related Skills - **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates) - **page-cro**: For optimizing the tool's landing page - **seo-audit**: For SEO-optimizing the tool - **analytics-tracking**: For measuring tool usage - **email-sequence**: For nurturing leads from the tool --- Source: https://vibegrow.io/skills/image.md Canonical: https://vibegrow.io/skills/image # Image Canonical: https://vibegrow.io/skills/image Markdown: https://vibegrow.io/skills/image.md Create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets. ## Skill Metadata - Slug: image - Category: Content - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create, generate, edit, or optimize images for marketing — blog heroes, social g ## Full Skill Source # Image You are an expert visual content producer who helps create marketing images using AI generation models, design tools, and optimization best practices. Your goal is to help users produce professional visual assets efficiently — from blog heroes and social graphics to product mockups and profile banners. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Image Goal - What type of image? (Blog hero, social graphic, product mockup, banner, brand asset, OG image) - What platform or placement? (Website, social, directory listing, app store, email) - What dimensions do you need? ### 2. Production Approach - Do you have existing brand assets? (Logo, colors, fonts, style guide) - Do you need photorealistic or illustrative style? - Is this a one-off or a template for repeated use? ### 3. Technical Context - Do you have API keys for any image tools? (Gemini, Replicate/Flux, Ideogram) - Budget constraints? (Some tools charge per image) - Do you need the image optimized for web performance? --- ## Choosing Your Approach Pick the right tool for the job: | Approach | Best For | Tools | When to Use | |----------|----------|-------|-------------| | **AI Generation** | Original images from text prompts | Gemini/Nano Banana, Flux, Ideogram | Blog heroes, social graphics, lifestyle scenes | | **AI Editing** | Modify existing images | Gemini, Flux Flex | Background removal, style changes, variations | | **Design Tools** | Templated, brand-consistent assets | Canva, Figma | Profile banners, social templates, presentations | | **Screenshot + Overlay** | Product UI showcases | Browser screenshot + code overlay | Product mockups, feature announcements | | **Stock Photography** | Generic business/lifestyle scenes | Unsplash, Pexels | When speed matters more than uniqueness | --- ## AI Image Generation Generate original images from text prompts. The fastest way to create unique marketing visuals. ### Model Comparison | Model | Best For | Text in Images | API | Cost | |-------|----------|:-:|-----|------| | **Gemini Image** (Google) | All-around, editing, text rendering | Good | [Gemini API](https://ai.google.dev/gemini-api/docs/image-generation) | Check [pricing](https://ai.google.dev/gemini-api/docs/pricing) | | **Flux** (Black Forest Labs) | Photorealism, brand consistency, batch | Limited | [BFL API](https://docs.bfl.ai/), Replicate, fal.ai | Check [pricing](https://docs.bfl.ai/quick_start/pricing) | | **Ideogram** | Typography, branded graphics | Best | [Ideogram API](https://developer.ideogram.ai/) | Check [pricing](https://about.ideogram.ai/api-pricing) | | **GPT Image** (OpenAI) | General purpose, ChatGPT integration | Good | [OpenAI API](https://platform.openai.com/docs/guides/image-generation) | Check [pricing](https://platform.openai.com/docs/pricing) | | **Midjourney** | Artistic, high-aesthetic | Poor | No official API | Subscription-based | | **Stable Diffusion** | Self-hosted, customizable | Varies | Open source | Free (GPU costs) | **Note:** DALL-E 3 is deprecated. OpenAI's current image models are the GPT Image family (`gpt-image-1`, etc.). ### When to Use Which ``` Need text/headlines in the image? ├── Yes → Ideogram (best), Gemini (good), GPT Image (decent) └── No ↓ Need product/brand consistency across images? ├── Yes → Flux (multi-image reference) └── No ↓ Need to edit an existing image? ├── Yes → Gemini (native editing), Flux Flex └── No ↓ Need highest visual quality? ├── Yes → Flux Pro, Midjourney └── No ↓ Need volume at low cost? └── Flux Klein, Gemini Flash ``` ### Prompting Basics A strong image prompt follows: **Subject + Setting + Style + Lighting + Composition + Technical** ``` A laptop on a minimal white desk showing a dashboard UI, soft directional lighting from the left, shallow depth of field, clean commercial photography style, 16:9 aspect ratio, 4K ``` **Common mistakes:** - Too vague ("a business image") — add specific details - Forgetting aspect ratio — always specify dimensions - Requesting complex text — use overlays instead for anything beyond short headlines - No style direction — "photorealistic," "flat illustration," "3D render" For detailed prompting guides per model, see [references/ai-image-prompting.md](references/ai-image-prompting.md). --- ## Design Tools For templated, brand-consistent work where AI generation is overkill or too unpredictable. ### Canva Best for non-designers who need polished output fast. - **Strengths:** Massive template library, brand kit, Magic Resize (one design → all sizes), team collaboration - **Best for:** Social graphics, presentations, email headers, simple banners - **Limitations:** Less control than Figma, templates can look generic - **Agent-friendliness:** Has an API but limited — better as a human-in-the-loop tool ### Figma Best for teams with design systems or pixel-perfect needs. - **Strengths:** Design system components, auto layout, developer handoff, plugins - **Best for:** OG images via templates, design system assets, complex layouts - **Limitations:** Steeper learning curve, requires design skill - **Agent-friendliness:** Has an API and MCP server for reading designs ### When to Use Design Tools vs. AI Generation | Scenario | Design Tool | AI Generation | |----------|:-:|:-:| | Exact brand guidelines must be followed | Yes | Maybe (with strong ref images) | | Need 20 size variants of one design | Yes (Canva Magic Resize) | No | | Unique hero image for a blog post | No | Yes | | Recurring social media template | Yes | No | | Product mockup with real UI | No (use screenshots) | No (hallucinated UI) | | Abstract/creative visual | No | Yes | --- ## Marketing Image Workflows ### Blog & Article Hero Images The image at the top of every post. Sets tone, improves shareability, required for OG/social previews. 1. **Define the concept** — what visual metaphor represents the topic? 2. **Generate with AI** — use Flux or Gemini for photorealistic, Ideogram if text needed 3. **Specify 1200x630** (works for both hero and OG image) or **1920x1080** for full-width 4. **Optimize** — compress to <200KB, serve as WebP with JPEG fallback **Prompt pattern:** ``` [Visual metaphor for topic], clean modern style, bright natural lighting, shallow depth of field, professional blog header aesthetic, 1200x630 ``` ### Social Media Graphics Platform-specific images for organic posts. | Platform | Primary Size | Aspect Ratio | Notes | |----------|-------------|:---:|-------| | Twitter/X | 1200x675 | 16:9 | Large image card | | LinkedIn | 1200x627 | 1.91:1 | Feed image | | Instagram Feed | 1080x1080 | 1:1 | Square; 1080x1350 (4:5) also strong | | Instagram Stories | 1080x1920 | 9:16 | Full screen vertical | | Facebook | 1200x630 | 1.91:1 | Link share image | **Workflow:** 1. Create the hero concept at highest resolution needed 2. Use Canva Magic Resize or manual crop for platform variants 3. Add text overlays programmatically (Ideogram or post-processing) if needed 4. Export at platform-specific dimensions ### Product Mockups & Screenshots Showcase your product UI in context. AI models hallucinate UI — don't use them for this. 1. **Capture real screenshots** of your product at 2x resolution 2. **Frame in device mockups** — use browser frame, laptop, or phone templates 3. **Add context** — callout arrows, feature labels, before/after comparisons 4. **Annotate with code** — Hyperframes or HTML/CSS for programmatic overlays **Tools:** Browser DevTools (screenshot), Shottr (Mac), CleanShot X, or `screencapture` CLI. ### Profile & Listing Banners Banners for profiles, directory listings, and marketplace pages. Often the first visual impression. | Platform | Size | Notes | |----------|------|-------| | LinkedIn personal cover | 1584x396 | 4:1, safe zone center | | LinkedIn company cover | 1128x191 | 5.9:1; LinkedIn recommends up to 4200x700 | | Twitter/X header | 1500x500 | 3:1, partially obscured by avatar | | Product Hunt gallery | 1270x760 | 5:3, up to 6 images | | G2 profile | 1280x720 | 16:9, product screenshots preferred | | GitHub social preview | 1280x640 | 2:1, shows in link cards | | App Store screenshots | Varies by device | See aso-audit skill for full specs | | Google Play feature graphic | 1024x500 | ~2:1, required for store listing | **Best practices:** - **Keep text minimal** — banners are seen at small sizes on mobile - **Center critical content** — edges get cropped differently per device - **Show the product** — real UI screenshots outperform abstract graphics on directory listings - **Match your brand** — use consistent colors, fonts, logo placement - **Update seasonally** — stale banners signal an inactive product **Workflow:** 1. Pick the platform(s) and note exact dimensions 2. For directories (Product Hunt, G2): use real product screenshots with light annotation 3. For profiles (LinkedIn, Twitter): use brand colors + tagline + optional product shot 4. Generate with Canva/Figma templates or Ideogram (if text-heavy) 5. Test at actual display size — zoom out to check readability ### Brand Assets Logos, icons, and illustrations. AI generation has limits here. | Asset | AI Generation | Design Tool | Notes | |-------|:-:|:-:|-------| | Logo | Poor — inconsistent, not vector | Yes (Figma) | Always design or commission logos | | App icon | Decent starting point | Yes (Figma) | Generate concepts, refine manually | | Illustrations | Good for style exploration | Depends | AI for concepts, finalize in design tool | | Favicons | No | Yes | Derive from logo | | Social icons | No | Yes | Use platform-provided assets | --- ## Image Optimization Every image on your site affects page speed, which affects SEO and conversions. ### Format Guide | Format | Best For | Compression | Browser Support | |--------|----------|-------------|:---:| | **WebP** | Photos, graphics — default choice | Lossy + lossless | ~96% | | **AVIF** | Highest compression, newest | Better than WebP | ~94% | | **JPEG** | Fallback for older browsers | Lossy only | Universal | | **PNG** | Transparency, screenshots | Lossless | Universal | | **SVG** | Logos, icons, illustrations | Vector (scales) | Universal | ### Optimization Checklist - [ ] **Serve WebP** with JPEG/PNG fallback (`` element or CDN auto-format) - [ ] **Resize to display size** — don't serve 4000px images in 800px containers - [ ] **Compress** — target quality 75-85% for photos, near-lossless for screenshots - [ ] **Lazy load** below-the-fold images (`loading="lazy"`) - [ ] **Set explicit dimensions** — `width` and `height` attributes prevent layout shift (CLS) - [ ] **Use a CDN** with auto-optimization (Cloudflare, Vercel, Imgix, Cloudinary) - [ ] **Add alt text** — descriptive, keyword-relevant, not stuffed ### Quick Optimization Commands ```bash # Convert to WebP (using cwebp) cwebp -q 80 input.png -o output.webp # Batch convert with ImageMagick mogrify -format webp -quality 80 *.png # Optimize JPEG (using jpegoptim) jpegoptim --max=80 --strip-all *.jpg # Check image sizes on a page curl -s https://yoursite.com | grep -oP 'src="[^"]+\.(jpg|png|webp)"' | head -20 ``` --- ## OG & Social Preview Images The image that appears when your URL is shared on social media, Slack, Discord, etc. ### Required Meta Tags ```html ``` ### Dynamic OG Images Generate OG images programmatically for pages with dynamic content (blog posts, user profiles): - **Vercel OG** (`@vercel/og`) — generates images at the edge using JSX - **Satori** — converts HTML/CSS to SVG (powers Vercel OG) - **Cloudinary** — URL-based text overlay on template images **Best for programmatic SEO:** Generate unique OG images per page using templates + dynamic data. --- ## Common Mistakes 1. **Using AI for product UI screenshots** — models hallucinate interfaces; capture real screenshots 2. **Skipping image optimization** — unoptimized images are the #1 page speed killer 3. **No OG image** — shared links look broken without a preview image 4. **Wrong aspect ratio** — always check platform specs before generating 5. **Text-heavy images without Ideogram** — most AI models butcher text; use Ideogram or add text in post 6. **Generating without style direction** — "photorealistic," "flat illustration," "3D render" drastically changes output 7. **Inconsistent brand visuals** — use Flux multi-reference or design templates for consistency 8. **Huge images on landing pages** — compress, resize, lazy load --- ## Task-Specific Questions 1. What type of image do you need? (Blog hero, social graphic, mockup, banner, brand asset) 2. What platform or placement? (This determines dimensions) 3. Do you have brand assets to match? (Colors, fonts, logo, style guide) 4. Is this a one-off or a repeatable template? 5. Do you have API keys for any image generation tools? 6. Does this need to be optimized for web performance? --- ## Related Skills - **ad-creative**: For paid ad image creative, platform-specific ad specs, and scaled ad production - **video**: For AI video production and programmatic video - **social-content**: For what to post and content strategy - **page-cro**: For image placement and conversion optimization on landing pages - **seo-audit**: For image SEO (alt text, file names, lazy loading) - **aso-audit**: For app store screenshot specs and optimization - **directory-submissions**: For Product Hunt gallery images and directory listing visuals --- Source: https://vibegrow.io/skills/instagrow.md Canonical: https://vibegrow.io/skills/instagrow # Instagrow Instagram Scheduling Canonical: https://vibegrow.io/skills/instagrow Markdown: https://vibegrow.io/skills/instagrow.md Use when scheduling, publishing, drafting, or verifying Instagram posts with the Vibegrow Instagrow Chrome extension and Pi Chrome. ## Skill Metadata - Slug: instagrow - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Full Skill Source # Instagrow Instagram Scheduling Use this skill to schedule Instagram posts through **Instagrow Post Assistant** in the user's real signed-in Chrome profile. The goal is to create a scheduled Instagrow draft, verify it in Instagrow's queue, and avoid accidentally publishing through Instagram's native Share button. ## Core rule Use **Instagrow / Post Assistant**, not Instagram's default composer, for scheduling. Do not click native Instagram **Share** unless the user explicitly asks to publish immediately. Scheduling should end with a visible Instagrow queue item such as `Scheduled Today, 19:45`. ## Required setup ### 1. Pi Chrome access Pi Chrome lets the agent control the user's existing signed-in Chrome profile. If chrome tools are unavailable or locked, ask the user to run: ```bash pi install npm:pi-chrome /chrome onboard /chrome doctor /chrome authorize indefinite ``` Install flow from `https://pi.dev/packages/pi-chrome`: 1. Run `pi install npm:pi-chrome`. 2. Run `/chrome onboard` in Pi. 3. Load the bundled Chrome connector extension in `chrome://extensions`: - Enable **Developer mode**. - Click **Load unpacked**. - Select the `browser-extension/` folder revealed by `/chrome onboard`. 4. Run `/chrome doctor` and confirm the companion extension responds. 5. Run `/chrome authorize indefinite` for long scheduling sessions. Useful commands: ```bash /chrome status /chrome background on # default, work silently /chrome background off # user can watch /chrome revoke # lock access again when done ``` Security note: Pi Chrome controls the user's real signed-in Chrome profile only after explicit authorization. Prefer `/chrome revoke` after sensitive workflows are done. ### 2. Instagrow Chrome extension Install Instagrow from `https://vibegrow.io/instagrow`: 1. Open `https://vibegrow.io/instagrow`. 2. Click **Download Chrome ZIP** for the current release. 3. Unzip the folder and keep it somewhere stable. 4. Open `chrome://extensions`. 5. Enable **Developer mode**. 6. Click **Load unpacked**. 7. Select the unzipped Instagrow extension folder. 8. Open `https://www.instagram.com/` in the same Chrome profile. 9. Verify Instagrow is present: the page should expose a right-side **Post Assistant** panel or a left-nav **Assistant+ / Instagrow** control. The extension runs in the browser session. Do not ask the user for their Instagram password. ## Scheduling workflow ### 1. Confirm inputs Before scheduling, confirm: - Instagram account, e.g. `vibegrow.io`. - Asset path and format. - Caption text. - Schedule date and local time. - Time zone. If the user says CET during summer in Germany, interpret it as local Berlin time unless they specify otherwise. June is usually **CEST**. Check local time when needed: ```bash TZ="Europe/Berlin" date "+%Y-%m-%d %H:%M %Z (%A)" ``` Instagrow has a minimum schedule lead time of about 5 minutes. If the requested time is already past or too soon, ask for a new time. ### 2. Prepare the asset Instagram/Instagrow usually accepts JPEG reliably for feed images. If the source is PNG, create a JPEG copy while preserving dimensions: ```bash python3 - <<'PY' from PIL import Image from pathlib import Path src = Path('path/to/post.png') dst = src.with_suffix('.jpg') Image.open(src).convert('RGB').save(dst, quality=95, optimize=True, progressive=True) print(dst) PY ``` For Instagram feed posts, verify dimensions. A 4:5 post should be `1080x1350`. ### 3. Open Instagram and verify account Use chrome tools only: 1. `chrome_tab(list)` to find Instagram. 2. `chrome_snapshot` on the Instagram tab. 3. Verify the active/account context is the intended account, usually by checking profile links or Instagrow's selected user label. Do not switch accounts unless the user asks. ### 4. Prefer direct Instagrow scheduling through its app API Instagrow exposes its app in the page as `window.$instagrow.app` once loaded. This is the most reliable way to schedule from an agent because the extension UI lives inside Shadow DOM and native file pickers can be brittle. First verify Instagrow exists: ```js await window.$instagrow?.app ``` Inspect state if needed: ```js const app = await window.$instagrow.app; ({ selectedUserId: app.$s?.later?.selectedUserId, posts: app.$later.proxy.getSelectedUserPosts().map(p => ({ id: p.id, status: p.status, date: p.date, local: p.date ? new Date(p.date).toString() : null, type: p.type, caption: p.caption?.slice(0, 80), mediaCount: p.mediaList?.length, })) }) ``` If the local asset must be fetched by the page, serve the directory locally with CORS: ```bash python3 - <<'PY' > /tmp/instagrow-cors-server.log 2>&1 & from http.server import ThreadingHTTPServer, SimpleHTTPRequestHandler from pathlib import Path import os ROOT = Path('path/to/asset/folder').resolve() os.chdir(ROOT) class Handler(SimpleHTTPRequestHandler): def end_headers(self): self.send_header('Access-Control-Allow-Origin', '*') self.send_header('Access-Control-Allow-Methods', 'GET, OPTIONS') self.send_header('Access-Control-Allow-Headers', '*') super().end_headers() def do_OPTIONS(self): self.send_response(204) self.end_headers() ThreadingHTTPServer(('127.0.0.1', 8765), Handler).serve_forever() PY ``` Then schedule via `chrome_evaluate`: ```js (async () => { const app = await window.$instagrow.app; const caption = `CAPTION_TEXT_HERE`; // Local browser time. Month is zero-based: June = 5. const scheduledFor = new Date(2026, 5, 2, 19, 45, 0, 0).getTime(); const res = await fetch('http://127.0.0.1:8765/asset.jpg'); if (!res.ok) throw new Error(`Failed to fetch asset: ${res.status}`); const blob = await res.blob(); const file = new File([blob], 'asset.jpg', { type: 'image/jpeg', lastModified: Date.now(), }); const selectedUserId = app.$s?.later?.selectedUserId || app.$later?.proxy?.getSelectedUserState?.()?.auth?.userId; if (!selectedUserId) throw new Error('No Instagrow selected user/account.'); const postId = await app.$later.controller.createPost(selectedUserId, [file], { caption, date: scheduledFor, status: 'scheduled', type: 'post', options: { besties: false, disableComments: false, hideLikes: false, }, }); app.$s.transaction?.(s => { if (!s?.later) return; s.later.processing = false; s.later.selectedUserId = selectedUserId; s.later.selectedPostId = postId; s.later.showBodyPanel = true; s.later.selectedPillId = null; s.later.lastDate = scheduledFor; }); const post = app.$later.proxy.getPost(postId); return { ok: true, postId, selectedUserId, scheduledFor, scheduledForLocal: new Date(scheduledFor).toString(), post: { id: post?.id, status: post?.status, date: post?.date, caption: post?.caption, type: post?.type, mediaCount: post?.mediaList?.length, media: post?.mediaList?.[0] && { width: post.mediaList[0].width, height: post.mediaList[0].height, isVideo: post.mediaList[0].isVideo, fileId: post.mediaList[0].fileId, previewId: post.mediaList[0].previewId, }, }, }; })() ``` Use local time in `new Date(...)`. If the user gives an absolute timezone, convert carefully before scheduling. ### 5. Verify the schedule Immediately verify through Instagrow state: ```js (async () => { const app = await window.$instagrow.app; return app.$later.proxy.getSelectedUserPosts().map(p => ({ id: p.id, status: p.status, date: p.date, local: p.date ? new Date(p.date).toString() : null, type: p.type, caption: p.caption, mediaCount: p.mediaList?.length, width: p.mediaList?.[0]?.width, height: p.mediaList?.[0]?.height, isVideo: p.mediaList?.[0]?.isVideo, })); })() ``` Confirm: - `status` is `scheduled`. - `local` matches the requested date/time. - `caption` matches exactly. - `mediaCount` is correct. - dimensions match expected creative. - Instagrow side panel visually shows `Scheduled Today, HH:MM` or equivalent. Take a screenshot: ```text chrome_screenshot(path: ".pi/chrome-screenshots/.png") ``` Report the screenshot path to the user. ## UI-based fallback If direct scheduling is not appropriate, use Instagrow UI, not native Instagram UI: 1. Open Instagram. 2. Open **Assistant+ / Instagrow Post Assistant**. 3. Use **ADD FILES** inside the Post Assistant panel. 4. Fill caption in the Instagrow editor. 5. Open the **Schedule** tab inside the Instagrow editor. 6. Pick date/time or create a Time Slot, e.g. `19:45`. 7. Save/schedule. 8. Verify the queue item appears in Post Assistant. If Chrome snapshots do not expose controls inside Instagrow, inspect the Shadow DOM: ```js const sh = document.querySelector('#shadow')?.shadowRoot; sh?.textContent ``` Clickable controls can be found with: ```js [...document.querySelector('#shadow').shadowRoot.querySelectorAll('button,input,textarea,[role=button]')] .map(el => ({ text: (el.innerText || el.textContent || el.value || '').trim(), tag: el.tagName, rect: el.getBoundingClientRect().toJSON?.() || el.getBoundingClientRect(), })) ``` ## Mistakes to avoid - Do **not** use Instagram native Create/Share for scheduled posts. - Do **not** click **Share** unless the user explicitly asked to publish now. - Do **not** use OS-level automation, AppleScript, QuickTime screenshots, or manual file dialogs. Use `chrome_*` tools. - Do **not** assume `chrome_upload_file` will work against Instagrow's Shadow DOM or hidden extension inputs. Prefer direct Instagrow app scheduling. - Do **not** schedule before verifying the selected Instagram account. - Do **not** leave a native Instagram composer draft open if it was created accidentally. Close/discard it after confirming the Instagrow scheduled draft exists. - Do **not** silently convert time zones. Tell the user if CET/CEST ambiguity matters. ## Final response format Keep the final confirmation concise: ```text Done. Scheduled through Instagrow Post Assistant for @account. - Status: Scheduled - Time: Today, 19:45 CEST - Creative: path/to/file.jpg - Caption: final approved caption - Verification screenshot: .pi/chrome-screenshots/name.png ``` --- Source: https://vibegrow.io/skills/launch-strategy.md Canonical: https://vibegrow.io/skills/launch-strategy # Launch Strategy Canonical: https://vibegrow.io/skills/launch-strategy Markdown: https://vibegrow.io/skills/launch-strategy.md Plan a product launch, feature announcement, or release strategy. ## Skill Metadata - Slug: launch-strategy - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - plan a product launch, feature announcement, or release strategy ## Full Skill Source # Launch Strategy You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. --- ## Core Philosophy The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience. A strong launch isn't about a single moment. It's about: - Getting your product into users' hands early - Learning from real feedback - Making a splash at every stage - Building momentum that compounds over time --- ## The ORB Framework Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels. ### Owned Channels You own the channel (though not the audience). Direct access without algorithms or platform rules. **Examples:** - Email list - Blog - Podcast - Branded community (Slack, Discord) - Website/product **Why they matter:** - Get more effective over time - No algorithm changes or pay-to-play - Direct relationship with audience - Compound value from content **Start with 1-2 based on audience:** - Industry lacks quality content → Start a blog - People want direct updates → Focus on email - Engagement matters → Build a community **Example - Superhuman:** Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement. ### Rented Channels Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases. **Examples:** - Social media (Twitter/X, LinkedIn, Instagram) - App stores and marketplaces - YouTube - Reddit **How to use correctly:** - Pick 1-2 platforms where your audience is active - Use them to drive traffic to owned channels - Don't rely on them as your only strategy **Example - Notion:** Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding. **Platform-specific tactics:** - Twitter/X: Threads that spark conversation → link to newsletter - LinkedIn: High-value posts → lead to gated content or email signup - Marketplaces (Shopify, Slack): Optimize listing → drive to site for more Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem. ### Borrowed Channels Tap into someone else's audience to shortcut the hardest part—getting noticed. **Examples:** - Guest content (blog posts, podcast interviews, newsletter features) - Collaborations (webinars, co-marketing, social takeovers) - Speaking engagements (conferences, panels, virtual summits) - Influencer partnerships **Be proactive, not passive:** 1. List industry leaders your audience follows 2. Pitch win-win collaborations 3. Use tools like SparkToro or Listen Notes to find audience overlap 4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](../../tools/integrations/introw.md) to manage deal registration and commissions) **Example - TRMNL:** Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion. Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships. --- ## Five-Phase Launch Approach Launching isn't a one-day event. It's a phased process that builds momentum. ### Phase 1: Internal Launch Gather initial feedback and iron out major issues before going public. **Actions:** - Recruit early users one-on-one to test for free - Collect feedback on usability gaps and missing features - Ensure prototype is functional enough to demo (doesn't need to be production-ready) **Goal:** Validate core functionality with friendly users. ### Phase 2: Alpha Launch Put the product in front of external users in a controlled way. **Actions:** - Create landing page with early access signup form - Announce the product exists - Invite users individually to start testing - MVP should be working in production (even if still evolving) **Goal:** First external validation and initial waitlist building. ### Phase 3: Beta Launch Scale up early access while generating external buzz. **Actions:** - Work through early access list (some free, some paid) - Start marketing with teasers about problems you solve - Recruit friends, investors, and influencers to test and share **Consider adding:** - Coming soon landing page or waitlist - "Beta" sticker in dashboard navigation - Email invites to early access list - Early access toggle in settings for experimental features **Goal:** Build buzz and refine product with broader feedback. ### Phase 4: Early Access Launch Shift from small-scale testing to controlled expansion. **Actions:** - Leak product details: screenshots, feature GIFs, demos - Gather quantitative usage data and qualitative feedback - Run user research with engaged users (incentivize with credits) - Optionally run product/market fit survey to refine messaging **Expansion options:** - Option A: Throttle invites in batches (5-10% at a time) - Option B: Invite all users at once under "early access" framing **Goal:** Validate at scale and prepare for full launch. ### Phase 5: Full Launch Open the floodgates. **Actions:** - Open self-serve signups - Start charging (if not already) - Announce general availability across all channels **Launch touchpoints:** - Customer emails - In-app popups and product tours - Website banner linking to launch assets - "New" sticker in dashboard navigation - Blog post announcement - Social posts across platforms - Product Hunt, BetaList, Hacker News, etc. **Goal:** Maximum visibility and conversion to paying users. --- ## Product Hunt Launch Strategy Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation. ### Pros - Exposure to tech-savvy early adopter audience - Credibility bump (especially if Product of the Day) - Potential PR coverage and backlinks ### Cons - Very competitive to rank well - Short-lived traffic spikes - Requires significant pre-launch planning ### How to Launch Successfully **Before launch day:** 1. Build relationships with influential supporters, content hubs, and communities 2. Optimize your listing: compelling tagline, polished visuals, short demo video 3. Study successful launches to identify what worked 4. Engage in relevant communities—provide value before pitching 5. Prepare your team for all-day engagement **On launch day:** 1. Treat it as an all-day event 2. Respond to every comment in real-time 3. Answer questions and spark discussions 4. Encourage your existing audience to engage 5. Direct traffic back to your site to capture signups **After launch day:** 1. Follow up with everyone who engaged 2. Convert Product Hunt traffic into owned relationships (email signups) 3. Continue momentum with post-launch content ### Case Studies **SavvyCal** (Scheduling tool): - Optimized landing page and onboarding before launch - Built relationships with productivity/SaaS influencers in advance - Responded to every comment on launch day - Result: #2 Product of the Month **Reform** (Form builder): - Studied successful launches and applied insights - Crafted clear tagline, polished visuals, demo video - Engaged in communities before launch (provided value first) - Treated launch as all-day engagement event - Directed traffic to capture signups - Result: #1 Product of the Day --- ## Post-Launch Product Marketing Your launch isn't over when the announcement goes live. Now comes adoption and retention work. ### Immediate Post-Launch Actions **Educate new users:** Set up automated onboarding email sequence introducing key features and use cases. **Reinforce the launch:** Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it. **Differentiate against competitors:** Publish comparison pages highlighting why you're the obvious choice. **Update web pages:** Add dedicated sections about the new feature/product across your site. **Offer hands-on preview:** Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up. ### Keep Momentum Going It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch. --- ## Ongoing Launch Strategy Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement. ### How to Prioritize What to Announce Use this matrix to decide how much marketing each update deserves: **Major updates** (new features, product overhauls): - Full campaign across multiple channels - Blog post, email campaign, in-app messages, social media - Maximize exposure **Medium updates** (new integrations, UI enhancements): - Targeted announcement - Email to relevant segments, in-app banner - Don't need full fanfare **Minor updates** (bug fixes, small tweaks): - Changelog and release notes - Signal that product is improving - Don't dominate marketing ### Announcement Tactics **Space out releases:** Instead of shipping everything at once, stagger announcements to maintain momentum. **Reuse high-performing tactics:** If a previous announcement resonated, apply those insights to future updates. **Keep engaging:** Continue using email, social, and in-app messaging to highlight improvements. **Signal active development:** Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around. --- ## Launch Checklist ### Pre-Launch - [ ] Landing page with clear value proposition - [ ] Email capture / waitlist signup - [ ] Early access list built - [ ] Owned channels established (email, blog, community) - [ ] Rented channel presence (social profiles optimized) - [ ] Borrowed channel opportunities identified (podcasts, influencers) - [ ] Product Hunt listing prepared (if using) - [ ] Launch assets created (screenshots, demo video, GIFs) - [ ] Onboarding flow ready - [ ] Analytics/tracking in place ### Launch Day - [ ] Announcement email to list - [ ] Blog post published - [ ] Social posts scheduled and posted - [ ] Product Hunt listing live (if using) - [ ] In-app announcement for existing users - [ ] Website banner/notification active - [ ] Team ready to engage and respond - [ ] Monitor for issues and feedback ### Post-Launch - [ ] Onboarding email sequence active - [ ] Follow-up with engaged prospects - [ ] Roundup email includes announcement - [ ] Comparison pages published - [ ] Interactive demo created - [ ] Gather and act on feedback - [ ] Plan next launch moment --- ## Task-Specific Questions 1. What are you launching? (New product, major feature, minor update) 2. What's your current audience size and engagement? 3. What owned channels do you have? (Email list size, blog traffic, community) 4. What's your timeline for launch? 5. Have you launched before? What worked/didn't work? 6. Are you considering Product Hunt? What's your preparation status? --- ## Related Skills - **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals) - **email-sequence**: For launch and onboarding email sequences - **page-cro**: For optimizing launch landing pages - **marketing-psychology**: For psychology behind waitlists and exclusivity - **programmatic-seo**: For comparison pages mentioned in post-launch - **sales-enablement**: For launch sales collateral and enablement materials --- Source: https://vibegrow.io/skills/lead-magnets.md Canonical: https://vibegrow.io/skills/lead-magnets # Lead Magnets Canonical: https://vibegrow.io/skills/lead-magnets Markdown: https://vibegrow.io/skills/lead-magnets.md Create, plan, or optimize a lead magnet for email capture or lead generation. ## Skill Metadata - Slug: lead-magnets - Category: Lifecycle - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create, plan, or optimize a lead magnet for email capture or lead generation ## Full Skill Source # Lead Magnets You are an expert in lead magnet strategy. Your goal is to help plan lead magnets that capture emails, generate qualified leads, and naturally lead to product adoption. ## Before Planning **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Business Context - What does the company do? - Who is the ideal customer? - What problems does your product solve? ### 2. Current Lead Generation - How do you currently capture leads? - What lead magnets or offers do you have? - What's your current conversion rate on email capture? ### 3. Content Assets - What existing content could be repurposed? (blog posts, guides, data) - What expertise can you package? - What templates or tools do you use internally? ### 4. Goals - Primary goal: email list growth, lead quality, product education? - Target audience stage: awareness, consideration, or decision? - Timeline and resource constraints? --- ## Lead Magnet Principles ### 1. Solve a Specific Problem - Address one clear pain point, not a broad topic - "How to write cold emails that get replies" > "Marketing guide" ### 2. Match the Buyer Stage - Awareness leads need education - Consideration leads need comparison and evaluation - Decision leads need implementation help ### 3. High Perceived Value, Low Time Investment - Should look like it's worth paying for - Consumable in under 30 minutes (ideally under 10) - Immediate, actionable takeaway ### 4. Natural Path to Product - Solves a problem your product also solves - Creates awareness of a gap your product fills - Demonstrates your expertise in the space ### 5. Easy to Consume - One clear format (don't mix ebook + video + spreadsheet) - Works on mobile - No special software required --- ## Lead Magnet Types | Type | Best For | Effort | Time to Create | |------|----------|--------|----------------| | Checklist | Quick wins, process steps | Low | 1-2 hours | | Cheat sheet | Reference material, shortcuts | Low | 2-4 hours | | Template (doc/spreadsheet/Notion) | Repeatable processes, workflows | Low-Med | 2-8 hours | | Swipe file | Inspiration, examples | Medium | 4-8 hours | | Ebook/guide | Deep education, authority | High | 1-3 weeks | | Mini-course (email) | Education + nurture | Medium | 1-2 weeks | | Mini-course (video) | Education + personality | High | 2-4 weeks | | Quiz/assessment | Segmentation, engagement | Medium | 1-2 weeks | | Webinar | Authority, live engagement | Medium | 1 week prep | | Resource library | Ongoing value, return visits | High | Ongoing | | Free trial/community access | Product experience | Varies | Varies | **For detailed creation guidance per format**: See [references/format-guide.md](references/format-guide.md) --- ## Matching Lead Magnets to Buyer Stage ### Awareness Stage Goal: Educate on the problem. Attract people who don't know you yet. | Format | Example | |--------|---------| | Checklist | "10-Point Website Audit Checklist" | | Cheat sheet | "SEO Cheat Sheet for Beginners" | | Ebook/guide | "The Complete Guide to Email Marketing" | | Quiz | "What Type of Marketer Are You?" | ### Consideration Stage Goal: Help evaluate solutions. Build trust and demonstrate expertise. | Format | Example | |--------|---------| | Comparison template | "CRM Comparison Spreadsheet" | | Assessment | "Marketing Maturity Assessment" | | Case study collection | "5 Companies That 3x'd Their Pipeline" | | Webinar | "How to Choose the Right Analytics Tool" | ### Decision Stage Goal: Help implement. Remove friction to purchase. | Format | Example | |--------|---------| | Template | "Ready-to-Use Sales Email Templates" | | Free trial | "14-Day Free Trial" | | Implementation guide | "Migration Checklist: Switch in 30 Minutes" | | ROI calculator | "Calculate Your Savings" (→ see **free-tool-strategy**) | --- ## Gating Strategy ### Gating Options | Approach | When to Use | Trade-off | |----------|-------------|-----------| | **Full gate** | High-value content, bottom-funnel | Max capture, lower reach | | **Partial gate** | Preview + full version | Balance of reach and capture | | **Ungated + optional** | Top-funnel education | Max reach, lower capture | | **Content upgrade** | Blog post + bonus | Contextual, high-intent | ### What to Ask For - **Email only** — highest conversion, lowest friction - **Email + name** — enables personalization, slight friction increase - **Email + company/role** — better lead qualification, more friction - **Multi-field** — only for high-value offers (webinars, demos) Rule of thumb: Ask for the minimum needed. Every extra field reduces conversion by 5-10%. ### How to Frame the Exchange - Make the value obvious: "Get the full 25-page guide free" - Show a preview: table of contents, first page, sample results - Add social proof: "Downloaded by 5,000+ marketers" - Reduce risk: "No spam. Unsubscribe anytime." **For form optimization**: See **form-cro** skill **For popup implementation**: See **popup-cro** skill --- ## Landing Page & Delivery ### Landing Page Structure 1. **Headline** — Clear benefit: what they'll get and why it matters 2. **Preview/mockup** — Visual of the lead magnet (cover, screenshot, sample page) 3. **What's inside** — 3-5 bullet points of key takeaways 4. **Social proof** — Download count, testimonials, logos 5. **Form** — Minimal fields, clear CTA button 6. **FAQ** — Address hesitations (Is it really free? What format?) **For landing page optimization**: See **page-cro** skill ### Delivery Methods | Method | Pros | Cons | |--------|------|------| | **Instant download** | Immediate gratification | No email verification | | **Email delivery** | Verifies email, starts relationship | Slight delay | | **Thank you page + email** | Best of both—instant access + email copy | Slightly more complex | | **Drip delivery** | Builds habit, multiple touchpoints | Only for courses/series | ### Thank You Page Optimization Don't waste the thank you page. After they've converted: - Confirm delivery ("Check your inbox") - Offer a next step (book a demo, start trial, join community) - Share on social (pre-written tweet/post) - Recommend related content --- ## Promotion & Distribution ### Blog CTAs & Content Upgrades - Add relevant CTAs within blog posts (inline, end-of-post) - Create post-specific content upgrades (bonus checklist for a how-to post) - Content upgrades convert 2-5x better than generic sidebar CTAs ### Exit-Intent & Popups - Trigger on exit intent or scroll depth - Match the popup offer to the page content - **See popup-cro** for implementation ### Social Media - Share snippets and teasers from the lead magnet - Create carousel posts from key points - Use the lead magnet as the CTA in your bio/profile - **See social-content** for social strategy ### Paid Promotion - Facebook/Instagram lead ads for top-funnel lead magnets - Google Ads for high-intent lead magnets (templates, tools) - LinkedIn for B2B lead magnets - Retarget blog visitors with lead magnet ads - **See paid-ads** for campaign strategy ### Partner Co-Promotion - Cross-promote with complementary brands - Guest webinars with partner audiences - Include in partner newsletters - Bundle in resource collections --- ## Measuring Success ### Key Metrics | Metric | What It Tells You | Benchmark | |--------|-------------------|-----------| | **Landing page conversion rate** | Offer attractiveness | 20-40% (warm traffic), 5-15% (cold) | | **Cost per lead** | Acquisition efficiency | Varies by channel and industry | | **Lead-to-customer rate** | Lead quality | 1-5% (B2B), varies widely | | **Email engagement** | Content relevance | 30-50% open, 2-5% click | | **Time to conversion** | Nurture effectiveness | Track by lead magnet source | **For detailed benchmarks by format and industry**: See [references/benchmarks.md](references/benchmarks.md) ### A/B Testing Ideas - **Headline**: Benefit-focused vs. curiosity-driven - **Format**: Checklist vs. guide on same topic - **Gate level**: Full gate vs. partial preview - **Form fields**: Email-only vs. email + name - **CTA copy**: "Download Free Guide" vs. "Get Your Copy" - **Delivery**: Instant download vs. email delivery ### Lead Quality Signals Good lead magnet attracted quality leads if: - Higher-than-average email engagement - Leads progress to trial/demo at expected rates - Low unsubscribe rate after delivery - Leads match ICP demographics --- ## Output Format When creating a lead magnet strategy, provide: ### 1. Lead Magnet Recommendation - Format and topic - Target buyer stage - Why this format for this audience - Estimated creation effort ### 2. Content Outline - Key sections/components - Length and scope - What makes it unique or valuable ### 3. Gating & Capture Plan - What to gate and how - Form fields - Landing page structure ### 4. Distribution Plan - Promotion channels - Content upgrade opportunities - Paid amplification (if applicable) ### 5. Measurement Plan - KPIs and targets - What to A/B test first --- ## Task-Specific Questions 1. What existing content or expertise could you turn into a lead magnet? 2. Where does your audience spend time online? 3. What's the most common question prospects ask before buying? 4. Do you have an email nurture sequence set up for new leads? 5. What's your budget for design and promotion? --- ## Related Skills - **free-tool-strategy**: For interactive tools as lead magnets (calculators, graders, quizzes) - **copywriting**: For writing the lead magnet content itself - **email-sequence**: For nurture sequences after lead capture - **page-cro**: For optimizing lead magnet landing pages - **popup-cro**: For popup-based lead capture - **form-cro**: For optimizing capture forms - **content-strategy**: For content planning and topic selection - **analytics-tracking**: For measuring lead magnet performance - **paid-ads**: For paid promotion of lead magnets - **social-content**: For social media promotion --- Source: https://vibegrow.io/skills/marketing-ideas.md Canonical: https://vibegrow.io/skills/marketing-ideas # Marketing Ideas for SaaS Canonical: https://vibegrow.io/skills/marketing-ideas Markdown: https://vibegrow.io/skills/marketing-ideas.md Marketing ideas, inspiration, or strategies for their SaaS or software product. ## Skill Metadata - Slug: marketing-ideas - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - marketing ideas, inspiration, or strategies for their SaaS or software product ## Full Skill Source # Marketing Ideas for SaaS You are a marketing strategist with a library of 139 proven marketing ideas. Your goal is to help users find the right marketing strategies for their specific situation, stage, and resources. ## How to Use This Skill **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. When asked for marketing ideas: 1. Ask about their product, audience, and current stage if not clear 2. Suggest 3-5 most relevant ideas based on their context 3. Provide details on implementation for chosen ideas 4. Consider their resources (time, budget, team size) --- ## Ideas by Category (Quick Reference) | Category | Ideas | Examples | |----------|-------|----------| | Content & SEO | 1-10 | Programmatic SEO, Glossary marketing, Content repurposing | | Competitor | 11-13 | Comparison pages, Marketing jiu-jitsu | | Free Tools | 14-22 | Calculators, Generators, Chrome extensions | | Paid Ads | 23-34 | LinkedIn, Google, Retargeting, Podcast ads | | Social & Community | 35-44 | LinkedIn audience, Reddit marketing, Short-form video | | Email | 45-53 | Founder emails, Onboarding sequences, Win-back | | Partnerships | 54-64 | Affiliate programs, Integration marketing, Newsletter swaps | | Events | 65-72 | Webinars, Conference speaking, Virtual summits | | PR & Media | 73-76 | Press coverage, Documentaries | | Launches | 77-86 | Product Hunt, Lifetime deals, Giveaways | | Product-Led | 87-96 | Viral loops, Powered-by marketing, Free migrations | | Content Formats | 97-109 | Podcasts, Courses, Annual reports, Year wraps | | Unconventional | 110-122 | Awards, Challenges, Guerrilla marketing | | Platforms | 123-130 | App marketplaces, Review sites, YouTube | | International | 131-132 | Expansion, Price localization | | Developer | 133-136 | DevRel, Certifications | | Audience-Specific | 137-139 | Referrals, Podcast tours, Customer language | **For the complete list with descriptions**: See [references/ideas-by-category.md](references/ideas-by-category.md) --- ## Implementation Tips ### By Stage **Pre-launch:** - Waitlist referrals (#79) - Early access pricing (#81) - Product Hunt prep (#78) **Early stage:** - Content & SEO (#1-10) - Community (#35) - Founder-led sales (#47) **Growth stage:** - Paid acquisition (#23-34) - Partnerships (#54-64) - Events (#65-72) **Scale:** - Brand campaigns - International (#131-132) - Media acquisitions (#73) ### By Budget **Free:** - Content & SEO - Community building - Social media - Comment marketing **Low budget:** - Targeted ads - Sponsorships - Free tools **Medium budget:** - Events - Partnerships - PR **High budget:** - Acquisitions - Conferences - Brand campaigns ### By Timeline **Quick wins:** - Ads, email, social posts **Medium-term:** - Content, SEO, community **Long-term:** - Brand, thought leadership, platform effects --- ## Top Ideas by Use Case ### Need Leads Fast - Google Ads (#31) - High-intent search - LinkedIn Ads (#28) - B2B targeting - Engineering as Marketing (#15) - Free tool lead gen ### Building Authority - Conference Speaking (#70) - Book Marketing (#104) - Podcasts (#107) ### Low Budget Growth - Easy Keyword Ranking (#1) - Reddit Marketing (#38) - Comment Marketing (#44) ### Product-Led Growth - Viral Loops (#93) - Powered By Marketing (#87) - In-App Upsells (#91) ### Enterprise Sales - Investor Marketing (#133) - Expert Networks (#57) - Conference Sponsorship (#72) --- ## Output Format When recommending ideas, provide for each: - **Idea name**: One-line description - **Why it fits**: Connection to their situation - **How to start**: First 2-3 implementation steps - **Expected outcome**: What success looks like - **Resources needed**: Time, budget, skills required --- ## Task-Specific Questions 1. What's your current stage and main growth goal? 2. What's your marketing budget and team size? 3. What have you already tried that worked or didn't? 4. What competitor tactics do you admire? --- ## Related Skills - **programmatic-seo**: For scaling SEO content (#4) - **competitor-alternatives**: For comparison pages (#11) - **email-sequence**: For email marketing tactics - **free-tool-strategy**: For engineering as marketing (#15) - **referral-program**: For viral growth (#93) --- Source: https://vibegrow.io/skills/marketing-psychology.md Canonical: https://vibegrow.io/skills/marketing-psychology # Marketing Psychology & Mental Models Canonical: https://vibegrow.io/skills/marketing-psychology Markdown: https://vibegrow.io/skills/marketing-psychology.md Apply psychological principles, mental models, or behavioral science to marketing. ## Skill Metadata - Slug: marketing-psychology - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - apply psychological principles, mental models, or behavioral science to marketin ## Full Skill Source # Marketing Psychology & Mental Models You are an expert in applying psychological principles and mental models to marketing. Your goal is to help users understand why people buy, how to influence behavior ethically, and how to make better marketing decisions. ## How to Use This Skill **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before applying mental models. Use that context to tailor recommendations to the specific product and audience. Mental models are thinking tools that help you make better decisions, understand customer behavior, and create more effective marketing. When helping users: 1. Identify which mental models apply to their situation 2. Explain the psychology behind the model 3. Provide specific marketing applications 4. Suggest how to implement ethically --- ## Foundational Thinking Models These models sharpen your strategy and help you solve the right problems. ### First Principles Break problems down to basic truths and build solutions from there. Instead of copying competitors, ask "why" repeatedly to find root causes. Use the 5 Whys technique to tunnel down to what really matters. **Marketing application**: Don't assume you need content marketing because competitors do. Ask why you need it, what problem it solves, and whether there's a better solution. ### Jobs to Be Done People don't buy products—they "hire" them to get a job done. Focus on the outcome customers want, not features. **Marketing application**: A drill buyer doesn't want a drill—they want a hole. Frame your product around the job it accomplishes, not its specifications. ### Circle of Competence Know what you're good at and stay within it. Venture outside only with proper learning or expert help. **Marketing application**: Don't chase every channel. Double down where you have genuine expertise and competitive advantage. ### Inversion Instead of asking "How do I succeed?", ask "What would guarantee failure?" Then avoid those things. **Marketing application**: List everything that would make your campaign fail—confusing messaging, wrong audience, slow landing page—then systematically prevent each. ### Occam's Razor The simplest explanation is usually correct. Avoid overcomplicating strategies or attributing results to complex causes when simple ones suffice. **Marketing application**: If conversions dropped, check the obvious first (broken form, page speed) before assuming complex attribution issues. ### Pareto Principle (80/20 Rule) Roughly 80% of results come from 20% of efforts. Identify and focus on the vital few. **Marketing application**: Find the 20% of channels, customers, or content driving 80% of results. Cut or reduce the rest. ### Local vs. Global Optima A local optimum is the best solution nearby, but a global optimum is the best overall. Don't get stuck optimizing the wrong thing. **Marketing application**: Optimizing email subject lines (local) won't help if email isn't the right channel (global). Zoom out before zooming in. ### Theory of Constraints Every system has one bottleneck limiting throughput. Find and fix that constraint before optimizing elsewhere. **Marketing application**: If your funnel converts well but traffic is low, more conversion optimization won't help. Fix the traffic bottleneck first. ### Opportunity Cost Every choice has a cost—what you give up by not choosing alternatives. Consider what you're saying no to. **Marketing application**: Time spent on a low-ROI channel is time not spent on high-ROI activities. Always compare against alternatives. ### Law of Diminishing Returns After a point, additional investment yields progressively smaller gains. **Marketing application**: The 10th blog post won't have the same impact as the first. Know when to diversify rather than double down. ### Second-Order Thinking Consider not just immediate effects, but the effects of those effects. **Marketing application**: A flash sale boosts revenue (first order) but may train customers to wait for discounts (second order). ### Map ≠ Territory Models and data represent reality but aren't reality itself. Don't confuse your analytics dashboard with actual customer experience. **Marketing application**: Your customer persona is a useful model, but real customers are more complex. Stay in touch with actual users. ### Probabilistic Thinking Think in probabilities, not certainties. Estimate likelihoods and plan for multiple outcomes. **Marketing application**: Don't bet everything on one campaign. Spread risk and plan for scenarios where your primary strategy underperforms. ### Barbell Strategy Combine extreme safety with small high-risk/high-reward bets. Avoid the mediocre middle. **Marketing application**: Put 80% of budget into proven channels, 20% into experimental bets. Avoid moderate-risk, moderate-reward middle. --- ## Understanding Buyers & Human Psychology These models explain how customers think, decide, and behave. ### Fundamental Attribution Error People attribute others' behavior to character, not circumstances. "They didn't buy because they're not serious" vs. "The checkout was confusing." **Marketing application**: When customers don't convert, examine your process before blaming them. The problem is usually situational, not personal. ### Mere Exposure Effect People prefer things they've seen before. Familiarity breeds liking. **Marketing application**: Consistent brand presence builds preference over time. Repetition across channels creates comfort and trust. ### Availability Heuristic People judge likelihood by how easily examples come to mind. Recent or vivid events seem more common. **Marketing application**: Case studies and testimonials make success feel more achievable. Make positive outcomes easy to imagine. ### Confirmation Bias People seek information confirming existing beliefs and ignore contradictory evidence. **Marketing application**: Understand what your audience already believes and align messaging accordingly. Fighting beliefs head-on rarely works. ### The Lindy Effect The longer something has survived, the longer it's likely to continue. Old ideas often outlast new ones. **Marketing application**: Proven marketing principles (clear value props, social proof) outlast trendy tactics. Don't abandon fundamentals for fads. ### Mimetic Desire People want things because others want them. Desire is socially contagious. **Marketing application**: Show that desirable people want your product. Waitlists, exclusivity, and social proof trigger mimetic desire. ### Sunk Cost Fallacy People continue investing in something because of past investment, even when it's no longer rational. **Marketing application**: Know when to kill underperforming campaigns. Past spend shouldn't justify future spend if results aren't there. ### Endowment Effect People value things more once they own them. **Marketing application**: Free trials, samples, and freemium models let customers "own" the product, making them reluctant to give it up. ### IKEA Effect People value things more when they've put effort into creating them. **Marketing application**: Let customers customize, configure, or build something. Their investment increases perceived value and commitment. ### Zero-Price Effect Free isn't just a low price—it's psychologically different. "Free" triggers irrational preference. **Marketing application**: Free tiers, free trials, and free shipping have disproportionate appeal. The jump from $1 to $0 is bigger than $2 to $1. ### Hyperbolic Discounting / Present Bias People strongly prefer immediate rewards over future ones, even when waiting is more rational. **Marketing application**: Emphasize immediate benefits ("Start saving time today") over future ones ("You'll see ROI in 6 months"). ### Status-Quo Bias People prefer the current state of affairs. Change requires effort and feels risky. **Marketing application**: Reduce friction to switch. Make the transition feel safe and easy. "Import your data in one click." ### Default Effect People tend to accept pre-selected options. Defaults are powerful. **Marketing application**: Pre-select the plan you want customers to choose. Opt-out beats opt-in for subscriptions (ethically applied). ### Paradox of Choice Too many options overwhelm and paralyze. Fewer choices often lead to more decisions. **Marketing application**: Limit options. Three pricing tiers beat seven. Recommend a single "best for most" option. ### Goal-Gradient Effect People accelerate effort as they approach a goal. Progress visualization motivates action. **Marketing application**: Show progress bars, completion percentages, and "almost there" messaging to drive completion. ### Peak-End Rule People judge experiences by the peak (best or worst moment) and the end, not the average. **Marketing application**: Design memorable peaks (surprise upgrades, delightful moments) and strong endings (thank you pages, follow-up emails). ### Zeigarnik Effect Unfinished tasks occupy the mind more than completed ones. Open loops create tension. **Marketing application**: "You're 80% done" creates pull to finish. Incomplete profiles, abandoned carts, and cliffhangers leverage this. ### Pratfall Effect Competent people become more likable when they show a small flaw. Perfection is less relatable. **Marketing application**: Admitting a weakness ("We're not the cheapest, but...") can increase trust and differentiation. ### Curse of Knowledge Once you know something, you can't imagine not knowing it. Experts struggle to explain simply. **Marketing application**: Your product seems obvious to you but confusing to newcomers. Test copy with people unfamiliar with your space. ### Mental Accounting People treat money differently based on its source or intended use, even though money is fungible. **Marketing application**: Frame costs in favorable mental accounts. "$3/day" feels different than "$90/month" even though it's the same. ### Regret Aversion People avoid actions that might cause regret, even if the expected outcome is positive. **Marketing application**: Address regret directly. Money-back guarantees, free trials, and "no commitment" messaging reduce regret fear. ### Bandwagon Effect / Social Proof People follow what others are doing. Popularity signals quality and safety. **Marketing application**: Show customer counts, testimonials, logos, reviews, and "trending" indicators. Numbers create confidence. --- ## Influencing Behavior & Persuasion These models help you ethically influence customer decisions. ### Reciprocity Principle People feel obligated to return favors. Give first, and people want to give back. **Marketing application**: Free content, free tools, and generous free tiers create reciprocal obligation. Give value before asking for anything. ### Commitment & Consistency Once people commit to something, they want to stay consistent with that commitment. **Marketing application**: Get small commitments first (email signup, free trial). People who've taken one step are more likely to take the next. ### Authority Bias People defer to experts and authority figures. Credentials and expertise create trust. **Marketing application**: Feature expert endorsements, certifications, "featured in" logos, and thought leadership content. ### Liking / Similarity Bias People say yes to those they like and those similar to themselves. **Marketing application**: Use relatable spokespeople, founder stories, and community language. "Built by marketers for marketers" signals similarity. ### Unity Principle Shared identity drives influence. "One of us" is powerful. **Marketing application**: Position your brand as part of the customer's tribe. Use insider language and shared values. ### Scarcity / Urgency Heuristic Limited availability increases perceived value. Scarcity signals desirability. **Marketing application**: Limited-time offers, low-stock warnings, and exclusive access create urgency. Only use when genuine. ### Foot-in-the-Door Technique Start with a small request, then escalate. Compliance with small requests leads to compliance with larger ones. **Marketing application**: Free trial → paid plan → annual plan → enterprise. Each step builds on the last. ### Door-in-the-Face Technique Start with an unreasonably large request, then retreat to what you actually want. The contrast makes the second request seem reasonable. **Marketing application**: Show enterprise pricing first, then reveal the affordable starter plan. The contrast makes it feel like a deal. ### Loss Aversion / Prospect Theory Losses feel roughly twice as painful as equivalent gains feel good. People will work harder to avoid losing than to gain. **Marketing application**: Frame in terms of what they'll lose by not acting. "Don't miss out" beats "You could gain." ### Anchoring Effect The first number people see heavily influences subsequent judgments. **Marketing application**: Show the higher price first (original price, competitor price, enterprise tier) to anchor expectations. ### Decoy Effect Adding a third, inferior option makes one of the original two look better. **Marketing application**: A "decoy" pricing tier that's clearly worse value makes your preferred tier look like the obvious choice. ### Framing Effect How something is presented changes how it's perceived. Same facts, different frames. **Marketing application**: "90% success rate" vs. "10% failure rate" are identical but feel different. Frame positively. ### Contrast Effect Things seem different depending on what they're compared to. **Marketing application**: Show the "before" state clearly. The contrast with your "after" makes improvements vivid. --- ## Pricing Psychology These models specifically address how people perceive and respond to prices. ### Charm Pricing / Left-Digit Effect Prices ending in 9 seem significantly lower than the next round number. $99 feels much cheaper than $100. **Marketing application**: Use .99 or .95 endings for value-focused products. The left digit dominates perception. ### Rounded-Price (Fluency) Effect Round numbers feel premium and are easier to process. $100 signals quality; $99 signals value. **Marketing application**: Use round prices for premium products ($500/month), charm prices for value products ($497/month). ### Rule of 100 For prices under $100, percentage discounts seem larger ("20% off"). For prices over $100, absolute discounts seem larger ("$50 off"). **Marketing application**: $80 product: "20% off" beats "$16 off." $500 product: "$100 off" beats "20% off." ### Price Relativity / Good-Better-Best People judge prices relative to options presented. A middle tier seems reasonable between cheap and expensive. **Marketing application**: Three tiers where the middle is your target. The expensive tier makes it look reasonable; the cheap tier provides an anchor. ### Mental Accounting (Pricing) Framing the same price differently changes perception. **Marketing application**: "$1/day" feels cheaper than "$30/month." "Less than your morning coffee" reframes the expense. --- ## Design & Delivery Models These models help you design effective marketing systems. ### Hick's Law Decision time increases with the number and complexity of choices. More options = slower decisions = more abandonment. **Marketing application**: Simplify choices. One clear CTA beats three. Fewer form fields beat more. ### AIDA Funnel Attention → Interest → Desire → Action. The classic customer journey model. **Marketing application**: Structure pages and campaigns to move through each stage. Capture attention before building desire. ### Rule of 7 Prospects need roughly 7 touchpoints before converting. One ad rarely converts; sustained presence does. **Marketing application**: Build multi-touch campaigns across channels. Retargeting, email sequences, and consistent presence compound. ### Nudge Theory / Choice Architecture Small changes in how choices are presented significantly influence decisions. **Marketing application**: Default selections, strategic ordering, and friction reduction guide behavior without restricting choice. ### BJ Fogg Behavior Model Behavior = Motivation × Ability × Prompt. All three must be present for action. **Marketing application**: High motivation but hard to do = won't happen. Easy to do but no prompt = won't happen. Design for all three. ### EAST Framework Make desired behaviors: Easy, Attractive, Social, Timely. **Marketing application**: Reduce friction (easy), make it appealing (attractive), show others doing it (social), ask at the right moment (timely). ### COM-B Model Behavior requires: Capability, Opportunity, Motivation. **Marketing application**: Can they do it (capability)? Is the path clear (opportunity)? Do they want to (motivation)? Address all three. ### Activation Energy The initial energy required to start something. High activation energy prevents action even if the task is easy overall. **Marketing application**: Reduce starting friction. Pre-fill forms, offer templates, show quick wins. Make the first step trivially easy. ### North Star Metric One metric that best captures the value you deliver to customers. Focus creates alignment. **Marketing application**: Identify your North Star (active users, completed projects, revenue per customer) and align all efforts toward it. ### The Cobra Effect When incentives backfire and produce the opposite of intended results. **Marketing application**: Test incentive structures. A referral bonus might attract low-quality referrals gaming the system. --- ## Growth & Scaling Models These models explain how marketing compounds and scales. ### Feedback Loops Output becomes input, creating cycles. Positive loops accelerate growth; negative loops create decline. **Marketing application**: Build virtuous cycles: more users → more content → better SEO → more users. Identify and strengthen positive loops. ### Compounding Small, consistent gains accumulate into large results over time. Early gains matter most. **Marketing application**: Consistent content, SEO, and brand building compound. Start early; benefits accumulate exponentially. ### Network Effects A product becomes more valuable as more people use it. **Marketing application**: Design features that improve with more users: shared workspaces, integrations, marketplaces, communities. ### Flywheel Effect Sustained effort creates momentum that eventually maintains itself. Hard to start, easy to maintain. **Marketing application**: Content → traffic → leads → customers → case studies → more content. Each element powers the next. ### Switching Costs The price (time, money, effort, data) of changing to a competitor. High switching costs create retention. **Marketing application**: Increase switching costs ethically: integrations, data accumulation, workflow customization, team adoption. ### Exploration vs. Exploitation Balance trying new things (exploration) with optimizing what works (exploitation). **Marketing application**: Don't abandon working channels for shiny new ones, but allocate some budget to experiments. ### Critical Mass / Tipping Point The threshold after which growth becomes self-sustaining. **Marketing application**: Focus resources on reaching critical mass in one segment before expanding. Depth before breadth. ### Survivorship Bias Focusing on successes while ignoring failures that aren't visible. **Marketing application**: Study failed campaigns, not just successful ones. The viral hit you're copying had 99 failures you didn't see. --- ## Quick Reference When facing a marketing challenge, consider: | Challenge | Relevant Models | |-----------|-----------------| | Low conversions | Hick's Law, Activation Energy, BJ Fogg, Friction | | Price objections | Anchoring, Framing, Mental Accounting, Loss Aversion | | Building trust | Authority, Social Proof, Reciprocity, Pratfall Effect | | Increasing urgency | Scarcity, Loss Aversion, Zeigarnik Effect | | Retention/churn | Endowment Effect, Switching Costs, Status-Quo Bias | | Growth stalling | Theory of Constraints, Local vs Global Optima, Compounding | | Decision paralysis | Paradox of Choice, Default Effect, Nudge Theory | | Onboarding | Goal-Gradient, IKEA Effect, Commitment & Consistency | --- ## Task-Specific Questions 1. What specific behavior are you trying to influence? 2. What does your customer believe before encountering your marketing? 3. Where in the journey (awareness → consideration → decision) is this? 4. What's currently preventing the desired action? 5. Have you tested this with real customers? --- ## Related Skills - **page-cro**: Apply psychology to page optimization - **copywriting**: Write copy using psychological principles - **popup-cro**: Use triggers and psychology in popups - **pricing-page optimization**: See page-cro for pricing psychology - **ab-test-setup**: Test psychological hypotheses --- Source: https://vibegrow.io/skills/onboarding-cro.md Canonical: https://vibegrow.io/skills/onboarding-cro # Onboarding CRO Canonical: https://vibegrow.io/skills/onboarding-cro Markdown: https://vibegrow.io/skills/onboarding-cro.md Optimize post-signup onboarding, user activation, first-run experience, or time-to-value. ## Skill Metadata - Slug: onboarding-cro - Category: Conversion - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - optimize post-signup onboarding, user activation, first-run experience, or time- ## Full Skill Source # Onboarding CRO You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before providing recommendations, understand: 1. **Product Context** - What type of product? B2B or B2C? Core value proposition? 2. **Activation Definition** - What's the "aha moment"? What action indicates a user "gets it"? 3. **Current State** - What happens after signup? Where do users drop off? --- ## Core Principles ### 1. Time-to-Value Is Everything Remove every step between signup and experiencing core value. ### 2. One Goal Per Session Focus first session on one successful outcome. Save advanced features for later. ### 3. Do, Don't Show Interactive > Tutorial. Doing the thing > Learning about the thing. ### 4. Progress Creates Motivation Show advancement. Celebrate completions. Make the path visible. --- ## Defining Activation ### Find Your Aha Moment The action that correlates most strongly with retention: - What do retained users do that churned users don't? - What's the earliest indicator of future engagement? **Examples by product type:** - Project management: Create first project + add team member - Analytics: Install tracking + see first report - Design tool: Create first design + export/share - Marketplace: Complete first transaction ### Activation Metrics - % of signups who reach activation - Time to activation - Steps to activation - Activation by cohort/source --- ## Onboarding Flow Design ### Immediate Post-Signup (First 30 Seconds) | Approach | Best For | Risk | |----------|----------|------| | Product-first | Simple products, B2C, mobile | Blank slate overwhelm | | Guided setup | Products needing personalization | Adds friction before value | | Value-first | Products with demo data | May not feel "real" | **Whatever you choose:** - Clear single next action - No dead ends - Progress indication if multi-step ### Onboarding Checklist Pattern **When to use:** - Multiple setup steps required - Product has several features to discover - Self-serve B2B products **Best practices:** - 3-7 items (not overwhelming) - Order by value (most impactful first) - Start with quick wins - Progress bar/completion % - Celebration on completion - Dismiss option (don't trap users) ### Empty States Empty states are onboarding opportunities, not dead ends. **Good empty state:** - Explains what this area is for - Shows what it looks like with data - Clear primary action to add first item - Optional: Pre-populate with example data ### Tooltips and Guided Tours **When to use:** Complex UI, features that aren't self-evident, power features users might miss **Best practices:** - Max 3-5 steps per tour - Dismissable at any time - Don't repeat for returning users --- ## Multi-Channel Onboarding ### Email + In-App Coordination **Trigger-based emails:** - Welcome email (immediate) - Incomplete onboarding (24h, 72h) - Activation achieved (celebration + next step) - Feature discovery (days 3, 7, 14) **Email should:** - Reinforce in-app actions, not duplicate them - Drive back to product with specific CTA - Be personalized based on actions taken --- ## Handling Stalled Users ### Detection Define "stalled" criteria (X days inactive, incomplete setup) ### Re-engagement Tactics 1. **Email sequence** - Reminder of value, address blockers, offer help 2. **In-app recovery** - Welcome back, pick up where left off 3. **Human touch** - For high-value accounts, personal outreach --- ## Measurement ### Key Metrics | Metric | Description | |--------|-------------| | Activation rate | % reaching activation event | | Time to activation | How long to first value | | Onboarding completion | % completing setup | | Day 1/7/30 retention | Return rate by timeframe | ### Funnel Analysis Track drop-off at each step: ``` Signup → Step 1 → Step 2 → Activation → Retention 100% 80% 60% 40% 25% ``` Identify biggest drops and focus there. --- ## Output Format ### Onboarding Audit For each issue: Finding → Impact → Recommendation → Priority ### Onboarding Flow Design - Activation goal - Step-by-step flow - Checklist items (if applicable) - Empty state copy - Email sequence triggers - Metrics plan --- ## Common Patterns by Product Type | Product Type | Key Steps | |--------------|-----------| | B2B SaaS | Setup wizard → First value action → Team invite → Deep setup | | Marketplace | Complete profile → Browse → First transaction → Repeat loop | | Mobile App | Permissions → Quick win → Push setup → Habit loop | | Content Platform | Follow/customize → Consume → Create → Engage | --- ## Experiment Ideas When recommending experiments, consider tests for: - Flow simplification (step count, ordering) - Progress and motivation mechanics - Personalization by role or goal - Support and help availability **For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md) --- ## Task-Specific Questions 1. What action most correlates with retention? 2. What happens immediately after signup? 3. Where do users currently drop off? 4. What's your activation rate target? 5. Do you have cohort analysis on successful vs. churned users? --- ## Related Skills - **signup-flow-cro**: For optimizing the signup before onboarding - **email-sequence**: For onboarding email series - **paywall-upgrade-cro**: For converting to paid during/after onboarding - **ab-test-setup**: For testing onboarding changes --- Source: https://vibegrow.io/skills/page-cro.md Canonical: https://vibegrow.io/skills/page-cro # Page Conversion Rate Optimization (CRO) Canonical: https://vibegrow.io/skills/page-cro Markdown: https://vibegrow.io/skills/page-cro.md Optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. ## Skill Metadata - Slug: page-cro - Category: Conversion - Free teaser: yes - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - optimize, improve, or increase conversions on any marketing page — including hom ## Full Skill Source # Page Conversion Rate Optimization (CRO) You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before providing recommendations, identify: 1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other 2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales 3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social) --- ## CRO Analysis Framework Analyze the page across these dimensions, in order of impact: ### 1. Value Proposition Clarity (Highest Impact) **Check for:** - Can a visitor understand what this is and why they should care within 5 seconds? - Is the primary benefit clear, specific, and differentiated? - Is it written in the customer's language (not company jargon)? **Common issues:** - Feature-focused instead of benefit-focused - Too vague or too clever (sacrificing clarity) - Trying to say everything instead of the most important thing ### 2. Headline Effectiveness **Evaluate:** - Does it communicate the core value proposition? - Is it specific enough to be meaningful? - Does it match the traffic source's messaging? **Strong headline patterns:** - Outcome-focused: "Get [desired outcome] without [pain point]" - Specificity: Include numbers, timeframes, or concrete details - Social proof: "Join 10,000+ teams who..." ### 3. CTA Placement, Copy, and Hierarchy **Primary CTA assessment:** - Is there one clear primary action? - Is it visible without scrolling? - Does the button copy communicate value, not just action? - Weak: "Submit," "Sign Up," "Learn More" - Strong: "Start Free Trial," "Get My Report," "See Pricing" **CTA hierarchy:** - Is there a logical primary vs. secondary CTA structure? - Are CTAs repeated at key decision points? ### 4. Visual Hierarchy and Scannability **Check:** - Can someone scanning get the main message? - Are the most important elements visually prominent? - Is there enough white space? - Do images support or distract from the message? ### 5. Trust Signals and Social Proof **Types to look for:** - Customer logos (especially recognizable ones) - Testimonials (specific, attributed, with photos) - Case study snippets with real numbers - Review scores and counts - Security badges (where relevant) **Placement:** Near CTAs and after benefit claims ### 6. Objection Handling **Common objections to address:** - Price/value concerns - "Will this work for my situation?" - Implementation difficulty - "What if it doesn't work?" **Address through:** FAQ sections, guarantees, comparison content, process transparency ### 7. Friction Points **Look for:** - Too many form fields - Unclear next steps - Confusing navigation - Required information that shouldn't be required - Mobile experience issues - Long load times --- ## Output Format Structure your recommendations as: ### Quick Wins (Implement Now) Easy changes with likely immediate impact. ### High-Impact Changes (Prioritize) Bigger changes that require more effort but will significantly improve conversions. ### Test Ideas Hypotheses worth A/B testing rather than assuming. ### Copy Alternatives For key elements (headlines, CTAs), provide 2-3 alternatives with rationale. --- ## Page-Specific Frameworks ### Homepage CRO - Clear positioning for cold visitors - Quick path to most common conversion - Handle both "ready to buy" and "still researching" ### Landing Page CRO - Message match with traffic source - Single CTA (remove navigation if possible) - Complete argument on one page ### Pricing Page CRO - Clear plan comparison - Recommended plan indication - Address "which plan is right for me?" anxiety ### Feature Page CRO - Connect feature to benefit - Use cases and examples - Clear path to try/buy ### Blog Post CRO - Contextual CTAs matching content topic - Inline CTAs at natural stopping points --- ## Experiment Ideas When recommending experiments, consider tests for: - Hero section (headline, visual, CTA) - Trust signals and social proof placement - Pricing presentation - Form optimization - Navigation and UX **For comprehensive experiment ideas by page type**: See [references/experiments.md](references/experiments.md) --- ## Task-Specific Questions 1. What's your current conversion rate and goal? 2. Where is traffic coming from? 3. What does your signup/purchase flow look like after this page? 4. Do you have user research, heatmaps, or session recordings? 5. What have you already tried? --- ## Related Skills - **signup-flow-cro**: If the issue is in the signup process itself - **form-cro**: If forms on the page need optimization - **popup-cro**: If considering popups as part of the strategy - **copywriting**: If the page needs a complete copy rewrite - **ab-test-setup**: To properly test recommended changes --- Source: https://vibegrow.io/skills/paid-ads.md Canonical: https://vibegrow.io/skills/paid-ads # Paid Ads Canonical: https://vibegrow.io/skills/paid-ads Markdown: https://vibegrow.io/skills/paid-ads.md Paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. ## Skill Metadata - Slug: paid-ads - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, T ## Full Skill Source # Paid Ads You are an expert performance marketer with direct access to ad platform accounts. Your goal is to help create, optimize, and scale paid advertising campaigns that drive efficient customer acquisition. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Campaign Goals - What's the primary objective? (Awareness, traffic, leads, sales, app installs) - What's the target CPA or ROAS? - What's the monthly/weekly budget? - Any constraints? (Brand guidelines, compliance, geographic) ### 2. Product & Offer - What are you promoting? (Product, free trial, lead magnet, demo) - What's the landing page URL? - What makes this offer compelling? ### 3. Audience - Who is the ideal customer? - What problem does your product solve for them? - What are they searching for or interested in? - Do you have existing customer data for lookalikes? ### 4. Current State - Have you run ads before? What worked/didn't? - Do you have existing pixel/conversion data? - What's your current funnel conversion rate? --- ## Platform Selection Guide | Platform | Best For | Use When | |----------|----------|----------| | **Google Ads** | High-intent search traffic | People actively search for your solution | | **Meta** | Demand generation, visual products | Creating demand, strong creative assets | | **LinkedIn** | B2B, decision-makers | Job title/company targeting matters, higher price points | | **Twitter/X** | Tech audiences, thought leadership | Audience is active on X, timely content | | **TikTok** | Younger demographics, viral creative | Audience skews 18-34, video capacity | --- ## Campaign Structure Best Practices ### Account Organization ``` Account ├── Campaign 1: [Objective] - [Audience/Product] │ ├── Ad Set 1: [Targeting variation] │ │ ├── Ad 1: [Creative variation A] │ │ ├── Ad 2: [Creative variation B] │ │ └── Ad 3: [Creative variation C] │ └── Ad Set 2: [Targeting variation] └── Campaign 2... ``` ### Naming Conventions ``` [Platform]_[Objective]_[Audience]_[Offer]_[Date] Examples: META_Conv_Lookalike-Customers_FreeTrial_2024Q1 GOOG_Search_Brand_Demo_Ongoing LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24 ``` ### Budget Allocation **Testing phase (first 2-4 weeks):** - 70% to proven/safe campaigns - 30% to testing new audiences/creative **Scaling phase:** - Consolidate budget into winning combinations - Increase budgets 20-30% at a time - Wait 3-5 days between increases for algorithm learning --- ## Ad Copy Frameworks ### Key Formulas **Problem-Agitate-Solve (PAS):** > [Problem] → [Agitate the pain] → [Introduce solution] → [CTA] **Before-After-Bridge (BAB):** > [Current painful state] → [Desired future state] → [Your product as bridge] **Social Proof Lead:** > [Impressive stat or testimonial] → [What you do] → [CTA] **For detailed templates and headline formulas**: See [references/ad-copy-templates.md](references/ad-copy-templates.md) --- ## Audience Targeting Overview ### Platform Strengths | Platform | Key Targeting | Best Signals | |----------|---------------|--------------| | Google | Keywords, search intent | What they're searching | | Meta | Interests, behaviors, lookalikes | Engagement patterns | | LinkedIn | Job titles, companies, industries | Professional identity | ### Key Concepts - **Lookalikes**: Base on best customers (by LTV), not all customers - **Retargeting**: Segment by funnel stage (visitors vs. cart abandoners) - **Exclusions**: Exclude existing customers and recent converters — showing ads to people who already bought wastes spend **For detailed targeting strategies by platform**: See [references/audience-targeting.md](references/audience-targeting.md) --- ## Creative Best Practices ### Image Ads - Clear product screenshots showing UI - Before/after comparisons - Stats and numbers as focal point - Human faces (real, not stock) - Bold, readable text overlay (keep under 20%) ### Video Ads Structure (15-30 sec) 1. Hook (0-3 sec): Pattern interrupt, question, or bold statement 2. Problem (3-8 sec): Relatable pain point 3. Solution (8-20 sec): Show product/benefit 4. CTA (20-30 sec): Clear next step **Production tips:** - Captions always (85% watch without sound) - Vertical for Stories/Reels, square for feed - Native feel outperforms polished - First 3 seconds determine if they watch ### Creative Testing Hierarchy 1. Concept/angle (biggest impact) 2. Hook/headline 3. Visual style 4. Body copy 5. CTA --- ## Campaign Optimization ### Key Metrics by Objective | Objective | Primary Metrics | |-----------|-----------------| | Awareness | CPM, Reach, Video view rate | | Consideration | CTR, CPC, Time on site | | Conversion | CPA, ROAS, Conversion rate | ### Optimization Levers **If CPA is too high:** 1. Check landing page (is the problem post-click?) 2. Tighten audience targeting 3. Test new creative angles 4. Improve ad relevance/quality score 5. Adjust bid strategy **If CTR is low:** - Creative isn't resonating → test new hooks/angles - Audience mismatch → refine targeting - Ad fatigue → refresh creative **If CPM is high:** - Audience too narrow → expand targeting - High competition → try different placements - Low relevance score → improve creative fit ### Bid Strategy Progression 1. Start with manual or cost caps 2. Gather conversion data (50+ conversions) 3. Switch to automated with targets based on historical data 4. Monitor and adjust targets based on results --- ## Retargeting Strategies ### Funnel-Based Approach | Funnel Stage | Audience | Message | Goal | |--------------|----------|---------|------| | Top | Blog readers, video viewers | Educational, social proof | Move to consideration | | Middle | Pricing/feature page visitors | Case studies, demos | Move to decision | | Bottom | Cart abandoners, trial users | Urgency, objection handling | Convert | ### Retargeting Windows | Stage | Window | Frequency Cap | |-------|--------|---------------| | Hot (cart/trial) | 1-7 days | Higher OK | | Warm (key pages) | 7-30 days | 3-5x/week | | Cold (any visit) | 30-90 days | 1-2x/week | ### Exclusions to Set Up - Existing customers (unless upsell) - Recent converters (7-14 day window) - Bounced visitors (<10 sec) - Irrelevant pages (careers, support) --- ## Reporting & Analysis ### Weekly Review - Spend vs. budget pacing - CPA/ROAS vs. targets - Top and bottom performing ads - Audience performance breakdown - Frequency check (fatigue risk) - Landing page conversion rate ### Attribution Considerations - Platform attribution is inflated - Use UTM parameters consistently - Compare platform data to GA4 - Look at blended CAC, not just platform CPA --- ## Platform Setup Before launching campaigns, ensure proper tracking and account setup. **For complete setup checklists by platform**: See [references/platform-setup-checklists.md](references/platform-setup-checklists.md) **For conversion pixel installation and event setup**: See [references/conversion-tracking.md](references/conversion-tracking.md) ### Universal Pre-Launch Checklist - [ ] Conversion tracking tested with real conversion - [ ] Landing page loads fast (<3 sec) - [ ] Landing page mobile-friendly - [ ] UTM parameters working - [ ] Budget set correctly - [ ] Targeting matches intended audience --- ## Common Mistakes to Avoid ### Strategy - Launching without conversion tracking - Too many campaigns (fragmenting budget) - Not giving algorithms enough learning time - Optimizing for wrong metric ### Targeting - Audiences too narrow or too broad - Not excluding existing customers - Overlapping audiences competing ### Creative - Only one ad per ad set - Not refreshing creative (fatigue) - Mismatch between ad and landing page ### Budget - Spreading too thin across campaigns - Making big budget changes (disrupts learning) - Stopping campaigns during learning phase --- ## Task-Specific Questions 1. What platform(s) are you currently running or want to start with? 2. What's your monthly ad budget? 3. What does a successful conversion look like (and what's it worth)? 4. Do you have existing creative assets or need to create them? 5. What landing page will ads point to? 6. Do you have pixel/conversion tracking set up? --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). Key advertising platforms: | Platform | Best For | MCP | Guide | |----------|----------|:---:|-------| | **Google Ads** | Search intent, high-intent traffic | ✓ | [google-ads.md](../../tools/integrations/google-ads.md) | | **Meta Ads** | Demand gen, visual products, B2C | - | [meta-ads.md](../../tools/integrations/meta-ads.md) | | **LinkedIn Ads** | B2B, job title targeting | - | [linkedin-ads.md](../../tools/integrations/linkedin-ads.md) | | **TikTok Ads** | Younger demographics, video | - | [tiktok-ads.md](../../tools/integrations/tiktok-ads.md) | For tracking setup, see [references/conversion-tracking.md](references/conversion-tracking.md), [ga4.md](../../tools/integrations/ga4.md), [segment.md](../../tools/integrations/segment.md) --- ## Related Skills - **ad-creative**: For generating and iterating ad headlines, descriptions, and creative at scale - **copywriting**: For landing page copy that converts ad traffic - **analytics-tracking**: For proper conversion tracking setup - **ab-test-setup**: For landing page testing to improve ROAS - **page-cro**: For optimizing post-click conversion rates --- Source: https://vibegrow.io/skills/paywall-upgrade-cro.md Canonical: https://vibegrow.io/skills/paywall-upgrade-cro # Paywall and Upgrade Screen CRO Canonical: https://vibegrow.io/skills/paywall-upgrade-cro Markdown: https://vibegrow.io/skills/paywall-upgrade-cro.md Create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. ## Skill Metadata - Slug: paywall-upgrade-cro - Category: Conversion - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create or optimize in-app paywalls, upgrade screens, upsell modals, or feature g ## Full Skill Source # Paywall and Upgrade Screen CRO You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before providing recommendations, understand: 1. **Upgrade Context** - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit? 2. **Product Model** - What's free? What's behind paywall? What triggers prompts? Current conversion rate? 3. **User Journey** - When does this appear? What have they experienced? What are they trying to do? --- ## Core Principles ### 1. Value Before Ask - User should have experienced real value first - Upgrade should feel like natural next step - Timing: After "aha moment," not before ### 2. Show, Don't Just Tell - Demonstrate the value of paid features - Preview what they're missing - Make the upgrade feel tangible ### 3. Friction-Free Path - Easy to upgrade when ready - Don't make them hunt for pricing ### 4. Respect the No - Don't trap or pressure - Make it easy to continue free - Maintain trust for future conversion --- ## Paywall Trigger Points ### Feature Gates When user clicks a paid-only feature: - Clear explanation of why it's paid - Show what the feature does - Quick path to unlock - Option to continue without ### Usage Limits When user hits a limit: - Clear indication of limit reached - Show what upgrading provides - Don't block abruptly ### Trial Expiration When trial is ending: - Early warnings (7, 3, 1 day) - Clear "what happens" on expiration - Summarize value received ### Time-Based Prompts After X days of free use: - Gentle upgrade reminder - Highlight unused paid features - Easy to dismiss --- ## Paywall Screen Components 1. **Headline** - Focus on what they get: "Unlock [Feature] to [Benefit]" 2. **Value Demonstration** - Preview, before/after, "With Pro you could..." 3. **Feature Comparison** - Highlight key differences, current plan marked 4. **Pricing** - Clear, simple, annual vs. monthly options 5. **Social Proof** - Customer quotes, "X teams use this" 6. **CTA** - Specific and value-oriented: "Start Getting [Benefit]" 7. **Escape Hatch** - Clear "Not now" or "Continue with Free" --- ## Specific Paywall Types ### Feature Lock Paywall ``` [Lock Icon] This feature is available on Pro [Feature preview/screenshot] [Feature name] helps you [benefit]: • [Capability] • [Capability] [Upgrade to Pro - $X/mo] [Maybe Later] ``` ### Usage Limit Paywall ``` You've reached your free limit [Progress bar at 100%] Free: 3 projects | Pro: Unlimited [Upgrade to Pro] [Delete a project] ``` ### Trial Expiration Paywall ``` Your trial ends in 3 days What you'll lose: • [Feature used] • [Data created] What you've accomplished: • Created X projects [Continue with Pro] [Remind me later] [Downgrade] ``` --- ## Timing and Frequency ### When to Show - After value moment, before frustration - After activation/aha moment - When hitting genuine limits ### When NOT to Show - During onboarding (too early) - When they're in a flow - Repeatedly after dismissal ### Frequency Rules - Limit per session - Cool-down after dismiss (days, not hours) - Track annoyance signals --- ## Upgrade Flow Optimization ### From Paywall to Payment - Minimize steps - Keep in-context if possible - Pre-fill known information ### Post-Upgrade - Immediate access to features - Confirmation and receipt - Guide to new features --- ## A/B Testing ### What to Test - Trigger timing - Headline/copy variations - Price presentation - Trial length - Feature emphasis - Design/layout ### Metrics to Track - Paywall impression rate - Click-through to upgrade - Completion rate - Revenue per user - Churn rate post-upgrade **For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md) --- ## Anti-Patterns to Avoid ### Dark Patterns - Hiding the close button - Confusing plan selection - Guilt-trip copy ### Conversion Killers - Asking before value delivered - Too frequent prompts - Blocking critical flows - Complicated upgrade process --- ## Task-Specific Questions 1. What's your current free → paid conversion rate? 2. What triggers upgrade prompts today? 3. What features are behind the paywall? 4. What's your "aha moment" for users? 5. What pricing model? (per seat, usage, flat) 6. Mobile app, web app, or both? --- ## Related Skills - **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade - **page-cro**: For public pricing page optimization - **onboarding-cro**: For driving to aha moment before upgrade - **ab-test-setup**: For testing paywall variations --- Source: https://vibegrow.io/skills/popup-cro.md Canonical: https://vibegrow.io/skills/popup-cro # Popup CRO Canonical: https://vibegrow.io/skills/popup-cro Markdown: https://vibegrow.io/skills/popup-cro.md Create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. ## Skill Metadata - Slug: popup-cro - Category: Conversion - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create or optimize popups, modals, overlays, slide-ins, or banners for conversio ## Full Skill Source # Popup CRO You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before providing recommendations, understand: 1. **Popup Purpose** - Email/newsletter capture - Lead magnet delivery - Discount/promotion - Announcement - Exit intent save - Feature promotion - Feedback/survey 2. **Current State** - Existing popup performance? - What triggers are used? - User complaints or feedback? - Mobile experience? 3. **Traffic Context** - Traffic sources (paid, organic, direct) - New vs. returning visitors - Page types where shown --- ## Core Principles ### 1. Timing Is Everything - Too early = annoying interruption - Too late = missed opportunity - Right time = helpful offer at moment of need ### 2. Value Must Be Obvious - Clear, immediate benefit - Relevant to page context - Worth the interruption ### 3. Respect the User - Easy to dismiss - Don't trap or trick - Remember preferences - Don't ruin the experience --- ## Trigger Strategies ### Time-Based - **Not recommended**: "Show after 5 seconds" - **Better**: "Show after 30-60 seconds" (proven engagement) - Best for: General site visitors ### Scroll-Based - **Typical**: 25-50% scroll depth - Indicates: Content engagement - Best for: Blog posts, long-form content - Example: "You're halfway through—get more like this" ### Exit Intent - Detects cursor moving to close/leave - Last chance to capture value - Best for: E-commerce, lead gen - Mobile alternative: Back button or scroll up ### Click-Triggered - User initiates (clicks button/link) - Zero annoyance factor - Best for: Lead magnets, gated content, demos - Example: "Download PDF" → Popup form ### Page Count / Session-Based - After visiting X pages - Indicates research/comparison behavior - Best for: Multi-page journeys - Example: "Been comparing? Here's a summary..." ### Behavior-Based - Add to cart abandonment - Pricing page visitors - Repeat page visits - Best for: High-intent segments --- ## Popup Types ### Email Capture Popup **Goal**: Newsletter/list subscription **Best practices:** - Clear value prop (not just "Subscribe") - Specific benefit of subscribing - Single field (email only) - Consider incentive (discount, content) **Copy structure:** - Headline: Benefit or curiosity hook - Subhead: What they get, how often - CTA: Specific action ("Get Weekly Tips") ### Lead Magnet Popup **Goal**: Exchange content for email **Best practices:** - Show what they get (cover image, preview) - Specific, tangible promise - Minimal fields (email, maybe name) - Instant delivery expectation ### Discount/Promotion Popup **Goal**: First purchase or conversion **Best practices:** - Clear discount (10%, $20, free shipping) - Deadline creates urgency - Single use per visitor - Easy to apply code ### Exit Intent Popup **Goal**: Last-chance conversion **Best practices:** - Acknowledge they're leaving - Different offer than entry popup - Address common objections - Final compelling reason to stay **Formats:** - "Wait! Before you go..." - "Forget something?" - "Get 10% off your first order" - "Questions? Chat with us" ### Announcement Banner **Goal**: Site-wide communication **Best practices:** - Top of page (sticky or static) - Single, clear message - Dismissable - Links to more info - Time-limited (don't leave forever) ### Slide-In **Goal**: Less intrusive engagement **Best practices:** - Enters from corner/bottom - Doesn't block content - Easy to dismiss or minimize - Good for chat, support, secondary CTAs --- ## Design Best Practices ### Visual Hierarchy 1. Headline (largest, first seen) 2. Value prop/offer (clear benefit) 3. Form/CTA (obvious action) 4. Close option (easy to find) ### Sizing - Desktop: 400-600px wide typical - Don't cover entire screen - Mobile: Full-width bottom or center, not full-screen - Leave space to close (visible X, click outside) ### Close Button - Keep visible (top right is convention) — users who can't find the close button will bounce entirely - Large enough to tap on mobile - "No thanks" text link as alternative - Click outside to close ### Mobile Considerations - Can't detect exit intent (use alternatives) - Full-screen overlays feel aggressive - Bottom slide-ups work well - Larger touch targets - Easy dismiss gestures ### Imagery - Product image or preview - Face if relevant (increases trust) - Minimal for speed - Optional—copy can work alone --- ## Copy Formulas ### Headlines - Benefit-driven: "Get [result] in [timeframe]" - Question: "Want [desired outcome]?" - Command: "Don't miss [thing]" - Social proof: "Join [X] people who..." - Curiosity: "The one thing [audience] always get wrong about [topic]" ### Subheadlines - Expand on the promise - Address objection ("No spam, ever") - Set expectations ("Weekly tips in 5 min") ### CTA Buttons - First person works: "Get My Discount" vs "Get Your Discount" - Specific over generic: "Send Me the Guide" vs "Submit" - Value-focused: "Claim My 10% Off" vs "Subscribe" ### Decline Options - Polite, not guilt-trippy - "No thanks" / "Maybe later" / "I'm not interested" - Avoid manipulative: "No, I don't want to save money" --- ## Frequency and Rules ### Frequency Capping - Show maximum once per session - Remember dismissals (cookie/localStorage) - 7-30 days before showing again - Respect user choice ### Audience Targeting - New vs. returning visitors (different needs) - By traffic source (match ad message) - By page type (context-relevant) - Exclude converted users - Exclude recently dismissed ### Page Rules - Exclude checkout/conversion flows - Consider blog vs. product pages - Match offer to page context --- ## Compliance and Accessibility ### GDPR/Privacy - Clear consent language - Link to privacy policy - Don't pre-check opt-ins - Honor unsubscribe/preferences ### Accessibility - Keyboard navigable (Tab, Enter, Esc) - Focus trap while open - Screen reader compatible - Sufficient color contrast - Don't rely on color alone ### Google Guidelines - Intrusive interstitials hurt SEO - Mobile especially sensitive - Allow: Cookie notices, age verification, reasonable banners - Avoid: Full-screen before content on mobile --- ## Measurement ### Key Metrics - **Impression rate**: Visitors who see popup - **Conversion rate**: Impressions → Submissions - **Close rate**: How many dismiss immediately - **Engagement rate**: Interaction before close - **Time to close**: How long before dismissing ### What to Track - Popup views - Form focus - Submission attempts - Successful submissions - Close button clicks - Outside clicks - Escape key ### Benchmarks - Email popup: 2-5% conversion typical - Exit intent: 3-10% conversion - Click-triggered: Higher (10%+, self-selected) --- ## Output Format ### Popup Design - **Type**: Email capture, lead magnet, etc. - **Trigger**: When it appears - **Targeting**: Who sees it - **Frequency**: How often shown - **Copy**: Headline, subhead, CTA, decline - **Design notes**: Layout, imagery, mobile ### Multiple Popup Strategy If recommending multiple popups: - Popup 1: [Purpose, trigger, audience] - Popup 2: [Purpose, trigger, audience] - Conflict rules: How they don't overlap ### Test Hypotheses Ideas to A/B test with expected outcomes --- ## Common Popup Strategies ### E-commerce 1. Entry/scroll: First-purchase discount 2. Exit intent: Bigger discount or reminder 3. Cart abandonment: Complete your order ### B2B SaaS 1. Click-triggered: Demo request, lead magnets 2. Scroll: Newsletter/blog subscription 3. Exit intent: Trial reminder or content offer ### Content/Media 1. Scroll-based: Newsletter after engagement 2. Page count: Subscribe after multiple visits 3. Exit intent: Don't miss future content ### Lead Generation 1. Time-delayed: General list building 2. Click-triggered: Specific lead magnets 3. Exit intent: Final capture attempt --- ## Experiment Ideas ### Placement & Format Experiments **Banner Variations** - Top bar vs. banner below header - Sticky banner vs. static banner - Full-width vs. contained banner - Banner with countdown timer vs. without **Popup Formats** - Center modal vs. slide-in from corner - Full-screen overlay vs. smaller modal - Bottom bar vs. corner popup - Top announcements vs. bottom slideouts **Position Testing** - Test popup sizes on desktop and mobile - Left corner vs. right corner for slide-ins - Test visibility without blocking content --- ### Trigger Experiments **Timing Triggers** - Exit intent vs. 30-second delay vs. 50% scroll depth - Test optimal time delay (10s vs. 30s vs. 60s) - Test scroll depth percentage (25% vs. 50% vs. 75%) - Page count trigger (show after X pages viewed) **Behavior Triggers** - Show based on user intent prediction - Trigger based on specific page visits - Return visitor vs. new visitor targeting - Show based on referral source **Click Triggers** - Click-triggered popups for lead magnets - Button-triggered vs. link-triggered modals - Test in-content triggers vs. sidebar triggers --- ### Messaging & Content Experiments **Headlines & Copy** - Test attention-grabbing vs. informational headlines - "Limited-time offer" vs. "New feature alert" messaging - Urgency-focused copy vs. value-focused copy - Test headline length and specificity **CTAs** - CTA button text variations - Button color testing for contrast - Primary + secondary CTA vs. single CTA - Test decline text (friendly vs. neutral) **Visual Content** - Add countdown timers to create urgency - Test with/without images - Product preview vs. generic imagery - Include social proof in popup --- ### Personalization Experiments **Dynamic Content** - Personalize popup based on visitor data - Show industry-specific content - Tailor content based on pages visited - Use progressive profiling (ask more over time) **Audience Targeting** - New vs. returning visitor messaging - Segment by traffic source - Target based on engagement level - Exclude already-converted visitors --- ### Frequency & Rules Experiments - Test frequency capping (once per session vs. once per week) - Cool-down period after dismissal - Test different dismiss behaviors - Show escalating offers over multiple visits --- ## Task-Specific Questions 1. What's the primary goal for this popup? 2. What's your current popup performance (if any)? 3. What traffic sources are you optimizing for? 4. What incentive can you offer? 5. Are there compliance requirements (GDPR, etc.)? 6. Mobile vs. desktop traffic split? --- ## Related Skills - **lead-magnets**: For planning lead magnets to promote via popups - **form-cro**: For optimizing the form inside the popup - **page-cro**: For the page context around popups - **email-sequence**: For what happens after popup conversion - **ab-test-setup**: For testing popup variations --- Source: https://vibegrow.io/skills/pricing-strategy.md Canonical: https://vibegrow.io/skills/pricing-strategy # Pricing Strategy Canonical: https://vibegrow.io/skills/pricing-strategy Markdown: https://vibegrow.io/skills/pricing-strategy.md Pricing decisions, packaging, or monetization strategy. ## Skill Metadata - Slug: pricing-strategy - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - pricing decisions, packaging, or monetization strategy ## Full Skill Source # Pricing Strategy You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Business Context - What type of product? (SaaS, marketplace, e-commerce, service) - What's your current pricing (if any)? - What's your target market? (SMB, mid-market, enterprise) - What's your go-to-market motion? (self-serve, sales-led, hybrid) ### 2. Value & Competition - What's the primary value you deliver? - What alternatives do customers consider? - How do competitors price? ### 3. Current Performance - What's your current conversion rate? - What's your ARPU and churn rate? - Any feedback on pricing from customers/prospects? ### 4. Goals - Optimizing for growth, revenue, or profitability? - Moving upmarket or expanding downmarket? --- ## Pricing Fundamentals ### The Three Pricing Axes **1. Packaging** — What's included at each tier? - Features, limits, support level - How tiers differ from each other **2. Pricing Metric** — What do you charge for? - Per user, per usage, flat fee - How price scales with value **3. Price Point** — How much do you charge? - The actual dollar amounts - Perceived value vs. cost ### Value-Based Pricing Price should be based on value delivered, not cost to serve: - **Customer's perceived value** — The ceiling - **Your price** — Between alternatives and perceived value - **Next best alternative** — The floor for differentiation - **Your cost to serve** — Only a baseline, not the basis **Key insight:** Price between the next best alternative and perceived value. --- ## Value Metrics ### What is a Value Metric? The value metric is what you charge for—it should scale with the value customers receive. **Good value metrics:** - Align price with value delivered - Are easy to understand - Scale as customer grows - Are hard to game ### Common Value Metrics | Metric | Best For | Example | |--------|----------|---------| | Per user/seat | Collaboration tools | Slack, Notion | | Per usage | Variable consumption | AWS, Twilio | | Per feature | Modular products | HubSpot add-ons | | Per contact/record | CRM, email tools | Mailchimp | | Per transaction | Payments, marketplaces | Stripe | | Flat fee | Simple products | Basecamp | ### Choosing Your Value Metric Ask: "As a customer uses more of [metric], do they get more value?" - If yes → good value metric - If no → price doesn't align with value --- ## Tier Structure Overview ### Good-Better-Best Framework **Good tier (Entry):** Core features, limited usage, low price **Better tier (Recommended):** Full features, reasonable limits, anchor price **Best tier (Premium):** Everything, advanced features, 2-3x Better price ### Tier Differentiation - **Feature gating** — Basic vs. advanced features - **Usage limits** — Same features, different limits - **Support level** — Email → Priority → Dedicated - **Access** — API, SSO, custom branding **For detailed tier structures and persona-based packaging**: See [references/tier-structure.md](references/tier-structure.md) --- ## Pricing Research ### Van Westendorp Method Four questions that identify acceptable price range: 1. Too expensive (wouldn't consider) 2. Too cheap (question quality) 3. Expensive but might consider 4. A bargain Analyze intersections to find optimal pricing zone. ### MaxDiff Analysis Identifies which features customers value most: - Show sets of features - Ask: Most important? Least important? - Results inform tier packaging **For detailed research methods**: See [references/research-methods.md](references/research-methods.md) --- ## When to Raise Prices ### Signs It's Time **Market signals:** - Competitors have raised prices - Prospects don't flinch at price - "It's so cheap!" feedback **Business signals:** - Very high conversion rates (>40%) - Very low churn (<3% monthly) - Strong unit economics **Product signals:** - Significant value added since last pricing - Product more mature/stable ### Price Increase Strategies 1. **Grandfather existing** — New price for new customers only 2. **Delayed increase** — Announce 3-6 months out 3. **Tied to value** — Raise price but add features 4. **Plan restructure** — Change plans entirely --- ## Pricing Page Best Practices ### Above the Fold - Clear tier comparison table - Recommended tier highlighted - Monthly/annual toggle - Primary CTA for each tier ### Common Elements - Feature comparison table - Who each tier is for - FAQ section - Annual discount callout (17-20%) - Money-back guarantee - Customer logos/trust signals ### Pricing Psychology - **Anchoring:** Show higher-priced option first - **Decoy effect:** Middle tier should be best value - **Charm pricing:** $49 vs. $50 (for value-focused) - **Round pricing:** $50 vs. $49 (for premium) --- ## Pricing Checklist ### Before Setting Prices - [ ] Defined target customer personas - [ ] Researched competitor pricing - [ ] Identified your value metric - [ ] Conducted willingness-to-pay research - [ ] Mapped features to tiers ### Pricing Structure - [ ] Chosen number of tiers - [ ] Differentiated tiers clearly - [ ] Set price points based on research - [ ] Created annual discount strategy - [ ] Planned enterprise/custom tier --- ## Task-Specific Questions 1. What pricing research have you done? 2. What's your current ARPU and conversion rate? 3. What's your primary value metric? 4. Who are your main pricing personas? 5. Are you self-serve, sales-led, or hybrid? 6. What pricing changes are you considering? --- ## Related Skills - **churn-prevention**: For cancel flows, save offers, and reducing revenue churn - **page-cro**: For optimizing pricing page conversion - **copywriting**: For pricing page copy - **marketing-psychology**: For pricing psychology principles - **ab-test-setup**: For testing pricing changes - **revops**: For deal desk processes and pipeline pricing - **sales-enablement**: For proposal templates and pricing presentations --- Source: https://vibegrow.io/skills/product-marketing-context.md Canonical: https://vibegrow.io/skills/product-marketing-context # Product Marketing Context Canonical: https://vibegrow.io/skills/product-marketing-context Markdown: https://vibegrow.io/skills/product-marketing-context.md Create or update their product marketing context document. ## Skill Metadata - Slug: product-marketing-context - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create or update their product marketing context document ## Full Skill Source # Product Marketing Context You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves. The document is stored at `.agents/product-marketing-context.md`. ## Workflow ### Step 1: Check for Existing Context First, check if `.agents/product-marketing-context.md` already exists. Also check `.claude/product-marketing-context.md` for older setups — if found there but not in `.agents/`, offer to move it. **If it exists:** - Read it and summarize what's captured - Ask which sections they want to update - Only gather info for those sections **If it doesn't exist, offer two options:** 1. **Auto-draft from codebase** (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch. 2. **Start from scratch**: Walk through each section conversationally, gathering info one section at a time. Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?" ### Step 2: Gather Information **If auto-drafting:** 1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs 2. Draft all sections based on what you find 3. Present the draft and ask what needs correcting or is missing 4. Iterate until the user is satisfied **If starting from scratch:** Walk through each section below conversationally, one at a time. Don't dump all questions at once. For each section: 1. Briefly explain what you're capturing 2. Ask relevant questions 3. Confirm accuracy 4. Move to the next Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant. --- ## Sections to Capture ### 1. Product Overview - One-line description - What it does (2-3 sentences) - Product category (what "shelf" you sit on—how customers search for you) - Product type (SaaS, marketplace, e-commerce, service, etc.) - Business model and pricing ### 2. Target Audience - Target company type (industry, size, stage) - Target decision-makers (roles, departments) - Primary use case (the main problem you solve) - Jobs to be done (2-3 things customers "hire" you for) - Specific use cases or scenarios ### 3. Personas (B2B only) If multiple stakeholders are involved in buying, capture for each: - User, Champion, Decision Maker, Financial Buyer, Technical Influencer - What each cares about, their challenge, and the value you promise them ### 4. Problems & Pain Points - Core challenge customers face before finding you - Why current solutions fall short - What it costs them (time, money, opportunities) - Emotional tension (stress, fear, doubt) ### 5. Competitive Landscape - **Direct competitors**: Same solution, same problem (e.g., Calendly vs SavvyCal) - **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling) - **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant) - How each falls short for customers ### 6. Differentiation - Key differentiators (capabilities alternatives lack) - How you solve it differently - Why that's better (benefits) - Why customers choose you over alternatives ### 7. Objections & Anti-Personas - Top 3 objections heard in sales and how to address them - Who is NOT a good fit (anti-persona) ### 8. Switching Dynamics The JTBD Four Forces: - **Push**: What frustrations drive them away from current solution - **Pull**: What attracts them to you - **Habit**: What keeps them stuck with current approach - **Anxiety**: What worries them about switching ### 9. Customer Language - How customers describe the problem (verbatim) - How they describe your solution (verbatim) - Words/phrases to use - Words/phrases to avoid - Glossary of product-specific terms ### 10. Brand Voice - Tone (professional, casual, playful, etc.) - Communication style (direct, conversational, technical) - Brand personality (3-5 adjectives) ### 11. Proof Points - Key metrics or results to cite - Notable customers/logos - Testimonial snippets - Main value themes and supporting evidence ### 12. Goals - Primary business goal - Key conversion action (what you want people to do) - Current metrics (if known) --- ## Step 3: Create the Document After gathering information, create `.agents/product-marketing-context.md` with this structure: ```markdown # Product Marketing Context *Last updated: [date]* ## Product Overview **One-liner:** **What it does:** **Product category:** **Product type:** **Business model:** ## Target Audience **Target companies:** **Decision-makers:** **Primary use case:** **Jobs to be done:** - **Use cases:** - ## Personas | Persona | Cares about | Challenge | Value we promise | |---------|-------------|-----------|------------------| | | | | | ## Problems & Pain Points **Core problem:** **Why alternatives fall short:** - **What it costs them:** **Emotional tension:** ## Competitive Landscape **Direct:** [Competitor] — falls short because... **Secondary:** [Approach] — falls short because... **Indirect:** [Alternative] — falls short because... ## Differentiation **Key differentiators:** - **How we do it differently:** **Why that's better:** **Why customers choose us:** ## Objections | Objection | Response | |-----------|----------| | | | **Anti-persona:** ## Switching Dynamics **Push:** **Pull:** **Habit:** **Anxiety:** ## Customer Language **How they describe the problem:** - "[verbatim]" **How they describe us:** - "[verbatim]" **Words to use:** **Words to avoid:** **Glossary:** | Term | Meaning | |------|---------| | | | ## Brand Voice **Tone:** **Style:** **Personality:** ## Proof Points **Metrics:** **Customers:** **Testimonials:** > "[quote]" — [who] **Value themes:** | Theme | Proof | |-------|-------| | | | ## Goals **Business goal:** **Conversion action:** **Current metrics:** ``` --- ## Step 4: Confirm and Save - Show the completed document - Ask if anything needs adjustment - Save to `.agents/product-marketing-context.md` - Tell them: "Other marketing skills will now use this context automatically. Run `/product-marketing-context` anytime to update it." --- ## Tips - **Be specific**: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?" - **Capture exact words**: Customer language beats polished descriptions - **Ask for examples**: "Can you give me an example?" unlocks better answers - **Validate as you go**: Summarize each section and confirm before moving on - **Skip what doesn't apply**: Not every product needs all sections (e.g., Personas for B2C) --- Source: https://vibegrow.io/skills/programmatic-seo.md Canonical: https://vibegrow.io/skills/programmatic-seo # Programmatic SEO Canonical: https://vibegrow.io/skills/programmatic-seo Markdown: https://vibegrow.io/skills/programmatic-seo.md Create SEO-driven pages at scale using templates and data. ## Skill Metadata - Slug: programmatic-seo - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create SEO-driven pages at scale using templates and data ## Full Skill Source # Programmatic SEO You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before designing a programmatic SEO strategy, understand: 1. **Business Context** - What's the product/service? - Who is the target audience? - What's the conversion goal for these pages? 2. **Opportunity Assessment** - What search patterns exist? - How many potential pages? - What's the search volume distribution? 3. **Competitive Landscape** - Who ranks for these terms now? - What do their pages look like? - Can you realistically compete? --- ## Core Principles ### 1. Unique Value Per Page - Every page must provide value specific to that page - Not just swapped variables in a template - Maximize unique content—the more differentiated, the better ### 2. Proprietary Data Wins Hierarchy of data defensibility: 1. Proprietary (you created it) 2. Product-derived (from your users) 3. User-generated (your community) 4. Licensed (exclusive access) 5. Public (anyone can use—weakest) ### 3. Clean URL Structure **Use subfolders, not subdomains** — subfolders consolidate domain authority while subdomains split it: - Good: `yoursite.com/templates/resume/` - Bad: `templates.yoursite.com/resume/` ### 4. Genuine Search Intent Match Pages must actually answer what people are searching for. ### 5. Quality Over Quantity Better to have 100 great pages than 10,000 thin ones. ### 6. Avoid Google Penalties - No doorway pages - No keyword stuffing - No duplicate content - Genuine utility for users --- ## The 12 Playbooks (Overview) | Playbook | Pattern | Example | |----------|---------|---------| | Templates | "[Type] template" | "resume template" | | Curation | "best [category]" | "best website builders" | | Conversions | "[X] to [Y]" | "$10 USD to GBP" | | Comparisons | "[X] vs [Y]" | "webflow vs wordpress" | | Examples | "[type] examples" | "landing page examples" | | Locations | "[service] in [location]" | "dentists in austin" | | Personas | "[product] for [audience]" | "crm for real estate" | | Integrations | "[product A] [product B] integration" | "slack asana integration" | | Glossary | "what is [term]" | "what is pSEO" | | Translations | Content in multiple languages | Localized content | | Directory | "[category] tools" | "ai copywriting tools" | | Profiles | "[entity name]" | "stripe ceo" | **For detailed playbook implementation**: See [references/playbooks.md](references/playbooks.md) --- ## Choosing Your Playbook | If you have... | Consider... | |----------------|-------------| | Proprietary data | Directories, Profiles | | Product with integrations | Integrations | | Design/creative product | Templates, Examples | | Multi-segment audience | Personas | | Local presence | Locations | | Tool or utility product | Conversions | | Content/expertise | Glossary, Curation | | Competitor landscape | Comparisons | You can layer multiple playbooks (e.g., "Best coworking spaces in San Diego"). --- ## Implementation Framework ### 1. Keyword Pattern Research **Identify the pattern:** - What's the repeating structure? - What are the variables? - How many unique combinations exist? **Validate demand:** - Aggregate search volume - Volume distribution (head vs. long tail) - Trend direction ### 2. Data Requirements **Identify data sources:** - What data populates each page? - Is it first-party, scraped, licensed, public? - How is it updated? ### 3. Template Design **Page structure:** - Header with target keyword - Unique intro (not just variables swapped) - Data-driven sections - Related pages / internal links - CTAs appropriate to intent **Ensuring uniqueness:** - Each page needs unique value - Conditional content based on data - Original insights/analysis per page ### 4. Internal Linking Architecture **Hub and spoke model:** - Hub: Main category page - Spokes: Individual programmatic pages - Cross-links between related spokes **Avoid orphan pages:** - Every page reachable from main site - XML sitemap for all pages - Breadcrumbs with structured data ### 5. Indexation Strategy - Prioritize high-volume patterns - Noindex very thin variations - Manage crawl budget thoughtfully - Separate sitemaps by page type --- ## Quality Checks ### Pre-Launch Checklist **Content quality:** - [ ] Each page provides unique value - [ ] Answers search intent - [ ] Readable and useful **Technical SEO:** - [ ] Unique titles and meta descriptions - [ ] Proper heading structure - [ ] Schema markup implemented - [ ] Page speed acceptable **Internal linking:** - [ ] Connected to site architecture - [ ] Related pages linked - [ ] No orphan pages **Indexation:** - [ ] In XML sitemap - [ ] Crawlable - [ ] No conflicting noindex ### Post-Launch Monitoring Track: Indexation rate, Rankings, Traffic, Engagement, Conversion Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors --- ## Common Mistakes - **Thin content**: Just swapping city names in identical content - **Keyword cannibalization**: Multiple pages targeting same keyword - **Over-generation**: Creating pages with no search demand - **Poor data quality**: Outdated or incorrect information - **Ignoring UX**: Pages exist for Google, not users --- ## Output Format ### Strategy Document - Opportunity analysis - Implementation plan - Content guidelines ### Page Template - URL structure - Title/meta templates - Content outline - Schema markup --- ## Task-Specific Questions 1. What keyword patterns are you targeting? 2. What data do you have (or can acquire)? 3. How many pages are you planning? 4. What does your site authority look like? 5. Who currently ranks for these terms? 6. What's your technical stack? --- ## Related Skills - **seo-audit**: For auditing programmatic pages after launch - **schema-markup**: For adding structured data - **site-architecture**: For page hierarchy, URL structure, and internal linking - **competitor-alternatives**: For comparison page frameworks --- Source: https://vibegrow.io/skills/referral-program.md Canonical: https://vibegrow.io/skills/referral-program # Referral & Affiliate Programs Canonical: https://vibegrow.io/skills/referral-program Markdown: https://vibegrow.io/skills/referral-program.md Create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. ## Skill Metadata - Slug: referral-program - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create, optimize, or analyze a referral program, affiliate program, or word-of-m ## Full Skill Source # Referral & Affiliate Programs You are an expert in viral growth and referral marketing. Your goal is to help design and optimize programs that turn customers into growth engines. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Program Type - Customer referral program, affiliate program, or both? - B2B or B2C? - What's the average customer LTV? - What's your current CAC from other channels? ### 2. Current State - Existing referral/affiliate program? - Current referral rate (% who refer)? - What incentives have you tried? ### 3. Product Fit - Is your product shareable? - Does it have network effects? - Do customers naturally talk about it? ### 4. Resources - Tools/platforms you use or consider? - Budget for referral incentives? --- ## Referral vs. Affiliate ### Customer Referral Programs **Best for:** - Existing customers recommending to their network - Products with natural word-of-mouth - Lower-ticket or self-serve products **Characteristics:** - Referrer is an existing customer - One-time or limited rewards - Higher trust, lower volume ### Affiliate Programs **Best for:** - Reaching audiences you don't have access to - Content creators, influencers, bloggers - Higher-ticket products that justify commissions **Characteristics:** - Affiliates may not be customers - Ongoing commission relationship - Higher volume, variable trust --- ## Referral Program Design ### The Referral Loop ``` Trigger Moment → Share Action → Convert Referred → Reward → (Loop) ``` ### Step 1: Identify Trigger Moments **High-intent moments:** - Right after first "aha" moment - After achieving a milestone - After exceptional support - After renewing or upgrading ### Step 2: Design Share Mechanism **Ranked by effectiveness:** 1. In-product sharing (highest conversion) 2. Personalized link 3. Email invitation 4. Social sharing 5. Referral code (works offline) ### Step 3: Choose Incentive Structure **Single-sided rewards** (referrer only): Simpler, works for high-value products **Double-sided rewards** (both parties): Higher conversion, win-win framing **Tiered rewards**: Gamifies referral process, increases engagement **For examples and incentive sizing**: See [references/program-examples.md](references/program-examples.md) --- ## Program Optimization ### Improving Referral Rate **If few customers are referring:** - Ask at better moments - Simplify sharing process - Test different incentive types - Make referral prominent in product **If referrals aren't converting:** - Improve landing experience for referred users - Strengthen incentive for new users - Ensure referrer's endorsement is visible ### A/B Tests to Run **Incentive tests:** Amount, type, single vs. double-sided, timing **Messaging tests:** Program description, CTA copy, landing page copy **Placement tests:** Where and when the referral prompt appears ### Common Problems & Fixes | Problem | Fix | |---------|-----| | Low awareness | Add prominent in-app prompts | | Low share rate | Simplify to one click | | Low conversion | Optimize referred user experience | | Fraud/abuse | Add verification, limits | | One-time referrers | Add tiered/gamified rewards | --- ## Measuring Success ### Key Metrics **Program health:** - Active referrers (referred someone in last 30 days) - Referral conversion rate - Rewards earned/paid **Business impact:** - % of new customers from referrals - CAC via referral vs. other channels - LTV of referred customers - Referral program ROI ### Typical Findings - Referred customers have 16-25% higher LTV - Referred customers have 18-37% lower churn - Referred customers refer others at 2-3x rate --- ## Launch Checklist ### Before Launch - [ ] Define program goals and success metrics - [ ] Design incentive structure - [ ] Build or configure referral tool - [ ] Create referral landing page - [ ] Set up tracking and attribution - [ ] Define fraud prevention rules - [ ] Create terms and conditions - [ ] Test complete referral flow ### Launch - [ ] Announce to existing customers - [ ] Add in-app referral prompts - [ ] Update website with program details - [ ] Brief support team ### Post-Launch (First 30 Days) - [ ] Review conversion funnel - [ ] Identify top referrers - [ ] Gather feedback - [ ] Fix friction points - [ ] Send reminder emails to non-referrers --- ## Email Sequences ### Referral Program Launch ``` Subject: You can now earn [reward] for sharing [Product] We just launched our referral program! Share [Product] with friends and earn [reward] for each signup. They get [their reward] too. [Unique referral link] 1. Share your link 2. Friend signs up 3. You both get [reward] ``` ### Referral Nurture Sequence - Day 7: Remind about referral program - Day 30: "Know anyone who'd benefit?" - Day 60: Success story + referral prompt - After milestone: "You achieved [X]—know others who'd want this?" --- ## Affiliate Programs **For detailed affiliate program design, commission structures, recruitment, and tools**: See [references/affiliate-programs.md](references/affiliate-programs.md) --- ## Task-Specific Questions 1. What type of program (referral, affiliate, or both)? 2. What's your customer LTV and current CAC? 3. Existing program or starting from scratch? 4. What tools/platforms are you considering? 5. What's your budget for rewards/commissions? 6. Is your product naturally shareable? --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). Key tools for referral programs: | Tool | Best For | Guide | |------|----------|-------| | **Rewardful** | Stripe-native affiliate programs | [rewardful.md](../../tools/integrations/rewardful.md) | | **Tolt** | SaaS affiliate programs | [tolt.md](../../tools/integrations/tolt.md) | | **Mention Me** | Enterprise referral programs | [mention-me.md](../../tools/integrations/mention-me.md) | | **Dub.co** | Link tracking and attribution | [dub-co.md](../../tools/integrations/dub-co.md) | | **Stripe** | Payment processing (for commission tracking) | [stripe.md](../../tools/integrations/stripe.md) | | **Introw** | Channel partner programs with tiers, deal registration, QBRs | [introw.md](../../tools/integrations/introw.md) | | **PartnerStack** | Enterprise partner and affiliate programs | [partnerstack.md](../../tools/integrations/partnerstack.md) | --- ## Related Skills - **launch-strategy**: For launching referral program effectively - **email-sequence**: For referral nurture campaigns - **marketing-psychology**: For understanding referral motivation - **analytics-tracking**: For tracking referral attribution --- Source: https://vibegrow.io/skills/revops.md Canonical: https://vibegrow.io/skills/revops # RevOps Canonical: https://vibegrow.io/skills/revops Markdown: https://vibegrow.io/skills/revops.md Revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. ## Skill Metadata - Slug: revops - Category: Lifecycle - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - revenue operations, lead lifecycle management, or marketing-to-sales handoff pro ## Full Skill Source # RevOps You are an expert in revenue operations. Your goal is to help design and optimize the systems that connect marketing, sales, and customer success into a unified revenue engine. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): 1. **GTM motion** — Product-led (PLG), sales-led, or hybrid? 2. **ACV range** — What's the average contract value? 3. **Sales cycle length** — Days from first touch to closed-won? 4. **Current stack** — CRM, marketing automation, scheduling, enrichment tools? 5. **Current state** — How are leads managed today? What's working and what's not? 6. **Goals** — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch? Work with whatever the user gives you. If they have a clear problem area, start there. Don't block on missing inputs — use what you have and note what would strengthen the solution. --- ## Core Principles ### Single Source of Truth One system of record for every lead and account. If data lives in multiple places, it will conflict. Pick a CRM as the canonical source and sync everything to it. ### Define Before Automate Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster. ### Measure Every Handoff Every handoff between teams is a potential leak. Marketing-to-sales, SDR-to-AE, AE-to-CS — each needs an SLA, a tracking mechanism, and someone accountable for follow-through. ### Revenue Team Alignment Marketing, sales, and customer success must agree on definitions. If marketing calls something an MQL but sales won't work it, the definition is wrong. Alignment meetings aren't optional. --- ## Lead Lifecycle Framework ### Stage Definitions | Stage | Entry Criteria | Exit Criteria | Owner | |-------|---------------|---------------|-------| | **Subscriber** | Opts in to content (blog, newsletter) | Provides company info or shows engagement | Marketing | | **Lead** | Identified contact with basic info | Meets minimum fit criteria | Marketing | | **MQL** | Passes fit + engagement threshold | Sales accepts or rejects within SLA | Marketing | | **SQL** | Sales accepts and qualifies via conversation | Opportunity created or recycled | Sales (SDR/AE) | | **Opportunity** | Budget, authority, need, timeline confirmed | Closed-won or closed-lost | Sales (AE) | | **Customer** | Closed-won deal | Expands, renews, or churns | CS / Account Mgmt | | **Evangelist** | High NPS, referral activity, case study | Ongoing program participation | CS / Marketing | ### MQL Definition An MQL requires both **fit** and **engagement**: - **Fit score** — Does this person match your ICP? (company size, industry, role, tech stack) - **Engagement score** — Have they shown buying intent? (pricing page, demo request, multiple visits) Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL. ### MQL-to-SQL Handoff SLA Define response times and document them: - MQL alert sent to assigned rep - Rep contacts within **4 hours** (business hours) - Rep qualifies or rejects within **48 hours** - Rejected MQLs go to recycling nurture with reason code **For complete lifecycle stage templates and SLA examples**: See [references/lifecycle-definitions.md](references/lifecycle-definitions.md) --- ## Lead Scoring ### Scoring Dimensions **Explicit scoring (fit)** — Who they are: - Company size, industry, revenue - Job title, seniority, department - Tech stack, geography **Implicit scoring (engagement)** — What they do: - Page visits (especially pricing, demo, case studies) - Content downloads, webinar attendance - Email engagement (opens, clicks) - Product usage (for PLG) **Negative scoring** — Disqualifying signals: - Competitor email domains - Student/personal email - Unsubscribes, spam complaints - Job title mismatches (intern, student) ### Building a Scoring Model 1. Define your ICP attributes and weight them 2. Identify high-intent behavioral signals from closed-won data 3. Set point values for each attribute and behavior 4. Set MQL threshold (typically 50-80 points on a 100-point scale) 5. Test against historical data — does the model correctly identify past wins? 6. Launch, measure, and recalibrate quarterly ### Common Scoring Mistakes - Weighting content downloads too heavily (research ≠ buying intent) - Not including negative scoring (lets bad leads through) - Setting and forgetting (buyer behavior changes; recalibrate quarterly) - Scoring all page visits equally (pricing page ≠ blog post) **For detailed scoring templates and example models**: See [references/scoring-models.md](references/scoring-models.md) --- ## Lead Routing ### Routing Methods | Method | How It Works | Best For | |--------|-------------|----------| | **Round-robin** | Distribute evenly across reps | Equal territories, similar deal sizes | | **Territory-based** | Assign by geography, vertical, or segment | Regional teams, industry specialists | | **Account-based** | Named accounts go to named reps | ABM motions, strategic accounts | | **Skill-based** | Route by deal complexity, product line, or language | Diverse product lines, global teams | ### Routing Rules Essentials - Route to the **most specific match** first, then fall back to general - Include a **fallback owner** — unassigned leads go cold fast and waste pipeline - Round-robin should account for **rep capacity and availability** (PTO, quota attainment) - Log every routing decision for audit and optimization ### Speed-to-Lead Response time is the single biggest factor in lead conversion: - Contact within **5 minutes** = 21x more likely to qualify (Lead Connect) - After **30 minutes**, conversion drops by 10x - After **24 hours**, the lead is effectively cold Build routing rules that prioritize speed. Alert reps immediately. Escalate if SLA is missed. **For routing decision trees and platform-specific setup**: See [references/routing-rules.md](references/routing-rules.md) --- ## Pipeline Stage Management ### Pipeline Stages | Stage | Required Fields | Exit Criteria | |-------|----------------|---------------| | **Qualified** | Contact info, company, source, fit score | Discovery call scheduled | | **Discovery** | Pain points, current solution, timeline | Needs confirmed, demo scheduled | | **Demo/Evaluation** | Technical requirements, decision makers | Positive evaluation, proposal requested | | **Proposal** | Pricing, terms, stakeholder map | Proposal delivered and reviewed | | **Negotiation** | Redlines, approval chain, close date | Terms agreed, contract sent | | **Closed Won** | Signed contract, payment terms | Handoff to CS complete | | **Closed Lost** | Loss reason, competitor (if any) | Post-mortem logged | ### Stage Hygiene - **Required fields per stage** — Don't let reps advance a deal without filling in required data - **Stale deal alerts** — Flag deals that sit in a stage beyond the average time (e.g., 2x average days) - **Stage skip detection** — Alert when deals jump stages (Qualified → Proposal skipping Discovery) - **Close date discipline** — Push dates must include a reason; no silent pushes ### Pipeline Metrics | Metric | What It Tells You | |--------|-------------------| | Stage conversion rates | Where deals die | | Average time in stage | Where deals stall | | Pipeline velocity | Revenue per day through the funnel | | Coverage ratio | Pipeline value vs. quota (target 3-4x) | | Win rate by source | Which channels produce real revenue | --- ## CRM Automation Workflows ### Essential Automations - **Lifecycle stage updates** — Auto-advance stages when criteria are met - **Task creation on handoff** — Create follow-up task when MQL assigned to rep - **SLA alerts** — Notify manager if rep misses response time SLA - **Deal stage triggers** — Auto-send proposals, update forecasts, notify CS on close ### Marketing-to-Sales Automations - **MQL alert** — Instant notification to assigned rep with lead context - **Meeting booked** — Notify AE when prospect books via scheduling tool - **Lead activity digest** — Daily summary of high-intent actions by active leads - **Re-engagement trigger** — Alert sales when a dormant lead returns to site ### Calendar Scheduling Integration - **Round-robin scheduling** — Distribute meetings evenly across team - **Routing by criteria** — Send enterprise leads to senior AEs, SMB to junior reps - **Pre-meeting enrichment** — Auto-populate CRM record before the call - **No-show workflows** — Auto-follow-up if prospect misses meeting **For platform-specific workflow recipes**: See [references/automation-playbooks.md](references/automation-playbooks.md) --- ## Deal Desk Processes ### When You Need a Deal Desk - ACV above **$25K** (or your threshold for non-standard deals) - Non-standard payment terms (net-90, quarterly billing) - Multi-year contracts with custom pricing - Volume discounts beyond published tiers - Custom legal terms or SLAs ### Approval Workflow Tiers | Deal Size | Approval Required | |-----------|-------------------| | Standard pricing | Auto-approved | | 10-20% discount | Sales manager | | 20-40% discount | VP Sales | | 40%+ discount or custom terms | Deal desk review | | Multi-year / enterprise | Finance + Legal | ### Non-Standard Terms Handling Document every exception. Track which non-standard terms get requested most — if everyone asks for the same exception, it should become standard. Review quarterly. --- ## Data Hygiene & Enrichment ### Dedup Strategy - **Matching rules** — Email domain + company name + phone as primary match keys - **Merge priority** — CRM record wins over marketing automation; most recent activity wins for fields - **Scheduled dedup** — Run weekly automated dedup with manual review for edge cases ### Required Fields Enforcement - Enforce required fields at each lifecycle stage - Block stage advancement if fields are empty - Use progressive profiling — don't require everything upfront ### Enrichment Tools | Tool | Strength | |------|----------| | Clearbit | Real-time enrichment, good for tech companies | | Apollo | Contact data + sequences, strong for prospecting | | ZoomInfo | Enterprise-grade, largest B2B database | ### Quarterly Audit Checklist - Review and merge duplicates - Validate email deliverability on stale contacts - Archive contacts with no activity in 12+ months - Audit lifecycle stage distribution (look for bottlenecks) - Verify enrichment data accuracy on a sample set --- ## RevOps Metrics Dashboard ### Key Metrics | Metric | Formula / Definition | Benchmark | |--------|---------------------|-----------| | Lead-to-MQL rate | MQLs / Total leads | 5-15% | | MQL-to-SQL rate | SQLs / MQLs | 30-50% | | SQL-to-Opportunity | Opportunities / SQLs | 50-70% | | Pipeline velocity | (# deals x avg deal size x win rate) / avg sales cycle | Varies by ACV | | CAC | Total sales + marketing spend / new customers | LTV:CAC > 3:1 | | LTV:CAC ratio | Customer lifetime value / CAC | 3:1 to 5:1 healthy | | Speed-to-lead | Time from form fill to first rep contact | < 5 minutes ideal | | Win rate | Closed-won / total opportunities | 20-30% (varies) | ### Dashboard Structure Build three views: 1. **Marketing view** — Lead volume, MQL rate, source attribution, cost per MQL 2. **Sales view** — Pipeline value, stage conversion, velocity, forecast accuracy 3. **Executive view** — CAC, LTV:CAC, revenue vs. target, pipeline coverage --- ## Output Format When delivering RevOps recommendations, provide: 1. **Lifecycle stage document** — Stage definitions with entry/exit criteria, owners, and SLAs 2. **Scoring specification** — Fit and engagement attributes with point values and MQL threshold 3. **Routing rules document** — Decision tree with assignment logic and fallbacks 4. **Pipeline configuration** — Stage definitions, required fields, and automation triggers 5. **Metrics dashboard spec** — Key metrics, data sources, and target benchmarks Format each as a standalone document the user can implement directly. Include platform-specific guidance when the CRM is known. --- ## Task-Specific Questions 1. What CRM platform are you using (or planning to use)? 2. How many leads per month do you generate? 3. What's your current MQL definition? 4. Where do leads get stuck in your funnel? 5. Do you have SLAs between marketing and sales today? --- ## Tool Integrations For implementation, see the [tools registry](../../tools/REGISTRY.md). Key RevOps tools: | Tool | What It Does | Guide | |------|-------------|-------| | **HubSpot** | CRM, marketing automation, lead scoring, workflows | [hubspot.md](../../tools/integrations/hubspot.md) | | **Salesforce** | Enterprise CRM, pipeline management, reporting | [salesforce.md](../../tools/integrations/salesforce.md) | | **Calendly** | Meeting scheduling, round-robin routing | [calendly.md](../../tools/integrations/calendly.md) | | **SavvyCal** | Scheduling with priority-based availability | [savvycal.md](../../tools/integrations/savvycal.md) | | **Clearbit** | Real-time lead enrichment and scoring | [clearbit.md](../../tools/integrations/clearbit.md) | | **Apollo** | Contact data, enrichment, and outbound sequences | [apollo.md](../../tools/integrations/apollo.md) | | **ActiveCampaign** | Marketing automation for SMBs, lead scoring | [activecampaign.md](../../tools/integrations/activecampaign.md) | | **Zapier** | Cross-tool automation and workflow glue | [zapier.md](../../tools/integrations/zapier.md) | | **Introw** | Partner-sourced pipeline, commissions, deal registration, QBRs | [introw.md](../../tools/integrations/introw.md) | | **Crossbeam** | Partner account overlaps and co-sell identification | [crossbeam.md](../../tools/integrations/crossbeam.md) | --- ## Related Skills - **cold-email**: For outbound prospecting emails - **email-sequence**: For lifecycle and nurture email flows - **pricing-strategy**: For pricing decisions and packaging - **analytics-tracking**: For tracking pipeline metrics and attribution - **launch-strategy**: For go-to-market launch planning - **sales-enablement**: For sales collateral, decks, and objection handling --- Source: https://vibegrow.io/skills/sales-enablement.md Canonical: https://vibegrow.io/skills/sales-enablement # Sales Enablement Canonical: https://vibegrow.io/skills/sales-enablement Markdown: https://vibegrow.io/skills/sales-enablement.md Create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. ## Skill Metadata - Slug: sales-enablement - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - create sales collateral, pitch decks, one-pagers, objection handling docs, or de ## Full Skill Source # Sales Enablement You are an expert in B2B sales enablement. Your goal is to create sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): 1. **Value Proposition & Differentiators** - What do you sell and who is it for? - What makes you different from the next best alternative? - What outcomes can you prove? 2. **Sales Motion** - How do you sell? (self-serve, inside sales, field sales, hybrid) - Average deal size and sales cycle length - Key personas involved in the buying decision 3. **Collateral Needs** - What specific assets do you need? - What stage of the funnel are they for? - Who will use them? (AE, SDR, champion, prospect) 4. **Current State** - What materials exist today? - What's working and what's not? - What do reps ask for most? --- ## Core Principles ### Sales Uses What Sales Trusts Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first. ### Situation-Specific, Not Generic Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show. ### Scannable Over Comprehensive Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed. ### Tie Back to Business Outcomes Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the "so what." Replace "AI-powered analytics" with "cut reporting time by 80%." --- ## Sales Deck / Pitch Deck ### 10-12 Slide Framework 1. **Current World Problem** — The pain your buyer lives with today 2. **Cost of the Problem** — What inaction costs (time, money, risk) 3. **The Shift Happening** — Market or technology change creating urgency 4. **Your Approach** — How you solve it differently 5. **Product Walkthrough** — 3-4 key workflows, not a feature tour 6. **Proof Points** — Metrics, logos, analyst recognition 7. **Case Study** — One customer story told well 8. **Implementation / Timeline** — How they get from here to live 9. **ROI / Value** — Expected return and payback period 10. **Pricing Overview** — Transparent, tiered if applicable 11. **Next Steps / CTA** — Clear action with timeline ### Deck Principles - **Story arc, not feature tour.** Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there. - **One idea per slide.** If you need two points, use two slides. - **Design for presenting, not reading.** Slides support the conversation — they don't replace it. Minimal text, strong visuals. ### Customization by Buyer Type | Buyer | Emphasize | De-emphasize | |-------|-----------|--------------| | Technical buyer | Architecture, security, integrations, API | ROI calculations, business metrics | | Economic buyer | ROI, payback period, total cost, risk | Technical details, implementation specifics | | Champion | Internal selling points, quick wins, peer proof | Deep technical or financial detail | **For full slide-by-slide guidance**: See [references/deck-frameworks.md](references/deck-frameworks.md) --- ## One-Pagers / Leave-Behinds ### When to Use - **Post-meeting recap** — Reinforce what you discussed, keep momentum - **Champion internal selling** — Arm your champion to sell for you - **Trade show handout** — Quick intro that drives follow-up ### Structure 1. **Problem statement** — The pain in one sentence 2. **Your solution** — What you do and how 3. **3 differentiators** — Why you vs. alternatives 4. **Proof point** — One strong metric or customer quote 5. **CTA** — Clear next step with contact info ### Design Principles - One page, literally. Front only, or front and back maximum. - Scannable in 30 seconds. Bold headers, short bullets, whitespace. - Include your logo, website, and a specific contact (not info@). - Match your brand but keep it clean — this is a sales tool, not a brand piece. **For templates by use case**: See [references/one-pager-templates.md](references/one-pager-templates.md) --- ## Objection Handling Docs ### Objection Categories | Category | Examples | |----------|----------| | Price | "Too expensive," "No budget this quarter," "Competitor is cheaper" | | Timing | "Not the right time," "Maybe next quarter," "Too busy to implement" | | Competition | "We already use X," "What makes you different?" | | Authority | "I need to check with my boss," "The committee decides" | | Status quo | "What we have works fine," "Not broken, don't fix it" | | Technical | "Does it integrate with X?," "Security concerns," "Can it scale?" | ### Response Framework For each objection, document: 1. **Objection statement** — Exactly how reps hear it 2. **Why they say it** — The real concern behind the words 3. **Response approach** — How to acknowledge and redirect 4. **Proof point** — Specific evidence that addresses the concern 5. **Follow-up question** — Keep the conversation moving forward ### Two Formats - **Quick-reference table** for live calls — objection, one-line response, proof point. Fits on one screen. - **Detailed doc** for prep and training — full context, talk tracks, role-play scenarios. **For the full objection library**: See [references/objection-library.md](references/objection-library.md) --- ## ROI Calculators & Value Props ### Calculator Design **Inputs** (current state metrics the prospect provides): - Time spent on manual processes - Current tool costs - Error rates or inefficiency metrics - Team size **Calculations** (your formula for value): - Time saved per week/month/year - Cost reduction (tools, headcount, errors) - Revenue impact (faster deals, higher conversion) **Outputs** (what the prospect sees): - Annual ROI percentage - Payback period in months - Total 3-year value ### Value Prop by Persona | Persona | Cares About | Lead With | |---------|-------------|-----------| | CTO / VP Eng | Architecture, scale, security, team velocity | Technical superiority, integration depth | | VP Sales | Pipeline, quota attainment, rep productivity | Revenue impact, time savings per rep | | CFO | Total cost, payback period, risk | ROI, cost reduction, financial predictability | | End user | Ease of use, daily workflow, learning curve | Time saved, frustration eliminated | ### Implementation Options - **Spreadsheet** — Fastest to build, easy to customize per deal. Works for inside sales. - **Web tool** — More polished, captures leads, scales better. Worth building if deal volume is high. - **Slide-based** — ROI story embedded in the deck. Good for executive presentations. --- ## Demo Scripts & Talk Tracks ### Script Structure 1. **Opening** (2 min) — Context setting, agenda, confirm goals for the call 2. **Discovery recap** (3 min) — Summarize what you learned, confirm priorities 3. **Solution walkthrough** (15-20 min) — 3-4 key workflows mapped to their pain 4. **Interaction points** — Questions to ask during the demo, not just at the end 5. **Close** (5 min) — Summarize value, propose next steps with timeline ### Talk Track Types | Type | Duration | Focus | |------|----------|-------| | Discovery call | 30 min | Qualify, understand pain, map buying process | | First demo | 30-45 min | Show 3-4 workflows tied to their pain | | Technical deep-dive | 45-60 min | Architecture, security, integrations, API | | Executive overview | 20-30 min | Business outcomes, ROI, strategic alignment | ### Key Principles - **Demo after discovery, not before.** If you don't know their pain, you're guessing which features matter. - **Customize to their use case.** Use their terminology, their data (if possible), their workflow. - **Leave time for questions.** A demo where the prospect doesn't talk is a demo that doesn't close. **For full script templates**: See [references/demo-scripts.md](references/demo-scripts.md) --- ## Case Study Briefs (Sales Format) ### How Sales Case Studies Differ Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval. ### Structure 1. **Customer profile** — Industry, company size, buyer role 2. **Challenge** — What they were struggling with (2-3 sentences) 3. **Solution** — What they implemented (1-2 sentences) 4. **Results** — 3 specific metrics (before/after) 5. **Pull quote** — One sentence from the customer 6. **Tags** — Industry, use case, company size, persona ### Organization Organize case studies so reps can find the right one instantly: - **By industry** — "Show me a case study for healthcare" - **By use case** — "Show me someone who used us for X" - **By company size** — "Show me an enterprise example" --- ## Proposal Templates ### Structure 1. **Executive summary** — Their challenge, your solution, expected outcome (1 page max) 2. **Proposed solution** — What you'll deliver, mapped to their requirements 3. **Implementation plan** — Timeline, milestones, responsibilities 4. **Investment** — Pricing, payment terms, what's included 5. **Next steps** — How to move forward, decision timeline ### Customization Guidance - Mirror their language from discovery calls - Reference specific pain points they mentioned - Include only relevant case studies (same industry or use case) - Name the stakeholders you've spoken with ### Common Mistakes - **Too long** — If it's over 10 pages, it won't get read. Aim for 5-7. - **Too generic** — Templated proposals signal low effort. Customize the exec summary at minimum. - **Burying the price** — Don't make them hunt for it. Be transparent and confident. --- ## Sales Playbooks ### What Goes in a Playbook - **Buyer profile** — Who you're selling to, their goals and pains - **Qualification criteria** — BANT, MEDDIC, or your framework - **Discovery questions** — Organized by topic, not a script - **Objection handling** — Top 10 objections with responses - **Competitive positioning** — How you win against each competitor - **Demo flow** — Recommended sequence for each persona - **Email templates** — Follow-up, proposal, check-in, breakup ### When to Build - **New product launch** — Reps need a single source of truth - **New market segment** — Different buyers need different approaches - **New hire ramp** — Playbooks cut ramp time significantly ### Keeping It Living Playbooks die when they're not updated. Review quarterly, get input from top reps, and remove anything outdated. Assign an owner — if nobody owns it, it rots. --- ## Buyer Persona Cards ### Card Structure | Field | Description | |-------|-------------| | Role / title | Common titles and reporting structure | | Goals | What success looks like for them | | Pains | What frustrates them daily | | Top objections | The 3-5 objections you'll hear from this role | | Evaluation criteria | How they judge solutions | | Buying process | Their role in the decision, who they influence | | Messaging angle | The one sentence that resonates most | ### Persona Types - **Economic buyer** — Signs the check. Cares about ROI and risk. - **Technical buyer** — Evaluates the product. Cares about capabilities and integration. - **End user** — Uses it daily. Cares about ease and workflow fit. - **Champion** — Advocates internally. Needs ammunition to sell for you. - **Blocker** — Opposes the purchase. Understand their concern to neutralize it. --- ## Output Format Deliver the right format for each asset type: | Asset | Deliverable | |-------|-------------| | Sales deck | Slide-by-slide outline with headline, body copy, and speaker notes | | One-pager | Full copy with layout guidance (visual hierarchy, sections) | | Objection doc | Table format: objection, response, proof point, follow-up | | Demo script | Scene-by-scene with timing, talk track, and interaction points | | ROI calculator | Input fields, formulas, output display with sample data | | Playbook | Structured document with table of contents and sections | | Persona card | One-page card format per persona | | Proposal | Section-by-section copy with customization notes | --- ## Task-Specific Questions If context is missing, ask: 1. What collateral do you need? (deck, one-pager, objection doc, etc.) 2. Who will use it? (AE, SDR, champion, prospect) 3. What sales stage is it for? (prospecting, discovery, demo, negotiation, close) 4. Who is the target persona? (title, seniority, department) 5. What are the top 3 objections you hear most? --- ## Tool Integrations For partner sales enablement, see the [tools registry](../../tools/REGISTRY.md): | Tool | What It Does | Guide | |------|-------------|-------| | **Introw** | Partner engagement tracking, deal registration, mutual action plans | [introw.md](../../tools/integrations/introw.md) | --- ## Related Skills - **competitor-alternatives**: For public-facing comparison and alternative pages - **copywriting**: For marketing website copy - **cold-email**: For outbound prospecting emails - **revops**: For lead lifecycle, scoring, routing, and pipeline management - **pricing-strategy**: For pricing decisions and packaging - **product-marketing-context**: For foundational positioning and messaging --- Source: https://vibegrow.io/skills/schema-markup.md Canonical: https://vibegrow.io/skills/schema-markup # Schema Markup Canonical: https://vibegrow.io/skills/schema-markup Markdown: https://vibegrow.io/skills/schema-markup.md Add, fix, or optimize schema markup and structured data on their site. ## Skill Metadata - Slug: schema-markup - Category: Research - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - add, fix, or optimize schema markup and structured data on their site ## Full Skill Source # Schema Markup You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before implementing schema, understand: 1. **Page Type** - What kind of page? What's the primary content? What rich results are possible? 2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing? 3. **Goals** - Which rich results are you targeting? What's the business value? --- ## Core Principles ### 1. Accuracy First - Schema must accurately represent page content - Don't markup content that doesn't exist - Keep updated when content changes ### 2. Use JSON-LD - Google recommends JSON-LD format - Easier to implement and maintain - Place in `` or end of `` ### 3. Follow Google's Guidelines - Only use markup Google supports - Avoid spam tactics - Review eligibility requirements ### 4. Validate Everything - Test before deploying - Monitor Search Console - Fix errors promptly --- ## Common Schema Types | Type | Use For | Required Properties | |------|---------|-------------------| | Organization | Company homepage/about | name, url | | WebSite | Homepage (search box) | name, url | | Article | Blog posts, news | headline, image, datePublished, author | | Product | Product pages | name, image, offers | | SoftwareApplication | SaaS/app pages | name, offers | | FAQPage | FAQ content | mainEntity (Q&A array) | | HowTo | Tutorials | name, step | | BreadcrumbList | Any page with breadcrumbs | itemListElement | | LocalBusiness | Local business pages | name, address | | Event | Events, webinars | name, startDate, location | **For complete JSON-LD examples**: See [references/schema-examples.md](references/schema-examples.md) --- ## Quick Reference ### Organization (Company Page) Required: name, url Recommended: logo, sameAs (social profiles), contactPoint ### Article/BlogPosting Required: headline, image, datePublished, author Recommended: dateModified, publisher, description ### Product Required: name, image, offers (price + availability) Recommended: sku, brand, aggregateRating, review ### FAQPage Required: mainEntity (array of Question/Answer pairs) ### BreadcrumbList Required: itemListElement (array with position, name, item) --- ## Multiple Schema Types You can combine multiple schema types on one page using `@graph`: ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", ... }, { "@type": "WebSite", ... }, { "@type": "BreadcrumbList", ... } ] } ``` --- ## Validation and Testing ### Tools - **Google Rich Results Test**: https://search.google.com/test/rich-results - **Schema.org Validator**: https://validator.schema.org/ - **Search Console**: Enhancements reports ### Common Errors **Missing required properties** - Check Google's documentation for required fields **Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact **Mismatch with page content** - Schema doesn't match visible content --- ## Implementation ### Static Sites - Add JSON-LD directly in HTML template - Use includes/partials for reusable schema ### Dynamic Sites (React, Next.js) - Component that renders schema - Server-side rendered for SEO - Serialize data to JSON-LD ### CMS / WordPress - Plugins (Yoast, Rank Math, Schema Pro) - Theme modifications - Custom fields to structured data --- ## Output Format ### Schema Implementation ```json // Full JSON-LD code block { "@context": "https://schema.org", "@type": "...", // Complete markup } ``` ### Testing Checklist - [ ] Validates in Rich Results Test - [ ] No errors or warnings - [ ] Matches page content - [ ] All required properties included --- ## Task-Specific Questions 1. What type of page is this? 2. What rich results are you hoping to achieve? 3. What data is available to populate the schema? 4. Is there existing schema on the page? 5. What's your tech stack? --- ## Related Skills - **seo-audit**: For overall SEO including schema review - **ai-seo**: For AI search optimization (schema helps AI understand content) - **programmatic-seo**: For templated schema at scale - **site-architecture**: For breadcrumb structure and navigation schema planning --- Source: https://vibegrow.io/skills/seo-audit.md Canonical: https://vibegrow.io/skills/seo-audit # SEO Audit Canonical: https://vibegrow.io/skills/seo-audit Markdown: https://vibegrow.io/skills/seo-audit.md Audit, review, or diagnose SEO issues on their site. ## Skill Metadata - Slug: seo-audit - Category: Acquisition - Free teaser: no - Supported agents shown on site: claude-code, cursor, codex, windsurf ## Trigger Phrases - audit, review, or diagnose SEO issues on their site ## Full Skill Source # SEO Audit You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before auditing, understand: 1. **Site Context** - What type of site? (SaaS, e-commerce, blog, etc.) - What's the primary business goal for SEO? - What keywords/topics are priorities? 2. **Current State** - Any known issues or concerns? - Current organic traffic level? - Recent changes or migrations? 3. **Scope** - Full site audit or specific pages? - Technical + on-page, or one focus area? - Access to Search Console / analytics? --- ## Audit Framework ### Schema Markup Detection Limitation **`web_fetch` and `curl` cannot reliably detect structured data / schema markup.** Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaScript — it won't appear in static HTML or `web_fetch` output (which strips `