skills/by-role/founder/investor-update/SKILL.md
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.
npx skillsauth add qa-aman/claude-skills investor-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Collect the following before drafting:
Metrics section (include all that apply to [your startup]):
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.
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:
Do not bury the lead. Do not open with pleasantries.
Concrete, specific, measurable:
Avoid: "We made great progress on product" / "The team is energized."
This is the section most founders skip. Horowitz is explicit: skipping it destroys trust.
Be specific about what is not working:
The struggles section is also where you build credibility. Investors who see you name problems accurately trust your wins more.
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:
Maximum 3 asks per update. Vague asks ("Let me know if you can help with anything!") get zero responses.
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.
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."
development
Plan a webinar end-to-end using April Dunford's Obviously Awesome positioning framework to find the topic angle that makes the webinar obviously valuable to the right audience. Produces topic positioning, abstract, speaker brief, registration page, promotion sequence, day-of run-of-show, and post-webinar follow-up. Use when the user asks to plan a webinar, virtual event, online workshop, "we need a webinar on X", host a webinar, online masterclass, or any live virtual event with promotion and follow-up. Reads ICP, services, and brand voice from knowledge/.
development
Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/.
development
Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/.
development
Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags.