agentleFS
SkillMedevSkillMedev/founder-fundraising-os/skills/investor-pipeline-crm/SKILL.md

investor-pipeline-crm

Skill0 starsChanged 5 months agoMITView on GitHub

Use when a founder is managing an active raise across many investors. Triggers on "track my fundraise", "investor pipeline", "fundraising CRM", "how to create FOMO", "run my raise as a process", "investor follow-up cadence", "how long should fundraising take". Turns a scattered raise into a managed, time-boxed process.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 it once [[investor-targeting]] produces the list and outreach begins.

    line 14
  2. Distinctive:

    Treat the raise as a 4-8 week sprint, not an open-ended search.

    line 35
  3. Distinctive:

    When one fund leans in, let the others know there is genuine interest and a timeline - never a fake competing term sheet.

    line 45
  4. Distinctive:

    Every meeting ends with an agreed, dated next step.

    line 52
  5. Distinctive:

    Follow up within 24 hours with the one new thing that advances the decision.

    line 54
  6. Distinctive:

    No recorded pass reasons, so the same flaw kills meeting after meeting.

    line 66

≈ “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

Investor Pipeline CRM

A raise that drifts dies. Investors are pattern-matchers; a process that wanders for months signals a company nobody else wants. The antidote is to run the raise like a disciplined sales pipeline, time-boxed to manufacture a decision window.

When to use this skill

Use it once [[investor-targeting]] produces the list and outreach begins. It is the operating system for the live raise, from first email to signed term sheet ([[term-sheet-negotiation]]).

Pipeline stages

Track every investor through one funnel:

  1. Intro requested - warm path in motion.
  2. First meeting - partner pitch done.
  3. Second / partner meeting - deeper dive, more of the firm involved.
  4. Diligence - data room shared ([[data-room-builder]]).
  5. Term sheet - offer in hand.
  6. Closed / Passed - record the reason on every pass.

For each: name, partner, source/referrer, stage, last touch, next step + date, temperature, and notes. A spreadsheet is enough; the discipline matters, not the tool.

Time-box the raise

  • Treat the raise as a 4-8 week sprint, not an open-ended search.
  • Batch first meetings into a tight window (~2 weeks) so offers land together. Sequential meetings let early passes cool you before the best funds see you.
  • A fundraise you "leave open" reads as a fundraise nobody closed.

Manufacture momentum honestly

Competitive tension is real leverage, but only the truthful kind survives diligence and reference calls between investors (they talk):

  • When one fund leans in, let the others know there is genuine interest and a timeline - never a fake competing term sheet.
  • Move the whole pipeline forward together so interest compounds into a window.
  • Tighten cadence as temperature rises: same-day replies, fast next steps.

Cadence and follow-up

  • Every meeting ends with an agreed, dated next step. No next step = a soft pass; treat it as one.
  • Follow up within 24 hours with the one new thing that advances the decision.
  • Send a brief weekly "raise momentum" note to warm-but-undecided investors - new metric, new logo, new commitment. Reuse the discipline of [[investor-update-writer]].
  • Log every pass reason. Three passes naming the same gap is a signal to fix the pitch or the company, not to send more emails.

Anti-patterns

  • An open-ended raise with no deadline and no batching.
  • Chasing warm-but-stalled investors instead of advancing the whole funnel.
  • Inventing competitive pressure that collapses on a reference call.
  • No recorded pass reasons, so the same flaw kills meeting after meeting.

Deliverable

A live pipeline tracker (stages, partner, source, next step + date, temperature, pass reason), a 4-8 week raise calendar with batched first meetings, and a weekly cadence plan for moving the funnel as one.

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.