New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Run the Markster OS fundraising playbook

Fundraising Operator

by markster · MIT license · ★ 64 on GitHub · updated May 15

Fundraising Operator cover

Run the Markster OS fundraising playbook. CHECK stage, traction, and funding path before building anything.

---
name: fundraising
description: 'Run the Markster OS fundraising playbook. CHECK stage, traction, and funding path before building anything. DO investor ICP + list + outreach + pitch + close. VERIFY investor pipeline is real before claiming readiness. Routes through ScaleOS Biz Dev.'
---

# Fundraising Operator

---

## CHECK

Do not proceed past any failed check.

**1. Stage and traction defined?**

Ask the user:
- What stage are they raising at? (Pre-seed / Seed / Series A / growth?)
- How much are they raising?

Overview

Ask the user: - What stage are they raising at? (Pre-seed / Seed / Series A / growth?) - How much are they raising? - What traction do they have right now? (ARR, MRR, customers, growth rate, retention -- whatever applies)

Manual install (npx, ZIP)
Claude Codenpx skills add markster/markster-os --skill fundraising -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/markster/markster-os/tar.gz/b1da50054715 \ | tar -xz -C ~/.claude/skills --strip-components=2 markster-os-b1da50054715/skills/fundraising
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/03619f3c1265736b9108/fundraising.zip" -OutFile "$env:TEMP\fundraising.zip"; Expand-Archive "$env:TEMP\fundraising.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md6.9 KB
Read the files here
markster/b1da5001 file
Shared references2SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text175 lines

Fundraising Operator


CHECK

Do not proceed past any failed check.

1. Stage and traction defined?

Ask the user:

  • What stage are they raising at? (Pre-seed / Seed / Series A / growth?)
  • How much are they raising?
  • What traction do they have right now? (ARR, MRR, customers, growth rate, retention -- whatever applies)

If they cannot state a specific traction number: "Investors fund traction, not potential. Before building an investor list, you need at least one measurable proof point. What is the most specific thing you can say about your results right now?"

2. Funding path confirmed for their archetype

Fundraising looks very different by business type. Read the right file before advising.

Read playbooks/biz-dev/fundraising/funding-mechanisms.md -- especially if the user is a service firm or trade business. VC is one path. It is not the only path.

Your type Relevant funding paths
SaaS, devtools, marketplace VC, angels, SAFE, priced round
Agency, consulting, advisory PE, SBA, revenue-based financing
Trade businesses SBA, equipment financing, PE roll-up
Hardware, DTC Strategic, VC with hardware thesis, debt

Read playbooks/biz-dev/fundraising/traction-by-archetype.md -- what traction means for your archetype at each stage.

Read playbooks/biz-dev/fundraising/round-sizing.md -- SAFE vs. convertible note vs. priced round, and how much to raise at each stage.

If the user is pursuing VC for a business type where it is not the optimal path, name it clearly before proceeding.

3. Which part do they need?

Ask which stage they are working on:

  • Building the investor target list
  • Writing outreach (warm intro requests or cold)
  • Preparing for pitch meetings
  • Managing follow-up and the close process

Do not build a full 4-stage plan if they only need one stage. Route directly.


DO

Run the relevant stage(s). If they are starting from zero, run all four in order.

Stage 1: Investor target list

Define the investor ICP -- the profile of an investor who is the right fit for this raise:

  • Stage fit: who invests at their current traction level?
  • Sector fit: who has portfolio companies in their category?
  • Check size: who writes the right check size for this raise?
  • Value-add: who brings relevant introductions or operating experience beyond capital?

Categorize into three tiers:

Tier Count Priority
Tier 1 10-20 Ideal fit, warm intro required to approach
Tier 2 30-50 Good fit, warm or cold both viable
Tier 3 50-100 Possible fit, cold only

Sources for building the list: Crunchbase, AngelList, LinkedIn (portfolio companies of target funds), Axios Pro Rata, fund websites.

Do not send to Tier 3 until Tier 1 and 2 are active.

Stage 2: Outreach

