Claude Prompt Library

30 Claude Prompts That Write Executive Summaries

30 copy-paste prompts

Paste a business plan, report, proposal, research paper, project doc, or pitch and Claude returns a sharp, one-page executive summary you can hand to a decision-maker. Every prompt yields a ready-to-use artifact, not "give me some text".

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly โ€” no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

Business Plan Summaries

5 prompts

Startup Business Plan Executive Summary

1/30

You are a venture advisor who writes the executive summary that opens investor business plans. <context> I have a full startup business plan and need a single-page executive summary a busy investor will actually read, delivered as a self-contained document I can drop onto page one. </context> <inputs> - Company and one-line pitch: [NAME PLUS WHAT IT DOES] - Problem and who has it: [PAIN POINT AND MARKET] - Solution and the edge: [PRODUCT AND WHY IT WINS] - Traction and key numbers: [REVENUE, USERS, GROWTH] - The ask: [RAISE AMOUNT AND USE OF FUNDS] - Full plan to condense: [PASTE PLAN] </inputs> <task> Write a one-page executive summary with labeled sections: Overview, Problem, Solution, Market Opportunity, Business Model, Traction, Team, Financial Highlights, and The Ask. Pull every claim from the pasted plan and lead with the single most compelling fact. </task> <constraints> - Fits one page (about 400-500 words); short paragraphs, scannable. - Every number traceable to the source; invent nothing and flag gaps with a [NEEDS INPUT] tag. - Plain, confident language; no hype words like "revolutionary". </constraints> <format> Return the executive summary as a formatted markdown artifact, then a two-line note on which section to strengthen before sending. </format>

Condenses a full startup business plan into an investor-ready one-page executive summary as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude your single strongest metric and have it open the Overview with that number instead of the company name.

Small Business Loan / SBA Plan Summary

2/30

You are a small-business lending consultant who prepares executive summaries for bank and SBA loan packages. <context> I need a one-page executive summary of my business plan to sit at the front of a loan application, written as a self-contained document a loan officer can skim in two minutes. </context> <inputs> - Business name, type, location: [DETAILS] - What we sell and to whom: [OFFERING AND CUSTOMERS] - Owner background and experience: [WHO RUNS IT] - Funding needed and purpose: [LOAN AMOUNT AND USE] - Financial snapshot: [REVENUE, MARGINS, PROJECTIONS] - Full plan to summarize: [PASTE PLAN] </inputs> <task> Write a one-page summary with sections: Business Description, Products and Services, Market and Customers, Competitive Advantage, Management, Financial Summary, and Funding Request with repayment rationale. Keep the tone credible and lender-friendly. </task> <constraints> - One page; specific numbers, no vague growth claims. - Tie the loan amount to concrete uses and show how it will be repaid. - Flag any missing financials with [NEEDS INPUT] rather than guessing. </constraints> <format> Return the summary as a markdown artifact, then note the one risk a lender will question and how to address it. </format>

Turns an SMB business plan into a lender-ready one-page executive summary for a loan or SBA application, ready to use.

๐Ÿ’ก

Pro tip: Give Claude your debt-service coverage ratio if you have it; lenders look for it and it makes the funding request far more convincing.

New Product Business Case Summary

3/30

You are a product strategist who writes the one-page business case that gets new products funded internally. <context> I want to pitch a new product or feature to leadership and need a one-page executive summary of my business case, as a self-contained document for an approval meeting. </context> <inputs> - Product or feature idea: [WHAT IT IS] - Customer problem and evidence: [PAIN AND SIGNALS] - Expected impact: [REVENUE, RETENTION, OR COST TARGET] - Cost and resources needed: [TEAM, BUDGET, TIMELINE] - Main risks and alternatives: [RISKS, DO-NOTHING OPTION] - Full business case to condense: [PASTE DOC] </inputs> <task> Write a one-page summary with sections: Recommendation, Problem and Opportunity, Proposed Solution, Expected Impact (with a simple cost-vs-return line), Investment Required, Key Risks, and Decision Requested. State the recommendation in the first sentence. </task> <constraints> - One page; quantify impact and cost wherever the source allows. - Frame it as a decision with a clear yes/no ask, not a status report. - No jargon; a non-specialist executive should understand it. </constraints> <format> Return the business case summary as a markdown artifact, then list the two questions leadership is most likely to ask. </format>

Compresses an internal product business case into a one-page, decision-focused executive summary as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to add a one-line 'cost of doing nothing' so the do-nothing option looks as expensive as it really is.

Nonprofit Strategic Plan Summary

4/30

You are a nonprofit strategy consultant who writes executive summaries for board and funder audiences. <context> I need a one-page executive summary of our nonprofit's strategic plan to share with the board and major funders, as a self-contained document. </context> <inputs> - Organization and mission: [NAME AND MISSION] - Who we serve and the need: [BENEFICIARIES AND PROBLEM] - Strategic priorities for the period: [3-5 GOALS] - Programs and reach: [KEY PROGRAMS, PEOPLE SERVED] - Budget and funding plan: [BUDGET, SOURCES] - Full strategic plan to condense: [PASTE PLAN] </inputs> <task> Write a one-page summary with sections: Mission and Need, Vision for the Period, Strategic Priorities, Programs and Impact, Financial Plan, and How Funders Can Help. Anchor impact in measurable outcomes, not activities. </task> <constraints> - One page; mission-driven but concrete, with numbers for people served and outcomes. - Distinguish outcomes (change created) from outputs (things done). - Warm, credible tone; no filler mission-speak. </constraints> <format> Return the summary as a markdown artifact, then note where a funder-facing version should differ from the board version. </format>

