SaaS Agreement
Draft a SaaS subscription or licensing agreement for "$ARGUMENTS". Generate a comprehensive agreement covering subscription terms, service levels, data handling, and liability.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"skipped","artifact":"01-draft.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Draft) of the Legal Lifecycle workflow (legal); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or legal when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"refused","artifact":"01-draft.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"started","artifact":"01-draft.md","note":""}.
Check that .singularskills/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g. /legal-risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
Read inputs:
- Read
.singularskills/legal/<project>/00-assess.md for risk and jurisdiction context
- Read
references/contract-template.md for standard contract provisions
Identify service context:
- Nature of the SaaS product and core functionality
- Target customers (B2B, B2C, or both)
- Pricing model (per-seat, usage-based, tiered, flat-rate)
- Deployment model (multi-tenant, single-tenant, hybrid)
- Data sensitivity level and regulatory requirements
Draft the following sections:
- License Grant — scope of access rights (non-exclusive, non-transferable, subscription-based), permitted users, restrictions (no sublicensing, no reverse engineering, no competitive use)
- Subscription Terms — plan descriptions, billing cycle (monthly/annual), auto-renewal terms, upgrade/downgrade procedures, free trial terms (if applicable)
- SLA and Uptime Commitments — uptime target (e.g., 99.9%), measurement methodology, scheduled maintenance windows, service credits for downtime, exclusions from SLA
- Data Ownership and Processing — customer retains ownership of customer data, provider's limited license to process, data processing agreement reference (GDPR Article 28), data location and transfer restrictions
- Security Obligations — provider security standards (SOC 2, ISO 27001, encryption at rest and in transit), breach notification timelines and procedures, security audit rights
- Acceptable Use Policy — prohibited uses, resource limits, abuse handling, account suspension triggers
- Support and Maintenance — support tiers and response times, included vs. paid support, maintenance windows and update policy, end-of-life and deprecation notice periods
- Payment Terms — fees and payment schedule, invoicing procedures, late payment consequences (interest, suspension), price change notice requirements, taxes and withholding
- Suspension Rights — grounds for suspension (non-payment, AUP violation, security threat), notice requirements, data preservation during suspension, reinstatement procedures
- Termination and Data Export/Deletion — termination for cause and convenience, notice periods, data export period post-termination (typically 30-90 days), data deletion certification, survival clauses
- Limitation of Liability — aggregate liability cap (typically 12 months of fees), exclusion of consequential damages, carve-outs (IP indemnification, confidentiality breach, willful misconduct)
- IP Ownership and Feedback — provider owns all IP in the service, customer feedback license (if customer suggestions are incorporated), no implied IP rights
- Compliance with Laws — each party's obligation to comply with applicable laws, specific regulatory compliance commitments (GDPR, HIPAA, SOX as applicable)
- Governing Law — choice of law, dispute resolution mechanism, venue selection
Write the artifact — append to .singularskills/legal/<project>/01-draft.md under a ## SaaS Agreement section. Create the file with a # Draft — <project> heading if it does not exist; if a ## SaaS Agreement section already exists, replace only that section.
Output
The SaaS agreement draft appended to .singularskills/legal/<project>/01-draft.md. Present a summary to the user highlighting:
- Service type and pricing model addressed
- SLA commitments proposed
- Data handling and security provisions included
- Key liability limitations and carve-outs
- Areas flagged for attorney review
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"finished","artifact":"01-draft.md","note":""}.
This artifact is shared by every skill of phase 1 (Draft). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Draft
workflow: legal
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## SaaS Agreement section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is legal-saas-agreement).
End your section with ### Decisions and ### Open questions (one level under your ## SaaS Agreement heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>
1---2name: legal-saas-agreement3description: Draft a SaaS subscription or licensing agreement for a software provider — license grant, subscription and billing, SLA and service credits, data ownership, security, suspension, data export and liability cap. Use when the user sells software as a service and needs the customer contract their business buyers sign. Not for public click-through terms; see /legal-terms-of-service.4metadata:5 source: https://skillmd.com/skills/bromso/legal-saas-agreement6 argument-hint: "[project] [--skip-checks]"7 workflow: legal8 phase: 19 artifact: 01-draft.md10---1112# SaaS Agreement1314Draft a SaaS subscription or licensing agreement for "$ARGUMENTS". Generate a comprehensive agreement covering subscription terms, service levels, data handling, and liability.1516> **Note:** AI-generated legal content does not constitute legal advice. Consult a qualified attorney.1718**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"skipped","artifact":"01-draft.md","note":"<reason or \"none given\">"}`.1920## Prerequisites2122**Part of a workflow.** This skill is phase 1 (Draft) of the Legal Lifecycle workflow (`legal`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `legal` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2324Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"refused","artifact":"01-draft.md","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"started","artifact":"01-draft.md","note":""}`.2526Check that `.singularskills/legal/<project>/00-assess.md` exists. If it does not exist, stop and tell the user:2728> "Run an Assess skill first (e.g. `/legal-risk-assessment <project>`) to generate the prerequisite assessment artifact."2930## Process31321. **Read inputs:**33 - Read `.singularskills/legal/<project>/00-assess.md` for risk and jurisdiction context34 - Read `references/contract-template.md` for standard contract provisions35362. **Identify service context:**37 - Nature of the SaaS product and core functionality38 - Target customers (B2B, B2C, or both)39 - Pricing model (per-seat, usage-based, tiered, flat-rate)40 - Deployment model (multi-tenant, single-tenant, hybrid)41 - Data sensitivity level and regulatory requirements42433. **Draft the following sections:**4445 - **License Grant** — scope of access rights (non-exclusive, non-transferable, subscription-based), permitted users, restrictions (no sublicensing, no reverse engineering, no competitive use)46 - **Subscription Terms** — plan descriptions, billing cycle (monthly/annual), auto-renewal terms, upgrade/downgrade procedures, free trial terms (if applicable)47 - **SLA and Uptime Commitments** — uptime target (e.g., 99.9%), measurement methodology, scheduled maintenance windows, service credits for downtime, exclusions from SLA48 - **Data Ownership and Processing** — customer retains ownership of customer data, provider's limited license to process, data processing agreement reference (GDPR Article 28), data location and transfer restrictions49 - **Security Obligations** — provider security standards (SOC 2, ISO 27001, encryption at rest and in transit), breach notification timelines and procedures, security audit rights50 - **Acceptable Use Policy** — prohibited uses, resource limits, abuse handling, account suspension triggers51 - **Support and Maintenance** — support tiers and response times, included vs. paid support, maintenance windows and update policy, end-of-life and deprecation notice periods52 - **Payment Terms** — fees and payment schedule, invoicing procedures, late payment consequences (interest, suspension), price change notice requirements, taxes and withholding53 - **Suspension Rights** — grounds for suspension (non-payment, AUP violation, security threat), notice requirements, data preservation during suspension, reinstatement procedures54 - **Termination and Data Export/Deletion** — termination for cause and convenience, notice periods, data export period post-termination (typically 30-90 days), data deletion certification, survival clauses55 - **Limitation of Liability** — aggregate liability cap (typically 12 months of fees), exclusion of consequential damages, carve-outs (IP indemnification, confidentiality breach, willful misconduct)56 - **IP Ownership and Feedback** — provider owns all IP in the service, customer feedback license (if customer suggestions are incorporated), no implied IP rights57 - **Compliance with Laws** — each party's obligation to comply with applicable laws, specific regulatory compliance commitments (GDPR, HIPAA, SOX as applicable)58 - **Governing Law** — choice of law, dispute resolution mechanism, venue selection59604. **Write the artifact** — append to `.singularskills/legal/<project>/01-draft.md` under a `## SaaS Agreement` section. Create the file with a `# Draft — <project>` heading if it does not exist; if a `## SaaS Agreement` section already exists, replace only that section.6162## Output6364The SaaS agreement draft appended to `.singularskills/legal/<project>/01-draft.md`. Present a summary to the user highlighting:65- Service type and pricing model addressed66- SLA commitments proposed67- Data handling and security provisions included68- Key liability limitations and carve-outs69- Areas flagged for attorney review7071**Record the run.** After you have written your section, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"legal-saas-agreement","workflow":"legal","phase":1,"project":"<project>","event":"finished","artifact":"01-draft.md","note":""}`.7273This artifact is shared by every skill of phase 1 (Draft). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (`skill` is the phase title, `started` the time of that first write; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`); if it already exists, leave the block alone except to update `finished` and to set `gate` to the worst value among the sections (`skipped` over `passed`).7475```yaml76---77skill: Draft78workflow: legal79phase: 180project: <project>81started: <ISO timestamp>82finished: <ISO timestamp>83agent: <the agent you run in, or "unknown">84gate: <passed|skipped>85---86```8788Open your `## SaaS Agreement` section with one italic line, `*<skill name> · <ISO timestamp> · gate: <passed|skipped>*` (your skill name is `legal-saas-agreement`).8990End your section with `### Decisions` and `### Open questions` (one level under your `## SaaS Agreement` heading, so the section stays one block), in this shape:9192```markdown93### Decisions94- <what was chosen> — <why> — <what was rejected>9596### Open questions97- <what the next phase or a reviewer must settle>98```