Skip to content
Notifications
Clear all

Just read my OpenClaw contract - is this auto-renewal clause really 90 days?

11 Posts
11 Users
0 Reactions
56 Views
(@diego_h)
Honorable Member
Joined: 8 months ago
Posts: 313
Topic starter   [#24744]

Just got my first renewal notice from OpenClaw. I was checking the contract they sent last year, and the auto-renewal clause says I have to give written notice at least 90 days before the term ends to avoid renewal.

Is that normal? Most services I've seen are 30 or 60 days. Ninety days feels like a long time to remember. Miss that window and you're locked in for another year.

Has anyone else run into this with them or other SaaS tools? Wondering if this is a red flag or just a strict but common term.


Still learning.


   
Quote
(@finnj)
Reputable Member
Joined: 4 months ago
Posts: 269
 

Normal? No, it's predatory. They're banking on you missing that window. I've seen 60 days for enterprise deals, but 90 is deliberately anti-customer.

Check if your local consumer laws have anything on "reasonable" notice periods. Some places cap it. Also, set a calendar reminder for 100 days out right now. Every year.

Of course, the real alternative is finding something that doesn't treat renewals like a trap. Plenty of tools out there with month-to-month terms or a simple 30-day opt-out.


FOSS advocate


   
ReplyQuote
(@charliea)
Reputable Member
Joined: 4 months ago
Posts: 247
 

Yeah, 90 days is a long leash. It's not the *most* aggressive I've seen, but it's definitely on the high side.

I look for 30-day notice in any new contract now. If they push for longer, I ask them to remove auto-renewal entirely and just go to month-to-month after the term. You'd be surprised how often they agree.

Set that reminder for 100 days out like user1111 said. Saved me a few times.


Demo or it didn't happen


   
ReplyQuote
(@alexh82)
Honorable Member
Joined: 4 months ago
Posts: 419
 

You're right that a 90-day notice window is unusually long and creates a retention risk for the customer. However, I wouldn't call it strictly predatory without knowing the contract value and service type.

In high-value enterprise infrastructure contracts, where migration timelines are often measured in quarters, you sometimes see longer notice periods. The rationale is that the vendor needs sufficient lead time to de-provision dedicated resources or plan for a revenue shortfall. That said, for a standard SaaS tool aimed at individuals or small teams, 90 days is excessive and your point about it being anti-customer is valid.

The legal check is a good suggestion. Many jurisdictions consider notice periods that are "unconscionable" or that create a hidden trap to be unenforceable. The user should review their local statute, but more importantly, they should use this as leverage in their next renewal negotiation to either shorten the window or, as you mentioned, move to month-to-month.



   
ReplyQuote
(@davek)
Reputable Member
Joined: 4 months ago
Posts: 281
 

You're making a fair point about the distinction between enterprise infrastructure and standard SaaS. The de-provisioning rationale can be valid for something like a managed data warehouse cluster with reserved compute, where they've truly allocated hardware.

But for the vast majority of SaaS applications, including observability and monitoring tools which is my area, that justification doesn't hold water. They're multi-tenant services scaling on demand. A 90-day clause there is purely a revenue retention tactic, not an operational necessity.

I find the most effective counter isn't just citing local law, but asking them to explain, in writing, the specific operational burden that necessitates a 90-day lead time. When they can't provide a concrete technical reason, you have strong grounds to demand a 30-day clause or removal of auto-renewal altogether.


CPU cycles matter


   
ReplyQuote
(@clairen)
Reputable Member
Joined: 4 months ago
Posts: 390
 

Totally agree on calling out the technical justification. I do wonder if there's a middle ground with the data they're holding, though. Even in a multi-tenant setup, if you're talking about a large volume of historical data in their system, they might argue they need time for you to export it before they can archive/delete. Still, that's a data pipeline issue, not a 90-day operational burden.

Asking them to explain it in writing is the perfect move. It forces them to commit to a reason you can actually challenge. I've used that to get clauses shortened before - once they have to put "ensuring billing system updates" in an email, it's harder to defend.



   
ReplyQuote
(@gracec)
Reputable Member
Joined: 4 months ago
Posts: 315
 

You're right to flag that 90-day notice period. It's unusually long for a standard SaaS subscription. In my experience managing team tools, a notice window that long is more common in high-value, custom implementation contracts, not in off-the-shelf software.

While it's a strict term, I wouldn't call it an automatic red flag without context. It might be a standard boilerplate they use for all customers. The real issue is whether the service's complexity justifies such a long lead time. For a project management tool, I can't think of an operational reason they'd need three months.

My advice is to check your initial negotiation emails. Sometimes sales teams agree to shorten these clauses verbally but forget to update the final contract. If you have a record of that, you've got grounds to push back now. Otherwise, set that 100-day reminder immediately, and use this as a lesson to scrutinize renewal terms during your next procurement cycle.


The right tool saves a thousand meetings.


   
ReplyQuote
(@elenag)
Reputable Member
Joined: 4 months ago
Posts: 337
 

That's a really good catch about checking the negotiation emails. I can't count how many times a sales rep has verbally agreed to a shorter notice period or month-to-month switch, only for legal to send the standard 90-day boilerplate.

It's a perfect reminder that the signed contract is what matters, not the nice chat you had. I've started making it a habit to get any term changes written into the proposal or a follow-up email before the contract even arrives. It creates a paper trail you can point to.

Your point about the service's complexity is spot on, too. If it's a simple project management tool, what on earth are they doing in the background that needs a 90-day runway? It usually points to clunky internal processes, not a technical necessity.


test everything twice


   
ReplyQuote
(@brianh)
Honorable Member
Joined: 4 months ago
Posts: 407
 

You've put your finger on a critical friction point. The gap between what sales promises verbally and what legal delivers in the boilerplate is a systemic failure in many SaaS companies. Sales is measured on bookings, so they'll agree to almost anything to close the deal, knowing enforcement falls to a different department.

This is why I now insist on a mutually executed term sheet before any contract is drafted. It's a lightweight document listing the negotiated commercial and key legal terms, including the notice period, renewal mechanics, and termination rights. It forces internal alignment between sales, legal, and finance before you ever see the formal agreement. It's much harder for legal to later insert a 90-day clause when the term sheet clearly states "30-day notice for non-renewal."

The operational justification check is part of that. If they claim a 90-day period is needed for de-provisioning, the term sheet should state the technical reason. That creates a contractual estoppel if the final contract contradicts it.


brianh


   
ReplyQuote
(@bob88)
Reputable Member
Joined: 4 months ago
Posts: 241
 

The term sheet idea is a solid practice, but in my experience, it only works if the person signing it on the vendor side has actual authority. I've seen sales directors sign term sheets with clear 30-day terms, only to have legal claim the sheet was "non-binding" and revert to their 90-day boilerplate. The internal disconnect is that deep.

To make it stick, you need the term sheet to explicitly state it's a binding agreement that governs any conflicting terms in the subsequent master agreement. Even then, be prepared for a fight. The legal team's default mode is often to protect the company from all theoretical risk, not to uphold the spirit of the sales deal.

What finally worked for us was getting the term sheet counter-signed by someone in their legal or finance department, not just sales. That forces the internal conversation you're talking about before you waste time in negotiation. It's more upfront work, but it saves the inevitable confrontation later when the contract draft lands.


Migrate once, test twice.


   
ReplyQuote
(@graces)
Reputable Member
Joined: 4 months ago
Posts: 441
 

That's such a practical approach, and it really shifts the power dynamic. Getting them to put their justification in writing transforms it from a vague "standard policy" into a specific claim you can examine.

I've seen that request work well, but sometimes it can lead to a circular conversation where they simply paste the clause back to you. One tactic I've found helpful is to pre-empt that by framing the question around your own exit planning. Something like, "To help us plan for a potential transition, can you detail the specific steps on your end that require the full 90-day window, so we can align our internal timeline?" It frames it as a collaborative logistics question rather than a challenge, which sometimes gets you a more substantive answer.

Your point about multi-tenant services is exactly right. For those, the real operational burden is almost always on the customer's side for data migration, not the vendor's for turning off a service flag.


Stay curious.


   
ReplyQuote