🟣 Deliverables & Best Practices

What it is

Three files that capture the current situation: 01_tech_inventory (the technology the company already uses), 02_pain_points (the pain points, area by area) and 04_maturity_assessment (an AI maturity score from 1 to 5).

Why learn

This is the starting point for the entire strategy: you can only know where to go after understanding where you're starting from. They serve as the basis for the plan and ROI.

Key concepts

• 01 = current technology inventory
• 02 = pain points mapped by department
• 04 = AI maturity score (1 to 5)

What it is

05_roadmap maps the path in phases (30 / 60 / 90 / 180 / 360 days) and 06_quick_wins lists 5 to 10 high-impact quick wins to get started right away.

Why learn

This is the part that turns into action: the roadmap gives you the full-year view; the quick wins show what to do in the first week to deliver results and build confidence.

Key concepts

• 05 = phased plan (30/60/90/180/360)
• 06 = high-impact quick wins
• Start with quick wins to prove value

What it is

09_roi_calculator shows cost-effectiveness and payback period; 07_vendor_comparison compare building vs. buying and provide a vendor matrix (OpenAI, Anthropic, Google...); 08_license_consolidation points to how to combine tools and save money.

Why learn

This is what convinces the person signing the check. Executives think in numbers: returns, payback period, and where duplicate spending can be cut.

Key concepts

• 09 = cost-benefit and payback
• 07 = build vs. buy + vendor matrix
• 08 = consolidate licenses and save

What it is

10_ai_policy is the company’s acceptable use policy for AI (what’s allowed and what isn’t); 11_data_governance covers data management, security, and compliance.

Why learn

Adopting AI without rules is risky. These two documents protect the company from leaks, misuse, and legal issues—and give teams the confidence to use AI.

Key concepts

• 10 = acceptable use policy
• 11 = data management, security, and compliance
• Reduce risk and give the team confidence

What it is

Four documents for people: 12_prompt_library (ready-to-use prompts by area), 13_glossary (glossary for nontechnical readers), 14_use_case_library (use cases by area) and 15_change_management (training and adoption plan).

Why learn

A strategy only works if people get on board. These documents turn the plan into something the team understands, uses every day, and truly adopts.

Key concepts

• 12 = prompt library by department
• 13 = glossary for nontechnical readers
• 14 = use cases · 15 = adoption plan

What it is

The document 03_mermaid_diagrams isn't ordinary text: it stores the code (in Mermaid language) that, during the Generation phase, becomes five PNG images — current state, future state, data flow, roadmap, and integration.

Why learn

Knowing that the Markdown is the "source" and the PNGs are the "result" helps explain why the image sometimes doesn’t come out (covered in Track 3.3) — and how to edit the diagram in the code.

Key concepts

• 03 = Markdown with the Mermaid code
• Turn into 5 PNGs during the Generation phase
• current, future, data_flow, roadmap, integration

What it is

The natural sequence is: Diagnosis → Plan → Finance → Governance → Training. Each group prepares the next, like a story that starts with the problem and ends with execution.

Why learn

You don't need to read everything in order to understand it—but following the sequence makes it easier to explain the strategy to others and put together the presentation.

Key concepts

• Diagnosis → Plan → Finance → Governance → Training
• Executives start with the executive summary
• Next: roadmap (05) and ROI (09)

What it is

The file executive_summary_deck.pptx is a short presentation, 10 to 15 slides, designed for the board. It gives only the big picture: the essentials, without technical details.

Why learn

This is the material you use when you have 15 minutes to convince the decision-maker. Short, direct, and focused on value and numbers.

Key concepts

• File: executive_summary_deck.pptx
• 10-15 slides, high-level overview
• Audience: executive leadership / board

What it is

The file full_findings_presentation.pptx is the full version, 40 to 50 slides, with all findings and recommendations in detail—the expanded version of the executive summary.

Why learn

It’s useful for workshops, technical meetings, or when the team asks for details. It’s background material for anyone who wants to go beyond the high-level overview.

Key concepts

• File: full_findings_presentation.pptx
• 40-50 slides, findings + recommendations
• Audience: technical team / deeper dive

What it is

The file final_strategy_report.docx is the complete written report in Word: it brings all the compiled documents together in a single continuous text, ready to read from beginning to end.

Why learn

