본문으로 건너뛰기
cccskills
무료GitHub에 공개

investor-update

Use when the user says "write my investor update", "monthly update for investors", "quarterly investor email", "investor communication", "LP update", "board update", "shareholder update", "what do I tell my investors this month", "how do I write a good investor update", or wants to communicate progress, metrics, and needs to existing investors or board members on a recurring basis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Overview

Based on "The Hard Thing About Hard Things" by Ben Horowitz. The core principle: the CEO's job is to manage the truth - not spin it, not hide it, and not dump it unfiltered. Investor updates are trust infrastructure. Horowitz argues that great CEOs communicate bad news faster than good news, ask for help specifically, and never let investors be surprised. An update that only reports wins trains investors to distrust you the moment things go wrong.

Workflow

Step 1: Pull the numbers before writing a word

Collect the following before drafting:

Metrics section (include all that apply to [your startup]):

  • MRR or ARR and month-over-month change (absolute and percentage)
  • New customers added and churned this period
  • Burn rate and runway (months remaining at current burn)
  • Cash in bank
  • Key product metrics (DAU, activation rate, NPS, or whatever your north star is)
  • Pipeline (if B2B): qualified deals, average deal size, sales cycle length

Do not estimate. If a number is not ready, note it explicitly and send the update anyway. "We are still closing the books on MRR - will send an addendum Friday" is better than delaying the whole update.

Step 2: State the headline in the first sentence

Investors read dozens of updates. Your first sentence should tell them whether this is a good month, a hard month, or a turning-point month.

Format options:

  • Good month: "[Month] was [your startup]'s strongest month to date. MRR hit $[X], up [Y]% MoM."
  • Hard month: "[Month] was difficult. We missed our MRR target by [X]% and I want to explain what happened."
  • Turning point: "We made a significant strategic change in [month] that will affect how you read these numbers going forward."

Do not bury the lead. Do not open with pleasantries.

Step 3: Write the wins section (3-5 bullets)

Concrete, specific, measurable:

  • "Closed [Company type] as a customer at $[ARR]. This is our first [industry] logo."
  • "Shipped [feature]. Early data: [metric] improved [X]%."
  • "Hired [role]. [One sentence on why this person matters]."

Avoid: "We made great progress on product" / "The team is energized."

Step 4: Write the struggles section (2-4 bullets)

This is the section most founders skip. Horowitz is explicit: skipping it destroys trust.

Be specific about what is not working:

  • "Churn this month was [X]%, above our [Y]% target. Root cause: [specific reason]. Fix in progress: [what you are doing]."
  • "Enterprise sales cycle is running [X] weeks vs. [Y] weeks expected. We are [specific adjustment]."
  • "We missed the [feature] ship date by [X] weeks. [Why]. New target: [date]."

The struggles section is also where you build credibility. Investors who see you name problems accurately trust your wins more.

Step 5: Write the asks section

This is the highest-value section and the most neglected. Horowitz's advice: investors want to help but they do not know how unless you tell them exactly what you need.

Format each ask as a specific, actionable request:

  • "Intro to VP of Engineering at [company type] - we are trying to close a key hire."
  • "Anyone who has sold into [industry vertical] and can share their procurement process experience."
  • "Feedback on our pricing page - link here: [URL]. Specifically: does the enterprise tier feel defensible?"

Maximum 3 asks per update. Vague asks ("Let me know if you can help with anything!") get zero responses.

Step 6: State the focus for next period

One paragraph. Three priorities maximum.

Format: "In [next month/quarter], we are focused on: (1) [specific goal with metric], (2) [specific goal with metric], (3) [specific goal with metric]."

This closes the update and creates accountability for the next one. Investors will remember what you said you would do.

Anti-Patterns

1. Only sending updates when things are good Bad: Sending 3 updates when MRR is up, then going silent for 2 months during a hard stretch. Good: Sending updates on a fixed cadence regardless of whether the news is good or bad. Hard-month updates build more trust than good-month ones.

2. Vanity metrics without context Bad: "We had 50,000 sign-ups this month!" Good: "50,000 sign-ups, 1,200 activated (2.4% activation rate). Activation is the problem we are solving in Q[X]."

3. Burying bad news in the middle Bad: Three paragraphs of wins, then a brief mention that "churn was a bit high", then more wins. Good: If churn is the real story, put it in paragraph two. Name it clearly.

4. Generic asks Bad: "Let us know if you can make any intros!" Good: "We need an intro to a Head of Revenue at a Series B or C SaaS company who has scaled from $1M to $5M ARR. Specifically someone who has built an outbound motion."

Quality Checklist

  • First sentence states the headline clearly - good month, hard month, or inflection
  • All metrics are real numbers, not estimates, with period-over-period comparison
  • Burn and runway are included every update without exception
  • Struggles section exists and is at least as long as the wins section
  • Each struggle names the root cause and the current response
  • Asks are specific, actionable, and limited to 3 or fewer
  • Next period priorities are stated with measurable targets
  • Update is sent on a consistent cadence regardless of performance

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

qa-aman의 스킬 모두 보기

이 스킬의 문제 신고