Stakeholder Update Generator

Draft a polished periodic update letter from whatever raw inputs the user provides — to investors, a board, clients, donors, members, partners, or an internal leadership team.

Why This Skill Exists

Writing periodic updates is one of the most time-consuming communication tasks for any leader. The inputs are usually scattered — metrics in one place, project notes in another, a rough take on the environment jotted somewhere else — and turning them into a clean, professional letter takes hours. This skill does that conversion fast.

The output is a working draft, not a finished letter. Every organization has its own voice, disclosure posture, and relationship nuances that the leader or communications owner must apply before sending. Treat this as a strong first draft that needs a human review pass.

What This Skill Does Not Do

• It does not pull live data or calculate results. The user must provide the figures.
• It does not make up numbers. If data is missing, it flags the gap.
• It does not know your organization's legal, regulatory, contractual, or grant-reporting obligations. Counsel or the compliance owner should review before any communication goes to external stakeholders.
• It does not guarantee completeness. Every organization has different disclosure norms — what goes in this letter is the sender's call.

Inputs

The user may provide any combination of the following. The skill works with whatever is available — more inputs produce a better draft, but the skill will always produce something useful.

Common inputs:

• Organization, team, program, or fund name and the period being reported
• Headline results (revenue, growth, retention, pipeline, funds raised, people served, units shipped, milestones hit, fund performance metrics — or none of these)
• Progress on initiatives, projects, products, programs, or portfolio companies (news, milestones, challenges, completions)
• New initiatives, launches, hires, clients, grants, or investments during the period
• Wins, completions, exits, or closures during the period
• Financial or resource activity (cash position, budget vs. actual, capital raised, capital calls, distributions, grants received)
• Context or environment commentary the sender wants to include (market, regulatory, competitive, community)
• Asks of the audience (introductions, hires, referrals, votes, funding, feedback)
• Notes on what tone to strike
• Prior updates to match style and voice
• Any topics the sender specifically wants to address or avoid

Missing-input behavior: If key inputs are missing, do not stop. Produce the best draft possible and append a clearly labeled section at the end listing what information would improve it. Ask a clarifying question only when the audience is genuinely unknowable from the material (a board letter and a customer letter are different documents).

Core Principles

Only use what the user provides. Do not invent results, names, figures, dates, or commentary. If the user says "we had a strong quarter" but provides no numbers, write around that directionally without fabricating specifics.

Preserve the sender's voice. If prior updates are provided, match their tone and structure. If not, default to a professional, measured tone — confident but not promotional.

Be honest about gaps. Placeholder language is better than invented language. Where data is missing, use clearly marked placeholders like [INSERT Q3 REVENUE] so the sender knows exactly what needs to be filled in.

Write for the actual audience. A board wants decisions and risks; investors want results and trajectory; clients want what changed for them; donors want impact and stewardship; members want what they get and what's coming; an internal leadership team wants priorities and blockers. Sophisticated readers do not need over-explanation. Be direct.

Proportionate honesty. If the period had setbacks, they get space proportional to their importance — not buried in a subordinate clause, not dramatized either. Readers who learn about problems late trust the sender less.

Output Format

Produce a complete letter draft using the structure below. Not every section is required — use judgment based on what inputs are available, who the audience is, and what makes sense for the period. A quiet quarter with no launches or closures does not need a section on those topics.

Letter Structure

[Organization / Team / Program / Fund Name]
[Period] Update — [Month or Quarter] [Year]

[Opening paragraph]
Set the tone for the letter. Acknowledge the period, reference the broader environment if relevant, and orient the reader on what the letter covers. Keep to 2–4 sentences.

---

**Results**
[Summary of the headline metrics the sender has provided — revenue, growth, retention, pipeline, funds raised, people served, milestones, fund performance, or whatever the organization measures. If no metrics are provided, omit this section or use placeholders. Do not derive, estimate, or calculate figures the user has not supplied.]

---