This is the “official” document you deliver or archive. Good for anyone who prefers reading over slides, and easy to edit in Word.

Key concepts

• File: final_strategy_report.docx
• All compiled documents
• Word format, easy to edit

What it is

The file statement_of_work.docx is a statement of work (SOW): it describes what will be done, with a timeline, required resources, and estimated costs.

Why learn

This is the bridge between strategy and execution. Consultants use it as the basis for a business proposal; internal teams use it as a project plan.

Key concepts

• File: statement_of_work.docx
• Timeline + resources + costs
• Proposal or project template

What it is

Five PNG images ready to paste into slides: current_state (current state), future_state (future state), data_flow (data flow), roadmap e integration (integration).

Why learn

A diagram is worth a thousand words in a meeting. These PNGs are in the folder mermaid_images/ and can be dragged directly into the presentation.

Key concepts

• 5 PNGs: current, future, data_flow, roadmap, integration
• Are stored in mermaid_images/
• Ready to paste into slides

What it is

A simple agenda for running the meeting: start with the executive summary, show the assessment, present the roadmap and ROI, and wrap up with the quick wins (what you can do right away).

Why learn

Having the files isn’t enough — the order of presentation makes a difference. This workflow tells a story: where we are, where we’re going, what it yields, and where to start.

Key concepts

• Summary → diagnosis → roadmap → ROI → quick wins
• Customize before presenting
• Review the numbers (it's an AI draft)

What it is

The error 401 means "unauthorized": the key is incorrect or missing. Check whether the file .env exists and whether the keys are in the right format (pplx-... / AIzaSy...), with no spaces. Then restart the app.

Why learn

This is the number one mistake beginners make. Almost always, it's a small detail: an extra space, a key that was only partially pasted, or the file in the wrong place.

Key concepts

• 401 = incorrect or missing key
• Format: pplx-... and AIzaSy..., with no spaces
• Restart the app after fixing the .env

What it is

The "Module not found" error usually means the virtual environment (venv) isn't active. Activate the venv and run pip install -r requirements.txt. On Windows, also check that Python is on the PATH.

Why learn

It's easy to forget to activate the venv when you open a new terminal. Without it, Python can't see the installed libraries and complains that modules are missing.

Key concepts

• Activate the venv before running
• Reinstall: pip install -r requirements.txt
• Windows: Python must be on the PATH

What it is

If port 8888 is already in use, the app automatically finds another available port. If you prefer to choose one, run it with --port 9000 (or any other number).

Why learn

This “problem” almost never stops you—it’s just a warning. Knowing this prevents surprises when the address in your browser shows a different number.

Key concepts

• App finds an available port automatically
• Force: --port 9000
• It's not a serious error

What it is

The error 429 means "too many requests" — you hit the API rate limit. Wait 5 to 10 minutes and resume where you left off with the command resume. There’s already a delay of about 5s built in between Gemini calls.

Why learn

You don't lose your work: the resume picks up where you left off. Waiting a little usually solves it, without having to start from scratch.

Key concepts

• 429 = rate limit reached
• Wait 5-10 min and run resume
• A ~5s delay is already built in (Gemini)

What it is

If the diagrams are generated as blank PNGs, Chrome is usually missing (Puppeteer uses it to “take a picture” of the diagram). The solution is to install Chrome on your computer or run the tool via Docker.

Why learn

The documents may turn out perfectly while only the images fail — an isolated problem in the Generation phase. Knowing the cause keeps you from thinking that "everything went wrong."

Key concepts

• Blank PNG = Chrome/Puppeteer is missing
• Install Chrome on your computer
• Alternative: run via Docker

What it is

Four habits: start in quick mode, give it a good --context, run several companies in quick mode and only dig deeper into the one you choose, and always review the outputs before using it.

Why learn

These practices save money and greatly improve quality. The difference between an average draft and a great one usually comes down to context and review.

Key concepts

• Start in quick mode · provide a good --context
• Scan quickly, then dig deeper into the one you choose
• Always review before delivering

What it is

The tool uses public data (not confidential company data), and the result is a draft that requires human review; it is not definitive legal or financial advice. Track spending with the commands status e list.

Why learn

Using it responsibly protects you and the company. Treating the result as a draft — not absolute truth — is what maintains quality and trust.

Key concepts

• Public data only · draft with human review
• Not definitive legal or financial advice
• Track spending with status / list