AI Company Board Reporting: A Decision-Ready Pack

An AI company board pack should help directors understand the current financial position and make the decisions put to them. Start with a short decision register. Support it with consistent revenue, delivery-cost, cash, and hiring views, then show what changed from the previous plan. The exact pack and meeting cadence should follow the company’s governance requirements and the decisions ahead.

The structure below is Amafi Advisory’s practitioner framework for management reporting. It is a working outline, not a reporting standard or a claim about how every board operates.

Put decisions before the dashboard

For each proposed decision, give the board enough information to respond without reconstructing the model during the meeting.

Board item	What management should show
Decision or approval	The precise question, the required approval route, and the date a decision is needed
Recommendation	Management’s preferred course and the reason for it
Alternatives	At least the practical option of deferring or changing scope, where relevant
Financial effect	Cash timing, expected margin, capacity, and the assumptions that could change the answer
Follow-through	The owner, next checkpoint, and where the outcome will appear in the next pack

Approval authority depends on the company’s governing documents and board practices. Management should confirm that authority with its counsel or company secretary. A commercial choice can still merit discussion when formal board approval is not required. If there is no decision request, say so and use the section to record material risks or changes since the previous meeting.

Show revenue with its source and timing

Separate contracted recurring amounts, variable usage, and one-time services in the management view. For each, show actuals against plan, the reason for a material variance, and what management expects next. If ARR appears, define the contract and usage rules behind it and reconcile it to recognized revenue and collections. ARR, revenue, and cash answer different questions.

The SEC’s guide to financial statements distinguishes the income statement from the cash flow statement. That distinction supports showing a cash bridge alongside revenue, but the particular management metrics and bridge design are company decisions (accessed November 2, 2026).

Keep a KPI definition register for each reported measure: calculation, source system, data owner, and prior-period treatment. When a definition changes, show the old and new basis before comparing growth rates.

Reconcile reported gross margin to delivery economics

Reported gross margin should retain the cost classification used in the accounts. A separate management view can ask which costs vary with a customer or workflow. For an AI product, candidates may include model usage, cloud processing, retrieval or data charges, human review, implementation, and support. Include a cost only where the company can explain its source and allocation rule.

View	Board question	Reconciliation check
Reported gross margin	What do the accounts show?	Tie revenue and cost of revenue to the closed financials
Direct delivery view	What did the measured usage and service work cost?	Trace provider bills and operating records to customers or workflows
Unallocated costs	What is excluded from the direct view?	Name shared infrastructure, support, or overhead and avoid implying it is zero

For example, if a model provider bill rose while customer revenue was flat, show whether the change came from more requests, a different model, a changed provider rate, or an allocation error. OpenAI’s API pricing page is one current example of provider charges that depend on model and usage category (accessed November 2, 2026). The reconciliation and the decision to allocate a cost to a customer are Amafi Advisory practitioner judgment. The board should see the bridge, not an unsupported headline margin. The AI unit economics guide sets out the underlying cost trace.

Connect cash scenarios to decision dates

Show the cash balance from the closed record, expected collections and payments, and the decisions that could change them. A base view and a plausible downside view are useful when they lead to different actions. State the assumption that separates the cases, the first date at which management must decide, and the owner of that decision.

Do not substitute a single runway number for this schedule. Runway depends on the cash definition, burn assumption, and timing of receipts and commitments. The cash and runway planning guide explains how to record triggers and decision dates without treating a forecast as a guarantee.

Make hiring and capacity part of the plan

Show committed hires, planned hires, contractor work, and their cash effect against the product and commercial milestones they support. If a proposed hire changes the downside cash case, bring the trade-off into the decision register. The pack should identify who owns any capacity constraint, not merely list open roles.

Establish a repeatable reporting handoff

Finance should own the financial definitions, reconciliations, forecast, and version history. Product and operations should verify usage and delivery inputs; commercial leaders should verify customer and pipeline assumptions; the CEO should own the management recommendation. Assign a source owner and review date to each input before setting a pack deadline. A fixed number of days before the board meeting is not credible if the close and source checks cannot support it.

A workable sequence is: close the period, reconcile the source data, update the model, review material variances with input owners, agree the decision register with management, and circulate the pack on the board’s agreed timetable. Keep the prior forecast so directors can see what changed. The variance analysis guide describes how to make that comparison useful.

Common questions

What should an AI company board pack include?

Start with the decisions and approvals requested, then show revenue and customer movement, a defined delivery-cost view, cash scenarios, hiring commitments, and material variances. Give each measure a definition, source, and owner.

How often should an AI company send a board pack?

Agree the cadence with the board and the company’s reporting capacity. A monthly management pack can support a different board-meeting schedule, provided management updates cash and material risks between meetings.

How should an AI company show delivery margin to its board?

Show reported gross margin from the accounts and a separate management view that traces model, cloud, data, human-review, and other delivery costs to the customers or workflows that caused them. Reconcile the two views and state which costs remain unallocated.

Which decisions belong in the board pack?

List decisions that require board approval under the company’s governing documents and material choices on which management wants a board view. For each, state the recommendation, alternatives, cash effect, decision date, and accountable owner.

If recurring reporting and board decisions need a senior finance owner, see the fractional CFO retainer. If the company needs a defined pack design and management handoff, see corporate finance projects. Use the contact form to describe the reporting cycle, current finance owner, and next board decision.