Distills a nonprofit strategic plan into a one-page executive summary for boards and funders, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude one outcome metric you're proud of and have it lead the Impact section with that instead of a list of activities.

Market-Entry / Expansion Plan Summary

5/30

You are a growth strategist who summarizes market-entry and expansion plans for executive sign-off. <context> We are planning to enter a new market or launch a new location and I need a one-page executive summary of the expansion plan, as a self-contained document for the leadership team. </context> <inputs> - What we are expanding: [PRODUCT, REGION, OR LOCATION] - Why this market now: [OPPORTUNITY AND TIMING] - Target customer and demand evidence: [WHO AND PROOF] - Go-to-market approach: [CHANNELS AND MODEL] - Investment, timeline, and expected return: [BUDGET, DATES, ROI] - Full expansion plan to condense: [PASTE PLAN] </inputs> <task> Write a one-page summary with sections: Recommendation, Market Opportunity, Target Customer, Entry Strategy, Investment and Timeline, Expected Return, and Key Risks with mitigations. Make the go/no-go recommendation explicit up front. </task> <constraints> - One page; quantify market size, investment, and return where the source supports it. - Name the top three risks and a mitigation for each. - Decisive, executive tone; flag missing data with [NEEDS INPUT]. </constraints> <format> Return the expansion summary as a markdown artifact, then add a one-line break-even estimate if the numbers allow. </format>

Summarizes a market-entry or expansion plan into a one-page, go/no-go executive summary as a previewable artifact.

๐Ÿ’ก

Pro tip: Give Claude your assumed payback period; it will pressure-test whether the expected return actually clears it.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 7-Day Free Trial

Report & Analysis Summaries

5 prompts

Annual Report Executive Summary

6/30

You are a corporate communications writer who drafts the executive summary that opens annual reports. <context> I have our full annual report and need a one-page executive summary for the front of the document and for stakeholders who won't read the whole thing, as a self-contained artifact. </context> <inputs> - Company and reporting year: [NAME AND YEAR] - Headline results: [REVENUE, PROFIT, GROWTH VS LAST YEAR] - Key wins this year: [ACHIEVEMENTS, MILESTONES] - Challenges faced: [SETBACKS, HEADWINDS] - Priorities for next year: [FORWARD GOALS] - Full annual report to condense: [PASTE REPORT] </inputs> <task> Write a one-page summary with sections: Year at a Glance (3-4 headline metrics), Financial Performance, Operational Highlights, Challenges and Responses, and Outlook for Next Year. Open with the single most important result of the year. </task> <constraints> - One page; every metric pulled from the source with year-over-year context where available. - Balanced and honest; acknowledge setbacks, don't only cheerlead. - Clear, non-technical language for a mixed stakeholder audience. </constraints> <format> Return the summary as a markdown artifact, then a short bulleted 'at a glance' metrics box to sit above it. </format>

Condenses a full annual report into a balanced one-page executive summary with a metrics box, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to render the top four metrics as a compact table so stakeholders grasp performance before reading a word.

Financial Analysis Summary

7/30

You are a financial analyst who writes executive summaries of detailed financial analyses. <context> I have a detailed financial analysis and need a one-page executive summary that a non-finance executive can act on, delivered as a self-contained document. </context> <inputs> - What was analyzed: [PERIOD, ENTITY, OR SCENARIO] - Key figures and trends: [REVENUE, MARGINS, CASH, RATIOS] - What the numbers reveal: [FINDINGS] - Risks or red flags: [CONCERNS] - Recommended actions: [WHAT TO DO] - Full analysis to condense: [PASTE ANALYSIS] </inputs> <task> Write a one-page summary with sections: Bottom Line, Key Financial Metrics, What's Driving the Numbers, Risks and Red Flags, and Recommended Actions. State the bottom-line conclusion in the first sentence, then support it. </task> <constraints> - One page; translate finance jargon into plain implications (e.g., what a falling margin means for the business). - Every figure traceable to the source; note the reporting period clearly. - Prioritize the two or three numbers that actually matter for the decision. </constraints> <format> Return the summary as a markdown artifact with a small key-metrics table, then flag the single number to watch next quarter. </format>

Turns a detailed financial analysis into a plain-language one-page executive summary with a metrics table as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude who the reader is (CEO, board, lender); it changes which ratios lead and how much interpretation to add.

Industry / Market Report Summary

8/30

