fundraising-strategy-planner

fundraising-strategy-planner is a command for Claude Code from maigentic/stratarts. It costs 42 tokens per session (8,411 once invoked), scanned A, original, MIT.

A tool for organising the full process of raising startup funding, from choosing investors and contacting them to due diligence, negotiating terms, and closing.

In plain words
What is it for?
Use it to create a fundraising timeline, investor tiers, outreach cadence, meeting stages, due-diligence preparation, term-sheet goals, and closing steps.
Why use it?
It turns fundraising into a sequence with deadlines and targets, reducing the risk of missed follow-ups or unprepared meetings.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: positional $N argument.

Part of the stratarts plugin — 27 commands shipped together

Good fit Use it to create a fundraising timeline, investor tiers, outreach cadence, meeting stages, due-diligence preparation, term-sheet goals, and closing steps.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/maigentic/stratarts/fundraising-strategy-planner
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/maigentic/stratarts

Made for: Claude Code.

Or install stratarts, the plugin that ships this one along with the rest of its 27 commands.

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 fundraising-strategy-planner

README.md
[![agentmods](https://agentmods.dev/badge/commands/maigentic/stratarts/fundraising-strategy-planner/github.svg)](https://agentmods.dev/commands/maigentic/stratarts/fundraising-strategy-planner)
Your own site
<a href="https://agentmods.dev/commands/maigentic/stratarts/fundraising-strategy-planner"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/fundraising-strategy-planner/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 fundraising-strategy-planner

Your own site · 80×15
<a href="https://agentmods.dev/commands/maigentic/stratarts/fundraising-strategy-planner"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/fundraising-strategy-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,411 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.00042 $0.08411
Opus 5 $0.00021 $0.04206
Sonnet 5 $0.00008 $0.01682
Haiku 4.5 $0.00004 $0.00841

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

Security

Grade A, and why

fundraising-strategy-planner 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 9d 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.

stratarts/commands/fundraising-strategy-planner.md · 859 lines

How it starts

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

fundraising-strategy-planner

Mission: Create a comprehensive fundraising strategy covering timeline, investor targeting, outreach cadence, meeting progression, due diligence, negotiation, and closing. Run a disciplined fundraising process that maximizes leverage, minimizes distraction, and closes your round on favorable terms.


STEP 0: Pre-Generation Verification

Before generating HTML output, verify all placeholders are populated:

Score Banner Placeholders

  • {{COMPANY_NAME}} - Company name
  • {{ROUND_NAME}} - Round type (Pre-Seed/Seed/Series A)
  • {{TIMESTAMP}} - Generation timestamp
  • {{RAISE_AMOUNT}} - Target raise amount (e.g., "$2.5M")
  • {{VALUATION}} - Post-money valuation (e.g., "$12M")
  • {{TIMELINE_MONTHS}} - Fundraising timeline (e.g., "5 mo")
  • {{TOTAL_INVESTORS}} - Target investor count (e.g., "100")
  • {{TERM_SHEET_TARGET}} - Term sheet goal (e.g., "2-3")
  • {{RUNWAY_MONTHS}} - Current runway (e.g., "8 mo")

Content Section Placeholders

  • {{EXECUTIVE_SUMMARY}} - 4 exec cards (goals, traction, profile, outcomes)
  • {{TIMELINE_PHASES}} - 4 timeline phase blocks with items
  • {{INVESTOR_TIERS}} - 3 tier cards (Tier 1/2/3 counts and descriptions)
  • {{OUTREACH_STRATEGIES}} - 2 outreach cards (warm intros, cold outreach)
  • {{FUNNEL_STAGES}} - 6 funnel stages with counts and conversion rates
  • {{MEETING_STAGES}} - 5 meeting stage items (intro → closing)
  • {{DATAROOM_CATEGORIES}} - 4 data room category checklists
  • {{TERM_SHEET_TERMS}} - 6 term sheet term cards
  • {{CLOSING_WEEKS}} - 5 closing week items
  • {{DISCIPLINE_METRICS}} - 4 discipline metric cards
  • {{NEXT_STEPS}} - 6 prioritized next step items

Chart Data Placeholders

  • {{TIMELINE_LABELS}} - JSON array of phase names
  • {{TIMELINE_DATA}} - JSON array of week durations
  • {{TIER_DATA}} - JSON array [tier1, tier2, tier3] counts
  • {{FUNNEL_LABELS}} - JSON array of funnel stage names
  • {{FUNNEL_DATA}} - JSON array of funnel counts

Read the full file on GitHub · 859 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. 9d ago First seen · 859 lines · 42 tokens per session scan A 8cef3a9a8b5c

Subscribe to this mod's changes

fundraising-strategy-planner is a command published in the GitHub repository maigentic/stratarts (40 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 8,411 once invoked, about $0.0002 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.