Skip to content

borghei/Claude-Skills / project-management/execution/pricing-prd

pricing-prd

Verified

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.

assets/grandfathering_communication_template.md

View on GitHub
# Grandfathering Communication Template

Customer email for a pricing change with grandfathering. Three variants for different scenarios. The template addresses the questions customers actually have:

1. What's changing?
2. When?
3. What does it mean for me specifically?
4. Do I have a choice?
5. Who can I talk to?

Send from a real human (PM, founder, or VPE), not a generic alias.

---

## Variant A — Price increase with 12-month grandfathering

**Subject:** A change to your {product} subscription

Hi {first_name},

I'm writing to let you know about a change to our pricing. I want to be upfront about what's changing, why, and what it means for you specifically.

**What's changing**

On {date}, we are updating the price of the {tier name} plan from ${old_price} to ${new_price} per month. The change applies to all new customers from that date.

**What this means for you**

Because you are an existing customer, **your current price of ${old_price}/month will remain in effect through {grandfathering_end_date} ({duration} months from today)**. After that, your subscription will move to the new price of ${new_price}/month at your next renewal.

We're giving you {duration} months because we want you to have time to plan for the change, and because we appreciate the trust you've placed in us by being an early customer.

**Why we're making this change**

A short, honest explanation. Examples:

- We've added significant new capabilities since you signed up — {specific examples}. The new pricing reflects what the product does now.
- Our infrastructure costs have grown as we've scaled to support customers like you. We've absorbed most of these costs, but maintaining our service level requires this adjustment.
- We're investing more in {specific area customers will recognize}, and this pricing supports that investment.

We aren't doing this lightly. It's the first price change in {N years/months}, and we expect the new price to remain stable for at least {N years} from launch.

**What you can do**

- **Do nothing**: your current price continues through {grandfathering_end_date}. We'll send you a reminder 60 days before that date.
- **Switch to annual billing now** to lock in the current monthly-equivalent for an additional 12 months at our current annual discount.
- **Reach out**: if you have questions or this is a significant change for your team's budget, reply to this email and I'll personally make sure we figure it out together.

**Common questions**

- *Will my features change?* No. Your current feature set continues unchanged through grandfathering.
- *Will my data move?* No. No technical changes.
- *Can I downgrade instead?* Yes — you can move to {lower tier} at any time at its current price.
- *What if I don't want to migrate at all?* If the new price doesn't work for your team, we'll help you export your data and offer a final-month refund.

Thank you for being a customer. If anything in this email is unclear or feels unfair, please tell me directly.

{exec_name}
{exec_title}

---

## Variant B — Pricing model change (per-seat to usage-based)

**Subject:** We're changing how {product} is priced — and what it means for you

Hi {first_name},

I want to walk you through a change to how we price {product}. This is a bigger change than a typical price update, so I'm going to be explicit about every aspect.

**What's changing**

Today, {product} is priced per user at ${old_price}/user/month. On {date}, we are moving to a usage-based model: ${platform_fee}/month + ${unit_price} per {unit}.

We're making this change because we've heard repeatedly that per-user pricing penalizes teams for the wrong thing. The value of {product} doesn't scale with seats — it scales with {actual value metric, e.g. "events processed", "decisions made", "automations run"}.

**What this means for you**

Based on your current usage over the past 90 days, your bill under the new model would be approximately **${projected_new_bill}/month**, compared to your current **${current_bill}/month**.

- If your projected new bill is lower: we'll move you to the new model on {date} and you'll save money.
- If your projected new bill is higher: you'll stay on per-user pricing at your current rate for {grandfathering_duration} months. After that, we'll work with you to find the right plan.

You can see your detailed usage and projected bill in your account: {link}.

**Why we're doing this**

A short, honest paragraph. Examples:

- Customers told us per-user pricing was preventing them from rolling out {product} to their full teams. Removing the seat-based gate aligns our success with theirs.
- Per-user pricing makes us harder to compare against the right alternatives. The new model is closer to how the market evaluates products in this category.
- We expect this model to be more predictable for you because {reason}.

