# How to put AI spend in front of a board without it becoming a line item > A model bill isn't a board metric. Gross margin falling 76.0% to 66.4% on 40% cost growth is, and both describe one quarter cut two ways. URL: https://getculpa.com/ai-cost-in-a-board-pack Last reviewed: 2026-08-05 Rates effective: 2026-07-02 ## Answer A board cares whether AI spend changes unit economics, not what it totalled. Report gross margin, cost per unit sold and the trend in both, with the bill as supporting detail. Culpa, a local-first LLM cost, margin, and forecast ledger, holds cost and revenue together so margin is a query rather than a spreadsheet. ## Why this happens AI spend usually reaches a board as a number and a direction, which is the least useful form it takes. A total tells nobody whether the business is working. It rises when you grow, which is good, and it rises when you're inefficient, which isn't, and the two are indistinguishable in a single figure. What a board is actually deciding is whether the unit economics hold as volume increases, and that needs the cost divided by something: gross margin, cost per customer, cost per transaction. The failure isn't ignorance, it's that the join is genuinely hard. Model spend arrives on a provider invoice with no customer attached, revenue lives in a billing system with no tokens attached, and nothing joins them by default. So the metric that would answer the question doesn't exist, and a total gets reported because a total is what's available. The second failure follows: a point estimate for next year, when what a board needs is a range and the trigger for acting on the top of it. ## What this usually looks like - AI cost reaches the board as a total and a percentage change. - Nobody can state gross margin with model spend inside cost of goods sold. - Cost per customer isn't reported because it can't be produced. - Next year's AI line is a single number with no range. - The board asks whether it scales and the answer is a chart of spend. ## Common mistakes - Reporting AI spend as a total. Why it hurts: It rises with growth and with waste, and a total can't distinguish them. Do instead: Report gross margin and cost per unit sold, with the total as a footnote. - Leaving model spend out of cost of goods sold. Why it hurts: It overstates gross margin, and the correction arrives later as a restatement. Do instead: Book it in cost of goods sold and show the margin it produces. - Presenting a single number for next year. Why it hurts: It's wrong by construction and gives the board nothing to hold anyone to. Do instead: Present a range with the assumptions named, and the action at the top of it. - Showing cost without the revenue it supported. Why it hurts: The board can't tell an expensive product from a growing one. Do instead: Put cost and revenue on the same cut, by product or by customer segment. ## Self-check - Try to state gross margin with model spend in cost of goods sold, for last quarter. - Work out cost per paying customer and see whether it's rising or falling. - Check whether your AI line has a range around it or a single figure. - Ask what you'd cut at the top of that range, and whether anyone has agreed it. ## The same quarter, as a total and as a margin (illustrative) A modelled business at $50,000 of monthly revenue with $12,000 of model spend in cost of goods sold, where cost grows 40% over a period while revenue holds flat. Every figure is modelled, and the point is the comparison rather than the amounts. reported as a total: model spend rose from $12,000 to $16,800, up 40% gross margin before: ($50,000 - $12,000) / $50,000 = 76.0% gross margin after: ($50,000 - $16,800) / $50,000 = 66.4% the same movement, stated as margin: 9.6 percentage points of gross margin gone A 40% rise in a cost line invites a conversation about vendors. A 9.6-point fall in gross margin invites a conversation about the business. Both describe the identical quarter, and only one of them tells a board what it needs to decide. ## Cost figures Every figure carries its confidence and its source. No figure on this page is provider-reported. - 76.0% falling to 66.4%, modelled gross margin before and after a 40% rise in model spend at flat revenue [calculated] Source: A modelled $50,000 of monthly revenue with model spend rising from $12,000 to $16,800 in cost of goods sold. ($50,000 - $12,000) / $50,000 = 76.0% and ($50,000 - $16,800) / $50,000 = 66.4%, a fall of 9.6 percentage points. Every figure is modelled, and the comparison rather than the amounts is the point. ## FAQ Q: What AI metric should go in a board pack? A: Gross margin with model spend inside cost of goods sold, plus cost per unit sold and the trend in both. The total belongs in supporting detail. A total rises with growth and with waste equally, so on its own it can't answer the question a board is asking. Q: Why is a total misleading? A: Because it moves for opposite reasons. In the modelled example a 40% rise in model spend reads as a vendor problem, while the same movement stated as margin is 9.6 percentage points of gross margin, from 76.0% to 66.4%. Same quarter, two very different conversations. Q: Should AI spend sit in cost of goods sold? A: If it scales with usage, yes. Booking it elsewhere overstates gross margin and the correction tends to arrive later as a restatement. The test is whether the cost rises when a customer uses the product more, which for model spend it does almost by definition. Q: How should next year's AI budget be presented? A: As a range with its assumptions named, and with the action agreed for the top of it. A single number is wrong by construction, and a range that nobody has attached a decision to is only slightly better. What makes it useful is knowing in advance what gets cut if the high case arrives. ## Sources - Anthropic pricing: https://platform.claude.com/docs/en/docs/about-claude/pricing Run the free Cost Leak Scan: https://app.getculpa.com/scan?source=pseo&slug=ai-cost-in-a-board-pack&cluster=problem Machine-readable index of every guide: https://getculpa.com/api/pages Human-readable index of every guide: https://getculpa.com/guides Site overview: https://app.getculpa.com/llms.txt Privacy: Culpa runs on your infrastructure. Your prompts and responses never leave it. Culpa counts calls to run your plan, and it fails open, so if it ever breaks your app keeps running.