A group buys it. The platform or ML engineering lead usually chooses the product. The CTO, VP of Engineering or a business unit head owns the budget. Security, procurement and finance can each stop the deal. Innovation budgets fell from 25% to 7% of LLM spending (a16z, June 2025).
Which budget pays for AI infrastructure now?
Permanent budgets pay. In its 2025 survey of 100 CIOs across 15 industries, a16z found innovation budgets paid for 7% of LLM spending. A year earlier they paid for a quarter. Central IT and business unit budgets paid the rest.
The same CIOs expected their LLM spending to grow about 75% over the next year. A line item in an IT or business unit budget has an owner who must defend it. That owner wants a cost forecast, a security review and a name to call when the system fails.
Each layer of spend has a different owner. Menlo Ventures estimated 2025 enterprise infrastructure spending at $18 billion (Menlo Ventures, December 2025):
- Foundation model APIs: $12.5 billion. Usual owner: the CTO or a central AI team, often through a cloud contract.
- Model training infrastructure: $4.0 billion. Usual owner: the ML or research engineering lead.
- Data storage, retrieval and orchestration for AI: $1.5 billion. Usual owner: the data platform lead.
The owners are our reading of how these purchases run. Menlo's data covers spend only, so check the owner account by account.
Who sits in the buying group?
Plan for six roles. In a company of a few hundred people, one person can hold three of them. Two roles decide:
- Champion: a head of ML platform, staff engineer or director of AI engineering. They judge whether the product works on their workload. Give them a test on their own data with a pass mark.
- Economic buyer: the CTO, VP of Engineering or a business unit general manager. They decide whether to fund it. Give them cost per request now and after, at their volumes.
Four roles review:
- Security: the CISO, a security architect or an AI governance lead. Give them a data flow diagram, deployment options and the questionnaire.
- Procurement: give them standard terms, insurance and pricing that fits their contract types.
- Finance: a FinOps lead or finance partner. Give them usage caps, alerts and spend at two volume levels.
- User team lead: the head of the team that ships the AI feature. Confirm the launch date fits.
a16z reported that security was heavily emphasised in its CIO interviews. Security and cost had gained ground on accuracy as reasons to pick a model.
Most of the CIOs preferred usage-based pricing. Usage pricing moves with traffic, so it puts a finance reviewer in the room.
Who signs, and who can stop the deal?
The economic buyer signs, and any reviewer can stop it. A champion can carry a deal through the technical test and still lose it at security or procurement, often months later. On the first call, ask who signed the last contract of this size. Ask what stopped the last one that failed.
Switching costs make buyers careful. a16z found that agentic workflows made it harder to change models, and a switch could take a lot of engineering time. Buyers know your product will be hard to remove, so they review it more.
Does the buyer change outside the engineering team?
Yes. Indeed Hiring Lab counted 822 US job titles touched by AI in the first quarter of 2026 (Indeed Hiring Lab, July 2026). That was 8.3% of all titles, up from 264 in the first quarter of 2022. Of those titles, 63% sat outside tech occupations.
The user team often sits in operations, support, marketing or finance, while engineering runs the system. When a business unit pays, its general manager is the economic buyer and the platform team is a technical reviewer. Map both before you write the proposal.
How do you find the right names at an account?
Start from the system, then find the people. Read the company's engineering blog, conference talks and job posts to learn which team runs its models and data pipelines. Then find that team's leaders.
Check every title before you write. Contact databases attach titles to the wrong company.
In what order should you contact the group?
Contact them in the order the deal will need them:
- Champion first. Confirm the workload, the metric and the pain, in their numbers.
- Economic buyer second, through the champion, with a cost case at the buyer's volume.
- Security third, and early. Send the questionnaire and data flow before the technical test ends.
- Finance with the proposal. Bring the usage model and the caps.
- Procurement last, with standard terms ready, so legal review runs alongside the final test.
Give each extra contact a reason tied to their role. A copy of the champion's email does not count. To price meetings with these buyers, read how much to pay per qualified meeting.
A decision rule for multi-threading
Before you send a proposal, name one person for each of the six roles. If a role does not apply at this account, write down why. If you cannot name the economic buyer and the security reviewer, forecast the deal as a pilot.
To see the buyers at your top accounts, start with five named buyers, free.