pipeline-tracker
Skill4 starsChanged 5 months agoMITView on GitHub
Run a fundraise like a sales pipeline — track every investor conversation, its stage, the next action, and follow-up timing in a simple file-based CRM. Use when a founder says "track my fundraising", "set up an investor CRM", "who do I need to follow up with", "update my pipeline", or wants to manage investor outreach and momentum. Produces and maintains a plain-text/CSV tracker, no SaaS required.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- pepperworks/Job-Search-Skillstheir own version, first seen Nov 1, 2026
- sami2919/SignalForcetheir own version, first seen Aug 4, 2026
- megandmartin/agent-skills-repotheir own version, first seen Jul 24, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- sami2919/SignalForce★ 9same name
- megandmartin/agent-skills-repo★ 3same name
- pepperworks/Job-Search-Skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- cold-callSkill
- cold-emailSkill
- fundraising-agentsSkill
- investor-researchSkill
- investor-targetingSkill
- outreach-diagnosisSkill
- pitch-narrativeSkill
- warm-introSkill
- warm-path-finderSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read shared/references/outreach-ethics.md — follow-up discipline here must stay on the right side of persistent-vs-pestering.
- Very specific: line 19
Create a tracker file in the user's project (default: fundraising-pipeline.csv, or Markdown table if they prefer).
- Distinctive: line 38
Keep it simple and linear.
- Distinctive: line 51
When the founder gives an update ("had a call with X", "Y passed", "Z asked for the deck"), you:
- Very specific: line 81
Never invent investor names or activity to fill the tracker — it holds only what the founder reports or what was researched (with sources) …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fundraising pipeline tracker
A raise is a sales process, and the founder is running it against time. Momentum is everything: a tight, parallel process creates urgency; a slow, serial one leaks energy and signals weakness. This skill sets up and maintains a simple file-based CRM so nothing falls through and the founder always knows the next action.
Read shared/references/outreach-ethics.md — follow-up discipline here must stay
on the right side of persistent-vs-pestering.
Set it up (first run)
Create a tracker file in the user's project (default:
fundraising-pipeline.csv, or Markdown table if they prefer). Use the template
in references/pipeline-template.md. Columns:
| Field | What it holds |
| Investor | Firm or angel name |
| Partner | The specific person you're working |
| Tier | A / B / C (from investor-targeting) |
| Stage | Pipeline stage (see below) |
| Source | How you got in (warm intro via X / cold / inbound) |
| Last contact | Date of last touch |
| Next action | The single next thing you owe |
| Next action date | When to do it |
| Check / interest | Indicated check size or interest level |
| Notes | Anything said — objections, who they cc'd, asks |
Pipeline stages
Keep it simple and linear; every investor sits in exactly one:
- Researched — qualified as a fit, not yet contacted.
- Contacted — first outreach sent (cold or intro requested).
- Engaged — they replied / a call is booked.
- Met — first meeting done.
- Diligence — follow-up meetings, data room, partner meeting.
- Term sheet / Committed — verbal or written commitment.
- Passed — they said no (record why — it's signal).
- Dormant — no response after the follow-up sequence ended.
Running it (ongoing)
When the founder gives an update ("had a call with X", "Y passed", "Z asked for the deck"), you:
- Update the row — move the stage, set Last contact, write the Notes.
- Set the next action + date — every active investor must have a next action owned by the founder. No row in stages 2–6 should have an empty next action.
- Surface what's due — list who needs a follow-up today/this week, and draft
it via the
cold-emailorwarm-introskill if asked. - Watch the funnel — report simple counts (e.g., 24 researched, 11 contacted, 4 met, 1 in diligence) so the founder sees conversion and knows whether to add more top-of-funnel.
Momentum coaching (the point of tracking)
- Run in parallel, not serial. Batch outreach so meetings cluster — multiple interested investors at once creates real (not fake) urgency and better terms.
- Mind the follow-up cadence. Persistent = two value-adding follow-ups, then
stop (per the
cold-emailsequence). Pestering = more. The tracker enforces the gap, not just the nudge. - Log every pass and why. Five passes for the same reason = a pitch or targeting problem to fix, not just bad luck.
- Keep top-of-funnel full until you have committed term sheets. A thin pipeline tempts founders to over-chase one lukewarm investor.
Output
- On setup: the tracker file, created and explained.
- On update: confirm what changed, then a short "due now / due this week" action list and the current funnel counts.
- Never invent investor names or activity to fill the tracker — it holds only
what the founder reports or what was researched (with sources) in
investor-targeting/investor-research.
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
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.