**Progress Update**
[Organized summary of developments across initiatives, projects, products, programs, business units, or portfolio companies during the period. Group by theme, workstream, or outcome type — whatever makes the narrative cleaner. Include milestones, notable challenges, and leadership or team changes if provided. Write at the individual-item level only to the extent the user has provided information.]

---

**New This Period**
[If new initiatives, launches, clients, hires, grants, partnerships, or investments began during the period, briefly describe each: name, what it is, and a sentence on why it matters. Only include information the user provides.]

---

**Wins and Completions**
[If projects completed, deals closed, exits or realizations occurred, or goals were hit, summarize each: what, outcome, and implication for the organization. Only if provided.]

---

**Financial and Resource Activity**
[Cash position, budget vs. actual, capital raised, capital calls or distributions, grants received, or headcount changes during the period, if provided. Use exact figures the user supplies — do not estimate.]

---

**Context and Environment**
[The sender's commentary on the market, regulatory, competitive, or community environment, if provided. Write in the sender's voice. Keep to a short paragraph — readers generally want the sender's perspective, not a research report.]

---

**Looking Ahead**
[Forward-looking paragraph: pipeline, priorities, themes the organization is watching, what the sender expects over the next period. Keep it directional. Do not make specific performance commitments or guarantees.]

---

**How You Can Help** (optional — board, investor, donor, and member audiences)
[Specific, answerable asks: introductions, candidate referrals, feedback on a decision, a vote, a renewal. One to three items. Only if the sender wants to make asks.]

---

[Closing]
Brief closing — appreciation for the reader's partnership or support, invitation to reach out with questions, and signature block placeholder.

[Sender Name / Organization Name]
[Title]
[Contact]

Tone

Default to: professional, measured, confident without being promotional, and honest about uncertainty. Avoid:

• Superlatives ("incredible," "best-in-class," "exceptional")
• Vague reassurance with no substance ("we remain confident in our strategy")
• Overly technical jargon unless the user's prior updates use it
• Cherry-picking language — if the period had challenges, acknowledge them proportionally
• Forward-looking promises phrased as certainties

If the user provides prior updates, prioritize matching that voice over these defaults.

Audience Variants

The same structure flexes by reader. Examples of how emphasis shifts:

• Board or leadership team (a SaaS company, a hospital, a school): lead with decisions needed and risks; results and progress are context for those.
• Investors (a startup, a fund, a franchise group): lead with results and trajectory; new initiatives and asks matter; keep the environment section short.
• Clients (an agency, a consultancy, a managed-service provider): lead with what changed for them — deliverables, service levels, roadmap; keep internal matters out.
• Donors or members (a nonprofit, an association, a co-op): lead with impact and stewardship — what their support made possible; the ask is natural here.
• Internal team (a department, a project, a business unit): lead with priorities, blockers, and what's changing; skip formal closings.

When Context Is Limited

If the user provides minimal inputs (e.g., just "draft a Q2 update for our board"), produce a template-style draft with clearly labeled placeholders throughout. Label the placeholders consistently — [INSERT ...] — so the user can work through them one by one.

Append at the end:

---
**To complete this draft, please provide:**
- [List specific missing inputs that would materially improve the letter]

A placeholder-filled draft is far more useful than a refusal to proceed.

Quality Checks

Before delivering the draft, verify:

• No invented numbers, names, or facts
• All missing data is marked with [INSERT ...] placeholders
• Sections with no available information are either omitted or clearly flagged
• Setbacks, if any, are present and proportionate
• Tone is consistent throughout and fits the audience
• The letter reads like something this sender would actually send — not a generic template
• Length is appropriate: most periodic updates run 300–600 words. Longer is not better.

Important Reminder

This is a first draft. It should be reviewed by the sender and, where relevant, counsel or the compliance owner before distribution. Communications to investors, donors, members, regulators, and customers may be subject to legal, regulatory, contractual, or grant-reporting obligations that this skill cannot assess.

Works well with

The "what drove the result" narrative for the Results section can come from performance-attribution-narrator; a business-one-pager can be attached for new readers; call-transcript-followup outputs often supply the progress notes.