Individual skill

the-due-diligence-call

Simulate the due-diligence call where an acquirer's or investor's analyst takes your metrics apart — the questions behind the spreadsheet, the moment a number wobbles, and a debrief on which answers create risk. Use when asked simulate due diligence on my startup, stress-test my metrics before the raise, what will the acquirer's analyst ask, or prep me for the DD call. Produces the call transcript with the analyst's private notes, the internal memo they write afterward, and a debrief separating fixable presentation from fix-the-business findings.

plugins/pm-simulators/skills/the-due-diligence-call/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,542
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# The Due Diligence Call Skill

Founders present metrics; analysts reconcile them. The due-diligence call is where "150% net revenue retention" meets "walk me through the cohort math," and where numbers that were directionally fine become credibility problems because they don't tie to each other. This skill runs that call early — an analyst who has already read the data room, asking the questions the spreadsheet raised — then writes the internal memo and debriefs on the difference between numbers that need better presentation and numbers that need a better business. Honesty is structural: the exercise finds the wobbles so they can be *fixed or disclosed*, never dressed.

## What This Skill Produces

- **The transcript** — 12–18 exchanges, with the analyst's private note after each answer
- **The internal memo** — what the analyst tells their partner/corp-dev lead: proceed / proceed-with-reps / pass, with the real reasons
- **The debrief** — every wobble sorted: presentation-fixable / disclose-and-explain / fix-the-business

## Required Inputs

Ask for these if not provided:
- **The metrics as presented** — the deck's numbers: revenue, growth, retention/NRR, CAC/LTV, pipeline, burn — whatever's claimed
Back to top