What does a real AI programme cost?
A planning tool for the problem definition and solution exploration phase. Use it to frame the investment, align your internal group, and walk into vendor conversations with the right questions — before anyone has scoped anything.
AI Programme Cost Estimate
Four budget lines make up a complete AI programme. The sections below break each one down in detail — this card gives you the full picture at a glance.
Your Internal Team
The people you need in place — most drawn from existing headcount
Running an AI programme requires protected time from people who already have full-time jobs. These roles aren't new hires — with one exception — but they need real commitment, not a side-of-desk addition. The total time commitment across key roles is approximately ~70–100 person-days.
| Role | Commitment | What they need to do |
|---|---|---|
Executive Sponsor CEO, COO, or CIO | ~2 days/month Full programme duration | Champion the programme visibly at board level. Approve the programme announcement and key communications. Remove blockers. When the CEO mentions Claude in an all-hands, it does more for adoption than 50 training sessions. |
Programme Manager Internal counterpart to the programme director | 2–3 months full-time | Day-to-day coordination, internal navigation, and department scheduling. Your counterpart to the external Programme Director. Often the most underestimated resource requirement — this role needs protected time, not a side-of-desk commitment. |
IT / Security Lead Infrastructure and compliance | 3–4 weeks intensive, then ~1 day/month | Handles Claude Enterprise configuration, SSO setup, security controls, and data integration priorities during Phase 1. The Kowalah platform — including Discoveries, ICE-scored Opportunities, and Expert Requests — is also configured at this stage, giving your team a structured process for surfacing and prioritising AI use cases from day one. Light-touch involvement after setup — roughly one day per month. |
Internal Comms Your existing comms team | ~2–3 days/week during rollout | Distributes programme communications through your established channels. The external programme team writes the content, messaging framework, and key announcements — your team handles distribution, localisation, and internal channel management. |
Department Heads est. 6–10 people | ~1 day each | Each receives a briefing before their team is activated and provides input into workflow mapping. No sustained involvement required — just availability for a half-day each, spaced across the programme. |
Claude Guides — your most important internal asset
5–10% of your workforce, recruited from within. These are not teachers — they are facilitators. Their job is to notice when a colleague is struggling with a task where Claude could help, guide them to the right setup, and follow up 48 hours later. Guide training takes 1 day. Ongoing commitment is roughly 2 hours per week during rollout. Recruited on curiosity and influence — technical skill is not a prerequisite.
@Kowalah to surface use case ideas, submit expert requests, and get contextual guidance without leaving their day-to-day workflow. No new tools to learn, no separate login.AI Builder — the emerging internal role
As your programme matures from basic adoption into agent-powered workflows, you need someone who sits between IT and the business. Not a developer. Not a trainer. Someone who can translate business processes into the structured context agents need to do real work — and redesign workflows for a world where humans and agents share tasks.
- Connect agents to your data — set up secure integrations across legacy and modern systems so agents have the context they need
- Design human + agent workflows — map where agents take over, where humans step in, and who is accountable for what
- Manage access controls and monitoring — ensure agents operate within the right entitlements, and that you can see and audit what they do
- Build evals — create the tests that tell you whether your agents are doing what you intended
- Keep up with the architecture — the agent landscape is changing faster than any other area of enterprise technology. Someone needs to own this as their full-time job.
This role doesn't exist yet in most HR job libraries. You will likely need to define it from scratch — or second a technically curious operator from within your business.
Kowalah Change Enablement
A structured, one-off programme to take your organisation from pre-AI to post-AI
Programme phases
External programme team
The roles included in the programme cost. The team scales to your organisation size.
| Role | Commitment | Focus |
|---|---|---|
Programme Director | Full-time for programme duration | Owns the executive sponsor relationship, AI Operating Model, and programme-level decisions. In early-stage programmes, typically the most senior person on the account. |
Claude Specialists (1–2) | 1–2 specialists, full-time Phases 1–3 | Each specialist owns a cluster of departments — building their Claude Projects, prompt templates, Skills, and custom workflows. Scales with the number of departments in scope. |
Technical Lead | 3 weeks intensive (Phase 1), then advisory | Claude Enterprise configuration, SSO, security controls, and data integrations. Heaviest involvement during Phase 1 setup — mostly done once the infrastructure is live. |
Change Lead | Full-time | Owns adoption — programme communications, department head briefings, resistance management, and monitoring uptake across the rollout. |
Enablement Leads (2) | 2 leads, full-time during Phases 2–3 | Design and deliver foundation training; train, certify, and quality-control subcontracted facilitators. Set the quality bar for all delivery. |
Domain Coaches | 2–3 days/month per executive | 4–6 coaches, each matched by functional domain — a former CFO for the CFO, former CHRO for the CHRO. White-glove one-to-one coaching, not generic AI training. |
Facilitators | 3–5 people, full-time during rollout | Deliver foundation training sessions. Certified by Enablement Leads before delivery. Scaled to the rollout schedule. |
AI Platform Licensing
What you'll pay Anthropic directly — separate from professional services
Claude Enterprise uses a two-part billing model: a base seat charge for all users, plus consumption-based usage on top. The more your people use Claude, the higher the usage charges — but unlike traditional SaaS, you're not paying for unused seats at a premium rate. Anthropic bills self-serve Enterprise in USD; sales-assisted plans can accommodate other currencies. Figures here convert with the currency selector above for reference, but Anthropic's source-of-truth pricing remains in USD.
Cost by user type
Anthropic's current Enterprise plan uses a single unified seat type that includes Chat, Cowork, and Claude Code. The split below is a planning view of how usage actually varies by user behaviour — what you'll spend in practice — not a description of Anthropic's billing model.
| User type | Base seat | Typical consumption | All-in monthly | Who this covers |
|---|---|---|---|---|
| Chat / Cowork user | $20 | ~$23 | ~$43 | Most employees — daily Claude use for writing, research, analysis |
| Claude Code / builder | $20 | ~$100 | ~$120 | Developers and AI Builders using agentic coding tools |
| Your blended estimate | $20 | $25–$45 | $45–$65 | Assumes 85% Chat users, 15% builders/power users |
For your organisation
Pricing is negotiated directly with Anthropic — there is no public rate card. For an accurate quote, contact Anthropic's enterprise sales team or read how Enterprise billing works ↗.
Ongoing Managed Services
A recurring cost line most organisations underestimate — or forget to budget for entirely
The change programme builds the foundation. What comes next is less predictable but just as real: every department will surface ideas they want to act on, new starters will need onboarding into AI workflows, and the technology itself will keep evolving. Your internal IT team will be focused on what it should be — keeping infrastructure running, managing internal systems, maintaining the operational baseline. That work doesn't stop, and it leaves little bandwidth for ongoing AI development at the frontier.
Budget for some form of ongoing external AI support. The specific shape will depend on your pace and ambition, but the organisations that sustain AI impact treat it as a capability to keep investing in — not a project to close.
What this typically covers
Ongoing AI support is usually delivered through a quota of Expert Requests — structured asks your team raises when they have something to build or a problem to solve. Common examples include:
- Building a Claude skill or automated workflow for a specific team or process
- Running targeted training sessions as new departments come on board
- On-site office hours — your people bring real problems, an expert works through them live
- Joining client-facing sessions to help co-design AI-powered services
- Regular coaching for your internal AI lead or Guide champion network
- Strategic reviews, department audits, and roadmap planning as the programme matures
Indicative cost by tier
Figures are indicative. Actual scope and cost depend on pace of deployment, team size, and how actively your organisation builds on the initial programme foundation.
The Business Case
Where hard returns come from — and how to measure them
The organisations seeing real AI returns are tracking growth they couldn't have achieved otherwise — not just hours saved. According to Wharton's 2025 enterprise AI research, 46% of enterprises now formally track AI profitability. The three value levers below are where those returns typically show up: growth first, then cost.
Budget benchmarks and ROI measurement data: Wharton Human-AI Research & GBK Collective, Accountable Acceleration: Gen AI Fast-Tracks into the Enterprise, October 2025.
A planning tool, not a proposal
The figures in this tool are indicative ranges based on typical programme parameters for organisations of your size. We haven't spoken to you, we haven't scoped your requirements, and nothing here constitutes a quote — from Kowalah or from Anthropic.
AI programme costs vary significantly based on your specific situation, what's already in place, and how ambitiously you want to move. The numbers here are a starting point for an internal conversation, not a number to put in a budget.
Share it with your buying group — CEO, CFO, CIO — before anyone has formed a strong view. It's most useful when it opens up the conversation, not closes it.
- Frame the four budget lines before vendor meetings
- Align your internal group on realistic scale and investment shape
- Prepare the questions that matter before scoping begins
- Identify which value lever is most material to your business case
When you're ready for actual numbers, speak to our team ↗
Take this to your team
Download a clean version of this estimate to share internally, or copy a link that opens this exact configuration for your buying group. No forms. No follow-up unless you want it.
The share link saves your selections so colleagues open the calculator with the same configuration you've set.
Indicative estimates based on typical programme parameters. Actual costs and timelines vary based on detailed scoping, organisational complexity, and specific delivery requirements. Professional services figures are exclusive of VAT. AI platform licensing is billed directly by Anthropic in USD at base seat rates plus consumption — figures are indicative. Managed services figures assume a post-programme ongoing retainer. Business case figures (Section 5) are illustrative ranges based on stated assumptions — not projections. Budget benchmarks referenced from: Wharton Human-AI Research & GBK Collective, Accountable Acceleration, October 2025.