A new kind of AI agent now logs into a company's software vendors on its own, checks who is actually using each seat, and takes back the ones that are not. Cledara launched this agent today. For early-stage SaaS founders who sell to other businesses, that means the slow, manual process of "right-sizing" a software bill just got automated, and it will not always show up as a full cancellation.
What did Cledara just launch?
Cledara, a software subscription and spend management platform, launched Cledara Agent, an AI agent that handles software administration tasks a finance or IT team used to do by hand. According to Finextra's coverage of the launch and Cledara's own help center article, the agent:
- Signs into a company's connected vendor billing pages, often overnight, to download invoices and match them against payments.
- Handles joiner and leaver workflows: setting up new employees in a tool and removing them when they leave.
- Reclaims seats that have gone unused, across the more than 8,000 SaaS and AI tools Cledara says it can connect to.
- Keeps login credentials in a per-company vault that, per Cledara, the AI itself never sees, and is listed in Cloudflare's directory of verified bots.
It is sold as an add-on to any Cledara plan. One capability is notably not live yet: Cledara's own help center lists "cancel or pause a subscription" as "coming soon." The seat-reclaiming agent is already running. The cancellation agent is next.
Why does this matter if you sell B2B SaaS?
Because it targets a kind of revenue loss that is easy to miss: a shrinking account that never actually cancels. Most churn dashboards are built to catch the moment a customer hits "cancel." They are not built to catch a 20-seat account quietly dropping to 14 seats because a procurement tool flagged six logins as inactive.
This is a contraction problem, not just a churn problem, and it hits net revenue retention the same way a cancellation does, just more quietly:
| What changes | Old process | With a seat-reclaiming agent |
|---|---|---|
| Who notices unused seats | Usually nobody, until a renewal review | The agent, running on a schedule |
| How it's decided | A manager asks around informally | Login activity, checked automatically |
| When it happens | Once a year, at renewal | Continuously, any month |
| How it shows up on your side | A downgrade request | A reduced seat count, sometimes with no request at all |
The agent's own task list confirms where this is headed. If "reclaim unused seats" ships before "cancel the subscription," expect seat-level contraction to show up in your billing data well before full cancellations do.
How is this different from AI agents canceling consumer subscriptions?
It is the enterprise mirror of the same trend. We've already covered how consumer AI agents like Meta's Muse now find and cancel personal subscriptions people forgot about. Cledara Agent does the equivalent job for a business's software stack, but with two differences that matter for B2B SaaS founders specifically:
- The decision-maker is a finance or IT admin's tool, not the end user who actually logs in and uses your product day to day.
- The action it takes first is shrinking a contract, not necessarily ending one. A full cancel usually requires a deliberate decision; removing "unused" seats is designed to be close to automatic.
That means the usual early-warning signs of churn, like a single admin going quiet, may no longer be the first signal. The first signal could be individual end users going quiet while the account itself keeps paying, until the next seat audit.
What should founders do about this?
- Make per-seat usage visible to your own customers, not just to you. If an admin's procurement tool can see who logged in last, your own dashboard should show the same thing first, with enough context that an unused seat looks like a training problem to solve, not dead weight to cut.
- Separate "seat" from "value" where you can. If your pricing is purely per-seat, an idle login is pure downside risk. Usage-based or outcome-based components give an admin a reason to keep access even when login frequency dips.
- Treat a seat-reduction request as a save opportunity, not just a billing update. The same logic behind a good cancel flow applies here: ask why the seats are going unused before processing the change, since the answer (wrong plan, missing onboarding, a reorg) is often fixable.
- Get ahead of the "cancel or pause" feature. Cledara has told customers that automated cancellation is coming. If a procurement agent will eventually be the one clicking cancel, your cancel flow needs to work for a request that arrives with no context and no person to ask follow-up questions of in real time.
- Watch contraction, not just logo churn. If you track monthly recurring revenue by customer, start flagging seat-count or plan downgrades the same way you flag cancellations. By the time it's a full cancellation, the account was already shrinking.
Key takeaways
- Cledara launched an AI agent on November 10, 2026 that reclaims unused software seats automatically, with subscription cancellation and pausing listed as "coming soon."
- This is a buyer-side agent: it acts for the company paying for your software, not the vendor, which is a different dynamic than consumer apps that cancel subscriptions for individuals.
- Seat reclamation shrinks revenue without triggering a cancellation event, so it can hide inside net revenue retention numbers until a renewal review.
- The fix is the same discipline that prevents full churn: make value visible per seat, and ask why before you process a downgrade.
Lokuna's hosted cancel page offers each customer the one option most likely to keep them, a pause, a discount, a call, or no offer, whether the request comes from a person or arrives through an automated tool acting on their behalf.
