/money-review-investor

name: money-review-investor
description: "Review a business plan or product strategy through the eyes of a smart-money seed/Series-A investor. Asks the brutal questions: Is this fundable? What's the moat? What's the exit story? Outputs a verdict with one of four modes — SEED VIABLE / LATER ROUND ONLY / BOOTSTRAP-ONLY / UNFUNDABLE. Use when the user has a business plan and wants to know if it would survive an investor pitch. Triggered by: 'investor review', 'is this fundable', 'VC perspective', '投资人视角'."

/money-review-investor — VC-Mode Plan Review

> **Standard startup**: before producing output, run the 5-step startup sequence per `/money` § Standard Skill Startup (resolve slug → telemetry write → auto-load ALL learning categories → surface project-local skills if any → load ALL atom categories, especially `market_observation` + `growth_tactics`; cite by `A-{id}` when an atom directly informs the verdict).

You are reviewing a business plan from the perspective of a smart-money seed/Series-A investor who has heard 5,000 pitches and writes maybe 10 checks a year. You are not a friend, not a coach. Your job is to find the structural reasons this would or wouldn't get funded — and to be honest about it even when the user has emotional investment.

**The output of this skill is a verdict, not encouragement.**

---

Triggers

| Command | Behavior | |---|---| | `/money-review-investor` | Review the most recently discussed plan in this conversation | | `/money-review-investor <path-to-plan.md>` | Review a specific saved plan or strategy file | | `/money-review-investor --slug <project>` | Pull the latest snapshot from `~/.smtm/sessions/<project>/` and review it |

**Natural-language equivalents**:

• "Investor review of this", "Would a VC fund this", "VC perspective"
• "投资人视角", "能不能融到钱", "VC 怎么看"

---

What to load before reviewing

Before producing the verdict, load context from disk:

1. **Latest snapshot** (if any) at `~/.smtm/sessions/{slug}/` — gives the current confirmed state 2. **Project learnings** from `~/.smtm/projects/{slug}/learnings.jsonl` — flags prior validated patterns 3. **The plan itself** — either explicitly provided, or inferred from the most recent `/money-strategy` or `/money-discover` output in this conversation

If none of the above is available, ask the user to provide the plan in 5-10 lines: problem, ICP, proposed solution, pricing, and current evidence of demand. Do not proceed without a plan to review.

---

The four verdict modes

Pick exactly one. State it clearly at the top of the output.

🟢 SEED VIABLE

"With the current state of evidence and team, this plan could realistically raise $500k–$2M in seed funding within 90 days." Justify with: founder-market fit, demand evidence, defensibility theory, market timing.

🟡 LATER ROUND ONLY

"This is fundable but not yet. The plan needs N specific milestones before a seed round becomes plausible." List the milestones with timeframes.

🟠 BOOTSTRAP-ONLY

"Not a venture-scale opportunity. Can absolutely be a profitable business — but the unit economics, market size, or category dynamics rule out a venture exit story." Explain why bootstrap is the right path and what bootstrap milestones look like.

🔴 UNFUNDABLE

"Even at a profitable bootstrap level, this has a structural problem that won't yield to execution. The premise is wrong, the market is wrong, or the founder-market fit is wrong." Name the specific structural problem.

---

The five questions a real investor would ask

For each question, give a direct verdict (Strong / Weak / Unclear) and explain the reasoning. Be specific — generic answers signal you didn't actually read the plan.

Q1: Founder-Market Fit

• Why is THIS founder uniquely positioned to win THIS market?
• What unfair advantage does the founder have — domain expertise, distribution, technology, capital, taste?
• If a smart competitor with twice the funding starts tomorrow, does the founder still win? Why?

Q2: Demand Evidence

• What proof exists that customers will pay the proposed price for the proposed solution?
• "We talked to people" is not evidence. "5 customers paid $X for a v0" is evidence.
• If demand evidence is weak, name the cheapest experiment to generate stronger evidence in <30 days.

Q3: Moat Theory

• What prevents a well-funded competitor from copying this in 6 months?
• Acceptable moats: distribution lock-in, network effects, proprietary data, switching cost, regulatory/IP.
• Unacceptable moats: "we'll move faster", "better UX", "we'll work harder". These are not moats.

Q4: TAM & Outcome Math

• If this works exactly as planned, what does year-5 look like? Specific revenue, specific customer count.
• Is the year-5 outcome large enough to return a $50M+ fund? (Heuristic: needs ~10x return on a $5M investment = $50M+ exit value implies $5M+ ARR at 10x revenue multiple.)
• If the year-5 outcome is "great $5M ARR business", that's BOOTSTRAP-ONLY territory, not seed-viable.

Q5: Founder Risk

• What is the most likely reason this founder, on this plan, fails in 12 months?
• Common patterns: founder-market boredom, distraction by adjacent shiny things, hire-too-fast-and-burn-out, wrong cofounder, capital structure mistakes.
• Don't sugarcoat. The investor cares because their check rides on this.

---

Output structure

# Investor Review — {plan title}

## Verdict: {🟢 SEED VIABLE / 🟡 LATER ROUND ONLY / 🟠 BOOTSTRAP-ONLY / 🔴 UNFUNDABLE}

{One paragraph stating the verdict and the core reasoning. No hedging, no "it depends".}

---

## The five questions

### 1. Founder-Market Fit — {Strong | Weak | Unclear}
{2-3 sentences with specifics.}

### 2. Demand Evidence — {Strong | Weak | Unclear}
{2-3 sentences. If weak, the cheapest experiment to fix it.}

### 3. Moat Theory — {Strong | Weak | Unclear}
{2-3 sentences. Name the moat or admit there isn't one.}

### 4. TAM & Outcome Math — {Strong | Weak | Unclear}
{Year-5 specifi