victor-wang-yc-saas-drafter

name	victor-wang-yc-saas-drafter
title	Output Requirements
description	Drafts a customized Customer Agreement starting from the Y Combinator standard form SaaS template. Tailors the agreement through structured intake questions covering fee structure, data handling, ML rights, implementation services, and more. Applies 18 always-on defaults that transform the raw YC form into a professional starting point (renamed to "Customer Agreement", data privacy section added, warranty restructured, consolidated SLA/support exhibit, etc.). Produces a clean .docx and a lawyer-facing memo explaining every change from the YC standard. Use when user says "draft a SaaS agreement", "YC SaaS", "startup SaaS contract", "customer agreement", "SaaS subscription agreement", or "I need a SaaS agreement starting from the YC form". Also trigger when the user is a startup founder discussing SaaS contracting, even if they don't mention YC specifically.
author	Victor Wang
author_url	https://lawve.ai/en/skills/victor-wang-yc-saas-drafter
license	MIT
version	0.1.0
execution_mode	open
jurisdiction	us
practice	commercial
language	en
sources	[{"title":"Decision Matrix","path":"references/decision-matrix.md"},{"title":"Intake Questions","path":"references/intake-questions.md"},{"title":"Supplementary Language","path":"references/supplementary-language.md"}]

Output Requirements

The final .docx must read like a lawyer drafted it. The output must contain:

• Zero YC drafting annotations (*[Note:...]*, *[OPTIONAL:...]*)
• Zero placeholder scaffolding ([OPTIONAL] markers, option guides)
• Zero unfilled template brackets — except deliberate [TBD — description] markers for values the user couldn't provide, documented in the memo

The agreement title is "Customer Agreement" — NOT "SaaS Services Agreement".

If any annotation, note, or non-TBD bracket appears in the output, the draft is not ready. Fix it before delivering.

---

Workflow

Step 1: Load References

Before asking any questions, read all three reference files:

• references/intake-questions.md — 15 question groups with branching and defaults
• references/decision-matrix.md — maps answers to YC template actions (18 always-apply defaults, 12 conditional decisions, variable substitutions, raise-with-lawyer flags)
• references/supplementary-language.md — pre-written clause text anchored by ID (always-apply blocks and conditional blocks)

The decision matrix tells you WHAT to change. The supplementary language gives you the EXACT TEXT to insert. Do not improvise contract language — if the matrix says to insert #DATA-PRIVACY, use the verbatim text from supplementary-language.md. The ONE exception is Order Form Service Fees, where the LLM composes from fee pattern examples.

Step 2: Run Intake

Follow the questions in references/intake-questions.md in order. Apply branching logic (e.g., skip implementation fee if no implementation, skip pilot details if no pilot, skip service capacity if flat pricing).

Key principles:

• Offer defaults but let the user override
• Use [TBD — description] for any value the user can't provide yet
• Confirm all decisions in a summary before proceeding (template at the end of intake-questions.md)
• Do NOT proceed to document assembly without user confirmation

Step 3: Produce the Agreement

Read the YC template from assets/YC_Form_SaaS_Agreement.docx.

Apply modifications in this order:

First — Always-apply defaults (decision-matrix.md Section A, items A1-A18):

1. Rename Order Form title → "Order Form Number One"