For warm intros (Tier 1 and 2):

  1. Map intro paths through LinkedIn second-degree connections
  2. Help write the mutual connection request -- short, honest, specific on why this investor is the right fit
  3. Help write the forward blurb -- one paragraph, lead with traction not vision

Forward blurb structure:

  • One sentence on what the company does
  • One number (traction metric)
  • One sentence on why you thought of this investor specifically
  • The ask (15-minute intro call)

For cold outreach (Tier 2 and 3):

Use playbooks/biz-dev/fundraising/templates/investor-outreach.md.

Rules:

  • Under 100 words
  • Lead with traction, not vision or market size
  • Specific ask: 15-minute intro call (not "let me know if you're interested")
  • No deck in the first message
Stage 3: Pitch preparation

Walk through the 10-slide deck structure:

Slide Content
1. Cover Company name, one-liner, date
2. Problem Specific scenario -- a story, not a statistic
3. Solution What you built, one sentence
4. Why now Market timing argument -- what changed that makes this the right moment
5. Traction Most compelling numbers first
6. Product Screenshots or demo, not diagrams
7. Business model How you make money -- unit economics if available
8. Market size Bottom-up logic, not TAM from a report
9. Team The 2-3 things that make you the right people for this specific problem
10. The ask Amount, use of funds, milestones this raise gets you to

Also help with the verbal narrative: 2 minutes max, covers why you, why this market, why now.

Pitch quality gates before taking meetings:

  • The problem slide uses a specific scenario, not a statistic
  • Slide 5 (traction) leads with the most compelling number
  • Market size uses bottom-up logic the investor can follow
  • The ask slide states what milestone the money reaches (not "growth")
Stage 4: Follow-up and close

After every meeting, send a follow-up within 24 hours. Use playbooks/biz-dev/fundraising/templates/follow-up.md.

Pipeline management rules:

  • Track every investor with: stage, last contact date, next action, notes from last meeting
  • Review active investor relationships weekly
  • Create momentum: when other investors express genuine interest, share it transparently

When an investor passes: send a feedback request within 48 hours. Their answer is the product roadmap.

When closing: state the close timeline clearly. "We are targeting to close this round by [date]. Current commitments are [amount]. We have space for [X] more investors at this stage."


VERIFY

Before this session ends:

1. Investor list is tiered?

Confirm Tier 1, 2, and 3 are defined with clear criteria. Tier 1 should require a warm intro -- if everything is cold, the target list is probably too broad.

2. Outreach passes the traction-first check?

Read the first sentence of the outreach message. Does it lead with a traction metric or a vision statement? If it starts with vision, rewrite.

3. Pitch deck structure is complete?

Confirm all 10 slides exist and the quality gates from Stage 3 pass.

4. CRM tracking is set?

Confirm every active investor has a next action and a next contact date. No investor in active conversations should have a blank next action field.

5. Raise timeline is stated?

Confirm they have a close target date and know the current commitments. Fundraises without deadlines drift.


Reference files

  • Full playbook: playbooks/biz-dev/fundraising/README.md
  • Funding mechanisms: playbooks/biz-dev/fundraising/funding-mechanisms.md
  • Traction by archetype: playbooks/biz-dev/fundraising/traction-by-archetype.md
  • Round sizing: playbooks/biz-dev/fundraising/round-sizing.md
  • Investor outreach template: playbooks/biz-dev/fundraising/templates/investor-outreach.md
  • Follow-up template: playbooks/biz-dev/fundraising/templates/follow-up.md
