pricing-prd
/pricing-prd
Pisze PRD zmiany cennika: model i pakietowanie, projekt eksperymentu, zasady dla obecnych klientów, komunikację i progi wycofania.
- Autor
- borghei ↗
- Repozytorium
- Claude-Skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 10
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pisze PRD zmiany cennika: model i pakietowanie, projekt eksperymentu, zasady dla obecnych klientów, komunikację i progi wycofania.
Oryginalny opis (EN)
Write the PRD for a pricing change: model and packaging, experiment design, grandfathering, communication and rollback thresholds. Use when turning a pricing decision into an experiment, a pricing-page launch or a tier change.
Jak działa
- Overview
- Core Capabilities
- When to Use
- Clarify First
- Workflow
- Anti-Patterns
- References
- Files
- Scope & Limitations
- Integration Points
Podgląd SKILL.md
--- name: pricing-prd description: > Write the PRD for a pricing change: model and packaging, experiment design, grandfathering, communication and rollback thresholds. Use when turning a pricing decision into an experiment, a pricing-page launch or a tier change. license: MIT + Commons Clause metadata: version: 1.0.2 author: borghei category: project-management domain: pm-execution updated: 2026-11-08 tech-stack: [pricing-prd, ab-testing, packaging, van-westendorp, monetizing-innovation] tags: [pricing, prd, packaging, ab-test, grandfathering, monetization] --- # Pricing PRD (Tactical) ## Overview A pricing PRD is the tactical artifact that converts a pricing strategy into a shipped change. Where `business-growth/pricing-strategy/` decides "we are moving from per-seat to per-usage and adding an enterprise tier", a pricing PRD decides "here is the page, the experiment, the rollout, and the rollback". Most PMs underinvest in this artifact — they treat pricing as a marketing problem until the rollout breaks revenue. This skill is opinionated about the structure of a pricing PRD (distinct from a feature PRD), the discipline of pricing experiments (small samples + revenue sensitivity == high risk of false-positive readouts), grandfathering and communication (the most-often-skipped sections that cause the most damage), A/B testing pricing without confusing customers or violating consumer-law principles, and rollback criteria written in advance rather than improvised under pressure. Source frameworks are listed in `references/pricing-prd-playbook.md`. ## Core Capabilities - **PRD structure** — the 13-section pricing PRD: pricing model, packaging, grandfathering, communication plan, A/B design, rollback, regional pricing, on top of the standard PRD spine. - **Pricing model & packaging decisions** — tier / usage / hybrid / per-seat / outcome-based selection with rationale; value carriers, tier boundaries, trial mechanisms. - **Willingness-to-pay research** — Van Westendorp, conjoint, and revealed-preference experiments. - **Experiment discipline** — hypothesis, primary metric, MDE, sample size, holdout, stop conditions, mix-shift detection. - **Risk management** — grandfathering policy, multi-channel communication plan, pre-written rollback thresholds, regional/compliance decisions. ## When to Use - Launching a new pricing model or tier - Updating prices on existing packages - Adding usage-based components to a previously flat-fee product - Reshaping packaging (moving features between tiers, sunsetting a tier, adding entitlements) - Running a pricing A/B test - Localizing prices to a new region or currency - Splitting self-serve and enterprise pricing surfaces **When NOT to use:** for the strategic question "should we change pricing at all?" (use `business-growth/pricing-strategy/`); for the financial-modeling side (use `finance/` skills); for SKU/billing implementation (engineering tickets generated from this PRD). ## Clarify First Before generating the pricing PRD, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used. - **Pricing model change:** tier / usage / hybrid / per-seat / outcome-based shift (drives the pricing-model + packaging sections). - **Existing customers' fate:** the grandfathering policy (drives the most-skipped grandfathering + communication sections that cause the most damage). - **Experiment vs hard launch:** A/B test or direct rollout (drives the experiment-design section: hypothesis, MDE, holdout). - **Rollback trigger:** the revenue/conversion threshold that aborts the change (drives the pre-written rollback criteria). Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top. ## Workflow 1. **Confirm the decision is made.** If "should we change pricing at all?" is still open, that belongs to `business-growth/pricing-strategy/`; this PRD ships a decision. 2. **Write the model and packaging sections** from `assets/pricing_prd_template.md`: what changes, for whom, and which value carrier each tier sells. 3. **Decide test or launch** [RECOMMENDED]. Pricing tests have small samples and revenue-sensitive readouts, so false positives are common. Run an A/B test only when the expected traffic reaches the sample size for your minimum detectable effect within the test window (worksheet: `assets/pricing_experiment_design.md`); otherwise launch to new customers only, with a holdout or a staged region, and say why. Use revenue per visitor or per account as the primary metric, not conversion alone. 4. **Write grandfathering and the communication plan** before the launch date: who keeps the old price, for how long, and the message each segment receives (`assets/grandfathering_communication_template.md`). 5. **Pre-write rollback thresholds**: the metric, the threshold, the window, and who decides. 6. **Check the page** with `assets/pricing_page_checklist.md`. **Done when** the PRD names the primary metric and its sample-size calculation (or the reason there is no test), the grandfathering policy, and a rollback threshold someone has agreed to act on. ## Anti-Patterns ### Van Westendorp without segmentation **Mistake:** One aggregate Van Westendorp curve across all respondents sets a single price for every segment. **Why it happens:** One curve is simpler to present, and the sample feels too small to split. **Instead:** Report the curves per segment (SMB, mid-market, enterprise) and price each tier inside its segment's IPP-to-OPP band. Treat the aggregate curve as informational only. ### Conversion as the primary test metric **Mistake:** A cheaper variant lifts conversion, the team ships it, and 90 days later ARPU and retention are down. **Why it happens:** Conversion moves fast and is easy to read inside a short test window. **Instead:** Make ARPU (revenue per visitor) the primary metric in `assets/pricing_experiment_design.md`. Track trial-to-paid, D30 downgrade and D90 retention as secondary metrics. If the primary-metric line says only "conversion rate", rewrite it. ### Testing prices on existing customers **Mistake:** The A/B split includes logged-in customers, who see a different price from the one they signed up at. **Why it happens:** Splitting all traffic is the default setup and gives the largest sample. **Instead:** Limit eligibility to anonymous visitors and new signups who haven't seen a price yet. Exclude existing customers and price-freeze contracts, get Legal sign-off on eligibility, and disclose pricing experiments in the Terms and the pricing FAQ. Nine more, each with a bad and a good example: `references/red-flags.md`. ## References Pull the reference that matches the task; keep this file lean and load detail on demand. - **[references/pricing-prd-playbook.md](references/pricing-prd-playbook.md)** — the full end-to-end playbook: pricing-PRD-vs-feature-PRD table, model decision, willingness-to-pay methods, packaging, grandfathering, communication plan, A/B test design, rollback criteria, regional pricing, UX checklist, anti-patterns, 12-step workflow, tools/assets table, troubleshooting, success criteria, and source frameworks. Read when authoring any pricing PRD. - **[references/pricing-experimentation-guide.md](references/pricing-experimentation-guide.md)** — deep guide on pricing A/B tests, mix-shift detection, and readout windows. Read when designing or reading out a pricing experiment. - **[references/packaging-frameworks.md](references/packaging-frameworks.md)** — tier vs usage vs hybrid frameworks and Ramanujam-style packaging. Read when deciding what goes in which tier. - **[references/red-flags.md](references/red-flags.md)** — concrete examples of how pricing PRDs go wrong and how to fix them. Read when reviewing a draft for quality. ## Files | File | Purpose | |---|---| | `assets/pricing_prd_template.md` | 13-section pricing PRD template | | `assets/pricing_experiment_design.md` | Test design worksheet: hypothesis, MDE, sample size, holdout | | `assets/pricing_page_checklist.md` | Pricing-page UX review | | `assets/grandfathering_communication_template.md` | Customer email for grandfathering | | `examples/usage-based-tier-pricing-prd.md` | Worked pricing PRD | ## Scope & Limitations **In Scope:** Tactical pricing PRD authoring, willingness-to-pay research summary (Van Westendorp, conjoint), packaging decisions, grandfathering policy, customer/sales/support communication plan, A/B test design, rollback criteria, regional pricing decisions, pricing-page UX checklist, anti-pattern avoidance. **Out of Scope:** Strategic pricing question "should we change pricing at all?" (see `business-growth/pricing-strategy/`). Financial modeling and revenue projection (see `finance/`). Billing and subscription-management implementation (engineering tickets). Detailed conjoint analysis methodology (specialist tooling). Legal review of pricing terms in regulated jurisdictions (must involve actual legal counsel; this skill is not legal advice). **Important Caveats:** - Pricing changes have asymmetric risk. A bad pricing change can erase a year of growth. The PRD discipline (rollback criteria, holdout, communication plan) is risk management, not bureaucracy. - A/B testing pricing on identified customers carries consumer-law risk in some jurisdictions. When in doubt, test on anonymous visitors only and consult legal. - The Van Westendorp method has known limitations — stated preference rather than revealed, feature-blind, segment-aggregated. Use as one input among three, not as the answer. - Pricing-page UX changes can be confounded with pricing-model changes in A/B tests. Run UX-only experiments separately from model-change experiments to attribute the lift correctly. ## Integration Points | Integration | Direction | What flows | |---|---|---| | `business-growth/pricing-strategy/` | Receives from | Strategic direction (new model, new tier, new segment) becomes the input to the tactical PRD | | `create-prd/` | Extends | Pricing PRD uses sections 1-2 of standard PRD plus 11 pricing-specific sections | | `feature-flag-strategy/` | Feeds into | Pricing rollout uses feature flags for tier entitlements and rollback | | `activation-funnel/` | Bidirectional | Pricing changes affect activation rates; activation funnel measures the impact | | `customer-feedback-triage/` | Receives from | Pricing-related feedback clusters surface willingness-to-pay signals and bill-shock issues | | `finance/` | Bidirectional | Finance models the revenue projection; pricing PRD constrains the model assumptions | | `senior-pm/` | Feeds into | Pricing change becomes a portfolio risk and an executive update item | | `prfaq/` | Feeds into | A new pricing model often warrants a PR/FAQ for internal alignment | | `eol-communication/` | Pattern overlap | EOL of a pricing tier uses similar grandfathering and communication patterns | | `launch-playbook/` | Feeds into | Pricing-page launch follows standard launch playbook for internal/external comm coordination |
Pliki w paczce (10)
- SKILL.md 11 KB
- assets/grandfathering_communication_template.md 9 KB
- assets/pricing_experiment_design.md 4 KB
- assets/pricing_page_checklist.md 5 KB
- assets/pricing_prd_template.md 7 KB
- examples/usage-based-tier-pricing-prd.md 15 KB
- references/packaging-frameworks.md 10 KB
- references/pricing-experimentation-guide.md 9 KB
- references/pricing-prd-playbook.md 19 KB
- references/red-flags.md 17 KB
Wersje
W bazie nie ma innych skilli o nazwie pricing-prd.
Migawka bazy z 13.11.2026 · wersja paczki c25931fa1bea (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100prd-v03-pricing-model
Dobiera i weryfikuje model cenowy w PRD v0.3: progi planów, gotowość do zapłaty i reguły cenowe na podstawie analizy konkurencji i typu produktu. - 100deal-pricing
Projektuje strategię cenową i pakietowanie produktu: progi cenowe, metryki wartości, ceny dla klientów korporacyjnych, model freemium oraz tekst strony z cennikiem. - 100pricing-packaging
Rekomenduje modele cenowe, struktury pakietów, metryki wartości i wskazówki do strony z cennikiem. - 100competitive-pricing-packaging-review
Analizuje lub weryfikuje cennik i pakietowanie własnego produktu na tle ofert konkurentów, zmian cen i dowodów od klientów, wspierając decyzje o monetyzacji. - 90pricing-strategy
Projektuje model cenowy ze strukturą poziomów, metrykami wartości i rekomendacjami pakietów oraz tworzy wskazówki do tekstu strony cennika, porównania cen konkurencji i strategię monetyzacji. - 100pm-pricing
Analizuje cennik SaaS: metryki wartości, pakietowanie, badanie gotowości do zapłaty, pozycjonowanie wobec konkurencji i projekt modelu cenowego.