buyer-list
Build and organize a universe of potential acquirers for sell-side M&A processes. Identifies strategic and financial buyers, assesses fit, and prioritizes outreach. Use when preparing for a sell-side mandate, building a buyer universe, or evaluating potential partners. Triggers on "buyer list", "buyer universe", "potential acquirers", "who would buy this", "strategic buyers", or "financial sponsors".
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- buyer-list
- description
- Build and organize a universe of potential acquirers for sell-side M&A processes. Identifies strategic and financial buyers, assesses fit, and prioritizes outreach. Use when preparing for a sell-side mandate, building a buyer universe, or evaluating potential partners. Triggers on "buyer list", "buyer universe", "potential acquirers", "who would buy this", "strategic buyers", or "financial sponsors".
03 SKILL.md 正文
Buyer List
Workflow
Step 1: Understand the Target
- Company description, sector, and business model
- Revenue, EBITDA, and growth profile
- Key assets and capabilities (IP, customer relationships, geographic footprint, team)
- Expected valuation range
- Seller preferences (strategic vs. financial, management continuity, timeline)
Step 2: Strategic Buyers
Identify strategic acquirers across categories:
Direct Competitors
- Companies in the same space that would gain market share
- Rationale: Revenue synergies, eliminate competitor, scale
Adjacent Players
- Companies in adjacent markets that could expand into the target's space
- Rationale: Product extension, cross-sell, new market entry
Vertical Integrators
- Customers or suppliers that could integrate vertically
- Rationale: Supply chain control, margin capture, strategic lock-in
Platform Builders
- Large companies building a platform in the space through M&A
- Rationale: Tuck-in acquisition, fill capability gap
For each strategic buyer, assess:
| Buyer | Sector | Revenue | Strategic Fit | Financial Capacity | M&A Track Record | Likelihood | Priority |
|---|---|---|---|---|---|---|---|
| High/Med/Low | Active/Moderate/None | A/B/C |
Step 3: Financial Sponsors
Identify PE/financial buyers:
Platform Investors
- Sponsors looking for a new platform in this sector
- Criteria: Fund size, sector focus, deal size range
Add-on Buyers
- Sponsors with existing portfolio companies that could acquire the target as a bolt-on
- Identify the specific portfolio company and synergy rationale
Growth Equity
- For earlier-stage or high-growth targets
- Minority vs. majority preference
For each sponsor:
| Sponsor | Fund Size | Sector Focus | Portfolio Overlap | Recent Activity | Priority |
|---|---|---|---|---|---|
| A/B/C |
Step 4: Prioritization
Tier the buyer list:
- Tier 1 (5-10): Highest strategic fit, proven acquirers, clear rationale — contact first
- Tier 2 (10-15): Good fit but less obvious — contact in second wave
- Tier 3 (10-20): Possible but lower probability — contact if process needs broadening
Step 5: Contact Mapping
For each Tier 1 buyer:
- Key decision maker (CEO, Corp Dev head, Partner)
- Relationship status (existing relationship, cold outreach, need introduction)
- Known preferences or constraints (size, geography, structure)
- Best approach channel
Step 6: Output
- Excel workbook with:
- Strategic buyers tab (sorted by tier)
- Financial sponsors tab (sorted by tier)
- Contact mapping for Tier 1
- Summary statistics (total buyers by tier, by type)
- One-page buyer universe summary for the engagement letter or pitch
Important Notes
- Quality over quantity — a focused list of 30-40 well-researched buyers beats a list of 200 names
- Research recent M&A activity — buyers who just did a deal in the space are either hungry for more or tapped out
- Check for antitrust concerns with direct competitors — flag any that might face regulatory issues
- Financial sponsors: check fund vintage and deployment pace — a fund nearing end of investment period may be more motivated
- Always ask the seller if there are buyers they want included or excluded
- Update the list as the process progresses — move buyers between tiers based on feedback
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.