You are a strategy consultant who writes executive summaries of long industry and market research reports. <context> I have a lengthy industry or market report and need a one-page executive summary that captures the insights leadership needs, as a self-contained document. </context> <inputs> - Report topic and scope: [INDUSTRY, REGION, PERIOD] - Market size and growth: [SIZE, CAGR IF GIVEN] - Key trends and shifts: [TRENDS] - Competitive landscape notes: [PLAYERS, DYNAMICS] - What it means for us: [OUR ANGLE OR DECISION] - Full report to condense: [PASTE REPORT] </inputs> <task> Write a one-page summary with sections: Key Takeaways (3-4 bullets), Market Size and Trajectory, Major Trends, Competitive Dynamics, and Implications and Recommended Moves for our company. Lead with the takeaway that most changes our thinking. </task> <constraints> - One page; distinguish established facts from the report's forecasts. - Always translate findings into 'so what for us' implications, not just recap. - Cite figures with their source period; flag anything speculative. </constraints> <format> Return the summary as a markdown artifact, then list two follow-up questions the report leaves unanswered. </format>

Distills a long industry or market report into a one-page executive summary with clear implications, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to separate 'what the report proves' from 'what it predicts' so you don't act on a forecast like it's a fact.

Operations / Performance Report Summary

9/30

You are an operations lead who writes executive summaries of detailed performance reports. <context> I have a detailed operations or performance report and need a one-page executive summary for leadership that shows how we're tracking against targets, as a self-contained artifact. </context> <inputs> - Reporting period and area: [PERIOD, TEAM OR FUNCTION] - Key KPIs and targets: [METRICS WITH GOALS] - Actual performance vs target: [RESULTS] - What went well and what didn't: [WINS AND MISSES] - Actions and next steps: [FIXES, PLANS] - Full report to condense: [PASTE REPORT] </inputs> <task> Write a one-page summary with sections: Headline (on/off track this period), KPI Scorecard (metric, target, actual, status), What's Working, What Needs Attention, and Next Steps with owners. Use a clear on-track / at-risk / off-track status for each KPI. </task> <constraints> - One page; the KPI scorecard must be a compact table with a status column. - Be honest about misses and pair each with a concrete corrective action. - No vague 'improving' claims without a number. </constraints> <format> Return the summary as a markdown artifact with the KPI table, then note the one metric most likely to slip next period. </format>

Compresses an operations or performance report into a one-page executive summary with a KPI scorecard as a previewable artifact.

๐Ÿ’ก

Pro tip: Give Claude your red/amber/green thresholds so the status column reflects your real definition of at-risk, not its guess.

Data Analysis Findings Summary

10/30

You are a senior data analyst who writes executive summaries of analytical deep-dives for non-technical leaders. <context> I ran a data analysis and need a one-page executive summary that explains the findings and what to do about them, without the statistical detail, as a self-contained document. </context> <inputs> - Question the analysis answered: [THE QUESTION] - Data and method in one line: [SOURCE AND APPROACH] - Main findings: [KEY RESULTS] - Confidence and caveats: [LIMITATIONS] - Recommended decisions: [ACTIONS] - Full analysis or notes to condense: [PASTE ANALYSIS] </inputs> <task> Write a one-page summary with sections: Question, Answer (the headline finding), Key Findings (3-5 bullets with the numbers that matter), Confidence and Caveats, and Recommended Actions. State the answer plainly before the supporting detail. </task> <constraints> - One page; explain statistical results in plain terms and their business meaning. - Be explicit about uncertainty; don't overstate correlation as causation. - Round numbers sensibly and keep only the figures that drive a decision. </constraints> <format> Return the summary as a markdown artifact, then suggest one chart that would make the headline finding land instantly. </format>

Turns a technical data analysis into a plain-language one-page findings summary for executives, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude the exact decision the analysis feeds; it will cut every finding that doesn't move that decision.

Proposal Summaries

5 prompts

Sales / RFP Response Summary

11/30

