The heart of the package is 15 documents in text. Instead of memorizing names, let’s group them by function — diagnostics, planning, finance, governance, and training — and understand in plain language what each one delivers and who uses it.
Illustrative diagram — 14 text documents grouped into five functions, plus 1 document with the diagram code.
Every strategy starts with an honest picture of the current situation. The group of diagnosis brings together three documents that answer: what the company already uses, what’s painful, and how mature it is in AI.
Lists the technology the company already has today: systems, tools, and where AI could fit. It’s the “floor plan” of the current environment.
Maps problems department by department (sales, support, operations...). Shows where AI would provide the most relief.
Give the company a score from 1 to 5 for how prepared it is to use AI. It serves as a “thermometer” and a point of comparison for the future.
Leaders and the strategy team read the assessment first—it justifies all the decisions that follow. The maturity score (1 to 5) is great for showing progress over time.
A diagnosis without a plan is just a complaint. These two documents turn the current picture into concrete steps: one for the entire year, the other for the first week.
30 days — quick wins and an initial foundation
60 days — first pilots up and running
90 days — consolidate and measure results
180 days — scale what worked
360 days — AI integrated into the business
5 to 10 high-impact, low-effort actions you can take right away. They're what prove AI's value early on and win support for the rest of the plan.
Instead of trying to tackle the entire roadmap at once, choose 1 or 2 quick wins. A fast, visible result convinces the team much more than a 360-day plan on paper.
Whoever signs the check thinks in numbers. These three documents answer the money questions: is it worth it, how long until it pays for itself, and can you spend less?
Cost-benefit and payback period for each AI initiative.
Build vs. buy and vendor matrix: OpenAI, Anthropic, Google...
How to bring scattered tools together and cut duplicate spending.
The finance team and anyone who approves budgets. The ROI (09) is the document that usually unlocks funding—always bring it to the decision-making meeting.
Adopting AI without rules invites trouble. The group of governance provides safeguards: what can be done with AI and how data should be handled.
The acceptable AI use policy: clear rules about what the team can and can’t do with AI tools.
Data management, security, and compliance: how to store, protect, and use data responsibly.
Good rules don't get in the way: they give the team confidence to use AI without fear. Think of the policy as a seat belt that lets everyone move ahead with confidence.
A strategy only becomes reality when people get on board. These four documents are designed to the team: teach, translate, and help you adopt AI in your day-to-day work.
Ready-made prompts organized by area. The team copies, pastes, and adapts them without needing to become AI experts.
Glossary for nontechnical readers: explains AI terms in clear Portuguese, without jargon.
Use case library by department: concrete examples of where AI can help in each department.
Training and adoption plan: how to prepare people and guide the change without resistance.
HR, team leaders, and any employee. The glossary (13) and prompt library (12) are the most useful for day-to-day work — share them early to speed up adoption.
There’s one document that’s different from the others: 03_mermaid_diagrams. It’s not for reading — it’s the code which, during the Generation phase, becomes five PNG images.
# O documento markdown guarda blocos como este:
```mermaid
graph LR
A[Hoje] --> B[Estado futuro com IA]
```
# Na fase de Geração, cada bloco vira um PNG em:
output/empresa/mermaid_images/
├── current_state.png
├── future_state.png
├── data_flow.png
├── roadmap.png
└── integration.pngThe markdown is the "source"; the PNGs are the "output." Editing the diagram means editing the Mermaid code.
It’s a common issue covered in Track 3.3: the Chrome browser is almost always missing to “take a picture” of the diagram. The text still comes out perfectly—the only thing missing is that component for the images.
With 15 documents, it’s easy to get lost. The good news: they tell a storyline in sequence. Following the order makes it easier to understand—and present.
1. Diagnosis — where we’re starting from
2. Plan — where we’re headed
3. Finance — how much it costs and how much it returns
4. Governance — how to do it safely
5. Training — how people run it
You don't need to read everything at once. Start with what you need: budget decision? Go to ROI. Team adoption? Go to training. The groups are designed to be used as needed.
3.2 — Presentations, documents & how to present — explore the 2 presentations, 2 Word documents, 5 diagrams, and script for presenting everything to leadership.