1---
2name: fundraising
3description: 'Run the Markster OS fundraising playbook. CHECK stage, traction, and funding path before building anything. DO investor ICP + list + outreach + pitch + close. VERIFY investor pipeline is real before claiming readiness. Routes through ScaleOS Biz Dev.'
4---
5 
6# Fundraising Operator
7 
8---
9 
10## CHECK
11 
12Do not proceed past any failed check.
13 
14**1. Stage and traction defined?**
15 
16Ask the user:
17- What stage are they raising at? (Pre-seed / Seed / Series A / growth?)
18- How much are they raising?
19- What traction do they have right now? (ARR, MRR, customers, growth rate, retention -- whatever applies)
20 
21If they cannot state a specific traction number: "Investors fund traction, not potential. Before building an investor list, you need at least one measurable proof point. What is the most specific thing you can say about your results right now?"
22 
23**2. Funding path confirmed for their archetype**
24 
25Fundraising looks very different by business type. Read the right file before advising.
26 
27Read `playbooks/biz-dev/fundraising/funding-mechanisms.md` -- especially if the user is a service firm or trade business. VC is one path. It is not the only path.
28 
29| Your type | Relevant funding paths |
30|-----------|----------------------|
31| SaaS, devtools, marketplace | VC, angels, SAFE, priced round |
32| Agency, consulting, advisory | PE, SBA, revenue-based financing |
33| Trade businesses | SBA, equipment financing, PE roll-up |
34| Hardware, DTC | Strategic, VC with hardware thesis, debt |
35 
36Read `playbooks/biz-dev/fundraising/traction-by-archetype.md` -- what traction means for your archetype at each stage.
37 
38Read `playbooks/biz-dev/fundraising/round-sizing.md` -- SAFE vs. convertible note vs. priced round, and how much to raise at each stage.
39 
40If the user is pursuing VC for a business type where it is not the optimal path, name it clearly before proceeding.
41 
42**3. Which part do they need?**
43 
44Ask which stage they are working on:
45- Building the investor target list
46- Writing outreach (warm intro requests or cold)
47- Preparing for pitch meetings
48- Managing follow-up and the close process
49 
50Do not build a full 4-stage plan if they only need one stage. Route directly.
51 
52---
53 
54## DO
55 
56Run the relevant stage(s). If they are starting from zero, run all four in order.
57 
58### Stage 1: Investor target list
59 
60Define the investor ICP -- the profile of an investor who is the right fit for this raise:
61- Stage fit: who invests at their current traction level?
62- Sector fit: who has portfolio companies in their category?
63- Check size: who writes the right check size for this raise?
64- Value-add: who brings relevant introductions or operating experience beyond capital?
65 
66Categorize into three tiers:
67 
68| Tier | Count | Priority |
69|------|-------|---------|
70| Tier 1 | 10-20 | Ideal fit, warm intro required to approach |
71| Tier 2 | 30-50 | Good fit, warm or cold both viable |
72| Tier 3 | 50-100 | Possible fit, cold only |
73 
74Sources for building the list: Crunchbase, AngelList, LinkedIn (portfolio companies of target funds), Axios Pro Rata, fund websites.
75 
76Do not send to Tier 3 until Tier 1 and 2 are active.
77 
78### Stage 2: Outreach
79 
80**For warm intros (Tier 1 and 2):**
811. Map intro paths through LinkedIn second-degree connections
822. Help write the mutual connection request -- short, honest, specific on why this investor is the right fit
833. Help write the forward blurb -- one paragraph, lead with traction not vision
84 
85Forward blurb structure:
86- One sentence on what the company does
87- One number (traction metric)
88- One sentence on why you thought of this investor specifically
89- The ask (15-minute intro call)
90 
91**For cold outreach (Tier 2 and 3):**
92 
93Use `playbooks/biz-dev/fundraising/templates/investor-outreach.md`.
94 
95Rules:
96- Under 100 words
97- Lead with traction, not vision or market size
98- Specific ask: 15-minute intro call (not "let me know if you're interested")
99- No deck in the first message
100 
101### Stage 3: Pitch preparation
102 
103Walk through the 10-slide deck structure:
104 
105| Slide | Content |
106|-------|---------|
107| 1. Cover | Company name, one-liner, date |
108| 2. Problem | Specific scenario -- a story, not a statistic |
109| 3. Solution | What you built, one sentence |
110| 4. Why now | Market timing argument -- what changed that makes this the right moment |
111| 5. Traction | Most compelling numbers first |
112| 6. Product | Screenshots or demo, not diagrams |
113| 7. Business model | How you make money -- unit economics if available |
114| 8. Market size | Bottom-up logic, not TAM from a report |
115| 9. Team | The 2-3 things that make you the right people for this specific problem |
116| 10. The ask | Amount, use of funds, milestones this raise gets you to |
117 
118Also help with the verbal narrative: 2 minutes max, covers why you, why this market, why now.
119 
120**Pitch quality gates before taking meetings:**
121- The problem slide uses a specific scenario, not a statistic
122- Slide 5 (traction) leads with the most compelling number
123- Market size uses bottom-up logic the investor can follow
124- The ask slide states what milestone the money reaches (not "growth")
125 
126### Stage 4: Follow-up and close
127 
128After every meeting, send a follow-up within 24 hours. Use `playbooks/biz-dev/fundraising/templates/follow-up.md`.
129 
130Pipeline management rules:
131- Track every investor with: stage, last contact date, next action, notes from last meeting
132- Review active investor relationships weekly
133- Create momentum: when other investors express genuine interest, share it transparently
134 
135When an investor passes: send a feedback request within 48 hours. Their answer is the product roadmap.
136 
137When closing: state the close timeline clearly. "We are targeting to close this round by [date]. Current commitments are [amount]. We have space for [X] more investors at this stage."
138 
139---
140 
141## VERIFY
142 
143Before this session ends:
144 
145**1. Investor list is tiered?**
146 
147Confirm Tier 1, 2, and 3 are defined with clear criteria. Tier 1 should require a warm intro -- if everything is cold, the target list is probably too broad.
148 
149**2. Outreach passes the traction-first check?**
150 
151Read the first sentence of the outreach message. Does it lead with a traction metric or a vision statement? If it starts with vision, rewrite.
152 
153**3. Pitch deck structure is complete?**
154 
155Confirm all 10 slides exist and the quality gates from Stage 3 pass.
156 
157**4. CRM tracking is set?**
158 
159Confirm every active investor has a next action and a next contact date. No investor in active conversations should have a blank next action field.
160 
161**5. Raise timeline is stated?**
162 
163Confirm they have a close target date and know the current commitments. Fundraises without deadlines drift.
164 
165---
166 
167## Reference files
168 
169- Full playbook: `playbooks/biz-dev/fundraising/README.md`
170- Funding mechanisms: `playbooks/biz-dev/fundraising/funding-mechanisms.md`
171- Traction by archetype: `playbooks/biz-dev/fundraising/traction-by-archetype.md`
172- Round sizing: `playbooks/biz-dev/fundraising/round-sizing.md`
173- Investor outreach template: `playbooks/biz-dev/fundraising/templates/investor-outreach.md`
174- Follow-up template: `playbooks/biz-dev/fundraising/templates/follow-up.md`
175 
View all files on GitHub →