You are a bid manager who writes the executive summary that opens winning proposals and RFP responses. <context> I have a full sales proposal or RFP response and need a one-page executive summary that makes the buyer want to keep reading, delivered as a self-contained document. </context> <inputs> - Client and what they need: [CLIENT AND REQUIREMENT] - Our proposed solution: [WHAT WE'LL DELIVER] - Why us over alternatives: [DIFFERENTIATORS] - Outcomes and value: [RESULTS, ROI, TIMELINE] - Price and terms: [INVESTMENT AND STRUCTURE] - Full proposal to condense: [PASTE PROPOSAL] </inputs> <task> Write a one-page executive summary with sections: Understanding of Your Need, Our Proposed Solution, Why [OUR COMPANY], Expected Outcomes, and Investment Overview. Open by mirroring the client's goal in their own words, then present the solution as the answer to it. </task> <constraints> - One page; client-centric (more 'you' than 'we'), tied to their stated requirements. - Quantify outcomes and value; make the differentiators specific, not generic claims. - Confident, no hard-sell hype; price framed against value. </constraints> <format> Return the summary as a markdown artifact, then note the one objection most likely to block the deal and how to preempt it. </format>

Condenses a sales proposal or RFP response into a client-centric one-page executive summary as a previewable artifact.

๐Ÿ’ก

Pro tip: Paste the client's own wording of their goal; Claude will echo it verbatim in the opening line so the buyer feels understood.

Grant Proposal Executive Summary

12/30

You are a grant writer who crafts the executive summary funders read first. <context> I have a full grant proposal and need a one-page executive summary that convinces a funder this project deserves their money, as a self-contained document. </context> <inputs> - Organization and project name: [WHO AND WHAT] - Problem and who it affects: [NEED AND POPULATION] - What the grant will fund: [PROJECT ACTIVITIES] - Goals and measurable outcomes: [TARGETS] - Amount requested and budget summary: [ASK AND USE] - Full proposal to condense: [PASTE PROPOSAL] </inputs> <task> Write a one-page summary with sections: Project Overview, Statement of Need, Goals and Measurable Outcomes, Approach, Budget Request, and Fit with Funder's Priorities. Tie the need to evidence and the outcomes to concrete metrics. </task> <constraints> - One page; align language to the funder's stated priorities if provided. - Outcomes must be measurable (number reached, change achieved), not aspirations. - Compelling but factual; every claim supported by the proposal. </constraints> <format> Return the summary as a markdown artifact, then note which sentence should be tailored per funder before submitting. </format>

Distills a grant proposal into a funder-ready one-page executive summary with measurable outcomes, ready to use.

๐Ÿ’ก

Pro tip: Paste the funder's priority statement into the inputs; Claude will mirror its keywords so your project reads as an obvious fit.

Consulting Engagement Proposal Summary

13/30

You are a management consultant who writes the executive summary for engagement proposals. <context> I have a full consulting proposal and need a one-page executive summary that frames the client's problem, our approach, and the value, as a self-contained document for a decision-maker. </context> <inputs> - Client and their challenge: [CLIENT AND PROBLEM] - Proposed engagement scope: [WHAT WE'LL DO] - Approach and phases: [METHOD, PHASES] - Deliverables and timeline: [OUTPUTS AND DATES] - Fees and expected ROI: [INVESTMENT AND RETURN] - Full proposal to condense: [PASTE PROPOSAL] </inputs> <task> Write a one-page summary with sections: The Challenge, Our Approach, Phases and Deliverables, Timeline, Expected Value, and Investment. Present the approach as a clear path from the client's current state to the desired outcome. </task> <constraints> - One page; scope is precise (what's in and out) so expectations are set. - Value framed in the client's terms (money saved, risk reduced, time gained). - Professional, credible tone; deliverables are concrete artifacts, not vague 'insights'. </constraints> <format> Return the summary as a markdown artifact, then add a one-line scope boundary noting what is explicitly out of scope. </format>

Compresses a consulting engagement proposal into a one-page executive summary with clear scope and value as a previewable artifact.

๐Ÿ’ก

Pro tip: Have Claude spell out what's out of scope; naming exclusions upfront prevents the scope creep that kills fixed-fee engagements.

Vendor / Partnership Proposal Summary

14/30

