Subscription and cloud agreements
Service levels · Security schedules · Procurement
In short
We draft and review the terms for software sold or bought as a service: uptime, support, where data is stored, renewal, and what happens when the contract ends.
Where problems usually start
Service levels are often copied from a competitor's website, so the credit regime commits to figures the infrastructure has never met. Exit and data return are left vague until a customer leaves and asks for its data in a usable format. On the buying side, vendor terms are signed unread, and the company later finds that termination needs a year's notice and its data is deleted thirty days after.
How we approach it
We work on cloud and subscription agreements for buyers and sellers, covering uptime and service credits, support tiers, data residency and deletion, suspension and termination, price increases, renewal and exit. Acting for both sides tells us whether a position the other side proposes is market standard or open to negotiation.
What our work involves
- Service levels, credits and support tiers that follow the architecture and the monitoring you run.
- Residency, retention, deletion and data-return terms with the format and timeline stated.
- Suspension, termination, renewal and price terms that leave neither side trapped or surprised.
- Review of vendor and cloud terms for lock-in, notice, data return and audit rights.
- A security schedule that matches your certifications and controls, so questionnaires can be answered from one document.
For startups and in-house teams
Startups selling software need service levels and credits that match their monitoring data, and a security schedule that matches their controls. In-house teams buying software need exit terms that say how their data comes back, and a liability cap that covers a breach.