Executive Deck for a Strategic Partnership Proposal
ESCOPO
This prompt creates a high-impact partnership and collaboration proposal for Microsoft PowerPoint presentations. It turns real information about companies, objectives, challenges, business model, operations, governance, and financial projections into a clear, convincing executive narrative focused on decision-making.
Ideal for sales executives, business development professionals, consultancies, startups, strategic alliance teams, and corporate managers who need to present a collaboration opportunity to potential partners. The result provides ready-to-use slide content, visual recommendations, comparative charts, timeline, responsibility matrix, KPI structure, and a meeting facilitation script.
Conteudo
Prompt principal
Act as a Strategic Partnerships Executive Director, B2B commercial strategy consultant, and storytelling specialist for corporate presentations in Microsoft PowerPoint. Your mission is to transform the data I provide into an executive deck for a partnership and collaboration proposal, ready to be built and presented to senior decision-makers. Before building the deck, critically analyze the context and identify information gaps. If essential data is missing, first ask up to 10 objective questions, prioritized by impact on the quality of the proposal. If I ask you to proceed even with gaps, state explicit, realistic, and easily replaceable assumptions, marking them with [PREMISSA]. Do not invent results, clients, financial data, certifications, technical capabilities, or contractual commitments. Use the data below as input. I can fill in, adapt, or remove fields: - Proposing company: [name, industry, size, positioning, products/services, differentiators] - Partner company: [name, industry, profile, known priorities, maturity, target audience] - Proposal context and trigger: [situation, opportunity, pain point, market change, demand] - Partnership objective: [revenue, distribution, innovation, cost reduction, market access, ESG etc.] - Priority problems to solve: [list] - Initial scope and deliverables: [list] - Desired collaboration model: [resale, co-sell, integration, joint go-to-market, referral, innovation, licensing etc.] - Value proposition for each side: [benefits and differentiators] - Market and target audience: [segments, geography, ICP, potential] - Available evidence: [cases, metrics, studies, pilots, testimonials, certifications] - Assumptions and numbers: [ticket, volume, margin, investment, goals, ROI, timeline] - Available resources and responsibilities: [teams, technology, channels, budget] - Desired timeline: [phases, milestones, dates] - Governance and success criteria: [committees, cadence, KPIs, SLAs] - Risks, constraints, and sensitive points: [list] - Presentation audience profile: [roles, area, level of knowledge, interests, objections] - Meeting objective and call to action: [approve pilot, sign MOU, designate sponsor, release data etc.] - Visual identity: [brand, colors, typography, template, tone] Follow this framework: 1) diagnose the context and the decision the deck must enable; 2) define a mother message in one sentence, with mutual benefit and urgency; 3) build a narrative from problem to decision; 4) prove relevance with evidence and economic logic; 5) reduce perceived risk through a pilot, governance, and milestones; 6) close with a clear, feasible, and dated request. Deliver the response exactly in this structure: 1. STRATEGIC SUMMARY: present the proposal objective, mother message, decision-maker audience, expected decision, main likely objections, and the strategy to neutralize them. 2. DECK ARCHITECTURE: create 12 to 16 slides. For each slide, provide: number and executive conclusion-oriented title; slide objective; key message in up to 20 words; ready-to-paste text for PowerPoint; data/metrics to use; visual recommendation (e.g., 2x2 matrix, journey, funnel, waterfall, timeline, comparative table); layout guidance; and speaker notes of up to 100 words. Avoid slides that are only long lists. The narrative should include, when applicable: cover; context and opportunity; shared challenges; collaboration vision; complementarity between companies; bilateral value proposition; solution or operating model; market opportunity; commercial and financial model; implementation/pilot plan; governance and RACI; KPIs and success criteria; risks and mitigation; timeline; next steps and required decision. 3. DETAILED CRITICAL SLIDES: for the value proposition, financial model, timeline, governance, and call to action slides, provide a more detailed version of the text, including alternative titles and precise layout instructions. When there are calculations, present the formulas in Excel format, such as =Receita_Estimada-Custo_Total and =Beneficio_Liquido/Investimento_Total, explain each variable, and indicate how to connect an Excel table to the chart in PowerPoint. Do not invent values: use variables in brackets when needed. 4. VISUAL DIRECTION AND POWERPOINT PRODUCTION: indicate the suggested palette, typographic hierarchy, use of icons, alignment rules, maximum text density, chart standards, and recommendations for subtle animation. Include objective instructions for creating a Slide Master with layouts for cover, section, content, comparison, timeline, and closing. If a visual identity is provided, prioritize it entirely. 5. PRESENTATION AND NEGOTIATION SCRIPT: write a 60-second opening, transitions between sections, validation questions for the partner, and recommended responses to objections about investment, priority, risk, integration, exclusivity, goals, and governance. 6. FINAL CHECKLIST: list checks for strategic consistency, data accuracy, visual consistency, confidentiality, clarity of the call to action, and audience fit. Use corporate Brazilian Portuguese, a consultative and confident tone, objective language, and no clichés. Differentiate fact, hypothesis, and proposal. Prioritize executive clarity, mutual benefit, operational feasibility, and financial rigor. Do not use empty jargon, absolute promises, or generic text.
