The moment every CAIGO faces: how to translate a successful 30-day proof into a budget request the board approves, funds at the right level, and holds the right person accountable for.
The 30-day proof worked. The metric moved. You have a result the board can hold. Now comes the moment that determines whether the AI Growth function becomes a permanent fixture on the org chart or gets folded back into IT under a different name: you have to ask for real money.
Most CAIGOs get this wrong not because they cannot build a business case but because they frame the ask incorrectly. They present a budget request as a cost, defend it like a cost, and then spend the next six months fighting to keep it from being cut like a cost. The CAIGO who survives the first budget cycle frames the ask as an investment with a defined return surface, a named owner, and a pre-agreed measurement cadence. Those are structurally different conversations, and the board treats them differently.
This post covers the mechanics of that conversation: how to size the ask, how to structure the slide, what objections will come and how to preempt them, and how to set up the accountability structure so you are not re-justifying the function every quarter. It builds directly on the proof initiative framework from the First 90 Days.
A common assumption among first-time CAIGOs is that a demonstrated proof result automatically generates funding momentum. In most organizations it does not, for a structural reason: the proof result lands in a budget process designed for known cost categories. AI investment does not fit any of those categories cleanly. It is not IT infrastructure (no depreciation schedule), not headcount (no salary benchmark), not vendor licensing (no renewal cycle). The CFO's standard evaluation templates have no row for it.
The result is that even a compelling proof can stall for months while finance figures out which bucket it belongs in. Organizations that do not have a CAIGO-level function with board visibility tend to resolve this ambiguity by defaulting to the most conservative option: approve a small extension of the pilot, defer the larger ask to the next planning cycle, or reassign the work to an existing function with a smaller budget and no mandate.
The budget stall is not a signal that the board does not believe in AI. It is a signal that the board has no mental model for what AI investment produces at what cost at what timeline. The CAIGO's job in the budget conversation is to supply that mental model, not just the proof result.
This is the core insight that separates CAIGOs who build durable functions from those who spend their tenure re-pitching. The proof result answers "did it work here." The budget request has to answer "what does it produce at scale, who owns the outcome, and what happens if it does not." Those are governance questions, not technical ones.
Revenue Surface Coverage (RSC) is the fraction of an organization's identifiable AI-addressable revenue processes that have an active, funded AI initiative. RSC does not measure outcomes; it measures intentionality. An RSC of 12% means the organization has explicitly scoped and funded AI work on 12% of the surfaces where AI could plausibly affect revenue. The remaining 88% is unaddressed, whether by choice or by default. The CAIGO's budget ask should be framed as a proposed increase in RSC, not as a line-item cost.
The Mandate Gap is the distance between the organizational scope the CAIGO needs to deliver a defined RSC target and the organizational scope they actually control. A CAIGO with a growth mandate but no authority over revenue operations, marketing attribution, or sales tooling has a Mandate Gap: they are accountable for outcomes on surfaces they cannot reach. Closing the Mandate Gap requires either expanding the CAIGO's scope or explicitly removing surfaces from the RSC target. Boards that approve a budget without closing the Mandate Gap are funding accountability without authority, which is the primary structural cause of CAIGO churn.
Both terms give the budget conversation a vocabulary that the board can use without technical fluency. "We are proposing to increase Revenue Surface Coverage from 8% to 31% over 18 months" is a sentence a CFO can write into the board minutes. "We are asking for $500K to expand our AI program" is not.
The $500K threshold referenced in this series title is not arbitrary. It represents, in most mid-to-large enterprise organizations, the boundary between a budget that can be approved at the VP or C-suite level without a formal board vote and a budget that requires a board resolution or capital allocation committee sign-off. Below that threshold, the process is faster but the mandate is narrower. Above it, the process is slower but the mandate is more durable.
Sizing an AI growth budget involves four inputs, all of which should have been partially mapped during the first 90 days:
From the audit conducted in weeks one and two, the CAIGO should have a documented list of revenue-adjacent processes: customer acquisition, conversion, retention, expansion, contract value optimization, pricing, and similar. Each surface has an estimated annual revenue impact and an estimated AI addressability score (the fraction of the process that AI can plausibly affect given current model capability and data availability). The RSC calculation is straightforward: total addressable impact across all surfaces, divided by total impact of currently funded surfaces.
The 30-day proof initiative established a cost-per-result for one surface. That unit cost does not scale linearly to new surfaces, but it provides an anchor. If the proof on the sales forecasting surface cost $40K in staff time, vendor access, and infrastructure and moved a measurable needle, the board has a reference point for evaluating the cost of addressing three, five, or ten additional surfaces.
Before sizing the ask, the CAIGO must document the Mandate Gap explicitly. Which surfaces are within the current organizational scope? Which require cross-functional authority that does not yet exist? The budget ask should only cover surfaces within the addressable mandate, or it should explicitly include a budget line for the organizational change required to close the Mandate Gap.
How many surfaces does the organization want to address in the next 18 months? This is a strategic choice, not a technical one. A conservative board might approve three to five surfaces. An aggressive board might approve eight to twelve. The budget size follows from the velocity target, not the other way around. The CAIGO who walks in with a number and then justifies it is weaker than the CAIGO who walks in with a velocity menu and lets the board choose the ambition level.
A credible AI growth budget has four components. Presenting them as a single undifferentiated number is the most common mistake. The board will decompose the number anyway during the approval process; presenting the decomposition proactively signals operational maturity.
Talent (40-50% of budget): The CAIGO's own salary is part of this function's cost. So is any embedded growth engineering or data science capacity. This is the most durable line: talent costs persist and compound. Underfunding here is the single fastest way to produce a CAIGO who is accountable for outcomes they lack the capacity to achieve.
Infrastructure (20-30%): Model API access, vector database infrastructure, evaluation and observability tooling, and the integration layer that connects AI outputs to revenue systems. This is not IT budget; it is the operational substrate of the growth function. Organizations that try to route this through the IT procurement process will spend most of the budget cycle in vendor approval queues.
Initiatives (20-25%): The per-surface proof sprints and scale deployments. This is the most visible component and the one boards will scrutinize most closely. Each initiative should have a named surface, a pre-agreed success metric, and a decision point. The budget for this component is essentially a portfolio of 30-day proof investments, each of which either proceeds to scale or is closed.
Reserve (10-15%): The AI tooling landscape changes faster than a 12-month budget cycle. Model providers change pricing, capability thresholds shift, vendors pivot. A CAIGO without reserve budget is one pricing change away from being unable to deliver on commitments made at budget time. Boards that resist this line tend to be the ones who later question why AI budgets are chronically underspent despite missed outcomes.
Presenting the budget as a single number without decomposition invites the board to negotiate against the total. The common result is a negotiated reduction that preserves the visible components (headcount) and eliminates the invisible ones (reserve, infrastructure). The CAIGO then operates for 12 months with a mandate they cannot execute because the substrate was cut. Early warning signal: the CFO asks "what exactly does this cover" before you have finished presenting. Mitigation: decompose proactively, as shown above, and give percentage ranges for each component before the number is challenged.
Framing the budget ask around AI capabilities ("we want to build a RAG pipeline, deploy an agent layer, implement LLM evaluation") rather than revenue outcomes is the technical team's native language and the board's second language at best. The board approves budgets for outcomes, not capabilities. A budget ask framed as "this will increase our RSC from 8% to 31%, addressing five revenue surfaces, with a measurable outcome defined for each" is categorically more fundable than one framed as "this will allow us to build enterprise AI infrastructure." Both might be equally true. Only one gets approved.
Boards that approve AI budgets without a named accountable owner for each outcome tend to discover, at the quarterly review, that everyone responsible for AI outcomes is partially responsible and therefore no one is fully responsible. This is the Mandate Gap in its most costly form. The CAIGO must enter the budget conversation with a clear accountability map: which outcomes does the CAIGO own, which outcomes require cross-functional co-ownership, and what organizational change is required to make the co-ownership functional. Boards that see this level of operational clarity are substantially more likely to approve at the requested level.
A budget approved without a pre-agreed measurement cadence will be re-evaluated on whatever cadence the CFO prefers, which is usually "whenever someone questions the spend." The CAIGO should propose the measurement cadence at the time of budget approval: monthly RSC updates, quarterly board reviews tied to RSC milestones, and an 18-month checkpoint at which the RSC target is evaluated and the next planning cycle begins. This converts the AI growth function from a budget line that requires periodic justification into a function with a defined operating rhythm that the board can track without intervention.
The board slide for the AI growth budget ask has a specific sequence that is structurally different from a standard capital request. This sequence is derived from how boards evaluate investment-with-accountability rather than cost-with-justification.
One number: current Revenue Surface Coverage percentage. One sentence: what it means. One sentence: what the industry-leading organizations are targeting (directionally, not with a fabricated benchmark). This is the "where we are" slide, and it should take under 90 seconds to present.
One surface. One metric. Before and after. The 30-day proof result presented in its most compressed, defensible form. If the proof showed that the AI forecasting tool improved forecast accuracy by a measurable percentage against the prior two quarters' baseline, that is the slide. No caveats, no qualifications beyond what is structurally necessary. The board will ask questions; let them.
Three scenarios: conservative (two to three additional surfaces over 18 months, lower budget, lower RSC target), moderate (five to seven surfaces, moderate budget, moderate RSC target), aggressive (nine to twelve surfaces, full budget, full RSC target). Each scenario has a cost, a projected RSC, and a named set of surfaces. The board chooses the scenario; the CAIGO builds the plan. This is the most important structural choice in the entire budget conversation: it converts the board from a body that approves or rejects a number into a body that chooses a strategic ambition level.
Who owns what. CAIGO owns the RSC target. CFO owns the budget envelope. Board reviews RSC quarterly. Each surface initiative has a named cross-functional owner for the revenue outcome (not the CAIGO; the CAIGO coordinates, the revenue owner is accountable for the business result). This slide exists because the most common board objection to AI investment is "who is accountable if it does not work." This slide answers that question before it is asked.
Budget decomposition across the four components. Timeline. First 30-day milestone (the next proof sprint, already scoped). The only question left is which scenario the board chooses.
The 90-day audit reveals that AI spend is distributed across 14 vendor contracts with no central visibility and no defined success metrics for any of them. The proof initiative demonstrates that a single contract, an AI sales coaching tool, can be evaluated against a measurable quota attainment metric in 30 days. Result: a 9-point improvement in the metric for reps using the tool versus a control group. The budget ask: $380K to address five additional revenue surfaces over 18 months, framed as increasing RSC from 7% to 28%. The board approves the moderate scenario at $380K. The Mandate Gap is partially closed by adding revenue operations to the CAIGO's dotted-line scope.
The firm has no prior AI investment in revenue-adjacent processes. The proof initiative maps the client renewal process and demonstrates that AI-assisted proposal generation reduces proposal cycle time by a measurable margin, allowing the firm to pursue more renewals per quarter. The budget ask is structured as a velocity menu: conservative ($180K, two surfaces), moderate ($310K, five surfaces), aggressive ($520K, eight surfaces). The board chooses moderate. The accountability structure names the Chief Revenue Officer as the co-owner for revenue outcomes, with the CAIGO owning the AI surface coverage and measurement cadence. This prevents the CAIGO from being evaluated on revenue numbers they do not control.
Regulatory constraints mean that AI deployment on client-facing surfaces requires a compliance review cycle that adds eight to twelve weeks per surface. The budget ask explicitly accounts for this by including a compliance review budget line ($60K of the $420K total) and reducing the velocity target to three surfaces over 18 months rather than seven. The board approves because the realistic velocity target, with the compliance constraint modeled explicitly, is more credible than an aggressive target that would have stalled at the first regulatory review. The measurement cadence is adjusted to account for the extended deployment timeline: RSC milestones are defined at surface-scoped and surface-deployed stages, not just surface-measured.
The following objections appear in the majority of AI budget conversations. Knowing them in advance is not optional for a CAIGO seeking approval at the requested level.
Objection: "We already have an AI budget in IT." The AI Growth function is not IT. IT manages AI as infrastructure. The CAIGO manages AI as a revenue lever. These require different governance, different measurement, and different accountability. The correct response is not to fight for the budget against IT but to draw the boundary explicitly: IT owns the capability substrate, the CAIGO owns the revenue application layer. Both budgets are necessary; neither is redundant.
Objection: "Can we start smaller?" Yes, and the velocity menu already provides that option. The CAIGO who arrives with three scenarios preempts this objection by having already offered the conservative scenario. The question becomes "which of the three scenarios would you like to fund" rather than a negotiation from an undifferentiated number downward.
Objection: "What happens if it does not work?" The accountability structure and the measurement cadence answer this question. The 30-day proof cadence means that a surface that does not move its metric is identified and closed within 30 days, not at the annual review. The reserve budget exists to pivot. The board should be comfortable because the structure limits downside exposure at the surface level, not because the CAIGO claims the outcomes are guaranteed.
Objection: "How do we know the AI is causing the result?" This is the hardest objection and the most legitimate one. The answer is the methodology from the proof initiative: control groups where feasible, before-and-after baselines where not, and an explicit statement of the causal model. The CAIGO should not claim causation they cannot support; they should be explicit about what the methodology can and cannot establish and let the board evaluate the evidence accordingly. As noted in the AI ROI measurement literature, attribution is structurally difficult in complex revenue environments, and claiming certainty undermines credibility more than acknowledging the limitation does.
A CAIGO funded below the talent threshold will be accountable for RSC targets they cannot staff. The result is a function that demonstrates capability at the proof level and cannot scale, producing exactly the pattern it was hired to break.
AI growth work on shared IT infrastructure means waiting in ticket queues for model access, data pipeline changes, and deployment slots. The velocity target becomes structurally unachievable independent of the quality of the AI work itself.
Model pricing changes, vendor pivots, and capability thresholds shift faster than annual budget cycles. A CAIGO with no reserve budget will spend the back half of the fiscal year either stopping work or seeking emergency supplemental approval, both of which damage the function's credibility with the board.
Funding a CAIGO without closing the Mandate Gap creates accountability without authority. The function will be evaluated on outcomes across surfaces it does not control, and the board will conclude the function does not work when the actual problem is the governance design.
| Component | Build | Buy | Configure | Rationale |
|---|---|---|---|---|
| Model access layer | No | Yes (API) | Partially | Foundation model training is not competitive differentiation for most enterprises. API access with prompt and context configuration covers the majority of growth use cases. |
| Evaluation framework | Partially | No | Partially | The metrics that matter (forecast accuracy, proposal conversion, retention score) are business-specific. Evaluation tooling should be configured around these metrics, not adopted wholesale from a vendor framework. |
| Vector / retrieval layer | No | Yes (managed service) | Yes | Managed vector database infrastructure removes the maintenance burden from a function that should be focused on revenue surfaces, not infrastructure operations. |
| Revenue surface integrations | Yes | No | Partially | The integration between AI outputs and revenue systems (CRM, pricing engine, proposal tool) is where the growth work actually lives. This is not a commodity; it requires custom development specific to the organization's systems. |
| Measurement and reporting | No | No | Yes | Existing BI tooling, configured with the RSC framework's metrics, is sufficient for most CAIGO reporting needs. Building a custom AI dashboard is a distraction from the work itself. |
Take the proof initiative result and deploy it at full organizational scope. Establish the measurement cadence. Run the second proof sprint on the next surface. Deliver the first RSC update to the board.
Run proof sprints on two to three surfaces in parallel while scaling the first surface deployment. The CAIGO team is operating at full capacity. The board is receiving monthly RSC updates. The Mandate Gap is being actively closed through cross-functional ownership agreements.
By month six, the function should have at least three surfaces in production measurement. By month twelve, the RSC target for the conservative scenario should be achievable. The 18-month milestone is the evaluation point for the next budget cycle: the board evaluates RSC delivered against RSC committed and decides the next velocity scenario.
This framework compounds with the First 90 Days sequence. The 90-day audit produces the Revenue Surface Map. The proof initiative produces the defensible result and the unit economics. The budget request packages both into a board-facing ask. Organizations that skip the 90-day sequence and go directly to a budget ask without a proof result will typically be asked to produce one before the ask is evaluated. The sequence is not optional; it is the architecture of a durable budget conversation.
The AI governance and accountability structures referenced in this framework connect to the broader pattern of how enterprises build durable AI functions, covered in AI Governance for Executives. The budget ask is a governance moment as much as a financial one: the accountability structure and measurement cadence established here will define how the function operates for the next two to three years.