pricing-conversation-framework
Skill0 starsChanged 8 months agoMITView on GitHub
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.
In this repository57 other files it gives its agents.
- account-strategy-builderSkill
- account-swot-analyserSkill
- action-item-extractorSkill
- book-prioritisationSkill
- business-review-frameworkSkill
- call-summary-generatorSkill
- capacity-calculatorSkill
- career-dev-plannerSkill
- celebration-note-writerSkill
- change-management-advisorSkill
- check-in-email-drafterSkill
- churn-post-mortemSkill
- competitive-threat-assessorSkill
- contract-review-assistantSkill
- cs-investment-case-builderSkill
- cs-metrics-explainerSkill
- customer-apology-crafterSkill
- customer-sentiment-decoderSkill
- difficult-conversation-drafterSkill
- escalation-brief-writerSkill
- escalation-decision-frameworkSkill
- executive-briefing-writerSkill
- executive-engagement-playbookSkill
- executive-outreach-drafterSkill
- expansion-opportunity-scorerSkill
- follow-up-email-writerSkill
- goal-setting-frameworkSkill
- handoff-intro-emailSkill
- internal-debrief-writerSkill
- internal-status-update-writerSkill
- interview-prep-csSkill
- manager-one-on-one-prepSkill
- manual-health-assessmentSkill
- meeting-agenda-builderSkill
- meeting-outcome-loggerSkill
- multi-threading-playbookSkill
- nps-response-analyserSkill
- objection-handlerSkill
- onboarding-plan-builderSkill
- peer-coaching-guideSkill
- pre-call-prepSkill
- presentation-personaliserSkill
- process-audit-worksheetSkill
- qbr-action-trackerSkill
- qbr-content-assemblerSkill
- quarterly-planning-builderSkill
- re-engagement-email-writerSkill
- renewal-conversation-openerSkill
- renewal-risk-scorerSkill
- save-play-designerSkill
- stakeholder-map-builderSkill
- stakeholder-research-prepSkill
- success-plan-creatorSkill
- territory-transition-plannerSkill
- usage-pattern-interpreterSkill
- value-narrative-builderSkill
- week-plannerSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
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 27
Every pricing conversation follows one rule: establish value before discussing price.
- Distinctive: line 58
What not to do: Do not apologise for the increase.
- Distinctive: line 76
Never discount without understanding why
- Distinctive: line 77
Never discount proactively (wait for them to ask)
- Distinctive: line 78
If you discount, tie it to something (longer term, more seats, case study, expansion commitment)
- Distinctive: line 86
Do not panic. Do not immediately offer a discount
- Distinctive: line 87
Ask: "What are you comparing?
- Distinctive: line 89
If the competitor genuinely offers equivalent value at a lower price, you may need to adjust.
- Distinctive: line 98
Follow-up plan (how to close the pricing discussion and move to commitment)
- Distinctive: line 103
Do you know your commercial authority?
- Distinctive: line 110
Every discount sets a precedent.
- Distinctive: line 112
Never compete on price alone.
≈ “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
Pricing Conversation Framework
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.
How to Use
Provide:
- The pricing situation (renewal at current price, price increase, discount request, competitive pricing pressure)
- Current ARR and pricing structure
- Value evidence (ROI, outcomes, usage metrics)
- The customer's stated concern (too expensive, budget cut, competitor is cheaper, need more for the same price)
- Your commercial authority (what you can offer without approval, what requires escalation)
- Relationship context (strong, adequate, strained)
The Value-First Principle
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:
- Confirm value delivered (lead with their outcomes, not your features)
- Frame the investment in context (cost per user, cost vs. manual alternative, cost vs. outcome generated)
- Address the pricing question directly (do not avoid it once value is established)
- Listen for the real objection (price, budget, value, competitive, or leverage)
- Respond to the real objection, not the surface one
Pricing Situations
Renewal at Current Price
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).
Price Increase
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:
- Acknowledge the partnership and value delivered
- Explain what is changing and why (investment in the platform they depend on)
- State the new pricing clearly (amount, effective date, what it includes)
- Connect to specific improvements that benefit them
- Offer to discuss (call, not email, for significant increases)
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.
Discount Request
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:
- Never discount without understanding why
- Never discount proactively (wait for them to ask)
- If you discount, tie it to something (longer term, more seats, case study, expansion commitment)
- Know your authority. If the discount exceeds your authority, say so: "Let me take this back to my team and come back with options"
Competitive Pricing Pressure
The customer says: "Competitor X is 30% cheaper." Your response framework:
- Do not panic. Do not immediately offer a discount
- Ask: "What are you comparing? Is it the same scope, the same capabilities, the same support level?"
- Reframe from price to total cost: "The price difference is EUR 10k/year. Your team saves an estimated 340 hours/year. At your team's loaded cost, that is EUR 50k in productivity. The ROI is 5x even at our current pricing"
- If the competitor genuinely offers equivalent value at a lower price, you may need to adjust. But make sure the comparison is valid first
Output Format
For each pricing situation, the skill produces:
- The recommended approach (value-first framing with specific talking points)
- Prepared responses for likely objections
- Your commercial authority summary (what you can offer without escalation)
- Escalation path (if the customer asks for more than your authority allows)
- Follow-up plan (how to close the pricing discussion and move to commitment)
Quality Gates
- Have you established value before any pricing discussion? If you cannot articulate the customer's ROI in one sentence, you are not ready for the pricing conversation
- Do you know your commercial authority? Walking into a pricing conversation without knowing what you can offer creates either false promises or awkward "let me check" moments
- Are you addressing the real objection? If they say "too expensive" but the real issue is competitive, your value argument will not land
- Are you prepared to hold? Not every discount request deserves a discount. Knowing when to hold firm is as important as knowing when to flex
Principles
- Price is only a problem when value is unclear. A customer who sees 5x ROI does not negotiate the same way as a customer who sees 1.5x ROI. Invest in value evidence before you need it for pricing conversations
- Every discount sets a precedent. A 15% discount this year becomes the expected baseline next year. Discount strategically, not reactively
- The customer's budget is real. Do not dismiss budget constraints as negotiation tactics. If they have a genuine budget problem, work with them on solutions (reduced scope, different payment terms) rather than insisting on the full price. The relationship matters more than one year's revenue
- Never compete on price alone. If the conversation becomes purely about the number, you have lost the framing. Bring it back to value, outcomes, and total cost of ownership
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.

