skills/pricing-conversation-framework/SKILL.md
Structures pricing discussions with customers including renewal pricing, discount requests, price increases, and competitive pricing pressure. Provides frameworks for leading with value, handling objections, and knowing when to concede versus when to hold. Use when asked to prepare for a pricing conversation, handle a discount request, communicate a price increase, respond to competitive pricing, or when any commercial discussion involves pricing. Also triggers for questions about pricing strategy, discount negotiation, price increase communication, commercial conversations, or handling the "it is too expensive" objection.
npx skillsauth add stephenrogan/csm-skills pricing-conversation-frameworkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structures pricing discussions so the CSM leads with value, handles objections constructively, and knows when to concede versus when to hold firm. Pricing conversations are where the CSM's value as a trusted advisor is tested most directly -- and where most CSMs feel least comfortable.
Provide:
Every pricing conversation follows one rule: establish value before discussing price. A customer who believes they are getting 5x ROI will negotiate differently than a customer who is unsure of the value. The pricing conversation is won or lost before the first number is mentioned.
Sequence:
The customer expects: The same price for the same product. Your position: Value has been demonstrated. Price is justified. Approach: "Your team achieved [outcome] this year. At the current investment, that represents a [X]x return. We will continue at the same terms for the renewal." If they push back: Investigate why. If value is clear and they still resist, the objection is about something else (budget, leverage, or competitive).
The customer expects: Stability or improvement, not a cost increase. Your position: You need to justify the increase with something the customer gains. Approach: Lead with what is changing that benefits them (new features, improved support, platform investment). Frame the increase as investment in the value they depend on.
Structure:
What not to do: Do not apologise for the increase. Do not lead with the number. Do not bury it in paragraph four. State it directly after establishing context.
The customer expects: A lower price. Your priority: Understand why before responding.
Five reasons customers ask for discounts -- each has a different response:
| Reason | Signal | Response | |--------|--------|---------| | Budget constraint (real) | Budget cut, hiring freeze, cost reduction initiative | Explore options: annual vs. monthly, reduced seats, different tier. Discount as last resort, tied to a longer commitment | | Value perception gap | "We are not getting enough value for the price" | This is a value problem, not a pricing problem. Address the value gap before discussing price. If value improves, the pricing objection may disappear | | Competitive pricing | "Competitor X is cheaper" | "What does Competitor X offer for that price?" Compare on ROI, not sticker price. If they are genuinely cheaper for equivalent value, you may need to adjust | | Negotiation tactic | Asking because it works. No genuine budget pressure or competitive threat | Hold firm. "The pricing reflects the value we deliver. I want to make sure the value case is clear -- let me walk through what your team has achieved" | | Precedent expectation | They received a discount last time and expect it again | This is the most common and most dangerous. Address it directly: "The initial discount was a one-time incentive. The renewal is at standard pricing based on the value delivered" |
Discount rules:
The customer says: "Competitor X is 30% cheaper." Your response framework:
For each pricing situation, the skill produces:
development
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.