fundraise-team-hiring
Skill0 starsChanged 4 months agoMITView on GitHub
Use when a founder is shaping the team for a raise or hiring against the round. Triggers on "team slide", "what hires do investors want", "how much equity for an early hire", "key hire before fundraising", "is my team fundable", "hiring plan for the round". Connects the team story, the gap-filling hires, and the equity to grant.
In this repository19 other files it gives its agents.
- cap-table-managerSkill
- data-room-builderSkill
- due-diligence-checklistSkill
- financial-plannerSkill
- fundraise-closing-mechanicsSkill
- fundraise-readiness-auditSkill
- fundraising-narrativeSkill
- fundraising-stage-selectorSkill
- investor-pipeline-crmSkill
- investor-targetingSkill
- investor-update-writerSkill
- market-sizingSkill
- pitch-deck-builderSkill
- pitch-practice-coachSkill
- safe-vs-priced-roundSkill
- series-a-readinessSkill
- term-sheet-explainerSkill
- term-sheet-negotiationSkill
- vc-pitch-emailSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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
- Distinctive: line 15
Use it while building the team slide in [[pitch-deck-builder]], when sizing the option pool in [[cap-table-manager]], and when use-of-funds …
- Distinctive: line 24
Named gaps, owned: every investor sees the holes.
- Distinctive: line 33
If the risk is "can they build it" -> a senior technical hire or co-founder.
- Distinctive: line 34
If the risk is "can they sell it" -> a first sales/GTM leader once there is repeatable pull.
- Distinctive: line 36
If the risk is "can they keep them" -> a hire that owns retention.
- Distinctive: line 49
All early grants vest over 4 years with a 1-year cliff - no exceptions for friends, advisors-turned-employees, or "we trust each other."
- Distinctive: line 98
Every named gap comes with a role, a rough timeline, and evidence of pipeline or a sourcing plan - never a bare admission.
- Distinctive: line 102
Every grant has a band, 4-year vesting with a 1-year cliff, and rolls up into a pool number derived from the plan - no round-number pool …
≈ “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.
Files
Fundraise Team & Hiring
Investors fund a team's ability to learn faster than the market changes. "Why this team wins this bet" must be answerable without hand-waving - and the gaps must be named with a credible plan, not hidden. This skill builds both the story and the hiring plan behind it.
When to use this skill
Use it while building the team slide in [[pitch-deck-builder]], when sizing the option pool in [[cap-table-manager]], and when use-of-funds in the ask is mostly "key hires."
The team story investors fund
- Earned right to win: the specific experience or insight that makes this team unusually suited to this problem. Not a resume - a reason.
- Founder-market fit: why you, why now, the unfair advantage you carry.
- Named gaps, owned: every investor sees the holes. Naming them first ("we need a VP Eng by Q3, here's the pipeline") signals self-awareness; hiding them signals you can't see your own business.
The hires that de-risk a round
The most fundable use-of-funds is hiring that converts your biggest risk into a plan. Identify the one or two roles that most reduce investor doubt:
- If the risk is "can they build it" -> a senior technical hire or co-founder.
- If the risk is "can they sell it" -> a first sales/GTM leader once there is repeatable pull.
- If the risk is "can they keep them" -> a hire that owns retention.
Hire against the milestone from [[fundraising-stage-selector]], not a generic org chart. A pre-seed company hiring a CFO is spending dilution on the wrong risk.
Equity for early hires (rough bands, calibrate to stage and seniority)
- First engineers (post-seed): ~0.25%-1.0%.
- Early senior leaders / first VPs: ~0.5%-2.0%.
- Pre-product-market-fit co-founder-level hire: 1%-5%+, vesting over 4 years with a 1-year cliff.
All early grants vest over 4 years with a 1-year cliff - no exceptions for friends, advisors-turned-employees, or "we trust each other."
Grant from a pool sized to the actual 18-month hiring plan: list the roles, assign each a band, sum it, add a small buffer. Investors often open by asking for a 15-20% post-money pool; a plan-backed number usually lands closer to 10-12%, and the difference is founder dilution you keep by showing the math. Size it deliberately in [[cap-table-manager]].
Worked example: seed-stage devtools company
Round: $3M seed to reach $1M ARR in 18 months. Team: two technical co-founders, one contract designer.
- Bad team slide: three headshots, university logos, a former employer's logo wall, "10+ years combined experience." No thesis, no gaps named. An investor reads it as "we hope the logos speak for us."
- Good team narrative: "We built the internal deploy tooling at [prior company] that this product replaces - we've felt this pain at 200-engineer scale and know exactly where the bodies are buried (earned right to win). Our gap is go-to-market: neither of us has sold. We're hiring a founding GTM lead in the first two quarters post-close - three candidates already in pipeline, all with devtools sales backgrounds."
- Hiring plan against the milestone ($1M ARR): founding GTM lead (1.0-1.5%, the round's key de-risking hire), two product engineers (0.4% each), a developer-relations hire in the back half if bottoms-up adoption is working (0.3%). Total planned grants ≈ 2.5%; buffer to 3.5%; pool ask: 10% post-money, defended with this list when the term sheet says 15%.
- What they did not hire: a CFO, a VP of Sales before a single repeatable deal, or a head of people for a team of six.
Anti-patterns
- A team slide of logos with no "why this team" thesis.
- Hiring senior executives before product-market fit to "look fundable."
- An option pool set at a round-number default instead of the hiring plan.
- Handshake equity with no documented grant or vesting - a diligence landmine ([[fundraise-readiness-audit]]).
Deliverable
A team narrative (earned right to win + founder-market fit + named gaps), a prioritized list of the 1-2 risk-reducing hires tied to the round's milestone, and an equity-grant plan with vesting that rolls up into the option-pool size.
Quality bar
- The "why this team" thesis survives the question "couldn't a smart generic team do this?" - it names specific earned insight, not credentials.
- Every named gap comes with a role, a rough timeline, and evidence of pipeline or a sourcing plan - never a bare admission.
- Each planned hire maps to a named risk the round must retire, not an org-chart slot.
- Every grant has a band, 4-year vesting with a 1-year cliff, and rolls up into a pool number derived from the plan - no round-number pool defaults.
- Nothing on the plan is a title the company only needs after the next milestone.
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.

