SUN, SEPTEMBER 13, 2026
Independent · In‑Depth · Practitioner‑Tested
Claude General

Terms Change Prompts: 6 for When a Vendor Moves the Goalposts

The Claude Code promotion was extended four times before ending today, and the replacement figure everyone quotes appears in a social post rather than in documentation. That is not unusual — it is how most product changes get communicated. These six prompts are for reading any vendor change and working out what is documented, what is merely announced, and what it actually costs you.

⌨️ 6 prompts 🕐 Updated Sep 13, 2026
💡 How to use these prompts: Replace everything in [BRACKETS] with your specific details before sending. Click Copy to copy any prompt to your clipboard instantly.
1
Separate documented from announced
This is the exact situation with the Claude Code change. The announced number is on no official page.
Here is a vendor announcement: [PASTE]
And here is their official documentation on the same thing: [PASTE OR DESCRIBE]

Tell me:
- What both sources agree on
- What appears only in the announcement
- What appears only in the documentation
- Where they could be read as saying different things

Quote the exact wording for each. A figure that exists only in a social post is not a documented commitment.
2
Work out what it actually costs me
A 17 percent reduction means nothing until you know whether you were near the ceiling.
A vendor is changing terms: [DESCRIBE THE CHANGE]

Given how I use the product: [DESCRIBE], tell me:
- What I lose in practical terms, not percentages
- Whether I would notice
- At what usage level it starts to matter
- What I would need to change if it does

Use my numbers, not theirs. Percentages are chosen to flatter.
3
Check which reference point they used
The whole Claude Code story is one change described as +25% and -17% depending on the starting point.
This announcement claims a change of [X PERCENT]: [PASTE]

Tell me:
- What baseline that percentage is measured against
- What the same change looks like from other reference points
- Which one a current customer would assume
- Whether the framing chosen is the one most favourable to the vendor

Both numbers can be true at once. Tell me both.
4
Find what a temporary measure implies
The Claude Code promo was extended four times before ending. Four chances to be reassured it would continue.
A vendor has extended a temporary offer: [DESCRIBE, INCLUDING HOW MANY TIMES]

Tell me:
- What repeated extension suggests about their intent
- What the risk is of building around it
- What I should do differently from treating it as permanent
- What would signal it is genuinely ending

Do not tell me it will definitely end. Tell me how to plan either way.
5
Draft the question to send them
Support answers are the closest thing to documentation you can get on an undocumented change.
A vendor announcement is ambiguous on: [DESCRIBE]

Write the question I should send support, phrased so a vague answer is obvious. Make it specific enough that they have to give a number or a date rather than a reassurance.

Include what I should do if they do not answer clearly.
6
Build the check that runs monthly
Terms changes are announced on social and documented later, if at all. A monthly check is how you catch them.
I depend on these vendors: [LIST]

Design a short monthly check that would catch a terms change before it affects me. Include what to look at, where, and roughly how long it should take.

Keep it to something I would genuinely do every month. An elaborate process I abandon is worse than none.