One-line snapshot: “We are a subscription marketplace for B2B training that will reach $3.6M ARR within 24 months by converting 4% of our pilot enterprise users.”<\/p>\n
- \n
- Ideal length: 150-300 words (one page max)<\/li>\n
- Primary CTA: Request $750k seed to fund 18 months runway<\/li>\n
- Lead metric: projected ARR and conversion rate (e.g., $3.6M ARR, 4% conversion)<\/li>\n<\/ul>\n<\/li>\n
- Project\u2011proposal summary (decision request)<\/strong>\n
One-line snapshot: “Replace the legacy billing engine to cut failed payments by 60% and save $420k annually; we need approval to start procurement next quarter.”<\/p>\n
- \n
- Ideal length: 150-400 words<\/li>\n
- Primary CTA: Approve $350k budget and a 6\u2011month timeline<\/li>\n
- Lead metric: cost savings or ROI (e.g., $420k\/year savings, 60% reduction)<\/li>\n<\/ul>\n<\/li>\n
- Project\u2011status summary (steering\u2011committee update)<\/strong>\n
One-line snapshot: “On track for release v2.1 on June 12; two supplier risks could delay launch by 3 weeks-decision needed on a $25k contingency.”<\/p>\n
- \n
- Ideal length: 75-200 words (email or slide)<\/li>\n
- Primary CTA: Approve $25k contingency by week’s end<\/li>\n
- Lead metric: timeline and risk probability (e.g., 3\u2011week delay risk)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
What an executive summary must achieve – get a decision, not a lecture<\/h2>\n
An executive summary exists to create action, not just explain. After one read a primary reader should be able to: decide, delegate, prioritize, or quickly pass the matter along with confidence. That means lead with the outcome-the number or timeline that matters-state the ask early, and make the next step obvious.<\/p>\n
Test for actionability: can the reader decide, ask one clarifying question, or schedule a follow\u2011up after one read? If not, rewrite.<\/p>\n
How an exec summary differs from an abstract or a full project plan:<\/p>\n
- \n
- Executive summary: action\u2011oriented-impact, risk, and explicit ask.<\/li>\n
- Abstract: neutral summary of methods and results-informational, not persuasive.<\/li>\n
- Project plan: detailed schedule, resources, and dependencies-used after a decision.<\/li>\n<\/ul>\n
Who reads it and what they want:<\/p>\n
- \n
- CEO: strategic impact and high\u2011level risk-quick yes\/no.<\/li>\n
- Investor: traction, unit economics, and the funding ask.<\/li>\n
- Project sponsor: timeline, ROI, and blockers.<\/li>\n
- PMO\/board: governance, milestones, and compliance.<\/li>\n<\/ul>\n
A compact 4\u2011phase framework to write an executive summary (Prepare \u2192 Draft \u2192 Trim \u2192 Package)<\/h2>\n
Follow these four phases to move from raw content to a decision\u2011ready executive summary quickly.<\/p>\n
Phase 1 – Prepare: know the document and your audience<\/h3>\n
Rapid audit: pull 3-5 must\u2011know facts, the single recommendation you want endorsed, and the highest\u2011risk assumption. Map the primary decision\u2011maker, secondary viewers, and which metric drives each reader.<\/p>\n
Phase 2 – Draft: hook, essentials, and the ask<\/h3>\n
Open with a one\u2011sentence hook: a value claim, a striking stat, or a tight problem statement. Then include objective, 1-3 headline findings (bulleted if useful), the top recommendation\/ask, and immediate next steps. Follow the numbers\u2011first rule: lead with the most persuasive metric or timeline.<\/p>\n
Phase 3 – Trim: edit for speed<\/h3>\n
Be ruthless. Target 150-300 words for an email summary and 300-800 words for a one\u2011page. Cut jargon, history that doesn’t support the ask, and every sentence that doesn’t help a decision. Check readability: one idea per sentence, active verbs, concrete nouns.<\/p>
\r\n
![\"Business\"](\"https:\/\/brainapps.io\/blog\/wp-content\/themes\/reboot_child\/bu2.svg\")
\r\n