playbook-saas-msa

Applies firm-approved positions and fallback clause text to US-law SaaS master subscription agreement reviews.

72|19|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/sure-scale/doc-haus --skill playbook-saas-msa-sure-scale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-saas-msa
Source: https://github.com/sure-scale/doc-haus/tree/main/dochaus/playbooks/playbook-saas-msa
Command: npx skills add https://github.com/sure-scale/doc-haus --skill playbook-saas-msa-sure-scale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing SaaS and cloud master subscription agreements clause-by-clause without a firm playbook leads to inconsistent positions, missed one-sided terms, and redlines that drift from approved language. This Skill gives the reviewer firm-approved positions, fallback text, and unacceptable-term red lines for every major clause type in a US-law SaaS MSA. ## Core Features & Use Cases - Approved clause text: Byte-exact firm-approved replacement language for availability/SLAs, customer data ownership, security obligations, suspension rights, liability caps and carve-outs, and term/renewal/termination, ready to paste into a redline tool. - Conditional fallbacks: Approved fallback formulations that apply only when a stated condition is met (e.g., counterparty rejects a chronic-failure termination right and the service is not business-critical). - Side-aware calibration: Per-clause position notes describing how customer-side and vendor-side asks diverge from the balanced baseline, anchored to published market standards (Bonterms Cloud Terms, Common Paper Cloud Service Agreement). - Use Case: While redlining a vendor's SaaS agreement, you find the liability section caps data-protection breaches at one month of fees. The playbook flags this as unacceptable and supplies the approved 12-month general cap with a 3x enhanced cap for security and data breaches. ## Quick Start Review this SaaS master subscription agreement against the firm playbook and propose redlines using the approved clause text for any position that falls short.

Frequently Asked Questions about playbook-saas-msa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a SaaS MSA against a firm playbook?

Check each clause type in the agreement against the playbook's preferred position, unacceptable list, and approved text. Where the agreement falls short, copy the approved replacement text byte-exact into the redline tool's replacement argument.

What clauses does a SaaS master subscription agreement playbook cover?

This playbook covers availability and service levels, customer data ownership and use, security obligations, suspension rights, limitation of liability caps and carve-outs, and term, renewal, and termination, each with preferred, fallback, and unacceptable positions.

When can I use the fallback clause text instead of the preferred text?

Fallback text may be used only when its stated condition is met, such as the counterparty rejecting a chronic-failure termination right for a non-business-critical service, or a 60-day non-renewal window the client accepts.

Does this playbook apply to agreements governed by non-US law?

No. The playbook states US commercial-market positions only. For matters governed by non-US law, the reviewer must flag the jurisdictional mismatch to the user and check the matter's jurisdiction pack before applying any position.

What liability cap is market standard for SaaS agreements?

The documented market baseline is a mutual aggregate cap of twelve months of fees, with an enhanced cap of three times that amount for confidentiality, data protection, and security breaches, matching Bonterms Cloud Terms and Common Paper structures.