# Assess Saas Renewal Pricing Sla > Contract review memorandum evaluating renewal pricing and service-level modifications against the operative agreement and historical performance data. - Skill: `finchipaiorg/assess-saas-renewal-pricing-sla` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/assess-saas-renewal-pricing-sla` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/assess-saas-renewal-pricing-sla/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/assess-saas-renewal-pricing-sla --- # Skill: Assess SaaS Renewal Pricing and SLA Changes ## 1. Subject-matter triage (only if applicable) - Identify the operative document set before analyzing economics or service terms: the base MSA, the renewal package, any order form, amendment, proposal, exhibit, SLA, or referenced policy that changes renewal rights or remedies. - Treat the renewal as a comparison exercise, not a standalone contract review: ask what changed, what stayed the same, and which document controls if terms conflict. - If historical performance data is supplied, use it as the benchmark for any uptime, response-time, support, or credit analysis; if it is absent, say so and limit conclusions accordingly. ## 2. Failure modes the skill is correcting - Evaluating service-level thresholds without anchoring them to actual historical performance, which is the only reliable basis for judging whether the promise is meaningful or effectively illusory. - Analyzing renewal pricing in isolation from SLA concessions, renewal credits, or scope changes, when the commercial package must be assessed as a single tradeoff. - Treating service credits as sufficient protection without checking whether they are the exclusive remedy, which can make the vendor’s exposure far smaller than the customer expects. - Missing changes to data portability, deletion timing, export support, and transition assistance, which can materially affect exit optionality. - Overlooking side changes that alter the bargain indirectly, including measurement windows, exclusions, support hours, escalation paths, auto-renew mechanics, or notice deadlines. - Failing to tie each adverse point to the governing clause hierarchy, the practical consequence for the client, and the specific negotiation ask. ## 3. Legal frameworks / domain conventions that apply - Renewal packages commonly contain layered documents; use the agreement’s order-of-precedence language, amendment clause, and incorporation-by-reference rules to determine which version governs each changed term. - Renewal pricing must be tested against the original price-adjustment mechanics, if any, and against whether the package preserves, expands, or removes contractual pricing discretion. - SLA changes should be evaluated under the governing SLA definition, measurement methodology, exclusions, service-credit schedule, and any cure or restart mechanics that affect recoverability. - If service credits are the exclusive remedy, the remedy structure materially defines the customer’s ceiling for outage recovery and should be analyzed with the limitation-of-liability clause. - Data-handling terms at renewal should be reviewed under the base agreement’s confidentiality, data return, deletion, and transition-assistance provisions, because those provisions often determine whether the customer can migrate cleanly at term end. - General contract interpretation principles apply: specific terms control over general ones, later-in-time amendments can modify earlier baseline terms, and incorporated schedules or exhibits can be binding if the hierarchy makes them so. ## 4. Analytical scaffolds - Document hierarchy: identify every operative document, note amendment dates, and state which terms control if there is inconsistency. - Pricing analysis: isolate each fee change, renewal uplift, discount removal, minimum commitment, or usage threshold; compare it to the original pricing mechanics and the commercial context reflected in the package. - Service-level analysis: for each modified metric, compare the proposed definition, threshold, exclusion, and credit structure against the original SLA and the historical performance record. - Remedy analysis: determine whether credits are exclusive, whether termination rights are preserved, and how any liability cap or carve-out affects outage exposure. - Data and exit analysis: review data export, deletion, retention, handoff, and transition-assistance provisions for practical exit feasibility. - Integrated assessment: evaluate whether the renewal improves, worsens, or simply rebalances overall value when pricing, SLA quality, and remedies are read together. - Recommendation synthesis: state whether the package is acceptable as-is, acceptable only with changes, or not acceptable, and identify the negotiation priorities in descending order of importance. ## 5. Vertical / structural / temporal relationships (only if applicable) - Compare original term, proposed renewal term, and historical performance on a clause-by-clause basis rather than averaging them into a general impression. - If multiple time periods matter, analyze them in sequence: prior contract baseline, current term performance, and renewal period economics. - If multiple service metrics are changed, enumerate each metric first and assess each one separately before giving an overall view. - If the package contains cross-referenced schedules or policies, trace the vertical chain from the amendment or order form down to the controlling SLA language. - If a provision affects future exit behavior, distinguish between obligations during the renewal term and obligations triggered at expiration or termination. ## 6. Output structure conventions - Use a contract review memorandum format with a concise executive summary followed by organized sections for hierarchy, pricing, service levels, remedies, data/exit provisions, and negotiation points. - Include a comparison table that shows, for each material change, the original term, the proposed renewal term, the governing source, and the practical impact. - For each issue, state: what changed, why it matters under the governing clause, how it compares to historical performance or prior rights, and the downstream consequence for the client. - Where the source set supplies figures or thresholds, use them; do not invent amounts, percentages, or reconciliation math. - If the deliverable is advisory, end with a short Recommended Actions section that assigns the next step to a business owner or counsel and ties it to the renewal timeline or response deadline. - Use plain, source-based legal reasoning; do not state a conclusion without identifying the controlling contractual provision that supports it.