agentleFS
alexsmedilealexsmedile/hormozi-skills/skills/pricing-strategy/SKILL.md

pricing-strategy

Skill208 starsChanged 3 months agoMITView on GitHub

Set the right price anchored to value, not guesswork. Use when pricing feels random, conversions are low due to price resistance, or you want to introduce tiers. Analyzes outcome value, delivery model, and market expectations to produce pricing range, strategy, tiers, psychological pricing, and a price justification story — outputs PRICING.md.

111 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 104 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a realistic range based on:

    line 97
  2. Distinctive:

    Create a simple narrative:

    line 168
  3. Distinctive:

    Before vs After Example

    line 288

“Common” is measured: kept by at least 6 in 10 of the 104 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Pricing Strategy (Value Anchoring Engine)

Purpose

Set the right price based on value, not guesswork.

This skill ensures the price:

  • reflects the outcome
  • feels justified to the buyer
  • matches the delivery model
  • maximizes conversions and revenue

It improves:

  • perceived value
  • positioning
  • profitability

When to Use

Activate this skill when:

  • pricing feels random or uncertain
  • conversions are low due to price resistance
  • the offer feels “too cheap” or “too expensive”
  • you want to introduce tiers
  • you’re launching a new offer
  • you need a clear pricing story

Inputs

This skill works with:

  • an OFFER.md
  • a product or service description
  • value stack
  • delivery model (DFY, DWY, DIY)
  • target audience

Core Outcome

The assistant produces:

  • a price anchored to value
  • pricing tier structure (if needed)
  • price positioning strategy
  • psychological pricing suggestions
  • a clear price justification story

Assistant Behavior

1. Understand the value

Extract:

  • the core outcome
  • how much that outcome is worth
  • urgency of the problem
  • financial or emotional impact

Then summarize:

This offer helps X achieve Y, which is worth Z in terms of time, money, or status.


2. Analyze the delivery model

Identify:

  • DIY → lower price, volume-based
  • DWY → mid-tier pricing
  • DFY → premium pricing

Then assess:

  • level of support
  • level of customization
  • level of effort saved

3. Anchor price to outcome

Estimate value based on:

  • money gained
  • time saved
  • pain avoided
  • opportunity unlocked

Frame it like:

If this helps achieve X, then even a fraction of that value justifies the price.


4. Define pricing range

Create a realistic range based on:

  • market expectations
  • delivery model
  • complexity
  • competition (if known)

Output:

  • low-end price
  • mid-range price
  • premium price

5. Choose pricing strategy

Select one:

Volume (Low-Ticket)

  • low price
  • high volume
  • simple delivery
  • fast decision

Margin (High-Ticket)

  • high price
  • lower volume
  • high support
  • strong transformation

Hybrid

  • entry offer + core offer + premium

Explain tradeoffs:

  • speed vs profit
  • scale vs depth
  • simplicity vs customization

6. Build pricing tiers (if needed)

Structure:

  • Tier 1: Entry (DIY)
  • Tier 2: Core (DWY)
  • Tier 3: Premium (DFY)

For each:

  • what’s included
  • who it’s for
  • price point
  • value difference

7. Apply psychological pricing

Suggest:

  • price anchoring (show higher value first)
  • charm pricing (e.g. 27, 97, 297)
  • round pricing for premium (e.g. 1000+)
  • tier contrast (clear jumps in value)

Explain:

  • why this pricing feels right
  • how it influences perception

8. Build the price justification story

Create a simple narrative:

Structure:

  1. Restate the outcome
  2. Show what it’s worth
  3. Compare to alternatives
  4. Anchor total value stack
  5. Reveal price as “small” relative to value

Example:

If this helps you get X, which is worth Y, then paying Z is a small step.


9. Stress test the price

Check:

  • does it feel cheap (low trust)?
  • does it feel expensive (low clarity)?
  • does it match the outcome?
  • does it match the audience’s ability to pay?

Adjust if needed.


10. Suggest pricing experiments

Recommend:

  • A/B testing price points
  • introducing payment plans
  • testing discounts vs bonuses
  • early-bird pricing

Output Format

# PRICING.md

## 1. Value Analysis
- Outcome
- Why it matters
- Estimated value

## 2. Delivery Model Impact
- Model (DIY, DWY, DFY)
- Pricing implications

## 3. Pricing Range
- Low price
- Mid price
- High price

## 4. Recommended Pricing Strategy
- Strategy type
- Reasoning

## 5. Pricing Tiers (if applicable)

### Tier 1
- Name
- What’s included
- Price

### Tier 2
- Name
- What’s included
- Price

### Tier 3
- Name
- What’s included
- Price

## 6. Psychological Pricing
- Techniques used
- Why they work

## 7. Price Justification Story
- Narrative

## 8. Risk Check
- Potential issues
- Adjustments

## 9. Pricing Experiments
- Tests to run

⸻

Decision Rules

Price higher when: • outcome is valuable • effort is low for the customer • speed is high • delivery includes DFY elements

Price lower when: • outcome is uncertain • delivery is DIY • trust is low • market is price-sensitive

Use tiers when: • audience has different budgets • multiple delivery levels exist • upsell potential is strong

Avoid underpricing when: • it reduces trust • it signals low value • it attracts the wrong audience

⸻

Before vs After Example

Before • Random price: $49

After • Value stack: $500+ • Anchored price: $97 • Justified by outcome and speed

⸻

Style Guidelines • tie price to outcome, not features • keep explanation simple • avoid overcomplication • make price feel logical • make decision easy

⸻

Success Criteria

The skill works when: • price feels fair and justified • value clearly exceeds price • buyers hesitate less • positioning improves • revenue increases

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.