Analyzing a SaaS subscription renewal proposal against the original agreement, service performance data, market benchmarks, and downstream customer service commitments to produce a renewal analysis memorandum.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill rnw-saas-subscription-renewal --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Rnw Saas Subscription Renewal?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-rnw-saas-subscription-renewal)More formats (shields.io, HTML) on the badges page.
---
name: rnw-saas-subscription-renewal
task_id: intellectual-property/rnw-saas-subscription-renewal
description: Analyzing a SaaS subscription renewal proposal against the original agreement, service performance data, market benchmarks, and downstream customer service commitments to produce a renewal analysis memorandum.
activates_for: [planner, solver, checker]
---
# Skill: SaaS Subscription Renewal Analysis
## 2. Failure modes the skill is correcting
- Reviewing the renewal proposal in isolation, without comparing it to the original commercial and service terms, which obscures price changes, service dilution, and any reset of negotiated protections.
- Treating performance data as background rather than leverage, which misses unpaid service credits, uncured service failures, or a pattern supporting price relief and tighter renewal terms.
- Ignoring downstream customer commitments, which can create a renewal that is commercially acceptable on paper but operationally insufficient to satisfy resale, pass-through, or customer-facing service levels.
- Assessing pricing without a market comparator, which prevents the memo from identifying whether the proposal is within market range or materially off-market.
- Overlooking auto-renewal and notice mechanics, which can forfeit leverage or lock in a renewal posture the client did not intend.
- Failing to separate issue spotting from recommendation, which leaves the reader with diagnosis but no negotiation path.
## 3. Legal frameworks / domain conventions that apply
- A customer-side SaaS renewal review is a comparative exercise: measure proposed renewal terms against the prior agreement, the actual service record, market pricing, and downstream obligations before concluding whether the proposal is acceptable.
- Renewal economics are often shaped by the original contract’s price-adjustment clause, renewal mechanics, scope definitions, and any vendor discretion to modify service tiers or support levels.
- Service performance matters because service credits, uncured availability failures, support misses, security incidents, and similar departures from commitments can be used as negotiating leverage and may inform breach, cure, or offset analysis under the governing contract.
- Market benchmarking should be treated as a reasonableness check, not a standalone conclusion: a favorable benchmark strengthens a negotiation position; an unfavorable benchmark may justify a narrower concession request.
- Downstream alignment is critical where the customer has committed service levels to its own customers or users; the renewal must preserve enough upstream functionality, support, and uptime to avoid a gap in pass-through obligations.
- Auto-renewal language, notice deadlines, and renewal election provisions control whether silence renews the deal and whether non-renewal notice is needed to preserve leverage.
- The analysis should cite the governing contractual provisions and any source-documented legal or regulatory standards that bear on customer-facing service commitments, but it should not state conclusions without tying them to the operative clause or authority.
## 4. Analytical scaffolds
1. Compare the renewal proposal to the original agreement.
- Identify each material change in price, term length, scope, support, service levels, credits, data rights, indemnities, termination rights, and renewal mechanics.
- Separate true amendments from confirmations of existing language.
2. Assess the service performance record.
- Review performance against each committed metric or operational promise in the source materials.
- Note whether any deficiencies were cured, credited, carried forward, or remain outstanding.
- Translate performance misses into negotiating leverage and contractual consequence.
3. Benchmark the commercial package.
- Compare the renewal price and key service terms against the market materials supplied.
- Distinguish headline price from total economic value, including credits, minimums, fees, and bundled services.
- Identify whether the proposal is market, rich, or below market, and what that means tactically.
4. Test downstream service alignment.
- Cross-check the proposed upstream service levels against the customer-facing commitments the client must meet.
- Flag any mismatch in availability, support hours, response times, data processing, incident handling, or remediation timing.
- State the operational or contractual gap created by any mismatch.
5. Review renewal mechanics and timing.
- Identify auto-renewal, non-renewal notice, true-up, pricing reset, and escalation mechanics.
- Determine whether the client should send notice, negotiate first, or allow renewal to proceed while reserving leverage.
- Tie the timing assessment to the contract deadline or other source-documented milestone.
6. Convert issues into recommendations.
- For each issue, state the proposed negotiation position, the business rationale, and the practical fallback.
- Distinguish terms that are essential from terms that are desirable.
- Close with an overall renewal posture: accept, negotiate, or prepare alternatives.
## 5. Vertical / structural / temporal relationships
- Treat the original agreement as the baseline, the performance record as the leverage layer, the market benchmark as the pricing comparator, and downstream commitments as the operational constraint.
- Read provisions vertically: a renewal clause may be constrained by a price-adjustment clause, which may be affected by service credits, which may in turn affect the business case for notice or non-renewal.
- Read timing temporally: current performance, renewal notice deadline, renewal effective date, and downstream commitment periods may all differ, and each can change the recommendation.
- Where more than one issue, period, or commitment is in scope, enumerate them explicitly before analysis and analyze each separately rather than blending them into a single general statement.
## 6. Output structure conventions
- Prepare a memorandum titled as a renewal analysis, written from the customer-side perspective, using conventional legal-business prose.
- Use clear sections for: executive takeaway, proposed term changes, service performance assessment, market benchmark comparison, downstream service alignment, renewal mechanics and timing, and negotiation recommendations.
- For each issue, include:
- a concise statement of the change or gap,
- the source-based comparator,
- the practical consequence for the client,
- the recommended negotiating position.
- Use an explicit ordinal severity scale defined once near the start of the memo and apply it consistently to each issue.
- Where the source materials support a legal proposition, identify the controlling contractual provision or other governing authority by name and section before stating the conclusion.
- End with a Recommended Actions section that assigns each action to a role and ties it to a concrete deadline or urgency trigger drawn from the record.
- Do not omit the final strategy recommendation; the memo should conclude with the overall renewal path and the next step if negotiations do not resolve the key gaps.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!