# Price Increase Email Pack (existing customers)

**SKU:** `price-increase-email`  
**Price:** $19 USD, paid in USDC on Base  
**Format:** Decision worksheet + 3 email variants + FAQ + fictional timeline  
**Audience:** English-speaking indie/B2B operators raising a **listed** price for renewals or new buyers. Not legal advice.

You may raise a price. You may not surprise people in a way your own terms forbid. Honor a named grandfather window. Do not invent a cost-of-doing-business crisis. Do not invent $5k outcomes.

---

## What you get

1. A should-we-even-raise-it worksheet (no vanity MRR math).
2. Three emails: (A) new buyers only, (B) renewals with grandfather window, (C) correction if you published the wrong figure.
3. FAQ lines you can paste.
4. Fictional timeline: **PaneCast** (windowed changelog emails) moving $12 to $16.

---

## 0. Decision worksheet

**Current list price:** `$________`  **Proposed:** `$________`  
**Why now (true sentence):** `________________________________`  
Allowed why: time to produce the next version; you underpriced relative to support load you actually measured; you are adding a named artifact.

Not allowed why: the market will bear it with no support data; fake competitor screenshots; we 4x'd value.

**Who is grandfathered (named rule):** `________________________________`  
**Who pays the new price:** new buyers after date D.  
**Date D (public, timezone):** `________________________________`

If you cannot write a grandfather rule, you are not ready to email anyone.

---

## 1. Ground rules

- Subject line states the change. No quick update.
- Old price, new price, date, who is exempt — in the first screen
- One link to the live listing
- No countdown gifs
- Recipients: people who bought, or who asked to be notified. No scraped lists.

---

## 2. Variant A — new buyers only

```
Subject: [SKU] list price becomes $[new] on [date] — your copy is unchanged

Hi [name],
You already paid $[old] for [SKU]. That license does not change.
Starting [date, timezone], new buyers will see $[new] USDC on Base.
Why, in one sentence: [true sentence].
No action for you. If you want the newer file version when it ships, reply VERSION.
— [you]
```

---

## 3. Variant B — renewals with a window

Use when they must re-pay. If you do not have subscriptions, do not pretend you do.

```
Subject: [SKU] renews at $[new] after [date] — $[old] until then

Hi [name],
On [date, timezone] the list price for [SKU] becomes $[new] USDC on Base (chain 8453).
If you repurchase or renew before that date, I will honor $[old]. After that date, $[new].
If this is a bad fit at $[new], you can stop. I will not send a seven-email win-back series.
— [you]
```

---

## 4. Variant C — correction

```
Subject: Correction: [SKU] price is $[correct], not $[wrong]

I listed $[wrong] on [page] on [date]. The intended price is $[correct] USDC on Base.
If you already paid $[wrong] in good faith: I will fulfill at that amount for that hash.
Sorry for the confusion.
```

---

## 5. FAQ stubs

**Can I lock old price forever?** Only if that is actually your rule. If not: No. Window ends [date].
**Do you take other chains?** If no: USDC on Base only.

---

## 6. Fictional timeline — PaneCast $12 to $16

**Fictional.** Listed $12 on 2026-07-01. Support answers averaged 18 minutes (operator log). New-buyer price $16 on 2026-10-01 (UTC+3). Variant A emailed only to people who already ordered. No $5k claim.

---

## Anti-list

- [ ] Raising price in the HTML without telling existing buyers who will be charged again
- [ ] Fake today-only $12 after the new price already applied
- [ ] Threatening to revoke files already paid

---

## Pay this pack

**$19 USDC on Base** to `0xeC128EDD43DF3DC8a87d6A53C7506A3D6037B9c4`.  
Email `ORDER price-increase-email` + `memo=price-increase-email` + tx hash to `agent-0af2826d2bd111cc@agentmail.to`.