You are a business development lead who writes executive summaries for partnership and vendor proposals. <context> I have a full partnership or vendor proposal and need a one-page executive summary that makes the mutual value obvious to the other side's decision-maker, as a self-contained document. </context> <inputs> - The two parties and the idea: [WHO AND WHAT PARTNERSHIP] - What each side brings: [OUR ASSETS, THEIR ASSETS] - The mutual opportunity: [WHY IT'S BIGGER TOGETHER] - Proposed structure and terms: [MODEL, SPLIT, COMMITMENTS] - Success metrics: [HOW WE'LL MEASURE IT] - Full proposal to condense: [PASTE PROPOSAL] </inputs> <task> Write a one-page summary with sections: The Opportunity, What Each Party Brings, How It Works, What Each Party Gets, Success Metrics, and Proposed Next Step. Frame value as mutual throughout, not one-sided. </task> <constraints> - One page; balance the 'what's in it for them' with our own goals. - Terms and commitments stated plainly so there's no ambiguity. - Concrete success metrics both sides can agree to; no vague 'synergy'. </constraints> <format> Return the summary as a markdown artifact, then note the one term the other party is most likely to push back on. </format>

Turns a partnership or vendor proposal into a mutual-value one-page executive summary, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to write the 'what each party gets' section from the partner's perspective first; it keeps the pitch from sounding one-sided.

Investment / Funding Proposal Summary

15/30

You are an investment associate who writes the executive summary for funding proposals and deal teasers. <context> I have a full investment or funding proposal and need a one-page executive summary that gets an investor to take the meeting, delivered as a self-contained document. </context> <inputs> - The opportunity: [COMPANY OR PROJECT AND STAGE] - The market and why now: [MARKET AND TIMING] - Traction and financials: [KEY NUMBERS] - Use of funds and milestones: [WHAT THE MONEY BUYS] - The ask and terms: [AMOUNT, STRUCTURE, RETURN] - Full proposal to condense: [PASTE PROPOSAL] </inputs> <task> Write a one-page summary with sections: The Opportunity, Market and Timing, Traction and Financials, Use of Funds and Milestones, The Ask, and Expected Return. Lead with the single most investable fact. </task> <constraints> - One page; every number traceable and stated with its period. - Return framed with a clear rationale, not a promise; risks acknowledged briefly. - Crisp, quantitative tone; flag missing figures with [NEEDS INPUT]. </constraints> <format> Return the summary as a markdown artifact with a compact key-figures table, then note the strongest and weakest points of the case. </format>

Distills an investment or funding proposal into a one-page executive summary with a key-figures table as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude the investor's typical check size and thesis; it will foreground the metrics that fund most cares about.

Research Paper Summaries

5 prompts

Academic Paper Executive Summary

16/30

You are a research communicator who turns dense academic papers into executive summaries for non-specialists. <context> I have a full academic paper and need a one-page executive summary that a smart non-expert can understand and act on, delivered as a self-contained document. </context> <inputs> - Paper title and field: [TITLE AND DISCIPLINE] - The research question: [WHAT IT INVESTIGATES] - Method in one line: [HOW THEY STUDIED IT] - Main findings: [KEY RESULTS] - Why it matters / applications: [SIGNIFICANCE] - Full paper to condense: [PASTE PAPER] </inputs> <task> Write a one-page summary with sections: What They Studied, How They Studied It, What They Found (the headline result first), Why It Matters, and Limitations. Replace jargon with plain language and define any unavoidable term inline. </task> <constraints> - One page; accurate to the paper, never overstating the findings. - Preserve important caveats and effect sizes; don't turn a modest result into a breakthrough. - Accessible to a reader outside the field. </constraints> <format> Return the summary as a markdown artifact, then give a two-sentence 'plain-English takeaway' a general audience would remember. </format>

Condenses a dense academic paper into a plain-language one-page executive summary for non-specialists as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to keep the reported effect size or confidence interval; stripping it is how summaries turn nuance into hype.

Literature Review Summary

17/30

You are a research synthesist who summarizes literature reviews for decision-makers. <context> I have a long literature review covering many studies and need a one-page executive summary of what the body of evidence actually says, as a self-contained document. </context> <inputs> - Topic and question reviewed: [SUBJECT AND QUESTION] - Scope: [NUMBER OF STUDIES, TIME RANGE IF GIVEN] - Points of consensus: [WHAT MOST STUDIES AGREE ON] - Points of disagreement: [WHERE FINDINGS CONFLICT] - Gaps and open questions: [WHAT'S UNRESOLVED] - Full review to condense: [PASTE REVIEW] </inputs> <task> Write a one-page summary with sections: Question and Scope, Where the Evidence Agrees, Where It Disagrees, Strength of the Evidence, Gaps and Open Questions, and Practical Implications. Distinguish strong consensus from single-study claims. </task> <constraints> - One page; represent the weight of evidence, not just the loudest study. - Be explicit about how confident the field is on each point. - Neutral, balanced tone; note where the review itself may be biased. </constraints> <format> Return the summary as a markdown artifact, then list the single most important unresolved question for future work. </format>

Synthesizes a long literature review into a one-page executive summary of the evidence, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude to weight findings by consensus, not recency; one flashy new study shouldn't outweigh a decade of replication.

White Paper Executive Summary

18/30

You are a B2B content strategist who writes the executive summary that opens white papers. <context> I have a full white paper and need a one-page executive summary that captures the argument and drives the reader to the recommendation, as a self-contained document. </context> <inputs> - White paper topic and thesis: [SUBJECT AND CLAIM] - The problem it addresses: [PAIN OR TREND] - Key evidence and arguments: [SUPPORTING POINTS] - The recommended approach or solution: [WHAT TO DO] - Intended reader: [AUDIENCE] - Full white paper to condense: [PASTE PAPER] </inputs> <task> Write a one-page summary with sections: The Problem, Why It Matters Now, Key Insights (3-4 bullets), The Recommended Approach, and Bottom Line. Make the thesis clear early and build toward the recommendation. </task> <constraints> - One page; persuasive but evidence-led, matching the reader's sophistication. - Insights are specific and drawn from the paper, not restated headings. - Professional tone; no vendor hype disguised as insight. </constraints> <format> Return the summary as a markdown artifact, then suggest a one-sentence hook to open the full paper. </format>

Turns a white paper into a persuasive one-page executive summary that leads to the recommendation as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude for three candidate hooks and pick the one that names a cost or risk; problem-led openers outperform solution-led ones.

Technical / Scientific Study Summary

19/30

You are a technical writer who summarizes engineering and scientific studies for management review. <context> I have a detailed technical or scientific study and need a one-page executive summary that management can act on without the technical depth, as a self-contained document. </context> <inputs> - Study objective: [WHAT WE SET OUT TO LEARN] - Method and setup: [APPROACH, TESTS, TOOLS] - Key results and measurements: [FINDINGS WITH NUMBERS] - Conclusions: [WHAT IT MEANS] - Recommendations and next steps: [ACTIONS] - Full study to condense: [PASTE STUDY] </inputs> <task> Write a one-page summary with sections: Objective, Approach, Key Results, Conclusions, and Recommendations. Report results with their units and significance, but explain what each result means for the product or decision. </task> <constraints> - One page; translate technical detail into business or operational implications. - Keep critical numbers and tolerances; drop derivations and raw data tables. - Precise and honest about uncertainty and test conditions. </constraints> <format> Return the summary as a markdown artifact, then flag any result that needs replication before it's relied upon. </format>

Compresses a technical or scientific study into a management-ready one-page executive summary, ready to use.

๐Ÿ’ก

Pro tip: Tell Claude the decision this study informs (ship, redesign, retest); it will elevate the results that actually gate that call.

Policy Research Brief

20/30

You are a policy analyst who writes one-page briefs summarizing research for decision-makers. <context> I have a body of policy research and need a one-page executive brief that gives a decision-maker the evidence and options, as a self-contained document. </context> <inputs> - Policy issue: [THE PROBLEM OR QUESTION] - Key evidence and data: [WHAT THE RESEARCH SHOWS] - Stakeholders affected: [WHO IS IMPACTED] - Policy options considered: [2-4 OPTIONS] - Trade-offs of each: [PROS AND CONS] - Full research to condense: [PASTE RESEARCH] </inputs> <task> Write a one-page brief with sections: Issue, What the Evidence Shows, Options (each with pros, cons, and cost), Trade-offs, and Recommendation. Present options neutrally, then make a clear, reasoned recommendation. </task> <constraints> - One page; evidence-based and non-partisan in framing the options. - Each option paired with its main trade-off and cost; no strawman choices. - Recommendation follows logically from the evidence presented. </constraints> <format> Return the brief as a markdown artifact with an options comparison table, then note the biggest assumption the recommendation rests on. </format>

Distills policy research into a one-page decision brief with an options table and recommendation as a previewable artifact.

๐Ÿ’ก

Pro tip: Have Claude include a 'do nothing' option in the table; it clarifies whether any proposed change actually beats the status quo.

Project Status Summaries

5 prompts

Weekly Project Status Summary

21/30

You are a project manager who writes concise weekly status summaries for stakeholders. <context> I have my raw project notes for the week and need a one-page executive status summary that stakeholders can read in under a minute, as a self-contained document. </context> <inputs> - Project name and overall status: [PROJECT, GREEN/AMBER/RED] - Progress this week: [WHAT GOT DONE] - Planned for next week: [WHAT'S NEXT] - Blockers and risks: [ISSUES NEEDING HELP] - Key metrics or milestones: [PROGRESS INDICATORS] - Raw notes to condense: [PASTE NOTES] </inputs> <task> Write a one-page status summary with sections: Status at a Glance (RAG plus one-line why), Accomplished This Week, Planned Next Week, Blockers and Help Needed, and Milestone Tracker. Put the overall status and any red flag at the very top. </task> <constraints> - One page, scannable; each blocker names the specific help or decision needed. - Progress stated as done/not-done facts, not effort ('worked on'). - Honest RAG status; don't paint amber as green. </constraints> <format> Return the summary as a markdown artifact, then note the single item that needs a stakeholder decision this week. </format>

Turns raw weekly project notes into a scannable one-page status summary with RAG status, ready to use.

๐Ÿ’ก

Pro tip: Feed Claude last week's summary too; it will highlight what changed and quietly flag any blocker that's been open too long.

Program / Portfolio Status Roll-Up

22/30

You are a program director who rolls up multiple project statuses into one executive summary. <context> I manage several projects and need a one-page executive roll-up that shows leadership the health of the whole portfolio at once, as a self-contained document. </context> <inputs> - Program or portfolio name: [NAME] - Projects and their statuses: [PROJECT, STATUS, % COMPLETE] - Overall program health: [GREEN/AMBER/RED AND WHY] - Cross-project risks and dependencies: [RISKS] - Budget and timeline position: [ON/OFF TRACK] - Individual status notes to condense: [PASTE NOTES] </inputs> <task> Write a one-page roll-up with sections: Program Health Summary, Project Scorecard (project, status, % complete, key note), Top Cross-Project Risks, Budget and Timeline, and Decisions Needed. Surface the projects that are off track first. </task> <constraints> - One page; the project scorecard must be a compact table with a status column. - Aggregate honestly: one red project shouldn't be hidden by green ones. - Escalate only decisions that truly need leadership, with a clear ask. </constraints> <format> Return the roll-up as a markdown artifact with the scorecard table, then note which project most threatens the overall timeline. </format>

Consolidates multiple project statuses into a one-page portfolio roll-up with a scorecard as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to sort the scorecard worst-status-first; leadership should hit the at-risk projects before the healthy ones.

Milestone / Phase-Gate Summary

23/30

You are a delivery lead who writes phase-gate summaries for go/no-go reviews. <context> We've reached a project milestone or phase gate and I need a one-page executive summary for the go/no-go review, as a self-contained document. </context> <inputs> - Project and the gate reached: [PROJECT AND PHASE] - Gate criteria and whether each is met: [CRITERIA, MET/NOT] - Deliverables completed this phase: [OUTPUTS] - Outstanding items and their impact: [OPEN ITEMS] - Recommendation: [PROCEED / HOLD / STOP] - Phase details to condense: [PASTE DETAILS] </inputs> <task> Write a one-page summary with sections: Recommendation (proceed/hold/stop up front), Gate Criteria Checklist (criterion, status, note), Phase Deliverables, Outstanding Items and Impact, and Readiness for Next Phase. Justify the recommendation against the criteria. </task> <constraints> - One page; the criteria checklist must be a clear met/not-met table. - Don't recommend 'proceed' if criteria are unmet without stating the accepted risk. - Decisive and evidence-based; no burying open items. </constraints> <format> Return the summary as a markdown artifact with the criteria checklist, then note any criterion being waived and who must approve the waiver. </format>

Compresses a phase-gate review into a one-page go/no-go executive summary with a criteria checklist, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to mark any 'proceed with conditions' criteria explicitly; unmet criteria approved on faith are where projects derail.

Project Post-Mortem Summary

24/30

You are a delivery lead who writes blameless post-mortem summaries after a project or incident. <context> A project or initiative has wrapped and I need a one-page executive post-mortem summary capturing what happened and what we'll change, as a self-contained document. </context> <inputs> - Project or incident and outcome: [WHAT AND HOW IT ENDED] - Goals vs actual results: [PLANNED VS DELIVERED] - What went well: [SUCCESSES] - What went wrong and why: [ISSUES AND ROOT CAUSES] - Lessons and action items: [CHANGES WITH OWNERS] - Full retro notes to condense: [PASTE NOTES] </inputs> <task> Write a one-page summary with sections: Outcome vs Goal, What Went Well, What Went Wrong (with root causes), Key Lessons, and Action Items with owners and dates. Focus on systems and decisions, not individuals. </task> <constraints> - One page; blameless framing, root causes over symptoms. - Every lesson tied to a concrete, assignable action item. - Honest about the gap between goal and result; no spin. </constraints> <format> Return the summary as a markdown artifact with an action-items table (action, owner, due), then note the one lesson most likely to be forgotten. </format>

Turns retro notes into a blameless one-page post-mortem summary with an action-items table as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to trace each 'what went wrong' to a root cause, not a symptom; otherwise you fix the flat tire, not the nail in the road.

Steering Committee Executive Update

25/30

You are a program manager who prepares executive updates for a steering committee. <context> I need a one-page executive update for the steering committee that gives senior sponsors what they need to steer and decide, as a self-contained document. </context> <inputs> - Initiative name and objective: [WHAT AND WHY] - Overall status and trajectory: [ON/OFF TRACK, TREND] - Progress against key objectives: [OBJECTIVES AND STATE] - Escalations and decisions needed: [WHAT SPONSORS MUST DECIDE] - Budget, timeline, scope health: [CONSTRAINTS STATUS] - Detailed update to condense: [PASTE DETAILS] </inputs> <task> Write a one-page update with sections: Executive Summary (status and headline), Progress Against Objectives, Budget/Timeline/Scope Health, Escalations and Decisions Needed, and Upcoming Key Dates. Lead with what the committee must decide today. </task> <constraints> - One page; written for senior sponsors, focused on decisions and risks, not task detail. - Each escalation states the decision, the options, and your recommendation. - Report all three constraints (budget, timeline, scope) with an honest status. </constraints> <format> Return the update as a markdown artifact, then note the single decision that will most affect the initiative's success. </format>

Distills a program update into a one-page steering-committee executive summary focused on decisions, ready to use.

๐Ÿ’ก

Pro tip: For each escalation, have Claude state your recommended option; committees decide faster when given a default to react to.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Pitch & Memo Summaries

5 prompts

Investor Pitch One-Pager

26/30

You are a startup fundraising advisor who writes the one-page pitch that gets investor meetings. <context> I have my full pitch materials and need a one-page investor pitch summary (a teaser one-pager) that makes an investor want to take the call, as a self-contained document. </context> <inputs> - Company and one-liner: [NAME AND WHAT IT DOES] - Problem and solution: [PAIN AND PRODUCT] - Market size: [TAM/SAM OR SIZING] - Traction: [REVENUE, GROWTH, USERS, LOGOS] - Team and the raise: [FOUNDERS, AMOUNT, USE] - Full pitch materials to condense: [PASTE MATERIALS] </inputs> <task> Write a one-page pitch with sections: One-Liner, Problem, Solution, Market, Traction (the numbers that matter most), Team, and The Ask. Lead with the most fundable proof point, whether that's growth, revenue, or a marquee customer. </task> <constraints> - One page, tight and quantitative; every claim backed by a number where possible. - No hype adjectives; let traction do the talking. - Flag any missing metric with [NEEDS INPUT] rather than inventing figures. </constraints> <format> Return the one-pager as a markdown artifact, then note the single strongest line to use as the cold-email hook. </format>

Condenses full pitch materials into a quantitative one-page investor teaser as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude your growth rate and let it lead with that; investors skim for a number that signals momentum before anything else.

Strategic Decision Memo

27/30

You are a chief of staff who writes one-page decision memos for executives. <context> We face a strategic decision and I need a one-page decision memo that lets a leader decide quickly and confidently, as a self-contained document. </context> <inputs> - The decision to be made: [THE QUESTION] - Background and why now: [CONTEXT AND URGENCY] - Options on the table: [2-4 OPTIONS] - Pros, cons, and cost of each: [TRADE-OFFS] - Recommendation and rationale: [WHAT AND WHY] - Supporting detail to condense: [PASTE DETAIL] </inputs> <task> Write a one-page memo with sections: Decision Required, Background, Options (each with pros, cons, cost), Recommendation, and Next Steps if approved. State the recommendation clearly and tie it to the decision criteria. </task> <constraints> - One page; options presented fairly before the recommendation. - Name the decision criteria being optimized (speed, cost, risk, revenue). - Crisp executive tone; the reader should be able to decide from this page alone. </constraints> <format> Return the memo as a markdown artifact with an options comparison table, then note what new information would change the recommendation. </format>

Turns background detail into a one-page strategic decision memo with an options table, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to name the decision criteria explicitly; leaders align faster on the criteria than on the options themselves.

Board Briefing Memo

28/30

You are an executive who prepares one-page briefing memos for the board of directors. <context> I need a one-page board briefing memo on a specific topic that gives directors the context and the ask, as a self-contained document. </context> <inputs> - Topic and purpose of the memo: [SUBJECT, INFORM OR DECIDE] - Key background the board needs: [CONTEXT] - Current situation and data: [WHERE THINGS STAND] - Implications or risks: [WHAT'S AT STAKE] - What we're asking of the board: [APPROVAL, INPUT, AWARENESS] - Full detail to condense: [PASTE DETAIL] </inputs> <task> Write a one-page memo with sections: Purpose, Background, Current Situation, Implications, and Recommendation or Ask. Open by stating whether this is for information or for a decision, then give directors exactly what they need. </task> <constraints> - One page; governance-appropriate tone, strategic not operational. - State the ask precisely (approve X, advise on Y, note Z). - Balanced presentation of risks; no surprises buried in the detail. </constraints> <format> Return the memo as a markdown artifact, then note the question a sharp director is most likely to raise. </format>

Compresses detail into a one-page board briefing memo with a clear purpose and ask as a previewable artifact.

๐Ÿ’ก

Pro tip: Have Claude label the memo 'for decision' or 'for information' in the first line; it sets the board's mode before they read a word.

Deal / M&A Summary Memo

29/30

You are a corporate development analyst who writes one-page deal summary memos for approval. <context> We're evaluating an acquisition, investment, or major deal and I need a one-page summary memo for the approval committee, as a self-contained document. </context> <inputs> - The deal and counterparty: [WHAT AND WHO] - Strategic rationale: [WHY WE'D DO THIS] - Key terms: [PRICE, STRUCTURE, TIMELINE] - Financial impact: [VALUATION, SYNERGIES, RETURN] - Risks and diligence findings: [CONCERNS] - Full deal detail to condense: [PASTE DETAIL] </inputs> <task> Write a one-page memo with sections: Deal Overview, Strategic Rationale, Key Terms, Financial Impact, Key Risks, and Recommendation. Lead with what the deal is and what we're being asked to approve. </task> <constraints> - One page; every figure traceable and stated with assumptions noted. - Present the risks honestly alongside the upside; no cheerleading. - Precise, quantitative tone; flag any diligence gap with [NEEDS INPUT]. </constraints> <format> Return the memo as a markdown artifact with a key-terms table, then note the single risk most likely to break the deal. </format>

Distills deal detail into a one-page M&A summary memo with a key-terms table for approval, ready to use.

๐Ÿ’ก

Pro tip: Ask Claude to separate hard synergies from assumed ones; deals get approved on the hard numbers and unwound by the soft ones.

Recommendation Memo (One-Page)

30/30

You are a senior manager who writes tight one-page recommendation memos to drive action. <context> I've done the analysis and need a one-page recommendation memo that gets a specific action approved, as a self-contained document I can send directly. </context> <inputs> - What I'm recommending: [THE ACTION] - The situation prompting it: [CONTEXT] - Why this is the right move: [REASONING AND EVIDENCE] - What it costs and delivers: [COST, BENEFIT, TIMELINE] - What could go wrong: [RISKS AND MITIGATIONS] - Full analysis to condense: [PASTE ANALYSIS] </inputs> <task> Write a one-page memo with sections: Recommendation (in the first line), Why Now, The Case (evidence in 3-4 bullets), Cost and Expected Benefit, Risks and Mitigations, and Ask. Make the recommendation impossible to miss and easy to approve. </task> <constraints> - One page; lead with the recommendation, then justify it; don't bury the ask. - Quantify cost and benefit; make the approval a simple yes/no. - Confident and specific; every claim supported by the analysis. </constraints> <format> Return the memo as a markdown artifact, then note the one sentence to put in the email subject or first line to get it read. </format>

Turns an analysis into a one-page recommendation memo built to get an action approved as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to put the recommendation in sentence one; busy approvers decide from the opening line and read the rest only to confirm.

Frequently Asked Questions

A strong executive summary states the most important conclusion first, then supports it with only the facts a decision-maker needs. It fits on one page, uses plain language, and every number traces back to the source document. These prompts enforce that structure so you get a decision-ready summary, not a shorter version of the whole report.
The classic rule is one page, or roughly 5-10% of the source document, whichever is shorter. Every prompt here is set to produce a single page (about 400-500 words) with scannable sections and short paragraphs so a busy reader can absorb it in a minute or two.
No. The prompts instruct Claude to synthesize and restructure the source into labeled sections led by the key conclusion, not lift sentences. It pulls every claim and number from what you paste, flags anything missing with a [NEEDS INPUT] tag, and translates jargon into plain implications rather than parroting the original text.
Yes. Paste the full document into the [PASTE ...] input and Claude condenses it to one page. For very long files, paste the sections that carry the conclusions, financials, and recommendations first, since those are what an executive summary is built from.
Write it last, from the finished document, so it accurately reflects the final content and numbers. That is exactly how these prompts are designed to work: you feed in the completed plan, report, or proposal and Claude produces the summary that goes on page one.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.