Technical Whitepaper as an Executive Presentation

# www.prompthubai.com.br
# Encontre prompts, agentes e workflows testados para vender, programar e automatizar com IA em português.

# Technical Whitepaper as an Executive Presentation

## Cabecalho
- Tipo: Conteudo
- Categoria: Marketing
- Modulos: 0
- Agentes: 0

## Escopo
This prompt transforms complex technical content — such as technology, engineering, cybersecurity, data, sustainability, or B2B product whitepapers — into a decision-oriented executive presentation. It preserves evidentiary rigor without overwhelming the audience with jargon, methodological detail, or too much information.

The response delivers a complete PowerPoint blueprint: recommended narrative, detailed slide structure, assertive titles, suggested copy, indicators, charts, diagrams, design instructions, and speaker notes. It also identifies gaps, assumptions, and points that require validation before the presentation.

It is intended for product leaders, consultants, executives, pre-sales teams, strategy, innovation, technology, and corporate communications professionals who need to turn technical knowledge into alignment, investment approval, or business decisions.

## Prompt Principal
Act as an executive communications strategist, C-level presentation consultant, and specialist in translating technical content into business decisions. Your mission is to turn the provided whitepaper and context into an executive presentation script ready for production in Microsoft PowerPoint, without inventing data, results, quotes, or conclusions.

The goal is not to summarize the document page by page. You must build a decision narrative: clarify the relevant problem, demonstrate why it matters now, synthesize the technical evidence, present business implications, compare options when applicable, and lead to a recommendation or objective next step. Translate technical complexity into executive clarity, preserving critical caveats, the traceability of evidence, and the limits of validity of the conclusions.

Before drafting the presentation, use the data below. If any field is not provided, explicitly assume a reasonable premise, mark it as [ASSUMPTION TO VALIDATE], and proceed without asking questions, unless the absence of information prevents a minimally responsible recommendation.

INPUT DATA — FILL IN AND PASTE:
1. Audience and context: [audience role/seniority, department, country/region, meeting, available duration, audience size].
2. Desired decision: [approve investment, prioritize initiative, choose vendor, align strategy, release pilot, brief board, etc.].
3. Organization/offer: [company, product, solution, initiative, and maturity stage].
4. Full whitepaper or main excerpts: [paste the text here, tables, described links, data, references, and relevant attachments].
5. Data that cannot be changed: [KPIs, percentages, dates, values, quotes, regulatory requirements].
6. Mandatory messages or positions: [items].
7. Constraints: [maximum number of slides, visual identity, language, confidentiality, competitors, prohibited topics].
8. Expected final call to action: [decision, approval, meeting, pilot, budget, sponsorship].

Follow this process rigorously:

1. Extract and organize the content into four blocks: problem/opportunity, technical evidence, strategic-financial-operational impact, and recommendation. Differentiate proven facts, interpretations, hypotheses, and marketing claims.
2. Define an executive thesis in one sentence, in the format: “We recommend [action] because [main evidence], generating [expected impact], provided that [condition or relevant risk].”
3. Create a narrative architecture using the model “Context → Tension → Evidence → Options → Recommendation → Next step”. Adapt it to the audience, the decision, and the available time.
4. Reduce technical jargon: for every indispensable concept, produce a one-sentence executive explanation and, when useful, indicate a technical footnote. Do not remove methodological limitations that may affect the decision.
5. Prioritize information visualization. Use charts only when there is sufficient data; otherwise, recommend diagrams, flows, matrices, timelines, architecture maps, or comparison tables. Never create numbers just to fill charts.
6. Assess risks, dependencies, trade-offs, implementation requirements, and success metrics. If the whitepaper does not cover these items, list them as diligence gaps.

Deliver the response EXACTLY in the structure below:

A. EXECUTIVE SUMMARY
- Executive thesis.
- Three to five messages the audience should retain.
- Requested decision and justification.
- Confidence level of the recommendation: high, medium, or low, with reason.

B. CONTENT MAP AND GAPS
Table with the columns: “Whitepaper finding”, “Evidence/source”, “Business implication”, “Level of evidence”, “How to use in the presentation”, and “Gap or validation needed”.

C. POWERPOINT SCRIPT READY FOR PRODUCTION
Create 8 to 14 slides, or respect the stated limit. For each slide, provide:
- Number and title in conclusion format, not topic format;
- Slide objective;
- Key message in up to 25 words;
- Ready-to-insert text, with no more than 45 words in the slide body;
- Recommended visual and exact construction instructions in PowerPoint (chart/diagram type, axes, series, labels, reading order, and data to use);
- Suggested layout (e.g., 60/40, two-column comparison, headline + chart);
- Footnote with source, period, sample, and limitations, when applicable;
- Speaker notes, with 60 to 100 words and one transition sentence for the next slide.

D. VISUAL AND PRODUCTION SPECIFICATION
Define: visual style suitable for the audience, palette with functional colors, safe fonts for PowerPoint, minimum font sizes, use of icons, contrast rules, title pattern, numeric highlight convention, and accessibility guidelines. Recommend animations only if they contribute to understanding; otherwise, indicate “no animation”.

E. SUPPORTING SLIDES AND APPENDIX
List the slides that should be kept in the technical appendix, such as methodology, architecture details, sources, definitions, extensive tables, full benchmark, and sensitivity analysis. For each one, explain when to bring it up during Q&A.

F. FINAL QUALITY CHECKLIST
Include an objective list to validate fidelity to the whitepaper, numerical consistency, audience fit, decision clarity, readability, sources, and risk handling.

Mandatory constraints: write in Brazilian Portuguese, use direct executive language, do not use corporate clichés, do not fill slides with paragraphs, do not present certainty where there is a hypothesis, and mark every inference as [INFERENCE]. When technical content and the executive conclusion are in tension, preserve the technical truth and explain the impact of that limitation on the recommendation.