From AI Spend to AI Budget: Building Your FY27 Number Live
Aleph FP&A
19 views
To build a defensible FY27 AI budget, start from actual spend by vendor, split it by department, and forecast each driver separately. Seats scale with headcount, while coding overage and API usage scale with volume. A flat percentage bump on last year won't survive a CEO or board review.
👉 See how Aleph builds driver-based forecasts right in your spreadsheet: https://getaleph.com/demo
Finance teams are being asked for an AI number for FY27, but the category barely existed in past budgets and there's no benchmark to anchor to. In this fireside chat, Andy Woods of DualEntry shares aggregated data on what companies actually spent on AI over the last twelve months. Median monthly AI spend grew 30x over two years. The median company spends about $39 per employee per month. Anthropic now leads vendor share, with Cursor and ChatGPT spend rising fast.
Sebastian Kontarovsky of Aleph then builds the FY27 number live in a spreadsheet. He reconciles bulk ERP spend to vendor usage exports (Claude, ChatGPT, Cursor), maps users to departments with roster data, and breaks each department into assistant seats, coding seats, coding overage, and internal vs. production API usage. Then he layers in headcount plans, adoption assumptions, and an experimentation reserve. The session also covers tying department AI spend to ROI metrics like CAC, where API usage belongs (COGS vs. CapEx), and which AI contract types companies are signing.
FEATURING
Andy Woods — Head of Product, DualEntry
Sebastian Kontarovsky — Head of Solutions, Aleph
WHAT YOU'LL LEARN
How much do companies spend on AI per employee, and how does it vary by company size?
Which AI vendors take the largest share of company AI spend?
How do you build a driver-based AI budget instead of a percentage bump on last year?
Which AI costs scale with headcount (seats) and which scale with usage (API, coding overage)?
How do you reconcile AI spend from your ERP to individual users and departments?
Should AI API usage be booked as COGS or CapEx?
How do you tie departmental AI spend to ROI, and why productivity metrics like lines of code mislead?
Should you sign pay-as-you-go, annual, or committed-spend AI contracts?
─────────────
Book a demo: https://getaleph.com/demo
Learn more: https://getaleph.com
Aleph is an AI-native FP&A platform that connects to your source systems and adds a semantic context layer — so finance teams can analyze, report, and plan without leaving their spreadsheet.
#FPandA #FinanceAI #AIforFinance #CFO #FinancialPlanning #UsageBasedPricing #FY27Budget
From AI Spend to AI Budget: Building Your FY27 Number Live
Aleph FP&A
19 views
To build a defensible FY27 AI budget, start from actual spend by vendor, split it by department, and forecast each driver separately. Seats scale with headcount, while coding overage and API usage scale with volume. A flat percentage bump on last year won't survive a CEO or board review.
👉 See how Aleph builds driver-based forecasts right in your spreadsheet: https://getaleph.com/demo
Finance teams are being asked for an AI number for FY27, but the category barely existed in past budgets and there's no benchmark to anchor to. In this fireside chat, Andy Woods of DualEntry shares aggregated data on what companies actually spent on AI over the last twelve months. Median monthly AI spend grew 30x over two years. The median company spends about $39 per employee per month. Anthropic now leads vendor share, with Cursor and ChatGPT spend rising fast.
Sebastian Kontarovsky of Aleph then builds the FY27 number live in a spreadsheet. He reconciles bulk ERP spend to vendor usage exports (Claude, ChatGPT, Cursor), maps users to departments with roster data, and breaks each department into assistant seats, coding seats, coding overage, and internal vs. production API usage. Then he layers in headcount plans, adoption assumptions, and an experimentation reserve. The session also covers tying department AI spend to ROI metrics like CAC, where API usage belongs (COGS vs. CapEx), and which AI contract types companies are signing.
FEATURING
Andy Woods — Head of Product, DualEntry
Sebastian Kontarovsky — Head of Solutions, Aleph
WHAT YOU'LL LEARN
How much do companies spend on AI per employee, and how does it vary by company size?
Which AI vendors take the largest share of company AI spend?
How do you build a driver-based AI budget instead of a percentage bump on last year?
Which AI costs scale with headcount (seats) and which scale with usage (API, coding overage)?
How do you reconcile AI spend from your ERP to individual users and departments?
Should AI API usage be booked as COGS or CapEx?
How do you tie departmental AI spend to ROI, and why productivity metrics like lines of code mislead?
Should you sign pay-as-you-go, annual, or committed-spend AI contracts?
─────────────
Book a demo: https://getaleph.com/demo
Learn more: https://getaleph.com
Aleph is an AI-native FP&A platform that connects to your source systems and adds a semantic context layer — so finance teams can analyze, report, and plan without leaving their spreadsheet.
#FPandA #FinanceAI #AIforFinance #CFO #FinancialPlanning #UsageBasedPricing #FY27Budget