renewal-negotiation
Skill2 starsChanged 3 months agoMITView on GitHub
Use when the user says "they want a discount", "procurement is involved", "how much can I give", "they want to cut seats", "competitor quoted us half", "prep the renewal negotiation", or "they are asking for utilization data". Produces a concession ladder (give, get, cost per rung), a written walk-away, the exact sentence for what is not on the table, and who holds the real deadline. Not for deciding if they will renew (use renewal-risk) or delivering a price increase (use hard-conversation).
In this repository54 other files it gives its agents.
- account-contextSkill
- account-planSkill
- account-reviewSkill
- adoption-planSkill
- advocacy-askSkill
- book-reviewSkill
- book-triageSkill
- business-reviewSkill
- call-prepSkill
- call-recapSkill
- champion-lossSkill
- churn-postmortemSkill
- coachingSkill
- commitmentsSkill
- coverage-modelSkill
- csm-hiringSkill
- csm-rampSkill
- csql-motionSkill
- cs-scorecardSkill
- cs-startSkill
- customer-updateSkill
- day-planSkill
- email-criticSkill
- escalationSkill
- exec-conversationSkill
- expansion-caseSkill
- expansion-scanSkill
- handoffSkill
- hard-conversationSkill
- health-scoreSkill
- internal-askSkill
- invoice-chaseSkill
- mutual-action-planSkill
- nrr-narrativeSkill
- offboardingSkill
- onboarding-planSkill
- one-pagerSkill
- playbook-builderSkill
- portfolio-reviewSkill
- price-increaseSkill
- renewal-forecastSkill
- renewal-riskSkill
- renewal-runwaySkill
- sales-handoffSkill
- save-planSkill
- stakeholder-mapSkill
- status-updateSkill
- survey-follow-upSkill
- team-rollupSkill
- usage-emailSkill
- value-ledgerSkill
- voice-of-customerSkill
- what-do-i-oweSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
If the user gave the account, ARR, term end and what the customer is asking for, go straight to "Do this".
- Distinctive: line 35
Use this skeleton. Concessions and numbers are suggestions for the user to confirm.
- Distinctive: line 65
Price needs value on the other side of the scale: If they have not agreed the thing is worth having, you argue a number against nothing and …
- Distinctive: line 71
The opt-out date is leverage for whoever knows it: If silence renews, they are under time pressure, not you.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Renewal Negotiation
A one-page plan to walk into a price conversation knowing what you will trade, what you will not, and where you walk away.
Start here
If the user gave the account, ARR, term end and what the customer is asking for, go straight to "Do this".
Otherwise ask for these in ONE message, then proceed with whatever comes back:
- Account, ARR, term end date, notice period, and whether silence renews or lapses
- What they asked for (discount, fewer seats, competitor price) and from whom
- The lowest number the user's company would accept
The contract, usage and a risk read are a bonus. If an "Account context" block exists in the conversation, use it for pricing model and who signs.
Do this
- Gate it. Is value agreed, meaning can you name a number they would accept as what they got? Is this a negotiation or a decision already taken? A downgrade request often means the scope decision is made. If either fails, say so first and change the plan.
- Pull the contract facts. Opt-out date = renewal date minus notice period, and that is the real deadline. Note auto-renewal, any uplift clause and the term end.
- Write both walk-aways. Yours as a number. Theirs honestly: do nothing, renew smaller, or switch, with the migration cost the person threatening it may not carry. Ask what the competitor demo or pilot actually covered.
- Name what each party is measured on. Procurement usually needs a visible saving, not your margin. List wins that cost you less than a rate cut: term length, payment timing, capped uplift, added scope at near-zero cost, services hours.
- Build the ladder. Three rungs and a floor, each with what you give, what you get, and what it costs in dollars. Lead the output with it.
- Write the not-on-the-table sentence word for word. Say it once, repeat it unchanged.
- Map the time. Whose deadline is real, who escalates on each side, and what you do if they go quiet near the opt-out date.
Output
Use this skeleton. Concessions and numbers are suggestions for the user to confirm; the user sends anything.
RENEWAL NEGOTIATION: [Account] | [ARR] | term ends [date] | opt-out by [date]
Call: NEGOTIATE / VALUE FIRST / BEING INFORMED
Target: $[x] Walk-away: $[floor] Their real alternative: [do nothing / smaller / switch]
Concession ladder
| Rung | I give | I get | It costs us |
| 1 | | | $[x] |
| 2 | | | |
| 3 | | | |
| Floor | below this we do not renew | | $[ARR at risk] |
Not on the table: "[exact sentence]"
Procurement win that is not our margin: [item]
Contract: auto-renew [yes/no] | uplift [clause] | opt-out [date]
Time: [whose deadline is real, and why]
Four asks: discount / low usage / competitor quote / month to month - [one line each]
If it stalls: [who escalates, silence plan, the one thing I will not do]
What I could not check
- [gap, marked (assumed, confirm) inline]A filled example is in examples/sample.md. Match its length and tone.
Rules
- Price needs value on the other side of the scale. If they have not agreed the thing is worth having, you argue a number against nothing and lose.
- Nothing is given free. A free concession tells them the price was never real and invites the next ask.
- Prefer a one-time credit to a rate cut. A credit costs once. A cut compounds every year and becomes the starting number next time. If you must move on rate, give it an end date or a cap.
- Separate rightsizing from rate. "We use 60% of our seats" is a value conversation in a commercial costume. Granting both double-pays them.
- Do not match a quote you have not seen. Half-price quotes are often half the scope, year one only, or without services. A named competitor with no demo behind it is a procurement tactic.
- Utilization data and contract copies are the negotiation starting. Treat it as early, not admin.
- The opt-out date is leverage for whoever knows it. If silence renews, they are under time pressure, not you. Your quarter end is leverage against you once they know it.
- Never close a number on the last three days of a quarter. The calendar set it, and the next owner inherits the price.
Related (only if installed)
renewal-risk first if there is no read yet. hard-conversation for delivering a price increase. expansion-case if scope and renewal are being discussed together.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

