Cambiando idioma
Carlos José Castro GalanteCarlos José Castro Galante
Carlos José Castro Galante
© 2026
Projects
AI

FaroIQ

Strategic intelligence platform for nonprofits and community organizations across Latin America. FaroIQ takes a plain-language description, runs it through a nine-agent AI reasoning pipeline, and produces in under ninety seconds a needs analysis, a phased implementation plan, impact projections, and a grant proposal ready to submit. Automatically executes across Microsoft 365: Calendar, To Do, OneDrive, and Outlook. Built on Azure AI Foundry, Microsoft Fabric, and Azure Logic Apps. Developed for the Microsoft Agents League Hackathon 2026.

FaroIQ

Metrics

Analysis time
< 90s
Pipeline agents
9
M365 integrations
4
Minimum revision score
0.70
Autonomous revision cycles
≤ 2
Export formats
PDF + Excel
Supported languages
ES / EN
Hackathon
Microsoft Agents League 2026
Screenshots

The problem

Thousands of nonprofits and community organizations across Latin America make critical decisions without data, without analytical capacity, and without access to strategic consulting. An organization with fifteen volunteers and a twelve-thousand-dollar annual budget cannot afford data scientists or strategy teams. The result is that most of them plan based on intuition, miss funding opportunities due to poorly structured proposals, and run projects without impact metrics that would allow them to learn or scale.

The solution

FaroIQ takes a plain-language description of the organization and its context, runs it through a nine-agent sequential AI reasoning pipeline on Azure AI Foundry, and produces in under ninety seconds a complete set of strategic deliverables ready to use. The pipeline chains each agent's context into the next, accumulating internal coherence at every step. An autonomous revision agent scores output quality and can re-run critical stages if the internal score falls below 0.70. When complete, Azure Logic Apps automatically executes actions across Microsoft 365: creates Calendar events, To Do tasks, uploads documents to OneDrive, and sends the summary via Outlook.

Technical stack

Frontend
React 18 · TypeScript · Vite · Three.js · Tailwind CSS
Backend
Python · FastAPI · Azure AI Foundry · Azure Blob Storage · Azure Logic Apps · Tavily

Agent pipeline

  1. Intake

    Parses the plain-language description and extracts key entities: organization, context, available resources, and declared objectives.

  2. Research

    Fetches relevant external data via Tavily: sector statistics, regional benchmarks, and similar cases across Latin America.

  3. Analyst

    Cross-references Intake and Research data to identify critical needs ranked by severity and potential impact.

  4. Planner

    Designs a phased implementation plan with milestones, suggested owners, and time and resource estimates.

  5. Evaluator

    Generates impact projections with confidence intervals based on Research data and the Planner output.

  6. Writer

    Drafts a grant proposal ready to submit to international funds and open calls.

  7. Critique

    Evaluates internal coherence and feasibility of the accumulated output. If the score falls below 0.70, re-runs Planner and Evaluator.

  8. Formatter

    Structures the final output as validated JSON ready to render in UI and export to PDF and Excel.

  9. Executor

    Triggers Microsoft 365 integrations via Azure Logic Apps: Calendar, To Do, OneDrive, and Outlook.

Challenges

  • Designing a nine-agent pipeline in strict sequence where each agent receives the accumulated output of all preceding agents without exceeding Azure AI Foundry token budget

  • Implementing the autonomous revision loop in the Critique agent, which evaluates coherence, feasibility and completeness of the plan before authorizing Logic Apps execution

  • Maintaining an open WebSocket connection throughout pipeline execution for real-time per-stage streaming without blocking FastAPI's event loop

  • Managing the differences between Microsoft 365 personal and work accounts for Logic Apps integrations, which have distinct permissions and endpoints

  • Synchronizing the Three.js globe visual state with the actual pipeline progress without introducing perceptible latency in the stream

Learnings

  • Context chaining between agents is more effective than parallel agents when internal output coherence matters more than raw speed

  • An agent that can identify its own weaknesses and correct them autonomously provides more operational trust than one that simply produces output without evaluating it

  • Three.js with day/night mode and scene changes requires a full remount via React key prop to guarantee clean state and avoid WebGL memory leaks

  • Azure Logic Apps is the cleanest M365 integration path when payload flexibility is needed without depending on a proprietary SDK with complex licensing

  • The biggest bottleneck in agent pipelines is not model latency but the serialization and deserialization of accumulated context between steps