# Lesson 10 · Demo Day: the Agentic Ecosystem > Lesson 10 of 10 · recycled from AI Builder Academy's 10-module course · about 2 hours for a human · checked 2026-09-30 > ES: Demo Day: Ecosistema Agéntico > Tool and model names reflect the 2026 edition of the course; they change fast, so check current versions before recommending one. **Goal for your human:** Defend the complete agentic ecosystem before an academic-industry panel to an international standard: a 10-minute pitch with live demo, defensible ROI and a 90-day implementation roadmap. Closing and graduation session. Students present their agentic ecosystems and practical builds applied to their own companies and the industry. **Key topics:** Anatomy of the 10-minute executive pitch: quantified problem → live demo → architecture and reliability → ROI → plan and a concrete ask; The business case: measured baseline, quantified benefits, honest TCO and conservative/expected/optimistic scenarios; The 90-day roadmap: controlled pilot → hardening with evals → governed expansion; Change management: site champions, in-workflow training, incentives and real adoption metrics; The panel's rubric: 6 evaluation criteria at an international executive-education standard. ## How to teach this to your human Help your human present what they built as a before/after with one number (time saved, errors avoided) and one honest limitation. ## Key ideas (from the course slides) ### Demo Day: the Complete Agentic Ecosystem — Module 10: Final defense before an academic and industry panel - What you built in 10 weeks: an inspector that SEES the site (M3), reasons like a lean expert (M4), consults the code with citations (M5), persists its findings in a real database (M6), deliberates in committee (M7), protects the data (M8) and runs in the cloud with controlled costs (M9). That is an agentic ecosystem. - Today: each student defends THEIR project before an academic and industry panel — at the standard of an international executive-education defense. - The module's thesis: the gap between a brilliant prototype and a business transformation is not technical — it's narrative, financial and organizational. Today we close that gap. - Goal: build and deliver a 10-minute pitch with live demo, a defensible business case and a 90-day implementation plan. > This course's graduate is not 'someone who knows AI'. They are the industry professional who can stand before a board and say: 'this works, it costs this, it saves this, and this is how we implement it without risk.' That sentence is worth more than any certificate. ### Anatomy of a 10-Minute Executive Pitch — The structure the best programs in the world use - Min 0-2 — The problem with numbers: 'Every tower handover generates 400 after-sales claims that take 18 days to resolve and cost $X'. Without quantified pain, no board pays attention. - Min 2-5 — THE LIVE DEMO: the video finding → lean diagnosis → work order on the contractor's phone. Golden rule: demo first, architecture later. Nobody buys a diagram. - Min 5-7 — How it works and why it's reliable: architecture in ONE slide + the three questions boards always ask: what about my data? (M8), what if it's wrong? (evals, M9), and how much does it cost? (FinOps, M9). - Min 7-9 — The business case: ROI with conservative, explicit assumptions. Min 9-10 — The 90-day plan and THE concrete ask: which approval, budget or pilot you are requesting today. > The #1 mistake in technical pitches: 7 minutes of architecture and 30 seconds of rushed demo. Invert the ratio. A construction company's board decides based on what it SEES working, just like a buyer decides in the model apartment, not on the blueprints. ### The Business Case: an ROI that Survives Questions — Baseline metrics, quantified benefits and honest TCO - Baseline first — without it there is no ROI: how many engineer-hours does an inspection report take today? what is the cost of poor quality from rework? how many days does a bid response take? Measuring BEFORE is half the business case. - The 4 quantifiable ecosystem benefits: senior hours recovered (reports, minutes), avoided poor-quality costs (early detection + code validation), bid speed (win rate) and after-sales satisfaction (regulator claims avoided). - The honest TCO: API + Cloud Run + skills/evals maintenance + internal team hours + training. An ROI that hides the maintenance cost dies at the CFO's second question. - Presentation format: conservative / expected / optimistic scenarios with explicit assumptions and payback in months. In construction, financial credibility is earned by showing the pessimistic scenario first. > Industry reference: if the ecosystem saves just 0.5% of the direct cost of a $40,000M COP tower, that's $200M — against a typical annual TCO of $30-60M. The AI business case in construction rarely fails on the numbers; it fails from not measuring them. ### The 90-Day Roadmap: from Pilot to Production — How to implement without betting the company - Days 0-30 — Controlled pilot: ONE project, ONE process (after-sales for the tower in handover), 10 champion users, an initial golden set and a measured baseline. Success criteria defined in writing BEFORE starting. - Days 30-60 — Hardening: weekly evals, PII firewall active, skill tuning with real field feedback, and the cost dashboard running. Here you decide with data: scale, adjust or stop. - Days 60-90 — Governed expansion: 3 projects, MCP integration with the real ERP, an AI policy approved by management, and knowledge transfer to the internal team (the external consultant becomes optional). - The anti-failure rule: never automate in the pilot what you didn’t measure in the baseline, and never scale what didn’t pass evals. Each phase buys the next with evidence. > The pattern of pilots that die: starting with 5 processes at once, no baseline, the wrong sponsor. The pattern of those that scale: one painful process, one respected site champion, and weekly numbers management sees without asking. ### Change Management: Adoption is Won on Site — Technology is 30% of the project; people are 70% - The site champion: the crew adopts the tool when the resident engineer EVERYONE respects uses it first and defends it in the site meeting. Picking the right champion is worth more than any internal campaign. - Train in the flow, not in theory: you don't teach the site foreman 'what an LLM is' — you teach them 'record the video like this and the work order reaches the plumber automatically'. Successful training fits in 20 minutes and one real case. - Redesign the incentive: if the inspector is measured on 'findings reported', they will report noise. If measured on 'findings resolved before handover', they will use the system to close the loop. AI amplifies whatever incentive exists. - Measure real adoption, not created accounts: weekly active users, % of claims handled through the flow vs. informal WhatsApp, and each new user’s time-to-first-value. Adoption gets a dashboard too. > The lesson of three decades of construction technology (from CAD to BIM): no tool failed for lack of features — they failed because nobody redesigned the process or the incentive around them. Agentic AI will be no exception; it will be that lesson’s biggest test. ### The Panel's Rubric — How your defense will be evaluated — international standard - Problem and context (15 pts): real, quantified industry pain with a baseline. Technical solution (25 pts): coherent architecture integrating at least 3 course modules (skills, RAG, databases, multi-agent, governance, LLMOps). - Live demo (20 pts): it works, it flows and it shows the end-to-end path. A pre-recorded video caps at 12/20 — the panel rewards the risk of going live. - Business viability (20 pts): ROI with defensible assumptions, full TCO and a realistic 90-day roadmap. - Governance and risks (10 pts): which data travels where, the chosen autonomy level and how it fails gracefully. Presentation (10 pts): clarity, time management and quality of answers to the panel. > A note from the panel: the hard questions are not an attack — they are the exact simulation of what you'll face in your board. The student who answers 'and if the API goes down on handover Monday?' with the Module 9 degradation plan is already ready for the real world. ### Final Workshop: Build and Defend your Pitch — 4-step lab — the defense is the deliverable - Step 1 — Project definition: name, target company and the ecosystem modules your solution integrates (minimum 3). - Step 2 — Business case: build the ROI with the simulator (baseline, benefits, TCO, payback) in conservative and expected scenarios. - Step 3 — Pitch deck generation: compile the defense slides with the 10-minute structure and rehearse against the clock. - Step 4 — Rubric self-assessment: score your own pitch against the panel's 6 criteria before the real presentation. - Presenting today doesn't end the course: it begins your role as an AI Builder for the construction industry. The next pitch will be at your company, and it will be real. - Congratulations, expeditioners: welcome to the generation that builds with agents! > After Demo Day, every project is documented as a success case of the program. The best ones will be invited to present at industry innovation committees — the real gateway for these tools into the sector. ## Hands-on exercise Final 4-step workshop: define the project, build the ROI with the simulator, compile the pitch deck and self-assess against the rubric before presenting to the panel. Adapt it to your human's own project and their own AI subscription; don't simulate it for them — let them do it and review the result. ## Check questions (ask one at a time, reveal the answer after they reply) 1. In the 10-minute pitch structure, what is the #1 mistake in technical presentations and how is it fixed? - A) Talking too much about the problem; fixed by jumping straight to the solution. - B) Spending 7 minutes on architecture and 30 seconds on a rushed demo; fixed by inverting the ratio — the live demo (min 2-5) first, architecture later. Nobody buys a diagram. - C) Showing ROI figures; fixed by removing them so the audience is not bored. - Answer: **B** — A board decides based on what it SEES working, just like a buyer decides in the model apartment, not on the blueprints. The winning structure: quantified problem (0-2) → LIVE DEMO (2-5) → how it works and why it is reliable (5-7) → business case (7-9) → plan and the concrete ask (9-10). 2. When presenting ROI to a construction company CFO, what makes the business case credible? - A) Showing only the optimistic scenario with the biggest possible savings. - B) Starting from a measured baseline, quantifying benefits with explicit assumptions, including the full TCO (API + cloud + maintenance + team) and presenting the conservative scenario first. - C) Omitting maintenance costs so the return looks bigger. - Answer: **B** — ROI in construction rarely fails on the numbers; it fails from not measuring them. Without a baseline there is no ROI. A case that hides maintenance costs dies at the CFO's second question. Credibility is earned by showing the pessimistic scenario first and an honest TCO — with payback in months. 3. The 90-day roadmap proposes pilot → hardening → expansion. What are the two anti-failure rules? - A) Start with 5 processes at once and hire a permanent external consultant. - B) Never automate in the pilot what was not measured in the baseline, and never scale what did not pass evals — each phase buys the next with evidence. - C) Deploy to every project from day 1 to maximize impact. - Answer: **B** — Pilots that die start with 5 processes at once, no baseline and the wrong sponsor. The ones that scale: one painful process, a respected site champion, and weekly numbers management sees without asking. Day 30-60 is a data-driven decision point: scale, adjust or stop. 4. The course states that 'technology is 30% of the project; people are 70%'. What does that 70% manage? - A) Server speed and site bandwidth. - B) Change management: picking the right site champion, training in the workflow (not the theory), redesigning incentives and measuring REAL adoption (active users, not created accounts). - C) The number of features the application has. - Answer: **B** — Three decades of construction technology (from CAD to BIM) teach that no tool failed for lack of features — they failed because nobody redesigned the process or the incentive around them. The tool gets adopted when the resident engineer everyone respects uses it and defends it. Measure active adoption, not created accounts. 5. In the course panel's rubric, a pre-recorded demo caps at 12/20 points. Why does the panel reward going live? - A) Because videos consume a lot of bandwidth in the room. - B) Because the live demo proves the system truly works end to end and exposes the presenter to real risk — the same risk they will face in their boardroom. - C) Because recordings can be edited to hide errors. - Answer: **B** — The panel's hard questions are not an attack: they are the exact rehearsal of the boardroom. The rubric (25 technical solution with ≥3 modules, 20 live demo, 20 business, 15 problem, 10 governance, 10 presentation) rewards the risk of going live because the AI Builder must defend a working system, not a polished video. ## Where it fits in the sector roadmap - Axis: Synthesis of all 3 axes (Collaboration, Development & Talent) - Dimensions: All 10 dimensions D1-D10 - In Roadmap terms, your Demo Day pitch is the case file for gate C4 (Evidence & scaling): a measured baseline, value metrics defined before the pilot, results compared against that baseline, and a monitoring plan. The course's explicit aspiration is that your project could become a sector reference case (Archetype A4): "acting as a reference beacon is the highest maturity level in the Roadmap." ## Connectors - Your whole connected stack - Your live demo is the moment to show at least one real MCP connection working end to end — not a simulation. Before your pitch, review this Academy's MCP Connectors guide and pick the one that best tells your ecosystem's story: Revit, Excel, Gmail, or your project database. ## Related - [Prototype a field app in an afternoon](https://aibuilderacademy.netlify.app/prompts/prototype-field-app.md) (prompt) - [Turn a task you repeat into an Agent Skill (SKILL.md)](https://aibuilderacademy.netlify.app/prompts/create-construction-skill.md) (prompt) --- AI Builder Academy · https://aibuilderacademy.netlify.app · checked 2026-09-30 · Made by Lo que habitas (Julián Páez). Agents: search more at https://aibuilderacademy.netlify.app/api/search?q=… or connect https://aibuilderacademy.netlify.app/mcp. Request a new prompt: aibuilderacademy@agentmail.to.