本文へ移動
cccskills
無料GitHub で公開

fundraising-and-investor-relations

Raises capital and manages the relationship afterward — deciding how much and why, understanding what dilution and preferences actually cost, running a process with real competitive tension, preparing for diligence before it starts, and reporting to investors and a board in a way that keeps support when results are bad. Use this to plan a raise, evaluate a term sheet beyond the valuation, prepare a data room, or fix reporting that is producing surprises.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.3 KB
  • references/sources.md2.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Fundraising and investor relations

Capital is bought, not received, and the terms matter more than the headline number. So does what happens for the years afterward, which is where most of the relationship actually lives.

Financing terms have legal and tax consequences that vary by structure and jurisdiction. Get qualified counsel and your accountant on any instrument before signing.

Decide the amount from the plan, not from the market

Raise against what the money buys: the milestones that will make the next raise possible, plus enough runway to reach them and to be wrong once. Working back from milestones gives a number you can defend and a story that connects the raise to the outcome.

Raising more than the plan needs is not free — it costs dilution now and sets a valuation you have to grow into. Raising too little is worse, because running out mid-plan is the weakest possible negotiating position and everyone on the other side of the table knows it.

Understand what the terms cost, because valuation is the least of them

A high valuation with punishing terms is worse than a lower one with clean terms, and founders routinely trade the second for the first because only the first is quotable.

  • Liquidation preference determines who gets paid first and how much before common shares see anything. A participating preference or a multiple can mean an apparently good exit returns little to founders and staff.
  • Anti-dilution decides what happens if the next round is lower. The broader forms can shift ownership substantially in exactly the circumstances where you can least afford it.
  • Board composition and protective provisions determine what you can do without asking. This is control, and it is permanent in a way valuation is not.
  • Option pool sizing placed before the investment dilutes existing holders only. Where the pool sits in the calculation is a real price negotiation dressed as an administrative detail.

Model the outcome at several exit values, not just the good one. The terms that matter most only express themselves in the mediocre cases, which are the most likely ones.

Run a process, because tension is what produces terms

A raise conducted sequentially with one interested party is a negotiation with one side. Run conversations in parallel on a compressed timeline so that decisions land close together.

Prepare before starting. A process that stalls while you assemble materials loses its momentum, and momentum is most of what you are manufacturing.

Assemble diligence before you need it

Cap table and every instrument that affects it, signed contracts, employment and contractor agreements with their IP assignments, financial statements and the model behind them, key metrics with their definitions, and the corporate record.

Diligence surfaces the things nobody dealt with earlier — a missing assignment from a contractor, an unsigned amendment, a metric defined differently in two places. Each is small alone and each costs time at the worst moment. Fix them before the process, not during it.

Never present a metric to investors that is defined differently from how you report it internally. That inconsistency is found, and it costs credibility disproportionately.

Report on a rhythm, and report the bad news first

Investor relationships are managed between raises. A regular update — monthly or quarterly, short, consistent in format — costs an hour and buys enormous latitude when something goes wrong.

Surprise is the thing that damages the relationship, not bad results. An investor told early about a problem is a resource; the same investor told late is a governance issue. Lead with what is not working, what you are doing, and what you need.

Ask for specific help. "Let us know if you can help" produces nothing; a named introduction or a specific question produces something.

The board is a different audience from investors

Board material goes out days ahead and is read before the meeting, so the meeting is for decisions rather than presentation. Bring the real questions, including the ones you do not have answers to — a board only shown finished thinking cannot help with anything and eventually stops trying.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Optimize a term sheet on valuation without modeling the preference stack at mediocre exits.
  • Start a process before the data room would survive being opened.
  • Present a metric to investors under a definition you do not use internally.
  • Let an investor learn about a material problem after it is already resolved or already worse.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する