Details

Updated
May 15, 2026
License
MIT
Stars on the repo
★ 64
Checked
Source
markster/markster-os ↗
Creator
markster · 7 listings
View creator

Similar skills

See all →
SkillAct as a comprehensive AI sales intelligenceAI Sales Team — Main Orchestratorzubair-trabzada/ai-sales-team-claude · by zubair-trabzadaYou are a comprehensive AI sales intelligence and outreach system for Claude Code. You help founders, sales teams, agency owners, and…★ 1.4k GitHub starsSkillAutonomous cold email campaign launcherAuto research publicgrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiAutonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".★ 736 GitHub starsSkillRun a full Account-Based Marketing campaign end-to-endABM Campaign — DIY Playbookexplorium-ai/gtm-skills · by explorium-aiABM campaign skill for Claude Code: run a full Account-Based Marketing campaign end-to-end — from ICP definition to live LinkedIn Ads. Builds targeted account lists with Vibe Prospecting, enriches and scores companies with real-time B2B data, generates personalized ad creatives with Claude Code and Figma, pushes matched audiences to LinkedIn Ads, and monitors campaigns daily at scale. The complete GTM skill for AI-driven account-based marketing in Claude Code, Codex, Hermes-Agent, and OpenClaw. No agency needed.★ 197 GitHub starsSkillContact data skill for Claude Code and Codex: build a rankedAccount contact shortlistexplorium-ai/gtm-skills · by explorium-aiContact data skill for Claude Code and Codex: build a ranked shortlist of decision-makers and contacts at a target company for outbound prospecting, deal acceleration, or renewal/expansion plays. Returns verified contact data including email, phone, LinkedIn profile, title, seniority, and department. Provide a company name or domain plus optional seniority focus or use case. Use for contact data enrichment, LinkedIn profile lookup, and building outbound contact lists. Works in Claude Code, Codex, Hermes-Agent, and OpenClaw.★ 197 GitHub starsSkillLead scoring and buying signals skill for Claude CodeAccount fit rankexplorium-ai/gtm-skills · by explorium-aiLead scoring and buying signals skill for Claude Code and Codex: rank a list of accounts by ICP fit, buying intent, real-time trigger events, and workforce momentum. Returns composite score (0-100), tier (A/B/C), and a 'why now' signal per account. Use for account-based selling, ABM list prioritization, territory planning, signal-based selling, and buyer-intent ranking. Triggers on 'score these accounts', 'rank by ICP fit and intent', 'prioritize this account list', 'which accounts have the strongest buying signals', 'ICP scoring', 'account prioritization'. Works in Claude Code, Codex, Hermes-Agent, OpenClaw, and Claude Cowork.★ 197 GitHub starsSkillRun end-to-end B2B cold-email outreach through the Hyper MCPhyperfx-ai/marketing-skills · by hyperfx-aiRun end-to-end B2B cold-email outreach through the Hyper MCP — enrich prospects with Apollo, scrape per-prospect signals from company sites and LinkedIn, draft personalized emails using proven hook frameworks, send via Gmail with safe defaults, and route replies into labeled folders. Use when the user wants to write cold emails, run an outbound sequence, prospect a list, build a follow-up cadence, "reach out to leads," or asks why nobody is replying to their cold emails.★ 90 GitHub stars

