<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Naigo Blog: AI for procurement]]></title><description><![CDATA[AI in procurement, explained by buyers: supplier contracts, RFPs, renewals and negotiation. Practical notes from the team building Naigo.]]></description><link>https://naigo.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6af72740950b33787463900f/16cc69dd-2442-42f0-8058-07e85d33e8f6.png</url><title>Naigo Blog: AI for procurement</title><link>https://naigo.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 18:15:23 GMT</lastBuildDate><atom:link href="https://naigo.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Before you sign that SaaS renewal: 7 things to check in the contract]]></title><description><![CDATA[Notice period, price cap, licence metric, scope, SLAs, data exit and amendments: what to check in the contract before signing any SaaS renewal.]]></description><link>https://naigo.hashnode.dev/before-you-sign-that-saas-renewal-7-things-to-check-in-the-contract</link><guid isPermaLink="true">https://naigo.hashnode.dev/before-you-sign-that-saas-renewal-7-things-to-check-in-the-contract</guid><category><![CDATA[SaaS]]></category><category><![CDATA[procurement ]]></category><category><![CDATA[Procurement Software]]></category><category><![CDATA[Procurement Intelligence]]></category><category><![CDATA[Contractor management software]]></category><category><![CDATA[RFP software]]></category><dc:creator><![CDATA[hello]]></dc:creator><pubDate>Fri, 13 Nov 2026 15:24:38 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6af72740950b33787463900f/54aab866-f06a-4739-b6fd-e5ef4e6f15c9.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The renewal email always arrives at the worst moment. A few weeks before the deadline, sometimes a few days before the notice period ends, with a new price, a new edition of the product and a friendly "nothing changes for you".</p>
<p>Something always changes. And most of the time, the only document that can tell you what is the one nobody has opened since it was signed: the contract.</p>
<p>Here are seven things worth checking before you sign a SaaS renewal. None of them requires a tool. All of them require the contract, its amendments and the new offer side by side.</p>
<h2>1. The notice period, before anything else</h2>
<p>Many SaaS contracts renew automatically unless you give notice within a set window: 30, 60 or 90 days before the end of the term, sometimes more. Miss it, and the negotiation is over before it starts: you are committed for another term, and your leverage is gone.</p>
<p>So the first question is not "is the price fair?". It is "until when can I still say no?". Count backwards from the end date, check the form required (registered letter, email to a specific address, notice through the vendor portal) and put the real deadline in a calendar that someone actually reads.</p>
<h2>2. The price revision clause</h2>
<p>A renewal offer often comes with an increase. Before discussing it, find out what the contract allows. Look for:</p>
<ul>
<li>a cap on annual increases, often a fixed percentage or a reference index;</li>
<li>the reference itself, if the increase is tied to an index such as a consumer price index or, in France, the Syntec index for IT services;</li>
<li>the date and the base on which the increase is calculated.</li>
</ul>
<p>If the contract caps the revision at 5% and the offer says 7%, you don't need a negotiation strategy. You need the clause number.</p>
<h2>3. The metric you actually pay for</h2>
<p>"Users" is not a definition. Is it named users, active users, users who logged in during the last 90 days, or every account ever created? Can a licence be reassigned when someone leaves? Can you reduce quantities at the anniversary date, or only increase them?</p>
<p>The metric is where most of the money hides. A renewal is the moment to align it with how the product is really used, not with how it was estimated three years ago.</p>
<h2>4. What changed in the product</h2>
<p>Vendors regularly move features between editions. The module you rely on may now sit in a higher plan, or be sold as an add-on. Compare the scope described in your contract and its order forms with the scope of the new offer, line by line. A "same price" renewal that quietly removes a feature is a price increase.</p>
<h2>5. The service levels and what happens when they are missed</h2>
<p>Check the availability commitment, the support response times and, above all, what you get when they are not met. Service credits are common; whether they are your only remedy is the real question. A renewal is a good time to ask for credits that are not the sole remedy, and for a right to terminate after repeated failures.</p>
<h2>6. Your data, on the way out</h2>
<p>Nobody wants to think about leaving while renewing. That is exactly why it should be done now, while you still have something to offer. Look for the export of your data (format, timeline, cost), the period during which the vendor keeps it after termination, and any assistance offered for the transition. If the contract says nothing, the renewal is the moment to add it.</p>
<h2>7. The amendments you forgot</h2>
<p>This is the classic trap. The master agreement says one thing, an amendment signed two years ago says another, and a third document quietly overrides both. The version in force is rarely the one at the top of the shared folder.</p>
<p>Before answering the vendor, rebuild the chain: master agreement, every amendment, every order form, in date order. What was negotiated last time, and what did the vendor already concede?</p>
<h2>The real problem: the pieces are never in the same place</h2>
<p>None of these checks is difficult. What makes renewals painful is that the answers are scattered: the contract in a shared drive, the amendments in someone's inbox, the usage data in an admin console, the new offer in a PDF that arrived last week. Every renewal starts with an archaeology session.</p>
<p>That is the problem we are working on at <a href="https://naigo.ai/en">Naigo</a>. The idea is simple: keep the full context of each supplier file in one place, and let AI do the reading. <a href="https://naigo.ai/en/supplier-contract-management">Supplier contracts</a> are imported once, and every clause, deadline and notice period is extracted with the exact passage it comes from. When a <a href="https://naigo.ai/en/supplier-contract-renewals">renewal</a> approaches, the file is already built, and the new offer is checked against the terms that were actually signed. The buyer still decides. The AI just makes sure the decision is made with the contract in hand.</p>
<h2>A checklist to keep</h2>
<p>Before signing any SaaS renewal:</p>
<ol>
<li>Note the real notice deadline and the form required.</li>
<li>Find the price revision clause and its reference.</li>
<li>Check the licence metric against real usage.</li>
<li>Compare the scope of the new offer with the current contract.</li>
<li>Read the service levels and the remedies.</li>
<li>Secure the data export and the exit terms.</li>
<li>Rebuild the chain of amendments and order forms.</li>
</ol>
<p>Seven checks, one afternoon, and usually a much better renewal.</p>
<p><em>Naigo is AI procurement software for supplier contracts, RFPs, renewals and negotiation.</em> <a href="https://naigo.ai/en/procurement-ai-agents"><em>See how it works</em></a> <em>or</em> <a href="https://naigo.ai/en/demo"><em>book a demo</em></a><em>.</em></p>
]]></content:encoded></item></channel></rss>