pricing-strategy
by phurynpricing-strategy skill for designing and evaluating pricing models with a value-first lens. Use it to compare flat-rate, per-seat, usage-based, tiered, freemium, or value-based pricing, assess willingness to pay, and plan a pricing change with competitive context.
This skill scores 78/100, which means it is a solid listing candidate for directory users: it has a clear trigger, a real pricing-strategy workflow, and enough operational guidance to outperform a generic prompt, though it still lacks some adoption aids like install commands, supporting files, and explicit constraints.
- Clear triggerability: the description specifies when to use it for pricing models, competitive pricing analysis, willingness-to-pay, price elasticity, and freemium vs paid decisions.
- Operational workflow is concrete: it instructs the agent to assess value delivered, alternatives, and quantifiable outcomes, then evaluate multiple pricing models in a structured way.
- Good immediate leverage for agents: it explicitly says to read user-provided pricing, survey, financial, or usage files first and use web search if needed.
- No supporting scripts, references, or resources were included, so the skill relies entirely on the prompt text for execution.
- No install command or repo/file references are present, which limits onboarding clarity and makes adoption slightly less self-serve.
Overview of pricing-strategy skill
The pricing-strategy skill helps you design or evaluate pricing with a value-first lens: what the product delivers, what customers would pay, and which pricing model best matches the business. It is a good fit if you need a pricing-strategy for Pricing Strategy work such as setting a new price, rethinking tiers, comparing freemium vs paid, or pressure-testing a change against competitors.
What this skill is for
Use the pricing-strategy skill when the real job is not just “pick a number,” but make a pricing decision that fits product value, customer segments, and market context. It is most useful for SaaS, APIs, and products with clear usage, seat, or outcome differences.
What makes it useful
The repo pushes you to assess value delivered, alternatives, willingness to pay, and price elasticity before recommending a model. That makes the output more decision-ready than a generic pricing prompt because it forces tradeoffs between flat-rate, per-seat, usage-based, tiered, freemium, and value-based approaches.
Best-fit users and misfit cases
This skill is best for founders, product managers, growth teams, and agents preparing a pricing memo or launch recommendation. It is a weaker fit if you need deep econometrics, advanced market research, or a full financial model; in those cases, use it as a framing tool, then bring in dedicated analysis.
How to Use pricing-strategy skill
Install and locate the source
Install with npx skills add phuryn/pm-skills --skill pricing-strategy. After install, start with SKILL.md; in this repo there are no supporting rules/, references/, resources/, or helper scripts, so the skill lives almost entirely in that single instruction file.
Give the skill decision-grade input
For better pricing-strategy usage, do not ask only “what should we charge?” Provide the product type, target customer, current model, competitor set, usage or seat pattern, cost drivers, and the decision you want made. A strong prompt looks like: “Evaluate pricing for a B2B AI note-taking app for sales teams. Current plan is flat-rate. Compare tiered vs per-seat vs usage-based, using our competitor list and assuming strong collaboration value but variable usage.”
What to ask it to produce
Ask for a recommendation, the rationale, the model alternatives rejected, and the pricing risks. If you want a practical outcome, request concrete artifacts such as a proposed tier structure, launch price ranges, packaging rationale, or questions to validate willingness to pay. That gives the skill enough direction to move from strategy into execution.
Workflow that improves output
Read SKILL.md first, then feed the skill any files you already have: competitor pricing tables, survey notes, financial assumptions, usage data, or customer interviews. If no files exist, instruct the agent to research competitor pricing before drafting a recommendation. Use the first answer to narrow the model choice, then iterate on tier boundaries, discounting, and upgrade triggers.
pricing-strategy skill FAQ
Is pricing-strategy just a generic prompt?
No. The pricing-strategy skill gives you a repeatable framework for comparing pricing models, testing willingness to pay, and tying price to delivered value. A generic prompt often skips the alternatives and jumps straight to a price.
When should I not use this skill?
Do not use it as a substitute for full market research, legal review, or detailed revenue modeling. If the product has highly regulated pricing constraints, complex enterprise negotiations, or sparse customer data, treat this skill as the starting layer, not the final answer.
Is it beginner-friendly?
Yes, if you can describe your product clearly. Beginners get the most value when they bring a simple brief: customer type, product value, competitor benchmarks, and the decision deadline. Without that input, the output can stay too abstract.
How does it fit with a broader product workflow?
It fits after product positioning and before launch or reprice decisions. The skill is strongest when paired with customer discovery, competitor scanning, and a quick financial sanity check.
How to Improve pricing-strategy skill
Give sharper market context
The best way to improve pricing-strategy results is to describe the customer alternative and the measurable value your product creates. “Saves time” is weaker than “reduces analyst prep from 3 hours to 20 minutes,” because the latter helps anchor willingness to pay and model choice.
Share constraints early
Tell the skill about margin floors, sales motion, procurement friction, channel conflicts, or packaging limits. Those constraints often change the right answer more than feature lists do. If you omit them, the first draft may recommend a model that is elegant but hard to ship.
Ask for validation, not just a recommendation
After the first output, ask it to identify what must be true for the recommendation to work and what evidence would falsify it. For example: “What customer interviews, pricing tests, or usage signals would confirm tiered pricing is better than per-seat pricing?” That turns the pricing-strategy skill into a useful iteration tool instead of a one-shot opinion generator.