More from markster

SkillRun the Markster OS cold email playbookCold Email Operatormarkster/markster-os · by marksterRun the Markster OS cold email playbook. CHECK prerequisites, DO the sequence build, VERIFY before sending. Routes through ScaleOS G3 Book with context from F1/F2.★ 64 GitHub starsSkillRun the Markster OS content playbookContent Operatormarkster/markster-os · by marksterRun the Markster OS content playbook. CHECK prerequisites (ICP, messaging guide, platform, time), DO theme definition + 30-day calendar + writing + distribution, VERIFY output before declaring done. Routes through ScaleOS G2 Warm.★ 64 GitHub starsSkillRun the Markster OS events playbookEvents Operatormarkster/markster-os · by marksterRun the Markster OS events playbook. CHECK prerequisites (ICP, offer, specific event), DO pre-event targeting + during-event conversation system + post-event follow-up, VERIFY before leaving the event pipeline empty. Routes through ScaleOS G2 Warm.★ 64 GitHub starsSkillDiagnostic operator for Markster OSMarkster OS Operatormarkster/markster-os · by marksterDiagnostic operator for Markster OS. Identifies the constraint brick, runs the Hormozi diagnostic, and routes to the right playbook with context pre-filled. Run this before any other skill.★ 64 GitHub starsSkillRun structured B2B research prompts from the Markster OSResearch Operatormarkster/markster-os · by marksterRun structured B2B research prompts from the Markster OS library. CHECK what they are trying to learn and ICP context. DO one or more of 9 prompts (competitive intelligence, buyer JTBD, buying signals, pricing perception, GTM channels, objection research, market positioning, mental category positioning, first 60 seconds). VERIFY output is documented back into Foundation.★ 64 GitHub starsSkillRun the Markster OS sales playbookSales Operatormarkster/markster-os · by marksterRun the Markster OS sales playbook. CHECK deal context, DO discovery/proposal/close, VERIFY before moving stages. Includes 9 Kill Skills audit for conversion problems.★ 64 GitHub stars