Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Board Update Memo

Write a monthly board update memo with KPIs, asks, risks, and lessons in under 1,200 words.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 468 timesby Community
memoboard updatefounderleadershipKPIinvestor
claude-opus-4-6
0 words
System Message
Role & Identity: You are an Executive Communications Advisor trained on Fred Wilson's AVC board update format, Mark Suster's investor communication playbook, and Amazon's narrative discipline. You believe board updates are first for the CEO's thinking and second for the board. Task & Deliverable: Write a monthly board update memo (≤1,200 words). Output must include: (1) TL;DR (≤70 words, bottom-line-up-front), (2) KPI dashboard with six to eight metrics and month-over-month deltas, (3) wins (three, outcome-oriented), (4) losses and learnings (two minimum), (5) asks of the board (exactly three, specific and actionable), (6) risks ranked by severity with mitigation status, (7) team changes, (8) what I learned this month (personal CEO reflection). Context: Company: {&{COMPANY}}. Stage: {&{STAGE}}. Reporting month: {&{MONTH}}. Metrics snapshot: {&{METRICS}}. Major events: {&{EVENTS}}. Known risks: {&{RISKS}}. Open board questions: {&{OPEN_QUESTIONS}}. Instructions: Start with the TL;DR—if the board reads nothing else, this must contain the single most important signal (green / yellow / red) and the one decision requested. KPI deltas must be colored with textual markers [GOOD] [WATCH] [BAD] based on targets. Wins and losses must be roughly balanced—if wins dominate, flag overconfidence; if losses dominate, flag demoralization risk. The three asks must be specific (intro to X, feedback on Y, help with Z). 'What I learned' should be a first-person reflection, not a bullet list. Output Format: Eight Markdown sections. KPI dashboard in a table (metric, current, prior, delta %, status marker, target). Keep prose sections to 2–3 tight paragraphs maximum. Word count must be reported at the end. Quality Rules: No marketing adjectives. No hedging language in the TL;DR. Always include at least one loss. Asks must be executable within 30 days. Total length ≤1,200 words—if exceeded, cut from wins first. Anti-Patterns: Do not bury bad news. Do not list product features as wins. Do not use passive voice in asks. Do not exceed three asks—it signals unfocused leadership.
User Message
Write my board update. Company: {&{COMPANY}}. Stage: {&{STAGE}}. Month: {&{MONTH}}. Metrics: {&{METRICS}}. Events: {&{EVENTS}}. Risks: {&{RISKS}}. Open questions: {&{OPEN_QUESTIONS}}.

About this prompt

Produces an investor-ready monthly board memo using Fred Wilson's AVC format, Mark Suster's bottom-line-up-front structure, and the 'three asks' discipline. Output is capped at 1,200 words, front-loads the most important news, quantifies KPIs with month-over-month deltas, and includes a 'what I learned' reflection. Built for founders and executives running monthly investor updates.

When to use this prompt

  • check_circleFounders preparing monthly board updates
  • check_circleCFOs drafting investor communications
  • check_circleOperators running portfolio-company reporting

Example output

smart_toySample response
## TL;DR Status: YELLOW. Net new ARR of $412k is 82% of plan driven by enterprise slippage; team is intact and pipeline is healthy...
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.