SaaS Contract Review & Drafting

Use these conditional thresholds to classify, sort, and greenlight risks, because numeric criteria enable consistent prioritization across deals.

Example: In IP bucket, sort $1.2M unilateral license delta (80% feasibility) over $300K audit right (95% feasibility) using IMPACT formula, because residual gap prioritizes deal-breakers.

Enforce these never/always rules to avoid disputes and scope creep, because violations expose clients to uncapped losses or procedural traps.

• Always cap mutual indemnity at 3x annual fees in vendor/MSA agreements, because it aligns exposure with contract economics.
• Never accept uncapped indemnity without explicit buyer consent in vendor or merger agreements, because it shifts asymmetric risk.
• Symmetric notice periods must be at least 90 days in MSAs/vendor agreements, because shorter terms enable vendor lock-in.
• Governing law must always be NY or DE in MSAs, because these jurisdictions offer predictability in commercial disputes.
• Never advance contract without resolving high scores (≥16), because unaddressed highs cascade to litigation.
• Never markup without DocuSign e-signature timestamp on the bundled summary, because it bounds negotiation scope.
• Always pause automation for bucket mismatches and log override before proceeding, because unlogged changes erode auditability.
• Never send client summary without Total Reset documented in Override Log, because undocumented black swans repeat.

Avoid these errors in sorting and bucketing to prevent misprioritization, because flawed deltas lead to over-focusing on low-impact items.

• Don't sort medium branches using raw exposure only (ignores post-redline subtraction, inflating low-feasibility items like $300K audits over $1.2M IP gaps). Instead, apply Delta and IMPACT formula in locked SORTBY, because it ranks residual risk.
• Don't skip tertiary precedence (IP first) or mix buckets when selecting top 3 for email. Instead, verify via pre-email VLOOKUP checklist with DocuSign timestamp, because it enforces consistent escalation.
• Don't initiate markups without signed client ack in medium branch. Instead, generate approval form first and train via 5 side-by-side reviews, because it curbs scope creep.
• Don't shoehorn outliers into wrong buckets (e.g., AI ethics indemnity into Liability, underrunning delta 40%). Instead, peer-review for new bucket post-template flag, because mismatches distort scoring.

Example: Re-run sorting when template catches junior ranking $300K audit > $800K IP gap, because forced re-run enforces delta priority.

Produce these tools to standardize outputs, because templated automation scales reviews without quality loss.

• Kira Systems AI: For initial clause extraction on 40-60 page docs; output categorized spreadsheet.
• Microsoft Word Track Changes + DocuSign: Redlined contracts with approval routing; include timestamped summaries.
• Excel Tiered Matrix: 10 buckets x 5 points; conditional formatting for flags/density/mismatches (yellow for overrides).
• Excel Risk Matrix: VLOOKUP/SORTBY for mediums; custom IMPACT (=Delta*(Feasibility/100)); Monte Carlo add-in for mergers.
• Excel Summary Sheet: Bundled top issues, email template, resolution log.
• Python-Excel Add-in: Monte Carlo exposure for high-stakes (e.g., black swans).
• Practical Law Templates: Baseline for MSAs post-extraction.

Always output deliverables in the Excel template structure above, because locked formulas prevent manual overrides.

Detect these signals to invoke overrides or resets, because standard buckets fail on hybrids or novelties.

• Bucket mismatch (e.g., sustainability reporting as ESG/data sec hybrid): Triggered by no dropdown match + yellow flag. Pause, log rationale in Override Log (e.g., "Hybrid; precedence=1.5"), apply 1.2 multiplier to delta (=Raw*(1-Feasibility/5)*1.2), re-run SORTBY, because it integrates without bucket proliferation.
• Black swan clause (e.g., quantum IP + metaverse arbitration; infinite exposure): Defies Emerging Risk bucket. Halt via "RESET" tab lock, run 24-hour autopsy (Decision Tree + Monte Carlo), draft standalone Rider for sign-off, reintegrate with log, because bespoke analysis contains uninsurable tails.

Example: For biotech gene-editing + unratified Hague clauses, invoke reset to add "Frontier Law" bucket, because it avoids $2M litigation via isolated Rider.

For detailed examples, walkthroughs, and edge cases, consult 'references/REFERENCE.md'.