**Safeguards**

We know "usage-based" can sound scary. Here's what we're doing to make it not scary:

- **No bill shock**: you can set a hard spend cap, and we'll halt your service rather than overrun it (with your consent).
- **Alerts**: you'll get notified at 50%, 75%, and 90% of your projected monthly spend.
- **Pricing calculator**: an in-app tool that lets you model "what if we doubled our usage?".
- **Grandfathering**: if you're worse off under the new model, you stay on the old model.

**What to do next**

1. **Review your projected bill**: {link}.
2. **Set up a spend cap or alerts**: {link}.
3. **Reach out** if anything is unclear, especially if your projected bill is materially different from what you're paying today.

This is a real change, and I expect questions. Reply to this email and the response will come from a human, not a bot.

{exec_name}
{exec_title}

---

## Variant C — Tier sunset (with migration path)

**Subject:** Important: changes to your {tier name} plan

Hi {first_name},

I'm writing to give you advance notice that the {tier name} plan you're currently on will be retired on {date}. This email explains what's happening, why, and what your options are.

**What's changing**

On {date}, we are retiring the {tier name} plan for all customers. New customers can no longer sign up for it as of today.

**Why we're doing this**

A short, honest paragraph. Examples:

- The {tier name} plan was created for a specific use case ({use case}) that has evolved. Customers in this segment are better served by {alternative}.
- Maintaining a tier with declining adoption pulls engineering capacity away from improvements that benefit more customers.
- We're simplifying our pricing from N tiers to (N-1) tiers based on customer feedback.

**Your options**

Because you're currently on {tier name}, you have three paths:

1. **Migrate to {recommended tier}**: closest match in capabilities. Price would be ${recommended_price}/month — a difference of ${delta} from your current ${current_price}/month.
2. **Migrate to {alternative tier}**: lighter option if the recommended tier is more than you need. Price would be ${alternative_price}/month.
3. **Stay on {tier name} through grandfathering**: you can remain on your current plan through {grandfathering_end_date}, after which you'll need to choose one of the above options.

**What you should do**

- **By {decision_date}**: tell us which option you'd like, or let us know you'd like to talk through the decision.
- **If we don't hear from you**: we'll move you to {recommended tier} at the end of the grandfathering period.
- **Migration is reversible**: if you migrate now and decide it's not right, we'll let you switch back during the grandfathering window.

**Common questions**

- *Will my data move?* Yes — same account, same data, same workflows.
- *Will I lose features?* Most likely no. If your usage pattern includes anything tier-specific, we'll flag it explicitly when you choose your migration path.
- *Can I cancel?* Yes, at any time. We'll help you export your data.

If this change is disruptive for your team, please tell me directly. We can offer migration credits, extended grandfathering, or a custom path for customers where the standard options don't fit.

{exec_name}
{exec_title}

---

## Customization checklist

Before sending any of these templates, customize:

- [ ] Recipient list filtered to the actual grandfathering cohort
- [ ] Per-customer projected bills computed (Variant B)
- [ ] Per-customer current tier and migration recommendation (Variant C)
- [ ] Real exec name and title in the signature (not "The team")
- [ ] Reply path goes to a real human, not an unmonitored alias
- [ ] Legal review for the region(s) of recipients
- [ ] Comm timing aligned with the published pricing page launch (do not send pre-launch surprise)
- [ ] Sales and CSM teams briefed before the email goes out
- [ ] Support team has macros for the top 5 questions this email will generate

## Anti-patterns

- Sending from a generic alias (`updates@company.com`) — destroys trust
- Burying the price in paragraph 4 — say it in paragraph 1
- Marketing-speak framing ("exciting changes") — customers can tell, and resent it
- Quiet rollout without email — customers find out at billing time, much worse
- Promising things ("this will be the last price change forever") — never make that promise
- Omitting the customer's specific impact ("the new prices are: ...") — customers need to know what THEY pay
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall