rate-increase-plan
Skill1 starsChanged 16 days agoMITView on GitHub
Use this skill when rates have not moved in a year or more and the firm is carrying clients at numbers it would never quote today. Produces who moves and who does not, what each one goes to, who gets grandfathered and why, the order to tell them in, and the message for each. Also use for "we need to raise rates", "put our prices up", "this client is underpriced", "how do I tell them the retainer is going up".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 45
MUST put current price, today's quote and the gap in one place for every client.
- Distinctive: line 46
MUST set the new number per client rather than one percentage across the book.
- Distinctive: line 47
MUST write a reason beside every client who is not moving.
- Distinctive: line 48
MUST lead the message with the number and the start date.
- Distinctive: line 49
MUST decide the fallback before the conversation.
- Distinctive: line 50
MUST set a review date.
- Distinctive: line 51
NEVER grandfather a client because the conversation is uncomfortable.
- Distinctive: line 52
NEVER open with a justification.
- Distinctive: line 53
NEVER improvise a concession during the call.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Applies to a book of existing clients priced below what the firm charges new ones. Produces the plan and the conversations, not a new rate card.
The play
- List every client with what they pay, what the same work would be quoted at today, and how long they have been at the current number. The gap column is the whole exercise, and most firms have never put it in one place.
- Sort by gap, not by size. The client paying furthest below current rates is the priority regardless of how much revenue they represent, because the size of the gap is what determines how awkward the conversation gets the longer it waits.
- Decide who does not move, deliberately, and write the reason next to each. Grandfathering is a legitimate choice. Grandfathering by default because the conversation is uncomfortable is how a firm ends up with half its revenue at two-year-old prices. Reasons that hold: they were a design partner, they took a risk early, they refer consistently, they are a reference you need. Reasons that do not: they are nice, they might leave.
- Set the new number per client rather than applying one percentage across the book. A flat increase under-corrects the worst gaps and over-corrects the ones already close to current rates.
- Decide the order you tell them in. Start with the client most likely to say yes, not the one with the biggest gap. The first conversation teaches you where the resistance actually is, and you want to learn that on an easy one.
- Write the message per client. Lead with the new number and the date it starts. Do not open with an explanation, do not apologise, and do not offer a justification nobody asked for, which invites a negotiation about whether the reasoning is sound rather than about the price.
- Decide the fallback before each conversation, not during it. A longer notice period, a phased step over two quarters, or a reduced scope at the old number. Going in without one means improvising a discount under pressure.
- Set a review date so this does not become a once-every-three-years event. The size of the conversation is a function of how long it was avoided.
What good looks like
- First thing I check that most people skip: what the firm would quote this exact client today, as a new deal. Not a percentage uplift, the real current number. The gap between that and what they pay is usually larger than anyone expects and it is the only honest basis for the conversation.
- The mediocre version: a flat percentage emailed to the whole book on the same day. It treats a client who is 40% under the same as one who is 5% under, and it guarantees the worst-priced clients stay the worst-priced.
- I know it is right when every client staying at the old rate has a written reason that is not "awkward".
- Second test: I know my fallback for each conversation before I open it.
- Red flag: the plan has been written and not sent for three weeks. The plan was never the hard part.
Rules
- MUST put current price, today's quote and the gap in one place for every client.
- MUST set the new number per client rather than one percentage across the book.
- MUST write a reason beside every client who is not moving.
- MUST lead the message with the number and the start date.
- MUST decide the fallback before the conversation.
- MUST set a review date.
- NEVER grandfather a client because the conversation is uncomfortable.
- NEVER open with a justification.
- NEVER improvise a concession during the call.
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.

