Prompts de IA

Create a comprehensive, persuasive, and professional project proposal tailored for executive stakeholders, using the provided input information. The document must follow industry best practices, address stakeholder concerns, and include robust, data-backed justification for recommendations, estimates, and risk mitigation. Ensure all required sections are present, with client-customizable placeholders where needed.

- Persist in exhaustively covering each section of the required structure before providing the final complete document.
- Think step-by-step and internally validate numbers, logic, flow, and compliance with the quality checklist as you assemble the document.

## Proposal Structure (Step-by-Step Ordering)

### Content Sequence (Reasoning First, Conclusions Last)
In every section that asks for justification, alternatives, or rationale (e.g., solution comparison, ROI calculation, risk assessment, budget analysis), first provide the supporting reasoning, data, or comparative matrix; only then give the recommendation, classification, or summary conclusion.

#### Examples:
- In the "Proposed Solution" section, first discuss alternatives and key factors; then present the recommended solution.
- For budget and ROI sections, show calculations, assumptions, and sensitivity analysis before stating expected figures or conclusions.
- In all tables and matrices, clearly separate factors (reasoning) from the chosen/assigned values (conclusions).
- MARK N/A SECTIONS with justification, not just an empty label.

### Visual Aids and Tables
- Include tables for alternatives, risk registers, cost breakdowns, and skills/resource matrices.
- Insert placeholder indicators [CUSTOMIZE: instruction] for required visuals (e.g., timeline chart, budget chart, risk matrix), with guiding notes for clients to update with project-specific data.
- Use bullet points, tables, and bolded headers to maintain legibility and logical flow.

### Output Formatting Requirements

- Structure the proposal as a Markdown document. 
- Use H1, H2, and H3 headers for organization.
- Insert visual aid placeholders and tables at appropriate sections.
- Include clearly labeled page and version control placeholders.
- Each proposal section must begin with a brief statement of purpose, followed by in-depth content.
- Place all explanations, justifications, and data before recommendations or conclusions in each section.
- Mark areas requiring user or client customization with [CUSTOMIZE: instruction].
- List appendices at the end; mark technical sections N/A if not applicable.
- Maintain document length of 15-25 pages (when fully filled); in examples/structure provide concise outlines, with placeholders for real content.

### Example Section (Abstracted with Placeholders)
#### Input Placeholder Example
- Project Name: [CUSTOMIZE: Name of the proposed project]
- Project Type: [CUSTOMIZE: Type]
- Industry Context: [CUSTOMIZE: Industry/Sector]
- Primary Stakeholders: [CUSTOMIZE: List]
- Estimated Budget Range: [CUSTOMIZE: Range]
- Timeline Expectations: [CUSTOMIZE: Timeline]
- Problem Statement: [CUSTOMIZE: Restate]
- Strategic Alignment: [CUSTOMIZE: Organization/Objective]

#### Output Example Start (Markdown)
# [CUSTOMIZE: Project Name]  
**Document Version:** [CUSTOMIZE: Vx.y] | **Date:** [CUSTOMIZE: Date] | **Page:** [CUSTOMIZE: Page X of Y]

## Executive Summary
**Purpose:** To succinctly outline the business case, solution, and key investment recommendations.

- **Overview:** [CUSTOMIZE: 2-3 sentences]
- **Drivers & Urgency:** [CUSTOMIZE: Summary of business drivers]
- **Expected Outcomes:** [CUSTOMIZE: Quantified value/business benefit]
- **Summary of Investment & ROI:**  
    - *Reasoning & Assumptions:* [CUSTOMIZE: Data sources, market benchmarks, calculation basis]
    - *Conclusion:* [CUSTOMIZE: ROI % and payback period summary]
- **Next Steps:** [CUSTOMIZE: Clear call to action]

---

## Problem Statement & Opportunity Analysis
**Purpose:** To substantiate the business need and potential.
1. **Analysis:**  
    - *Supporting Data:* [CUSTOMIZE: Data/table reference]
    - *Business Impact:* [CUSTOMIZE: Quantified pain points]
    - *Competitive/Market Context:* [CUSTOMIZE: Comparison]
    - *Opportunity Cost:* [CUSTOMIZE: Cost of delay/inaction]
    - *Root Cause Analysis:* [CUSTOMIZE: Issue tree/table or summary]
2. **Conclusion:** [CUSTOMIZE: Justified problem framing]

---

(… continue similarly for all remaining sections as per structure …)

## Appendices
- [CUSTOMIZE: Link/list of additional technical details, research, vendor quotes, etc.]

---

### Additional Instructions & Considerations

- Justify all estimates and conclusions before summarizing.
- Use [CUSTOMIZE: instruction] tags for all user/client-specific insertions.
- Table/visual placeholders should be clearly marked and include guidance.
- Strictly maintain the executive tone, clarity, and structure per requirements.
- All acronyms/technical terms must be defined at first use (include glossary).
- If any section is not applicable, label as “N/A” with concise justification.
- Carefully validate all numeric consistency, logic, and completeness before finalizing.
- Refer to the quality checklist before considering the document complete.

---

**REMINDER:**  
Your main objective is to produce a complete, client-ready, executive-level project proposal in well-structured Markdown, following all content, quality, and format requirements above. Be sure to present your data or reasoning before stating any recommendations or conclusions in each section. Use [CUSTOMIZE: instruction] tags for content to be filled in with client/project-specific detail. Do not omit any required section—mark “N/A with justification” if not relevant.