
A client terminates their retainer. The offboarding call is polite, the final invoice goes out, and your team starts winding down. Then the first of the month arrives, and your agency’s corporate card is charged for a renewal on a tool that existed only for that former client, such as a marketing platform, a multi-seat design tool or a data warehouse. (Say it is $14,000. The figure is illustrative, but five-figure renewals on enterprise tools are not unusual.)
You ask the client’s IT team to take over billing or migrate the workspace, and you get silence. Or you get a request to keep everything running while their internal team finishes a migration that will take months. You can’t just hit delete. Their data, their users or their identity provider (IdP) may be tied to an account you own, and shutting it down could expose you to a breach-of-contract claim.
This is what this article calls the post-termination ransom problem. It’s an informal label, not a legal term. It describes a structural weakness in agency operations: when the agency owns the account and the client depends on it, the departing client holds leverage the agency never meant to hand over.
This guide covers how these situations arise, where the real legal risks are (and where they are commonly overstated), which contract clauses help, which technical safeguards actually work, and what to do if you are already stuck. It is general information, not legal advice. Have a qualified lawyer in your jurisdiction review any clause before you rely on it.
How Subscription Hostage Scenarios Happen
Agencies often put client tools under their own accounts to simplify onboarding, keep a standard stack or pass on volume pricing. That is convenient at the start of an engagement and painful at the end. Three patterns cause most of the trouble.
1. Client workspaces that live under the agency’s account
On some platforms, the workspace belongs to whoever’s account it sits in, regardless of who pays. Webflow is explicit about this: by default a site is owned by the Workspace it is in, and a client who pays for hosting does not thereby get rights to transfer or duplicate the site unless that has been agreed. Webflow also offers separate tools for each job. Client Payments hands off billing only, while a site transfer moves the site, its plan and connected custom domains to the client’s Workspace. The agency receives a prorated credit if the transfer happens mid-billing cycle.
Other platforms work differently, so don’t assume a single model. HubSpot, for example, uses one portal per client. The client owns the subscription and data, and the agency works inside it through partner access. In that setup the hostage risk comes from who set up and paid for the portal, not from a shared master tenant. Check each vendor’s documentation for how ownership and billing actually work, and note it in your onboarding checklist.
2. Federated identity (SSO) deadlocks
When a client connects its own identity provider (Okta, Microsoft Entra ID, Google Workspace and similar) to a tool the agency owns, control is split. The client controls who can sign in, while the agency holds the billing relationship and often the root admin role. If the client changes or removes its IdP configuration and nobody on your side has another way in, you can be locked out of user management while the subscription keeps billing to you.
3. Client production systems on agency-owned cloud accounts
When a client’s live site, checkout, lead routing or data pipeline runs on infrastructure under the agency’s account, shutting it off can break the client’s business. That is where the biggest liability sits, and it is why you should never be the root owner of a client’s production environment.
Cloud providers do offer ways to separate accounts. In AWS Organizations, a member account can leave and become a standalone account, but only if it has the information needed to operate on its own: a valid payment method, verified contact details and a support plan. Once it leaves, the account owner becomes responsible for all new charges and the account’s own payment method is used. Plan for that handover in advance, and make sure the client has completed the standalone setup before you remove the account.
Why Exiting Clients Stall
Most departing clients are not trying to extort their former agency. The usual causes are ordinary:
- Procurement delays. If the client ends the retainer before arranging its own software contracts, it has nowhere to move the workspace. Enterprise purchasing can take weeks or months, depending on the organization.
- Budget and approval gaps. A change in leadership or a budget freeze can leave nobody authorized to sign a new subscription.
- Lost institutional knowledge. The person who approved the original setup may have left, and the remaining IT team may be reluctant to touch an SSO or API integration they don’t understand.
- Fee disputes. Where the relationship ended badly, a client may slow-walk technical cooperation to gain leverage on the final invoice. This does happen, but it is less common than plain disorganization, so open with a cooperative tone.
The Legal Picture: Why You Can’t Simply Pull the Plug
When a former client ignores decoupling requests and won’t reimburse pass-through costs, the instinct is to suspend access or terminate the license. That can be reasonable, but whether it is safe depends mostly on your contract and on what is stored in the account.
Where the real risk sits
- Contract risk comes first. The most likely claim is breach of contract, especially if your agreement promises transition help, continuity of service or return of client data, or if it says nothing clear about who owns the tools. A vague “cooperate during transition” clause leaves room for argument, so spell out what cooperation means and for how long.
- Property and interference claims. If the account holds client-owned content (customer lists, creative files, transaction records), abruptly deleting or locking it invites claims such as conversion or interference with the client’s business. How such claims are framed and how strong they are varies by jurisdiction and facts.
- Data protection duties. If the account holds personal data and your agency acts as the client’s processor, the GDPR (and the UK GDPR) requires the processor contract to say that, at the controller’s choice, the processor deletes or returns all personal data once the services end, and deletes existing copies unless law requires storage. This works in your favor as well as the client’s, because it justifies a documented export-and-delete process. It also means you shouldn’t keep a former client’s personal data indefinitely.
- Computer misuse laws are a narrower risk than they are often made out to be. The US Computer Fraud and Abuse Act (CFAA) targets accessing a computer without authorization or exceeding authorized access. In Van Buren v. United States (2021), the Supreme Court read that provision narrowly, as a “gates-up-or-down” question of whether someone can or cannot access a given system or area. An agency using its own admin rights over its own account to cancel its own subscription is a poor fit for those statutes. The risk rises if you go into systems or credentials that belong to the client after your authorization has ended. Treat criminal computer-misuse law as a reason to stay inside your own accounts, not as the main hazard.
Penalty clauses and holdover fees
Many agencies add a punitive holdover fee, such as a multiple of the vendor’s cost, to discourage stalling. Courts in many places will not enforce a clause that works as a penalty rather than a genuine pre-estimate of loss. In the US, the Restatement (Second) of Contracts § 356(1) allows stipulated damages only at an amount that is reasonable in light of the anticipated or actual loss and the difficulty of proving it. Arizona’s Supreme Court applied that test in Dobson Bay Club II v. La Sonrisa de Siena (2017) and held a flat 5% late fee on a loan’s balloon payment to be an unenforceable penalty. English law has its own penalty doctrine, and approaches differ by state and country.
The practical consequence is that a holdover fee tied to something you can document, such as the actual vendor cost plus a reasonable administrative charge, is much more likely to hold up than an arbitrary 150–200% multiplier. Whatever rate you choose, have counsel check it in your governing-law jurisdiction.
Contractual Protections Worth Having
Prevention starts before the statement of work is signed. Your master services agreement (MSA) should treat client tools, accounts and identity setup as separate, severable items rather than informal pass-through conveniences.
| Mechanism | Purpose | Drafting notes |
|---|---|---|
| Client-owned billing | Removes your liability for tools used only by the client | Have the client hold the vendor subscription directly from day one, with the agency given delegated admin or partner access |
| Defined decoupling window | Sets a clear deadline for migrating workspaces and IdP changes | Choose a window that matches how long migration realistically takes for that tool, and state what happens when it passes |
| Export and deletion protocol | Documents that the client received its data before anything is switched off | Authorize a standard export, delivery by secure link in writing, a defined retention period and then deletion, consistent with any data-processing terms |
| Cost-based holdover charge | Removes the financial incentive to stall | Tie the charge to actual vendor cost plus a reasonable administrative fee, not a punitive multiple |
| Suspension rights | Clarifies that you may suspend third-party tools for non-payment or failure to decouple | State that suspension under the clause is not a breach of the agreement. Don’t promise “immunity”: a contract cannot waive third parties’ or regulators’ rights, and the clause only helps against the other party to the contract |
| Unamortized cost recovery | Covers annual commitments bought for a client who leaves early | Allow you to recover the unused portion of non-cancellable third-party commitments |
Sample clause (starting point for your lawyer)
“Third-party software licenses, cloud environments, or single sign-on (SSO) integrations provisioned under Agency’s accounts for Client (‘Agency-Provisioned Tools’) are provided only for the duration of the applicable Statement of Work. On notice of termination or expiration, Client shall migrate its data and update or remove its identity provider (IdP) connection within [X] calendar days (‘Decoupling Period’). Agency will provide reasonable written transition instructions. If Client does not complete decoupling within the Decoupling Period, Agency may, on [Y] days’ written notice: (a) deliver a standard export of Client Data to Client; (b) suspend or terminate access to Agency-Provisioned Tools; and (c) invoice Client for the actual third-party fees incurred for any period after the Decoupling Period, plus a reasonable administrative charge of [Z]. Where applicable data-protection law requires, Agency will delete or return Client personal data at Client’s election after the services end.”
Fill in the bracketed periods based on how long migration really takes for the tools involved, and keep the notice step. A clause that lets you act with no warning is harder to defend than one that gives the client a documented final chance.
Technical Safeguards
Legal language works best alongside technical design that makes hostage situations less likely.
1. Keep the client as owner of its own systems
Wherever the vendor supports it, have the client own the root account and subscription and give your staff delegated roles. Don’t run a client’s production CRM, ERP or cloud infrastructure inside your agency’s primary account. Where a client wants to use your volume discount, ask the vendor in advance how the workspace could later be detached or its billing transferred to the client, and get that in writing. Some vendors have tools for exactly this, such as Webflow’s site transfer and AWS’s standalone-account process, and others require a support request, so find out before you need it.
2. Plan for identity lockout
When you configure SSO (SAML 2.0 or OIDC) for a client workspace, make sure you keep at least one way to administer the tool that does not depend on the client’s IdP.
- Break-glass accounts. Microsoft’s guidance for its own tenants is to keep at least two cloud-only emergency access accounts, protect them with phishing-resistant authentication such as passkeys (FIDO2) or certificate-based authentication, and test them at least every 90 days. That guidance is specific to Microsoft Entra, but the principle applies more widely. Whether a given SaaS tool lets a local administrator bypass SSO varies by vendor, so check this for each platform at setup, before you need it.
- Deprovisioning by contract status. Where a tool supports SCIM (System for Cross-domain Identity Management), tie user lifecycle to the engagement’s status in your professional services automation (PSA) or finance system, so that access ends when the contract does.
3. Match software commitments to contract terms
Don’t sign a non-cancellable annual SaaS commitment for a client whose retainer can be terminated on 30 days’ notice. If a client wants the short exit, they should pay month-to-month software pricing, pay the annual fee up front, or take out the subscription in their own name.
4. Use dedicated, capped virtual cards
Corporate card platforms such as Ramp and BILL’s Spend & Expense (formerly Divvy) let you issue virtual cards with spending limits. Brex, now owned by Capital One following a deal that closed in April 2026, offers the same. Paylocity acquired Airbase, which is now sold as part of Paylocity for Finance rather than as a standalone product. Giving each client’s software its own capped card means you can limit or freeze one card at the end of an engagement without disturbing other vendors. Freezing the card does not cancel the subscription, though, so you still have to cancel or transfer it with the vendor, or you may be left with an unpaid balance.
A 30-Day Offboarding Playbook
When a client gives notice, speed and documentation decide whether you exit cleanly. This timeline is a suggested starting point, not a legal standard, and you should adjust it to what your contract and the vendors allow.
Days 1–3: Audit and written notice
- Inventory everything shared. Use your SaaS management tool (Zylo, Torii, BetterCloud or a spreadsheet) together with your card ledger to list every license, API key, webhook, workspace and SSO connection tied to the client.
- Send a separate technical offboarding notice. Keep it apart from the relationship wrap-up. List each shared tool, its renewal date, the steps the client’s IT team must take to assume ownership, and the cutoff date.
Days 4–14: Assisted migration
- Provide cutover documentation. Include the vendor’s transfer forms or instructions, SAML metadata details and DNS checklists, so “we don’t know how to migrate this” stops being a blocker.
- Schedule a live handoff session with the client’s IT administrator, and record it with their consent.
Days 15–25: Export and escalation
- Take a defensive export of the client’s data and configuration if the client has not moved. Store it encrypted and send the client’s legal and IT contacts a secure download link. Keep the proof of delivery.
- Escalate in writing. Remind the client of the contractual consequences, and if they ask for an extension, make it conditional on prepayment of the underlying costs under your holdover clause.
Days 26–30: Decoupling
- Disconnect and rotate. On the cutoff date named in the notice, and only for accounts you own, remove the SSO connection, rotate shared API tokens and downgrade or cancel seats.
- Get written confirmation from each vendor that seats are cancelled or reduced and that no further charges will arise, then freeze or close the client-specific virtual card.
If You’re Already in the Middle of It
If you are dealing with a client holding a shared subscription over a contract that lacks these clauses, these steps reduce cost and legal risk:
- Offer a short transition services agreement (TSA). Agree in writing to keep the environment online for a fixed period (for example 30 days) in return for prepaid software costs and a clearly stated administrative fee. Framing it as a defined accommodation often gets a stalled approval moving.
- Ask the vendor for help. Contact your partner or account manager and ask what options exist for transferring the subscription to the client’s own legal entity, or splitting the workspace. Options differ widely by vendor and plan.
- Give written notice of non-renewal instead of deleting data. Tell the client and the vendor in writing that you will not renew at the end of the current billing period, and ask the vendor to contact the client about setting up its own account before that date. This stops the cost recurring without destroying the client’s data mid-cycle. Check whether the plan can be cancelled before the renewal date, and whether cancelling would delete data automatically.
- Get legal advice before suspending or deleting anything if the account holds client data you can’t export, or if the client is threatening a claim.
Frequently Asked Questions
Can an agency legally delete a former client’s data from a shared SaaS account if they refuse to pay?
It depends on your contract and the data involved, and deleting without warning carries real risk. The safer sequence is to export the data, deliver it to the client in writing with a clear deadline, and then suspend or delete as your agreement allows. If the data includes personal data, GDPR-style processor obligations mean you will typically need to return or delete it at the client’s choice once services end, so a documented process helps you comply. There is no universal “statutory window” for retention; the right period comes from your contract, data-protection law and any legal-hold obligations.
How do we handle annual SaaS seats bought for a client who cancels mid-year?
Look first at your MSA for a clause covering unrecovered third-party costs. For future agreements, have the client buy the subscription directly, prepay the annual commitment, or agree to reimburse the unused portion. Some vendors also let agencies reassign unused seats to other clients, but that depends on the vendor’s terms, so check yours.
What if the client’s SSO locks our administrators out?
First check whether the tool allows a local administrator account that bypasses SSO, and whether you set one up at onboarding. If you did, sign in with it, review the IdP connection and restore administrative control over billing and seats. If you didn’t, contact the vendor’s support with proof that you own the account. This is why you should confirm the bypass option for every platform before the client connects its IdP.
Is a 200% holdover fee enforceable?
Often not. Courts in many jurisdictions treat fees that go well beyond actual loss as unenforceable penalties. A fee tied to documented vendor costs plus a reasonable administrative charge is much safer. Have a lawyer review the figure for your governing law.
Can we shut down a client’s workspace after we’ve given notice?
If your contract expressly permits suspension on non-payment or failure to decouple, you have given the notice it requires, and the client has had the chance to export its data, you are in a much stronger position than if you act without those steps. Even then, a suspension is not a legal shield, because third parties and regulators are not bound by your contract. Get advice before acting if a lot of money or sensitive data is at stake.