> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Price Increase Letter

> Draft the client notice for an agreement price change — value-first framing, a clear effective date, and an honest one-line rationale — gated behind account-manager approval before anything leaves the desk.

<Info>
  **Category:** Communication · [View source ↗](https://github.com/bryan-getthread/skills/blob/main/skills/communication/price-increase-letter/SKILL.md)
</Info>

**Connectors:** none — works with Thread out of the box

**Role:** [CSM / Account Manager](/start-here/roles/csm-account-manager)

**Outcome:** Retention & Growth (CSAT/Expansion)

**When to use:** "Draft the price increase letter for \<client>" / "our rates go up \<date> — help me write the notice" — an agreement renewal or rate change needs formal written notice.

**Run it:** on one client's notice.

## Prompt

```
Draft a price change stated plainly, anchored to the value delivered, with a real effective
date — and no apology-spiral that invites the client to negotiate the letter instead of the
agreement.

1. Collect these facts from me before writing — NONE may be invented or inferred: the new
   price or percentage, the effective date, what agreement/services it covers, and the notice
   period the agreement requires. If any is missing, ask; do not draft around a blank.

2. Optionally pull supporting context: recent delivered work from the ticket history (resolved
   counts, projects completed, response performance) to ground the value paragraph in this
   client's actual service history — not generic claims.

3. Draft in this order:
   - Value first: one short paragraph on what the relationship has delivered — specific to
     this client where the record supports it.
   - The change: the new price/percentage and exactly what it applies to, stated once, plainly.
     No burying it below the fold.
   - Effective date: its own line. If the agreement requires a notice period, the date must
     respect it.
   - Honest rationale: one or two sentences max ("rising vendor and labor costs," "expanded
     coverage under your plan"). True, brief, done.
   - Next step: who to contact with questions — the account manager by name/role, not "the team."

4. Tone check: confident and respectful. Exactly one expression of appreciation; zero
   apologies. Cut any sentence that hedges the decision ("we hate to do this," "we hope you
   understand") — the change is decided, the letter informs.

5. Show me the draft labeled "PRICE INCREASE DRAFT — REQUIRES ACCOUNT MANAGER APPROVAL — do
   not send." State that AM sign-off on numbers, date, and framing is the gate before sending.

AM approval gate is absolute: never send, schedule, or hand off this letter for delivery. Never
invent or estimate numbers, percentages, effective dates, or notice periods; if my date
violates the agreement's notice period, flag it instead of drafting around it. No apology-spiral
— one thank-you, no sorries. Don't offer discounts, grandfathering, or exceptions unless I
provide them. Never name or compare other clients' pricing.
```


## Related topics

- [RFO Letter](/skill-library/change-and-problem-management/rfo-letter.md)
- [Renewal Prep](/skill-library/account-management/renewal-prep.md)
- [Zero-Touch Opportunity Mining](/skill-library/reporting-and-analytics/zero-touch-opportunity-mining.md)