Plugin

saas-corpus

A citation-backed knowledge base of how real B2B SaaS companies were actually built. Adds 153 entries to Claude Code: 25 company case studies (Figma, Stripe, Linear, Notion, Snowflake, Datadog, Cursor, Harvey, Atlassian, Ramp, and 15 more), 100+ atomic notes with verbatim founder quotes and dated metrics, 8 function guides (PLG, sales-led, pricing, fundraising, hiring, founder leadership), 4 stage playbooks (pre-seed through scale), 7 failure post-mortems (Quibi, Fast, WeWork, Theranos, Jawbone, Clubhouse, Homejoy), 4 framework syntheses (Obviously Awesome, Play Bigger, MEDDPICC, Crossing the Chasm), and benchmark tables. When you ask Claude about SaaS strategy, fundraising, pricing, GTM, or founder decisions — instead of generic LLM advice, you get specific cases with verbatim quotes, dated numbers, and explicit "when this pattern applies / when it does NOT apply" guardrails to prevent cargo-culting. Every claim cites primary sources (S-1 filings, founder interviews, annual letters). Updated regularly. MIT licensed.

• Published source
• Repository

Analysed

12 October 2026

Last observed

13 October 2026

What the code does

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.