agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/fundraising-readiness/SKILL.md

fundraising-readiness

Skill1 starsChanged 26 days agoMITView on GitHub

Prepares a business to raise investment when founders need the story, numbers, data room and investor questions ready.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use three to six months before raising equity or debt, before first investor meetings, or after investor feedback reveals gaps.

    line 9
  2. Distinctive:

    Test the raise against the plan: how much, which milestones it funds, and how many months of runway it buys.

    line 20
  3. Distinctive:

    Use of funds ties to specific milestones and runway

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fundraising Readiness

When to use it

Use three to six months before raising equity or debt, before first investor meetings, or after investor feedback reveals gaps.

What Claude needs

  • client-context.md for business background
  • Amount sought, type of instrument and intended use of funds
  • Historical financials and current forecast
  • Key metrics such as growth, retention, margins and unit economics
  • Cap table and prior funding rounds
  • Team, market and product facts

Method

  1. Test the raise against the plan: how much, which milestones it funds, and how many months of runway it buys.
  2. Score readiness across story, traction, financial model, team, market evidence and legal housekeeping.
  3. Build the core narrative: problem, solution, why now, traction, business model and use of funds.
  4. Prepare a metrics pack with clear definitions and consistent periods.
  5. List the data room contents and flag missing or inconsistent documents.
  6. Draft the 15 hardest investor questions with evidence-based answers, and name the weak spots to fix first.

Output format

Provide a readiness scorecard, narrative outline, metrics pack, data room checklist with status, investor question bank and a dated gap-closing plan.

Quality checks

  • Use of funds ties to specific milestones and runway
  • Metrics reconcile with the financial statements
  • Weaknesses are stated openly, not hidden
  • Legal, tax and securities matters are flagged for professional advisers

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.