Use when set prices using value-based, cost-plus, competitive, and subscription
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill pricing-frameworks --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pricing Frameworks?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-pricing-frameworks)More formats (shields.io, HTML) on the badges page.
---
name: pricing-frameworks
description: Use when set prices using value-based, cost-plus, competitive, and subscription
models. Includes tiering, anchoring, discounts, and pricing experiments. Use when
working with pricing frameworks.
domain: mindset
author: oyi77
license: Apache-2.0
subdomain: mindset
tags:
- frameworks
- mindset
- personal-development
- pricing
- soft-skills
version: 1.0.0
category: mindset
---
# Pricing Frameworks
## Overview
Mindset skill for pricing frameworks. Builds capability through deliberate practice and structured frameworks.
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |
## When to Use
**Trigger phrases:**
- "pricing frameworks"
- "Set prices using value-based, cost-plus, competitive, and subscription models"
- Setting initial prices for a new product
- Optimizing existing pricing (increasing revenue per customer)
- Launching new pricing tiers or plans
- Annual price review
- **When NOT to use**: Dynamic pricing for commodity (use market price), or internal transfer pricing (use cost accounting)
## When NOT to Use
- When the situation requires professional counseling or therapy
- For high-stakes decisions that need expert judgment
- When the skill conflicts with cultural or personal values
## Core Principles
- **Start small** — Begin with manageable pricing frameworks practices and build incrementally
- **Be consistent** — Daily practice beats occasional intense effort
- **Track progress** — Measure improvement to maintain motivation
- **Reflect regularly** — Review what's working and adjust your approach
## Daily Practice
1. **Morning intention** — Set a specific pricing frameworks goal for the day
2. **Active practice** — Apply pricing frameworks techniques during real situations
3. **Evening reflection** — Review the day's pricing frameworks moments and lessons learned
4. **Journal entry** — Record insights, wins, and areas for improvement
## Frameworks
- **OODA Loop** — Observe, Orient, Decide, Act — for rapid pricing frameworks decision cycles
- **PDCA Cycle** — Plan, Do, Check, Act — for iterative pricing frameworks improvement
- **After-Action Review** — What happened? Why? What to improve?
- **Deliberate Practice** — Focused effort on specific pricing frameworks weaknesses
## Common Pitfalls
- **Perfectionism** — Waiting for ideal conditions instead of starting now
- **Inconsistency** — Practicing sporadically instead of building a routine
- **Isolation** — Not seeking feedback or accountability partners
- **Overwhelm** — Trying to improve everything at once instead of focusing
## Resources
- Keep a pricing frameworks journal for tracking progress
- Find an accountability partner or mentor
- Set weekly pricing frameworks challenges with measurable outcomes
- Review and adjust your approach monthly
```markdown
# Daily Practice Template
## Morning (5 min)
- Set intention for the day
- Review top 3 priorities
## During the day
- Practice the skill in real situations
- Note moments of success and struggle
## Evening (5 min)
- Reflect: What worked? What did not?
- Log one lesson learned
```
## Process
1. **Design** — Define interface, identify patterns, plan implementation
1. **Implement** — Write code following existing conventions, add tests
1. **Verify** — Run tests, check integration, validate behavior
## Verification
- [ ] All steps executed successfully
- [ ] Results validated against acceptance criteria
- [ ] Error handling tested with edge cases
- [ ] Documentation updated with findingsIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!