# Assess Msa Renewal Terms Performance > Negotiation preparation memorandum evaluating proposed renewal terms against the existing agreement and historical account performance data. - Skill: `finchipaiorg/assess-msa-renewal-terms-performance` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/assess-msa-renewal-terms-performance` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/assess-msa-renewal-terms-performance/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-msa-renewal-terms-performance --- # Skill: Assess MSA Renewal Terms Against Historical Business Performance ## 1. Subject-matter triage (only if applicable) - Confirm the renewal is being evaluated as a comparison between the existing agreement, the proposed renewal, and the historical performance record for the same account. - Separate pure legal changes from commercial changes; the same clause may matter differently if performance data shows compliance, underperformance, waiver, or repeated concession. - If multiple contract periods, amendment layers, account segments, or service tiers exist, enumerate them before analysis and assess each separately rather than collapsing them into a single pass. - If the source set contains one renewal proposal only, state that the analysis is limited to that proposal and explain why no alternative scenario is in scope. ## 2. Failure modes the skill is correcting - Treating the renewal as a redline exercise without using performance history to test whether the proposed changes are commercially justified. - Missing provisions that improved in practice or caused friction during the expiring term, which changes negotiating leverage and concession strategy. - Analyzing pricing, service levels, remedies, and termination rights in isolation instead of as an integrated commercial package. - Failing to connect account performance data to the contractual remedy structure, especially where credits, cure rights, escalation paths, or termination triggers depend on measured performance. - Drafting conclusions that describe a change but do not say how the historical record strengthens or weakens the client’s position. - Overstating leverage where the data shows no sustained breach pattern, or underusing leverage where the data shows repeated underperformance or waived enforcement. ## 3. Legal frameworks / domain conventions that apply - Renewal negotiations are anchored in the existing agreement’s renewal, amendment, pricing, service-level, remedy, and termination provisions; the baseline text is the starting point for any deviation analysis. - Commercial reasonableness is assessed by comparing the proposed term against the operational history of the account, not by looking at the new language in isolation. - Pricing changes should be evaluated through the contract’s pricing mechanics, including escalation structure, measurement period, usage banding, minimum commitments, and any pass-through framework. - Service-level changes should be tested against the agreement’s measurement methodology, credits, exclusions, notice requirements, and any exclusive-remedy language. - Termination and non-renewal rights should be read with notice periods, cure mechanics, transition assistance, data return, and post-termination cooperation obligations. - Liability, indemnity, and exclusivity provisions should be reviewed as part of the commercial package because concessions in one area may justify resistance in another. - Historical performance facts that matter include recurring miss patterns, incident frequency, response and resolution timing, credits claimed or waived, audit results, customer complaints, and any prior amendment history. - Use the controlling contractual text and any stated legal authority in the source set; do not infer a legal standard without naming the clause, rule, statute, or doctrine that supports it. ## 4. Analytical scaffolds - Baseline comparison: list each proposed change against the corresponding existing provision and classify it as economic, operational, risk-allocation, or process-related. - Performance integration: for each changed pricing, service-level, remedy, or termination term, tie the proposal to the historical performance record and state whether the record supports tightening, maintaining, or conceding the term. - Leverage mapping: identify where the client can credibly press for protection because the account history shows underperformance, repeated exceptions, or prior waiver of strict enforcement. - Counterweight mapping: identify where the supplier can argue that the record shows stable performance, isolated incidents, customer-caused delay, or acceptance of the current structure. - Package tradeoff analysis: test whether concessions should be sequenced across price, term, service credits, scope, liability caps, or termination flexibility rather than negotiated one clause at a time. - Issue closure discipline: for each material issue, state the magnitude or duration drawn from the source materials, cross-reference the interacting clause or performance metric, and explain the practical consequence for the client. - Recommendation framing: translate each issue into a negotiation position with a clear ask, fallback, and red line where appropriate. - If a provision appears unchanged but the performance record makes it newly important, treat it as an issue and explain why the unchanged language now matters. ## 5. Vertical / structural / temporal relationships (only if applicable) - Track how a change in one term affects downstream terms in later periods, such as automatic renewal, annual escalators, cure windows, notice periods, and post-expiration assistance. - Compare performance across relevant periods only; distinguish launch-period issues from steady-state performance and avoid using an outlier period as the sole benchmark unless the record supports it. - If the renewal includes multiple dates or triggers, analyze the temporal sequence explicitly so the memo reflects when obligations arise, when leverage peaks, and when remedies expire. - If multiple products, services, geographies, or business units are covered, keep their performance and contractual treatment separate unless the contract expressly aggregates them. ## 6. Output structure conventions - Write a negotiation preparation memorandum that compares the existing agreement, the proposed renewal, and the account performance record in one integrated analysis. - Include a short executive overview, a deviation summary, a performance-and-leverage assessment, and a prioritized negotiation agenda. - Use a table or similarly structured format for the key deviations, with columns for provision, existing term, proposed term, performance context, leverage assessment, and recommended position. - Apply an ordinal severity label to each material issue using a defined scale stated once near the top of the memorandum, and use the same scale consistently throughout. - Each issue entry should end with the quantified performance context, the related clause or metric, and the client consequence. - Close with an explicit Recommended Actions section that uses imperative verbs, identifies the responsible role, and ties each step to a practical timing anchor or milestone. - If the source documents identify a controlling authority for a proposition, cite it by name and section or equivalent identifier in the memo. - The file to produce is `msa-renewal-review-memo.docx`; the memo should be the operative deliverable, not a summary of analysis outside the document.