The Fundraising OS.
Run your raise like a system.
Most rounds aren't lost on the pitch. They're lost on the process — the list you never built, the intro you didn't map, the follow-up that landed three days late. Twelve Claude skills orchestrate the operational raise so you can spend your attention on the conversations that matter.
Inbound won't fill a round. You build the list, find the paths in, and keep every thread moving in parallel — without dropping one.
And once you're in conversations, the operational signals matter as much as the pitch: how fast you follow up, how specific your outreach is, how ready your data room is the moment someone asks. The OS handles both — and configures its own intensity to whether you're running a quiet, passive raise or a sharp, time-boxed process.
Most founders raise by improvising. That's the wrong lever.
A raise is a parallel operation with a dozen live threads, each decaying if you miss the next action. Here's where it leaks.
Waiting on inbound
You take the meetings that come instead of building the 40 funds whose thesis actually fits. The round never gets a real top of funnel.
Cold into the void
You email partners with no warm path mapped. A trusted intro beats ten perfect cold emails — but only if you find it first.
Mail-merge outreach
The same email with the name swapped. A partner smells it in one line. Specificity is the difference between ignored and answered.
Threads fall through
Twelve conversations, twelve next-actions, no system. The follow-up that comes three days late tells the investor how you'll run the company.
Scrambled data room
A partner asks for the room and you spend two days assembling it. Readiness on the spot is itself a signal — absence of it is too.
Silence after a "no"
You go quiet on the funds that passed. They're often the leads of your next round — if they watch you execute for six months.
Four phases. Twelve skills. One context file.
You fill the context once; every skill inherits its numbers, names, and narrative. The phases run roughly in order, with warmth running the whole time and the close at the end.
Foundation
Set the source of truth, then decide how you're raising at all.
- raise-context
- fundraising-plan
Build
Targets, paths in, the story, and the numbers behind it.
- investor-list
- warm-intro-map
- deck
- financial-projection
Run
Reach out, manage the pipeline, pre-answer diligence.
- outreach
- pipeline
- data-room
Sustain & Close
Keep everyone warm, pace the whole thing, and drive a clean window to the wire.
- investor-comms
- pace
- closing
Twelve specialists. One source of truth. All free.
This is a Human-Assisted Autonomous Organization (HAAO) for your raise: the skills do the operational work and surface the calls only you can make.
Foundation
The single source of truth
Interviews you, pressure-tests every claim, and flags what's missing or weak before it ever reaches an investor. Everything downstream inherits this file.
Passive vs. active vs. hybrid
Decides the mode before you target anyone — a quiet "always slightly raising" or a sharp, time-boxed process — and sets the intensity for every skill after it.
Build
The 40 funds worth your time
Researched and scored by fit, output as a paste-ready sheet with a fit tier and a warm-path flag per partner. Depth over volume — a clean 35 beats a bloated 80.
The best path to each partner
Maps the strongest warm intro through your network and drafts the forwardable note your connector can send in fifteen seconds.
Story first, slides second
Headlines that are claims, not labels. A traction page partners screenshot. Hands the structure to the deck builder for the rendered file.
Defensible, not fantastical
A driver-based model plus the one-page assumptions memo you actually defend. Runway and ask reconcile exactly with the deck.
Run
Written for one partner
A researched hook, one proof point, a small specific ask — never the same body with the name swapped. Warm and cold variants per target.
Nothing drops
A weekly Monday brief of what needs action, same-day follow-up generators, and stage tracking across every thread in parallel. Speed is the message.
Answers before they're asked
The full index, a claim-to-proof map, a ranked gap list, and staged access. Ready the moment a partner asks — which is itself the signal.
Sustain & Close
Two tracks — yes and no
Monthly updates that show up like clockwork, with an honest challenges line. Out-execute the reason they passed, in writing, and the next round writes itself.
Makes the machine move
Sets the communication cadence, decides which skill runs next, keeps every artifact in sync, and surfaces the one thing that has to happen today. The glue that orchestrates the whole raise.
The terms that actually matter
A plain-language term-sheet readout — pool placement, preference, board — negotiation prep, and a real close window. Clarifies so you decide; not legal advice.
Plan → Build → Reach → Manage → Sustain → Close
The skills run at the cadence a live raise runs. Each feeds the next; the pipeline keeps every thread in sync.
| When | What runs |
|---|---|
| Per meeting | Same-day follow-up that answers their specific questions |
| Daily | Overdue-thread scan — anything live untouched >5 days |
| Weekly | Monday pipeline brief; the next wave of outreach |
| Monthly | Investor update to both tracks — committed and passed |
| Per stage | Decision gate — keep going, pause, or flip passive→active |
| At close | Term-sheet readout, negotiation prep, the close window |
Running in 5 minutes. No terminal needed.
Two ways in: as a Claude Code plugin, or dropped straight into a Claude project on the web.
Download Claude Code Desktop
Go to https://claude.com/code · download for your OS Open it and sign in with your Claude account.
Open any folder as a project
File → Open Folder… · pick any folder, even an empty one. The skills write their sheets and drafts into it.
Install the plugin (two commands)
/plugin marketplace add kalibrio/fundraising-os /plugin install fundraising-os@kalibrio/fundraising-os
Confirm 12 skills are loaded
Type "/" then "raise" — you should see: /raise-context /fundraising-plan ...
Run your first skill
/raise-context # It interviews you, builds your source-of-truth file, # and tells you exactly what to fix before outreach.
Common questions
What's the difference between passive and active fundraising? +
Passive is "always slightly raising": a rolling instrument kept quietly open, warm inbound only, founder stays building — lower intensity, no public in-market signal, but weaker competitive tension. Active is a structured, time-boxed process: full list, parallel conversations, an engineered close window — better terms and speed, but it consumes the founder and a stalled process is visible. The fundraising-plan skill makes that call deliberately, and then configures every other skill to match the mode you chose.
Do I need to be technical to use this? +
No. The skills are markdown — run them as slash commands in Claude Code, or drop them into a Claude project and use them in web chat. If you can paste a command and answer questions, you can run the whole raise.
Who is this for? +
Founders running an early raise (pre-seed through Series A) who can't rely on inbound and want the operational process handled with discipline — so their attention goes to the conversations, not the spreadsheet.
How does this relate to Atomic Scaling OS? +
It's the companion OS. Atomic Scaling OS runs your growth operating system on the 3P3R Method®; the Fundraising OS runs the raise. Same HAAO model — the skills do the work, you make the calls — same MIT license.
Is the closing skill giving me legal advice? +
No. It explains term-sheet clauses in plain language and flags what's standard vs. off-market so you can decide and brief your lawyer efficiently. It never tells you what to sign — anything non-standard goes to a real startup lawyer.
Can I fork and adapt it? +
Yes — MIT license, fork freely. Adapt the skills to your stage, sector, and geography, change the scoring, add your own. Pull requests welcome.
Built from running real raises, not a whiteboard.
Ludovic Bodin
Serial entrepreneur and author of Atomic Scaling, building a portfolio of ventures across AI, wealth, and creative work. The Fundraising OS encodes the operational discipline of a raise — the list, the paths, the pipeline, the warmth — into skills any founder can run.