# Build Clear SaaS Pricing Strategy

Pricing decisions are hard when customer value, packaging, and conversion data are scattered. This skill turns research, metrics, and tier design into practical pricing recommendations.

## Install

```bash
npx skillstore add coreyhaines31/pricing-strategy
```

## Metadata

- Status: approved
- Slug: coreyhaines31-pricing-strategy
- Skillstore revision: r1
- Version status: missing
- Tree hash: dc2a88123ec713ca415065a35b9c25ddbaaf1af0b4113c83edb79137fa835865
- Author: coreyhaines31
- GitHub username: coreyhaines31
- License: MIT
- Repository: https://github.com/coreyhaines31/marketingskills/tree/main/skills/pricing-strategy
- Ref: d11af420e07cd866fe39cfa937efef3223896c06
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/coreyhaines31-pricing-strategy
- Manifest: https://skillstore.pages.dev/api/skills/coreyhaines31-pricing-strategy/manifest

## Capabilities

- Guides value-based pricing decisions using perceived value, alternatives, and cost floors.
- Explains Van Westendorp, MaxDiff, Gabor-Granger, and conjoint research methods.
- Helps choose value metrics such as seats, usage, records, transactions, or flat fees.
- Designs good-better-best tiers with feature gates, usage limits, and support levels.
- Compares freemium, free trial, reverse trial, and hybrid monetization models.
- Plans price increases, pricing page structure, enterprise tiers, and price tests.

## Use Cases

- Launch New SaaS Pricing: Create initial tiers, value metrics, and price ranges before a product launch.
- Improve Packaging Conversion: Restructure plans when users are confused, upgrades are weak, or tiers do not match value.
- Plan an Enterprise Motion: Add custom pricing, support levels, contracts, and enterprise-ready packaging.

## Prompt Templates

### Review My Current Pricing

```
Review my current pricing. My product is [product], target market is [market], current tiers are [tiers], and my goal is [goal]. Identify the biggest issues and simple improvements.
```

### Choose a Value Metric

```
Help me choose a value metric for [product]. Customers get value from [outcomes], usage patterns are [usage], and current pricing is [pricing]. Compare the best options.
```

### Design Pricing Tiers

```
Design good-better-best pricing tiers for [product]. Use these personas, features, limits, support needs, and willingness-to-pay signals: [details]. Explain each tier.
```

### Plan a Price Increase

```
Create a price increase plan for [product]. Current prices are [current], proposed prices are [new], customer segments are [segments], and risks are [risks]. Include communication and measurement steps.
```

## Limitations

- Does not run surveys, statistical models, or pricing page experiments by itself.
- Requires accurate customer, competitor, conversion, churn, and revenue data from the user.
- Provides strategy guidance, not legal advice for regional pricing or A/B testing rules.
- Recommendations should be validated with customers before major pricing changes.

## Best Practices

- Bring current pricing, customer segments, conversion rates, churn, and competitor context before asking for recommendations.
- Validate price points with willingness-to-pay research and customer conversations before changing published pricing.
- Measure pricing changes with conversion, ARPU, LTV, churn, expansion, and segment-level performance.

## Anti Patterns

- Choosing prices only from internal costs without estimating customer value and alternatives.
- Creating many tiers or feature gates that make buying decisions harder.
- Running pricing tests that create unfair customer experiences or damage trust.

## Security Audit

- Audited at: 2026-07-06T08:13:04.279\+00:00
- Summary: All static findings are false positives. The backtick findings are Markdown fenced examples, and the reconnaissance findings are pricing and packaging terminology. No prompt injection, command execution, exfiltration, or malicious intent was found in SKILL.md.

## Stats

- Views: 149
- Downloads: 8
- Favorites: 0
- Popularity score: 0