Joule Pricing & Consumption
As of 2026-08-16
Joule's bill is the line item that most often blindsides an AI programme sponsor, because inference cost scales with usage and ambition the way a dashboard query never does. The rule for this module: model the consumption drivers — adoption breadth, interaction complexity, and above all agent autonomy, since a looping agent burns far more than a single answer — and price them against the client's own SAP contract, never a rate you assume. Build the ROI case per use case, not as a platform-wide promise: EY's ~30% delivery-time gain and KPMG's ~20% faster sprints are real, but they are those firms' results on their use cases, not this client's guarantee. Then govern what you've modelled — visibility, budget ceilings, and human-in-the-loop on every autonomous agent — so the programme scales without a finance ambush. Get this right and you are pricing AI value for a sponsor who has never had to before; that is a day-rate conversation most consultants can't yet have.
What you will learn
- Model Joule consumption drivers (adoption breadth, interaction complexity, agent autonomy, grounding retrieval) without inventing a per-call price — rates come from the SAP contract (§0i)
- Build a per-use-case ROI case against actual consumption, citing published anchors (EY, KPMG, Daimler) as those firms' results, not a guaranteed return
- Apply the FinOps loop to AI spend — consumption visibility, right-sized deployment, and budget guardrails — with explicit limits and human-in-the-loop on autonomous agent loops
- Defend the 'proportionate value' framing to a sponsor: neither runaway agent consumption nor under-investment that forfeits AI value
Module overview
Joule pricing and consumption is the FinOps of AI on the SAP stack — and it matters because generative AI is the one workload whose cost can surprise an organisation most sharply. Where a dashboard query is cheap and predictable, AI inference (especially over many users asking many questions, and increasingly autonomous agents acting in loops) is consumption that scales with usage and ambition. The consultant who understands Joule's consumption model prevents the "the AI bill is what?" conversation that derails AI programmes.
Consumption-based, like the rest of BDC. Joule usage is metered (AI units / consumption-based), consistent with BDC's overall consumption pricing (companion module M032). The exact units and bundling come from the customer's SAP contract — the consultant models the drivers, never invents a per-call price. The drivers are: number of users, queries per user, complexity of each interaction (a simple lookup vs a multi-step agentic task — companion module M049), and the degree of autonomy (an agent that loops consumes far more than a single answer).
Prerequisites
- Review core concepts first: C024, C029, C028
Outcomes
- Understand the core concepts behind joule pricing & consumption
- Apply Pricing in a typical SAP analytics engagement
- Explain the core architecture and decision points for Joule Pricing & Consumption
- Apply a repeatable implementation pattern in a 15-minute lab format
Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.