fundraise-plan

fundraise-plan is a command for Claude Code from tjboudreaux/cc-skills-vc-fundraising. It costs 17 tokens per session (655 once invoked), scanned A, original, MIT.

A command for planning a startup fundraising process from preparation through investor outreach. It assesses readiness, organizes target investors, and considers competitive conditions.

In plain words
What is it for?
Use it to review traction, team, investors, funding goals, timeline, runway, and introductions, then design a tiered investor list and fundraising process.
Why use it?
It helps founders find weaknesses before approaching investors and turn an open-ended fundraising effort into a structured process.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the vc-fundraising plugin — 2 skills, 6 commands, 5 agents shipped together

Good fit Use it to review traction, team, investors, funding goals, timeline, runway, and introductions, then design a tiered investor list and fundraising process.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/tjboudreaux/cc-skills-vc-fundraising/fundraise-plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/tjboudreaux/cc-skills-vc-fundraising

Made for: Claude Code.

Or install vc-fundraising, the plugin that ships this one along with the rest of its 2 skills, 6 commands, 5 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for fundraise-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/tjboudreaux/cc-skills-vc-fundraising/fundraise-plan/github.svg)](https://agentmods.dev/commands/tjboudreaux/cc-skills-vc-fundraising/fundraise-plan)
Your own site
<a href="https://agentmods.dev/commands/tjboudreaux/cc-skills-vc-fundraising/fundraise-plan"><img src="https://agentmods.dev/badge/commands/tjboudreaux/cc-skills-vc-fundraising/fundraise-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for fundraise-plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/tjboudreaux/cc-skills-vc-fundraising/fundraise-plan"><img src="https://agentmods.dev/badge/commands/tjboudreaux/cc-skills-vc-fundraising/fundraise-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 655 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00655
Opus 5 $0.00009 $0.00328
Sonnet 5 $0.00003 $0.00131
Haiku 4.5 $0.00002 $0.00065

Measured 12d ago against content hash 8d0c6ab6e45a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

fundraise-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/fundraise-plan.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fundraise Plan

You are helping a founder plan and structure their entire fundraising process for maximum effectiveness.

Input

The user provided: $ARGUMENTS

Process

Step 1: Readiness Assessment

Launch the fundraise-strategist agent to assess readiness across the 13 proof points. Instruct it to apply its thinking toolkit: map the investor ecosystem using systems thinking, identify the current bottleneck using theory of constraints, run a pre-mortem on the raise, and design the rapid decision-loop cadence for the active sprint. Gather:

  • Current traction metrics (MRR, growth rate, users)
  • Team composition and notable hires
  • Existing investor base and relationships
  • Target raise amount and stage
  • Desired timeline
  • Current runway
  • Any existing VC relationships or warm intros available

Score each proof point 1-5 and identify:

  • Green areas (ready to pitch)
  • Yellow areas (need strengthening but won't block)
  • Red areas (must fix before launching)

Step 2: Process Design

Based on readiness, design the fundraising process:

Target Investor List Strategy:

  • How to build the 3-tier target list (Tier 1 dream, Tier 2 strong, Tier 3 backup)
  • Research approach for identifying thesis-fit investors
  • Warm intro mapping strategy

Timeline:

  • Week-by-week plan from preparation through close
  • Key milestones and decision points
  • Optimal launch timing based on calendar and company trajectory

Materials Needed:

  • Pitch deck (Sequoia 10-slide format)
  • Executive summary (1-page)
  • Data room contents
  • Q&A preparation

Competitive Dynamics Plan:

  • How to compress meetings to create natural competitive dynamics
  • Decision deadline strategy
  • What to do when you get a term sheet

Step 3: Present the Plan

Deliver a complete fundraising playbook:

  1. Readiness Scorecard -- 13 proof points with scores and recommendations
  2. Pre-Launch Checklist -- Everything to prepare before first meeting
  3. Week-by-Week Timeline -- Specific actions each week
  4. Target List Framework -- How to build and prioritize your list
  5. Communication Templates -- Intro request, follow-up, and update emails
  6. Decision Framework -- How to evaluate term sheets
  7. Risk Mitigation -- Common mistakes to avoid
  8. Ecosystem Map -- How investors, intros, meetings, and momentum interconnect
  9. Bottleneck Analysis -- The single constraint currently limiting fundraising success and how to address it

Read the full file on GitHub · 81 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 81 lines · 17 tokens per session scan A 8d0c6ab6e45a

Subscribe to this mod's changes

fundraise-plan is a command published in the GitHub repository tjboudreaux/cc-skills-vc-fundraising (24 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 655 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.