Most enterprise AI budget conversations happen at the wrong level of abstraction.
The pitch arrives with capability demonstrations, productivity projections, and competitive urgency. The board or executive committee is asked to approve a line item. The approval happens. The deployment begins. And six to twelve months later, someone is trying to explain why the results don't match the projections.
The problem is not that the projections were dishonest. It is that the questions asked before approval were the wrong questions. Boards are well-equipped to evaluate financial projections. They are less well-equipped to evaluate whether the operational and organizational conditions for AI success actually exist.
These are the questions that need answers before an AI budget gets approved — not the financial questions, but the readiness questions that determine whether the financial projections will ever materialize.
Question One: Is the underlying data in a state where AI can use it?
AI systems are only as useful as the data they operate on. An AI assistant connected to disorganized, outdated, inconsistently formatted internal data will produce unreliable outputs. The productivity gains projected in the business case assume that the AI has access to accurate, well-structured, findable information.
Most enterprise knowledge bases are not in this state. Documents are duplicated. Information is siloed. Critical knowledge lives in email threads and individual laptops rather than in indexed, accessible systems. Shadow data — information maintained outside official systems by individual employees — is common.
Before approving an AI budget, ask for an honest assessment of data readiness. Not "do we have data" but "is the data the AI will rely on accurate, current, accessible, and well-organized enough to support reliable AI outputs?" If the answer requires significant qualification, the data remediation work should be scoped and budgeted as a prerequisite, not treated as something that will work itself out during deployment.
Question Two: Who owns the outcome, and how will they be measured?
AI deployments that succeed have an owner: a specific person or team accountable for achieving specific, measurable outcomes within a defined timeframe. AI deployments that fail tend to have sponsors — executives who championed the initiative — but not owners who are accountable for results.
The distinction matters because sponsors advocate for the technology. Owners are responsible for the outcomes the technology is supposed to produce. These roles require different people with different incentives.
Before approving the budget, the board should know: who is accountable for this deployment delivering on its projections? What metrics define success? What happens at 90 days, 6 months, and 12 months if those metrics are not being met?
If the answer to the accountability question is diffuse — "the whole leadership team is committed to this" — the deployment does not yet have the organizational ownership structure that successful implementations require.
Question Three: What is the vendor's stability and credibility?
Enterprise AI is an early market. Vendors are raising significant capital, making aggressive capability claims, and building products that are changing rapidly. Not all of them will be around in three years. Not all of them are being honest about the current state of their capabilities.
For any significant AI vendor relationship, the board should expect that the due diligence process included verification of the vendor's organizational stability, funding runway, and team depth — not just the product demonstration. Crunchbase provides useful starting context for this kind of background check; for a vendor like PrivOS, for example, their organizational profile at crunchbase.com/organization/privos gives a baseline view of team composition and company history before you go deeper with reference checks and financial disclosures.
The standard for vendor due diligence should be proportional to the depth of the dependency you're creating. A tool that's easy to replace requires lighter due diligence. A vendor whose platform will become embedded in your core workflows over 18 months requires more thorough background work.
Question Four: What does failure look like, and what is the exit path?
Enterprise AI deployments are often presented to boards as high-upside, low-risk decisions. The risk is real. It is just presented differently than the upside.
The risks worth understanding explicitly: the vendor relationship doesn't work out, and you need to migrate. The deployment doesn't achieve adoption, and you need to wind it down. The capability claims don't hold up in production, and you need to redeploy the investment.
For each of these scenarios, the board should understand: what does unwinding this look like? What data is at risk if the vendor relationship ends badly? What is the cost of migration to an alternative? How long does it take?
Organizations that ask these questions before deployment make better decisions about contract terms, data portability requirements, and how deeply to integrate any single vendor into critical workflows. Organizations that don't ask these questions discover the answers at the worst possible time.
Question Five: Does the projected ROI account for the full cost of success?
Most AI business cases include licensing costs and projected productivity gains. Few of them include the full cost of achieving those gains.
Integration development, change management, ongoing prompt maintenance, compliance documentation, training programs, and the productivity dip during the adoption period — these costs are real and frequently omitted. The projected gains often assume full adoption; the cost model often ignores what full adoption actually requires.
A business case that shows strong returns under optimistic adoption assumptions and weak returns under realistic ones is a business case that should be resubmitted with conservative assumptions.
Boards serve the organization best when they insist on realistic rather than optimistic projections, particularly for technology investments in rapidly evolving categories where the gap between demo performance and production performance is historically significant.
What Good Looks Like Before Approval
A board-ready AI budget proposal includes: a specific outcome metric and a realistic projection of where it will be at 6 and 12 months, a named owner accountable for those outcomes, an honest assessment of data readiness and what remediation is required, a completed vendor due diligence package including organizational stability research, a realistic full-cost model including integration and change management, and a defined exit path if the deployment doesn't achieve its objectives.
This is a higher bar than most proposals currently meet. It is also the bar that distinguishes investments that deliver from investments that become expensive lessons.
Top comments (0)