Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Exit Preparation

ASecurity

Structure an exit readiness plan covering vendor due diligence preparation, buyer universe mapping, equity story refinement, management presentation design, and process timeline.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoapiperformancedocumentation

Works with

cliapi

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-finance-skills --skill exit-preparation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Exit Preparation?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Exit Preparation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-exit-preparation/badge)](https://www.skillsdirectory.com/skills/andreworia-exit-preparation)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: Exit Preparation
description: Structure an exit readiness plan covering vendor due diligence preparation, buyer universe mapping, equity story refinement, management presentation design, and process timeline.
---

# Exit Preparation

## When to use

Use this skill 12-18 months before a planned exit. Exit preparation is not something to start when the banker is hired -- by then, it is too late to address the issues that depress valuation. The skill is also useful at the annual value creation review in year 3 of a 5-year hold, when the team needs to assess whether the business is on track for a premium exit or whether specific actions are required to maximise exit value. It is equally applicable to full company sales, secondary sales to other PE firms, and management buyouts.

## What it does

Produces: (1) a vendor due diligence (VDD) readiness assessment identifying the gaps most likely to surface in a buyer's diligence and impair the value; (2) a buyer universe map with strategic and financial buyer categories; (3) an equity story framework for the management presentation; and (4) a process timeline from mandate to close.

## Method

### Step 1 -- VDD readiness assessment

A VDD readiness assessment looks at the business from a buyer's perspective. The goal is to find the issues before the buyer does, fix them or explain them, and arrive at the data room in a position of control rather than defence. Structure the assessment across four workstreams:

**Financial readiness:**
- Are the management accounts accurate, timely (sub-10-day close), and internally consistent across all periods?
- Is the EBITDA reconciliation clean? Could a buyer's QoE advisor find significant add-backs that management did not disclose?
- Is the revenue recognised correctly and consistently? For subscription businesses: is ARR calculated consistently, and is NRR calculated using a method buyers will accept?
- Are working capital movements fully explained? A buyer will ask about working capital requirements at close.
- Are there any open tax exposures, warranty claims, or contingent liabilities that need to be resolved or disclosed?

**Commercial readiness:**
- Is the customer contract documentation complete and organised? Can the data room provide executed contracts for the top 20 customers within 48 hours?
- Are NDA and change-of-control provisions in customer contracts reviewed? Some contracts require customer consent for a change of control -- identify and address these before the process begins.
- Is the churn data clean and calculable? Buyers will request gross and net retention by cohort, by year. If this data does not exist in a clean form, begin building it now.
- Is there any customer concentration issue that has worsened since acquisition? Address through diversification before marketing, if possible.

**Legal and IP readiness:**
- Is the corporate structure clean? Any unnecessary holding entities, historical minority interests, or outstanding option pools should be resolved.
- Is IP ownership clear? All software, algorithms, data sets, and brand assets should be owned by the operating company, not a founder personally or a related entity.
- Are employment agreements in place for the full management team and key technical staff?
- Are there any open disputes, regulatory notices, or pending litigation items? Disclose early or resolve before process.

**Operational readiness:**
- Is the management team complete? A buyer will discount the business if a key seat is vacant at the time of process.
- Does the business have a clean IT environment (single ERP, no legacy systems relying on key-man maintenance)?
- Are there any deferred capex or maintenance obligations that a buyer will identify as a liability?

For each gap identified: state the issue, the impact on buyer perception or valuation, the action required, the owner, and the timeline to resolve.

### Step 2 -- Buyer universe mapping

Map the potential buyer universe across two categories:

**Strategic buyers:** Corporates or platforms for whom the acquisition would represent a strategic extension (geographic, product, customer, or capability). For each strategic buyer type:
- Rationale for acquisition (what gap does this fill for them?)
- Likely synergies they would underwrite (revenue synergies from cross-sell, cost synergies from overlap)
- Whether synergies are likely to support a higher valuation (strategic premium) or whether they are purely financial
- Any barriers to acquisition (regulatory overlap, cultural fit, prior M&A experience)

**Financial buyers (PE):** Sponsors for whom this asset fits a fund mandate. For each PE buyer category:
- Fund stage and size alignment (does the asset fit their target EBITDA range?)
- Platform fit: is this a standalone acquisition or an add-on to an existing portfolio company?
- Hold horizon alignment: is the buyer in deployment mode or near the end of fund life?

Identify the most likely 5-10 buyers who would compete in a full process. Competition among buyers is the primary driver of a premium price -- a process with fewer than 3-4 serious bidders is likely to result in a below-market outcome.

**Buyer universe summary:** State whether the business is more attractive to strategics or financials, and why. This drives the process design -- a broad strategic process is different from a targeted PE secondary.

### Step 3 -- Equity story framework

The equity story is the narrative that positions the business for premium valuation. It must be built around the evidence from the last 3-5 years of value creation -- not projections, not assertions. A buyer's IC will strip out forward projections and back-calculate what the management plan implies; they will rely more on historical evidence.

Structure the equity story around five themes:

**Quality of business:** The moat, the customer relationships, and the revenue quality evidence. Lead with the single most compelling quality indicator -- the one that makes this business stand out in the buyer's competitive set.

**Market position and growth:** The evidence for market share gains over the hold period, and the rationale for continued growth. Show the growth drivers as an operating decomposition (new customers, expansion, price) rather than a single top-line number.

**Financial performance:** The EBITDA bridge from acquisition to exit. Show how the fund's value creation plan was executed. Present adjusted EBITDA consistently with how it was calculated at acquisition -- buyers will back-calculate the seller's add-back history.

**Management team:** The track record of the team over the hold period, with specific operating achievements. If there have been management changes, explain them and demonstrate the quality of the resulting team.

**Scalability and exit multiple thesis:** Why this business should trade at a premium multiple. The argument for an exit at a higher multiple than entry must be grounded in: (a) scale achieved, (b) quality of revenue improvement, (c) sector re-rating, or (d) strategic value to the buyer. Do not claim a multiple premium without a specific reason.

### Step 4 -- Management presentation structure

The management presentation (typically 40-70 slides for a formal process) must be structured to answer the buyer's due diligence questions in advance, not just tell the company's story:

1. Executive summary: deal highlights, key financial metrics, investment thesis in 3 bullets
2. Company overview: history, business model, product / service description
3. Market: market size, growth drivers, competitive landscape
4. Business model: how revenue is generated, how the product is sold, gross margin drivers
5. Customer: the customer profile, key relationships, retention and expansion evidence
6. Product / technology: what makes it defensible
7. Financial performance: 3-year history and LTM, with clear EBITDA bridge
8. Growth plan: the next 3 years, with bottoms-up assumptions
9. Management team: bios, track record, incentive alignment post-transaction
10. Transaction overview: proposed structure, timing, conditions

Design principle: each section should answer the question a sophisticated buyer would ask before a management meeting. If a buyer could form their initial view entirely from the presentation, it has done its job.

### Step 5 -- Process timeline

A well-run sell-side process runs 16-22 weeks from mandate to signing:

**Weeks 1-3 (preparation):** Engage sell-side advisor, finalise VDD reports, prepare data room, write CIM draft.

**Weeks 4-6 (marketing):** Distribute teaser to buyer universe. Sign NDAs. Distribute CIM. Set indicative bid date.

**Weeks 7-9 (indicative bids):** Receive and evaluate indicative offers. Shortlist buyers for management meetings (typically 4-8).

**Weeks 10-12 (management meetings and data room):** Conduct management presentations for shortlisted buyers. Open full data room. Begin management Q&A sessions.

**Weeks 13-15 (final bids):** Buyer final diligence. Receive final offers. Select preferred bidder or run best-and-final round.

**Weeks 16-18 (exclusivity and negotiation):** Enter exclusivity with preferred bidder. Negotiate SPA. Confirm financing.

**Weeks 19-22 (signing and closing):** Sign SPA. Regulatory approvals (if required). Close.

Flag process risks: a concentrated buyer universe (fewer than 5 active bidders) reduces competitive tension and is the most common reason a process fails to achieve a premium price.

## Inputs

- The original IC memo (to compare exit EBITDA and multiple assumptions to actuals)
- Current financials: LTM revenue, EBITDA, ARR (if applicable), customer metrics
- A description of the business as it exists today (what has changed since acquisition)
- The management team roster and any changes since acquisition
- Target exit timeline (12 months, 18 months, or other)

## Output format

Five sections:
1. VDD readiness assessment (four workstreams -- financial, commercial, legal, operational -- each as a paragraph with a gap list)
2. Buyer universe map (strategic and financial categories, 5-10 specific buyer profiles, universe summary)
3. Equity story framework (five themes, each as 2-3 sentences)
4. Management presentation structure (10-section outline with one-sentence description of each section)
5. Process timeline (week-by-week from mandate to close, with key milestones and process risks flagged)

Total length: 1,200-1,800 words. Written for the deal team and the sell-side advisor briefing.

## Example

**Equity story quality of business (excerpt):**
SoftServe Analytics enters the exit process with 94% gross revenue retention and 118% NRR over the last 3 years of sponsor ownership, up from 85% GRR and 110% NRR at acquisition. The primary moat -- deep ERP integration requiring a 6-9 month migration to replace -- has strengthened as the average integration depth per customer has increased from 3 modules to 5 modules. The top-10 customer concentration has declined from 54% to 41% of revenue over the hold period, reducing the most significant quality risk identified at acquisition. These three data points form the core of the buyer's business quality argument: the moat is durable and widening, not eroding.

Attribution

andreworiaandreworia
View sourceMore from andreworia →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →