Purpose
Produce a decision-ready acquisition thesis for a SaaS target — grounding strategic rationale in actual SaaS metrics, quantifying revenue and cost synergies, surfacing the deal-killing risks early, and ending with a defensible go/no-go recommendation. Replaces the ad-hoc "why we should buy this" narrative with a structured memo an IC or deal team can act on.
When to Use
Invoke this skill when the user asks to:
- Build an acquisition thesis or investment memo for a SaaS target
- Evaluate whether a specific SaaS company is worth acquiring
- Screen an inbound deal or narrow a target shortlist
- Pressure-test the strategic rationale behind a proposed transaction
- Prepare materials for an investment committee or deal review
- Assess synergies, integration risk, or fit between an acquirer and a SaaS target
Inputs Required
Before starting, collect:
- Target description: What the company does, product, market, and stage (seed to growth to mature)
- Target SaaS metrics: Whatever is available — ARR/MRR, growth rate, gross retention (GRR), net retention (NRR), churn, gross margin, CAC, LTV, customer count, ACV
- Acquirer context: Who the acquirer is, their business, and why they're looking
- Strategic objective: What the acquisition is meant to achieve (market entry, consolidation, product gap, talent, defensive)
- Deal parameters: Rumored/proposed valuation, structure (cash/stock/earnout), or "TBD"
- Integration model: Bolt-on, tuck-in, platform, or standalone hold
- Known concerns: Anything already flagged — customer concentration, tech debt, key-person risk, competitive threats
If SaaS metrics are partial or missing, model the thesis around the available data, flag the gaps explicitly, and note which metrics must be confirmed in diligence.
Instructions
Step 1: Strategic Rationale
State the acquisition logic in one crisp paragraph, then classify it:
- Deal archetype: Market entry / Market consolidation / Product-line extension / Capability or talent acquisition / Defensive / Financial (multiple arbitrage)
- Strategic fit test: Does this target advance a stated acquirer objective, or is it opportunistic? Name the specific gap it closes.
- Build-vs-buy check: Could the acquirer build this capability faster/cheaper internally? If yes, the thesis weakens — say so.
Step 2: SaaS Metrics Diagnosis
Assess the quality of the revenue, not just the size. Benchmark against these bars:
- Growth: <20% (mature), 20–40% (solid), 40%+ (high-growth) YoY ARR
- Net Revenue Retention (NRR): <100% (leaky), 100–110% (healthy), 110%+ (strong expansion engine)
- Gross Revenue Retention (GRR): below 85% signals a churn problem; 90%+ is strong
- Gross margin: SaaS should be 70%+; below 65% suggests services-heavy or infrastructure-heavy revenue
- Rule of 40: growth rate + FCF (or EBITDA) margin ≥ 40 = healthy; flag if below
- CAC payback: under 12 months is strong; over 24 months signals inefficient acquisition
- Customer concentration: any single customer >10% of ARR is a risk flag
- ARR quality: contracted/committed vs. usage-based vs. month-to-month — durability differs
For each metric provided, state the value, the benchmark verdict, and the implication. Where data is missing, mark it as a diligence item.
Step 3: Synergy Modeling
Separate and size synergies — never blend them into one number:
- Revenue synergies: Cross-sell into acquirer base, upsell target's base, geographic expansion, pricing power, bundling. Estimate order of magnitude and time-to-realize (0–12 / 12–24 / 24+ months).
- Cost synergies: G&A consolidation, hosting/infrastructure, redundant tooling, go-to-market overlap, R&D consolidation. Flag which are one-time vs. recurring.
- Synergy discount: Apply a realistic haircut — revenue synergies routinely underdeliver; weight cost synergies higher in the base case.
- Dis-synergies: Customer overlap cannibalization, attrition of target's talent/customers post-close, integration distraction.
Step 4: Valuation Framing
Frame value without pretending to run a full model:
- Multiple context: ARR multiple or EBITDA multiple implied by the proposed price; compare to the metrics profile from Step 2 (high-NRR, high-growth targets warrant higher multiples)
- Payback lens: Roughly how synergies affect the effective multiple
- Structure implications: Where earnouts, retention packages, or stock make sense given the risk profile
Step 5: Integration Risk Assessment
Match risk to the integration model chosen:
- Tech stack: Architecture compatibility, migration burden, tech debt, multi-tenancy
- Product: Roadmap conflict, feature overlap, platform rationalization
- Team: Key-person dependency, culture fit, likely attrition, retention needs
- Customer: Contract assignability, churn risk from brand/pricing changes, support continuity
- Assign each a High / Medium / Low rating with a one-line justification.
Step 6: Deal Risks & Red Flags
List the risks that could kill or reprice the deal, ranked by severity:
- Concentration, declining NRR, unsustainable growth spend, competitive displacement, regulatory/data risk, misrepresented metrics
- For each: severity (High/Med/Low), what to confirm in diligence, and potential mitigation or deal-structure response
Step 7: Go / No-Go Recommendation
Take a position. Deliver:
- Verdict: Pursue / Pursue with conditions / Pass
- Rationale: 2–3 sentences tying strategic fit, metrics quality, and risk together
- Conditions or walk-away triggers: What must be true (or must not be true) for the deal to proceed
- Top 3 diligence priorities: The questions that most change the answer
Output Format
- Structure: Seven labeled sections in the order above; metrics and integration risks presented in tables; synergies split into revenue/cost sub-lists
- Length: 1,000–1,400 words
- Format: Structured memo — scannable headers, tables for metrics and risk ratings, tight prose for rationale
- Sections: Strategic Rationale → SaaS Metrics Diagnosis → Synergy Modeling → Valuation Framing → Integration Risk → Deal Risks & Red Flags → Go/No-Go Recommendation
- Tone: Corporate development / IC memo — analytical, direct, quantified, willing to recommend a pass
Quality Checklist
Before delivering output, verify:
- [ ] Every SaaS metric provided is stated with a benchmark verdict and implication — no metric quoted without interpretation
- [ ] Revenue and cost synergies are separated, sized by order of magnitude, and given a time-to-realize
- [ ] Rule of 40 and NRR are addressed explicitly (or flagged as missing diligence items)
- [ ] Integration and deal risks each carry a High/Med/Low rating with justification
- [ ] Missing inputs are surfaced as named diligence priorities, not silently ignored
- [ ] The recommendation takes a clear position (Pursue / Conditions / Pass) — no hedging
Notes
- A high ARR number with sub-100% NRR is a weaker asset than a smaller company compounding at 120% NRR — weight retention quality over headline size
- Revenue synergies are the most over-promised line in any thesis; a credible memo discounts them heavily and leans on cost synergies for the base case
- If build-vs-buy clearly favors build, the honest thesis is a "Pass" — say it rather than manufacturing rationale
- When metrics look too clean for the stage, treat it as a red flag and route it to diligence, not the strengths column
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills