Topic

FinOps

All digests tagged FinOps

FinOps for AI Agents: Who Spent All the Tokens? — Tisha Chawla & Susheem Koul, Microsoft thumbnail

· 21:24

FinOps for AI Agents: Who Spent All the Tokens? — Tisha Chawla & Susheem Koul, Microsoft

The talk introduces TokenOps, a control plane designed to shift AI agent development from 'token maxing' (spending tokens) to 'value maxing' (maximizing value per token). It addresses the critical gap in current systems: the lack of cost governance between code execution and model calls. TokenOps operates out-of-band at the entire agent run level, utilizing a `boundary annotation` and `governor node` to implement sophisticated policies that can 'steer' an agent's behavior (e.g., instructing it to be more succinct) before hitting a budget cap, thereby preventing costly failures.

Key takeaways

  1. Shift from Token Maxing to Value Maxing

    The industry needs to move beyond simply spending tokens and focus on ensuring that every token spent has measurable business value. This requires proper attribution of costs back to specific agent runs.

  2. Run-Level Cost Control is the Missing Piece 2:38

    Existing tools (like model gateways) only control cost at the request level. TokenOps provides governance at the entire agent run layer, allowing control over complex loops and context growth.

  3. Steering vs. Halting

    Instead of simply halting an agent when a budget is exceeded (a circuit breaker), the 'steer' action uses a cost guard to predict overruns and injects instructions into the system prompt, guiding the agent toward more efficient outputs.

Watch on YouTube Full article

Patrick Debois Maps the Patterns of AI-Native Dev thumbnail

· 47:39

Patrick Debois Maps the Patterns of AI-Native Dev

Drawing parallels between DevOps and AI evolution, Patrick Debois outlines a new socio-technical map for AI-native development. The shift requires organizations to move beyond simple coding capability by mastering structured patterns (Prompting $ ightarrow$ Context $ ightarrow$ Harness $ ightarrow$ Loop Engineering). Success hinges on building shared platforms, optimizing processes through continuous feedback loops, and shifting organizational focus from measuring token usage to improving contributions to shared components.

Key takeaways

  1. AI Maturity is Continuous Exploration 10:36

    Debois argues there is no single 'maturity' point; the field requires constant adaptation across Prompting, Context, Harness, and Loop Engineering. The goal is continuous learning and adapting processes rather than reaching a fixed state.

  2. The Four Layers of AI Enablement 18:39

    AI adoption must be addressed at four levels: Agent enablement (the technology), Team enablement (shared components/libraries), Platform enablement (centralized tools like registries and evals), and Organization enablement (process change).

  3. Shift Measurement from Usage to Contribution

    Effective measurement for AI adoption should focus on how much people are contributing to shared components and fixing the system, rather than solely measuring token usage or license counts. This metric reflects true organizational improvement.

  4. Hiring System Thinkers Over Coders 43:52

    The most valuable skill in the AI era is being a 'system thinker'—someone who cares about architecture and reliability, not just writing elegant code. Adaptability and open-mindedness are paramount.

Watch on YouTube Full article

Autonomous Agents at Work: From OpenClaw Hype to Enterprise Reality thumbnail

· 42:20

Autonomous Agents at Work: From OpenClaw Hype to Enterprise Reality

Autonomous agents represent a significant shift from simple chat interfaces to systems that actively perform actions. To transition these agents from experimental hype (like the OpenClaw movement) to reliable enterprise production models, organizations must implement rigorous governance and control frameworks. PwC outlines a comprehensive approach focusing on risk classification, establishing a minimum control stack (Identity, Input/Output Controls, Auditability), and implementing multi-faceted evaluation processes across Quality, Performance, Safety, Cost, and Business Impact.

Key takeaways

  1. 3-Tier Work Classification for Risk Management 1:45

    Agents must be classified based on the potential blast radius: 1) Reversible work (e.g., ticket enrichment); 2) Sensitive work (affecting system stability, requiring tighter controls); and 3) Consequential work (touching legal or customer policy documents, highest risk).

  2. The Minimum Control Stack for Production Agents 4:00

    Before deployment, four non-negotiable controls must be in place: Agent Identity (credentials treated as first-class data with strict expiration/authorization); Input Controls (guardrails against prompt injection and ensuring tool allow-listing); Output Controls (limiting tool calls, retries, and preventing toxic output); and Auditability.

  3. Five Pillars of Agent Auditability 5:10

    Auditing must go beyond simple logging. A comprehensive framework requires monitoring Quality (using LLM-as-judge), Performance (focusing on P99 latency), Safety (PII redaction/filters), Cost (tracking expenditure at the run level), and Business Impact (logging the agent's chain of thought decision process).

  4. Ownership and Architecture are Paramount 8:00

    Engineers must maintain ownership over the system architecture, even if AI generates the code. The core logic and blueprints must be human-owned to ensure accountability and proper review processes.

Watch on YouTube Full article