Pricing Strategy
When the user wants help with pricing decisions, packaging, or monetization strategy.
Overview
Pricing Strategy is a growth/marketing skill from Corey Haines’ Marketing Skills collection (github.com/coreyhaines31/marketingskills). When the user wants help with pricing decisions, packaging, or monetization strategy. The skill is structured around practical workflows—covering Before Starting, Pricing Fundamentals, Value Metrics, Tier Structure Overview, Pricing Research, When to Raise Prices—so Claude can move from context gathering to concrete artifacts (briefs, copy, checklists, or audit reports) instead of generic advice. Pair it with related skills in the same collection: `offers`, `paywalls`, `ab-testing`, `product-marketing`.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Option A — Install just this skill (recommended)
npx skills add coreyhaines31/marketingskills --skill pricingOption B — Install the full Marketing Skills collection
npx skills add coreyhaines31/marketingskillsThat unlocks related skills like `cro`, `copywriting`, `emails`, `ads`, and `seo-audit`.
Option C — Manual install (Claude Code)
git clone https://github.com/coreyhaines31/marketingskills.git /tmp/marketingskills
mkdir -p ~/.claude/skills
cp -R /tmp/marketingskills/skills/pricing ~/.claude/skills/pricingClaude.ai
Customize → Skills → Upload the `pricing` folder as a zip / `SKILL.md` → enable the skill.
Always skim `SKILL.md` before first use so you know its triggers and related skills.
How to use it
1. **Trigger it with pricing strategy language** — mention the job by name or ask for the deliverable this skill owns. 2. **Share product context up front** — ICP, offer, URL, constraints, and any metrics. If `.agents/product-marketing.md` (or `.claude/product-marketing.md`) exists, the skill will read it first. 3. **Let it run the assessment** — answer clarifying questions before asking for final copy/strategy. 4. **Request a concrete artifact** — brief, audit, page outline, sequence, scorecard, or launch checklist. 5. **Close the loop** — feed performance data back so the next iteration compounds.
**Typical sections it covers:** Before Starting, Pricing Fundamentals, Value Metrics, Tier Structure Overview, Pricing Research, When to Raise Prices, Pricing Page Best Practices, Pricing Page Teardown.
If Claude does not auto-select it, say: “Use the Pricing Strategy skill (`pricing`)…”.
Example prompts
- “Propose a 3-tier pricing model for a $29–$199 SaaS. Include what to gate, annual discount, and good/better/best logic.”
- “Rewrite our pricing page to reduce plan-choice paralysis. We have Starter/Pro/Business.”
- “Design an experiment to test showing annual pricing first vs monthly first.”
- “Help us package a usage-based add-on without confusing the core tiers.”
Use cases and examples
- Design a 2–3 tier pricing structure with packaging logic
- Write pricing-page copy and plan-comparison tables
- Model willingness-to-pay interviews into price points
- Plan a price-change communication and grandfathering policy
- Test annual vs monthly framing and anchors
- Align packaging with ICP segments and sales motion
Prerequisites
- Claude Code, Claude.ai Skills, or another Agent Skills–compatible host
- Product/brand context (ICP, offer, URLs, constraints) for grounded outputs
- Optional: `.agents/product-marketing.md` or `.claude/product-marketing.md` in the repo
- Permission to install third-party skills — audit SKILL.md first
- Optional: analytics or ad-platform access when the task needs real performance data
Tips
- Keep triggers specific so Pricing Strategy fires only when that job is requested (avoids context tax).
- Load product-marketing context (ICP, voice, offer) before asking for final copy or strategy.
- Prefer one sharp deliverable per turn—brief, audit, or draft—then iterate with data.
- Audit `SKILL.md` and any scripts before production use; treat community skills as code.
- Pair with `offers` and `paywalls` when the workflow spans channels.