Not the strategy deck. Not the all-hands slide. The real sequence an AI and Growth Officer runs in the first quarter to prove the function's value before the next board cycle.
You have just been appointed AI and Growth Officer. Or your organization has decided to create the role for the first time. Or you are advising a company that has one and wants to know if they are doing the job correctly.
The first 90 days are the highest-stakes window in the role. They determine whether AI becomes a strategic growth lever embedded in how the company competes, or another initiative that consumes budget and reports to a steering committee that reports to another steering committee.
Most first-90-day plans for this role are strategic documents: framework slides, operating model diagrams, governance charters. This post is not that. It is the operational sequence : the specific moves, in order, that a world-class AI and Growth Officer executes in the first quarter.
The Chief AI and Growth Officer (CAIGO) is the executive responsible for translating AI capability into measurable revenue and competitive advantage. Unlike a Chief AI Officer focused primarily on governance and risk, or a Chief Digital Officer focused on infrastructure, the CAIGO owns the connection between AI investment and growth outcomes. The role exists because that connection rarely happens without someone accountable for it.
There is a structural reason the first quarter matters disproportionately: it is the only window in which the AI and Growth Officer can audit, reset, and sequence before they own the results. After 90 days, everything that exists is yours. The vendor contracts that looked questionable on day one are now your responsibility. The pilot program that has been running for 18 months without a defined success metric is now your problem to solve in public.
The first 90 days are also the window in which the CAIGO establishes the terms on which their function will be evaluated. If you do not define those terms, the organization will define them for you, usually as a cost question: "How much are we spending on AI, and what are we getting back?"
The answer to that question, answered on the organization's terms rather than yours, is almost always unflattering : not because AI programs fail to generate value, but because the value is rarely measured in the language the organization uses to evaluate investments.
This is not an argument about whether AI creates value. It is an argument about who controls the narrative of whether it creates value. The CAIGO who waits for the organization to measure the function will be measured against the wrong things. The CAIGO who defines the measurement framework in the first 90 days controls the conversation for the next three years.
The first 90 days are not a planning phase. They are an execution phase with a specific sequence. Each move creates the conditions for the next. Doing them out of order is the most common failure pattern in this role.
Before anything else, the CAIGO needs to know what the organization is already spending on AI, what those investments are supposed to produce, and whether anyone is currently measuring whether they produce it. This is not a budget review. It is a signal detection exercise.
In practice, this means gathering every AI-related contract, pilot, internal tool, and vendor agreement across the organization, not just the ones that report through your function. At most mid-to-large enterprises, AI spend is distributed across departments, often without central visibility. Marketing has an AI content tool. Sales has an AI forecasting add-on. IT has three separate AI security products. Legal has a contract review tool from a vendor who may or may not still be operating. Finance has an AI anomaly detection layer in the ERP that no one has reviewed since implementation.
The audit produces three outputs:
The audit is not primarily about finding waste, though it often surfaces waste. It is about establishing a baseline. You cannot demonstrate that the AI function is generating growth if you do not know what growth baselines looked like before the function existed.
The second move is the one that distinguishes the AI and Growth Officer from a Chief AI Officer whose mandate is primarily governance. The CAIGO's job is not to manage AI risk : it is to find the places where AI creates durable competitive advantage and sequence them for execution.
A revenue surface is a place in the business where AI capability, if applied correctly, creates a structural improvement in revenue generation, retention, pricing power, or competitive moat. Revenue surfaces are different from cost reduction opportunities. Cost reduction is real and valuable, but it is not the CAIGO's primary job. The CFO can find cost reduction opportunities. The CAIGO finds the places where AI makes the business structurally more valuable.
A revenue surface is a point in the customer or competitive cycle where AI capability, applied with sufficient precision and reliability, creates a measurable and durable improvement in the organization's ability to generate, retain, or expand revenue. Revenue surfaces have three properties: they are specific (a named business process or decision, not a broad domain), they are measurable (a metric that moves when the surface is addressed), and they are defensible (the improvement compounds over time rather than being immediately replicable by a competitor).
In practice, identifying revenue surfaces requires a structured set of conversations across the business, not a technology audit. The questions are:
These conversations are not technology conversations. They are business conversations. The CAIGO who walks into them as a technologist asking "where can we use AI?" gets a very different (and less useful) answer than the CAIGO who walks in as a growth strategist asking "where is revenue leaking, and what information would stop the leak?"
The third move is the one that either validates the first 90 days or reveals that the audit and mapping were incomplete. By day 61, the CAIGO has a baseline (what AI spend exists and whether it is producing outcomes) and a surface map (where AI could create growth leverage). The third move is to select one initiative, narrow enough to complete in 30 days, and execute it well enough that the result is unambiguous.
The proof initiative is not a pilot in the traditional enterprise sense : an 18-month proof of concept with a steering committee and quarterly review gates. It is a 30-day execution sprint with a single, pre-agreed success metric and a decision point at the end: either the metric moved and the next initiative gets funded, or it did not move and the methodology gets revised.
Selecting the right proof initiative is a constraint satisfaction problem. The initiative must meet all of the following criteria simultaneously:
The most common mistake in selecting a proof initiative is optimizing for strategic importance rather than executability. The most strategically important AI initiative in the organization may be the hardest to execute and the hardest to measure. The CAIGO who spends the first 90 days pursuing it correctly may have no credible result to show. The CAIGO who selects a narrower, more certain initiative and executes it cleanly walks into the 90-day review with a metric that moved. Credibility is a prerequisite for influence, and influence is what funds the strategic initiatives.
The 90-day review is not a status report. It is a funding decision. The CAIGO walks in with three things: the baseline (what AI spend existed and what it was producing), the surface map (where growth leverage was identified), and the proof result (what happened when one of those surfaces was addressed).
If the proof initiative succeeded, the review is straightforward: this is the surface we addressed, this is the metric that moved, here is the methodology we will apply to the next three surfaces, here is the budget we need. The board is being asked to fund a known methodology applied to new surfaces, not a speculative new capability.
If the proof initiative did not succeed, the review is a different conversation. The CAIGO presents the result honestly, presents the diagnostic of what prevented success, and presents a revised surface selection and methodology. The 90-day review that shows a failed proof initiative and a credible analysis of why it failed is substantially more valuable than the 90-day review that shows a collection of pilots with inconclusive results.
Avoid presenting a portfolio of early-stage pilots with no measurable outcomes. This is the default output of a first-90-day plan that was organized as a planning exercise rather than an execution sequence. A board seeing ten pilots in progress, none with a result, does not conclude that progress is being made. It concludes that the function has not yet demonstrated the ability to close.
A 600-person SaaS company has 11 AI vendor contracts across sales, marketing, and customer success. None has a defined revenue metric. The new CAIGO runs the audit in week two and discovers that the largest contract, an AI sales forecasting tool, has no defined success metric and no before/after comparison. The proof initiative: define a forecast accuracy baseline against the prior two quarters, run the AI tool against the next quarter, measure deviation. Result either validates the $340K annual contract or creates the evidence needed to renegotiate or cancel it.
A regional bank has a Chief AI Officer focused on risk and compliance. The board asks for an AI and Growth Officer to complement that function and identify where AI can expand fee income without increasing regulatory exposure. The first 30-day audit reveals that three revenue surfaces exist in the wealth management division: client portfolio review frequency, product recommendation relevance, and advisor scheduling efficiency. The proof initiative targets advisor scheduling, where an AI-assisted scheduling tool reduces average time-to-meeting by a measurable amount. The metric is a pre-existing operational KPI, so the result cannot be contested.
A manufacturer has invested substantially in AI for quality control and predictive maintenance. The CTO wants to extend AI into pricing and supply chain but lacks a methodology for sequencing the investments. The CAIGO's first 60 days are entirely diagnostic: mapping where AI spend already exists, identifying which surface to address first, and building the case that pricing intelligence has a measurable revenue surface that can be addressed before the supply chain work requires a full data infrastructure overhaul. The proof initiative is a pricing signal analysis on a single product line, using data that already exists in the ERP.
Use this scoring framework to select the proof initiative at the end of the 30-to-60-day mapping phase. Score each candidate initiative on four criteria, each on a scale of one to three. Select the initiative with the highest total score, not the highest strategic appeal.
| Criterion | Score 1 | Score 2 | Score 3 | Why it matters |
|---|---|---|---|---|
| Executability | Requires new infrastructure or vendor contract | Requires configuration of existing tools | Uses data and systems already in place | A 30-day sprint cannot survive a dependency on a six-week procurement cycle |
| Measurability | Metric does not yet exist; must be created | Metric exists but has no historical baseline | Metric exists with at least two quarters of history | A result against a pre-existing metric cannot be contested; a result against a new metric can always be questioned |
| Visibility | Metric is not visible to board or CEO | Metric is visible to one C-suite member | Metric appears in board-level reporting | The proof initiative must produce a result that the person controlling the budget considers meaningful |
| Probability of success | Outcome is genuinely uncertain; novel application | Similar applications have worked elsewhere | This specific approach has worked at this organization in a related context | The CAIGO's credibility is on the line; first initiative should be high-probability |
An initiative scoring 10 to 12 is the right proof initiative. An initiative scoring 7 to 9 is a second-priority candidate. An initiative scoring below 7 belongs in the second quarter, not the first.
The CAIGO's first 90 days are almost never the right time to build new AI capability. The audit and mapping phases are diagnostic. The proof initiative should be executed with what already exists in the organization, configured for a specific purpose, not with new tooling that adds procurement, integration, and operational risk to an already time-constrained sprint.
| Component | Recommendation (First 90 Days) | Rationale |
|---|---|---|
| Data infrastructure | Use what exists | A data infrastructure project cannot close in 30 days; building one in parallel adds risk to the proof initiative without adding value |
| AI model or system | Configure existing vendor tools or internal models | Fine-tuning or prompt-engineering an existing system is weeks; building and evaluating a new model is months |
| Measurement tooling | Use existing analytics stack | The proof initiative requires a pre-existing metric; the tooling to read that metric is already in place |
| Process integration | Minimum viable integration only | Full process integration is a second-quarter workstream; the proof initiative needs enough integration to affect the metric, not enough to scale |
| Risk | Early Signal | Mitigation |
|---|---|---|
| Stakeholder resistance to audit | Department heads slow-walking data sharing or vendor contract access | Secure executive sponsor commitment before day one that audit access is not optional; frame as organizational intelligence, not performance review |
| No pre-existing baseline for proof initiative | The metric you want to move has no historical data | Select a different proof initiative with an existing baseline; creating a new metric to measure is a second-quarter activity |
| Proof initiative selected for strategy, not executability | The initiative requires a vendor negotiation, a data pipeline build, or an integration with a system that has a long lead time | Run the four-criterion scoring framework and select the highest-scoring initiative, not the most strategically appealing one |
| Board expectation mismatch | The board expects a portfolio update at 90 days, not a single result | Align at day one on what the 90-day review will contain; a single clear result with clear methodology is more valuable than a portfolio of inconclusive pilots |
| Function conflated with IT or Data Science | The CAIGO is pulled into infrastructure decisions, model evaluation, or vendor selection outside the growth mandate | Establish at day one that the AI and Growth function owns the connection between AI capability and revenue outcomes, not the capability itself; the capability is owned by IT, Engineering, or Data Science |
If you are building the organizational case for this role, Do I Need a Chief AI Officer? covers the structural decision between governance-focused and growth-focused AI leadership. For the hiring question, How to Hire a Chief AI Officer addresses what the role actually requires versus what job descriptions typically ask for. The Chief AI Officer Playbook covers the broader operating model once the 90-day foundation is in place.