What does AI-first transformation cost?
The lines behind an operational AI program budget: partner fee, your own hours, ERP work, security review, run costs. With a labeled 36-month scenario.
A CFO who asks what this costs rarely wants a price list. You want to know which lines make up the total, which of them you control, and whether the number will hold up in the approval paper. This article covers cost only. Whether the program pays back is a separate model, covered in the business case article, and it should stay out of the cost view.
The short answer
Sembium does not publish a price. Scope and investment are set after the call and sized against a bottleneck worth $1M or more. The number itself comes from a costed statement of work, once the baseline and the systems involved are understood.
The more useful answer is structural. The fee paid to an implementation partner is usually only part of what a transformation costs you. If you plan the budget as “the partner’s number”, you will be surprised twice, once during delivery and once when run costs arrive.
What an operational transformation actually buys
Sembium sells whole-operation programs: the people, process, decisions, information, systems, exceptions, adoption and measurement of one operating domain. Known paths are handled by deterministic rules. AI is used where interpretation helps, for example reading an unstructured document or classifying a free-text reason. Accountable humans keep consequential decisions. A pilot proves one hard stage inside the funded program; it is not the product.
That scope explains the cost shape. Most of the effort is not model usage. It is understanding how work really flows, redesigning it, connecting systems that were never designed to talk to each other, handling the exceptions that make up the long tail, and getting people to work differently.
Cost drivers, in the order a CFO will meet them
1. The program fee. Specialist time for diagnosis and baseline, process and control redesign, rules and AI design, integration, evaluation and handover. Sembium is founder-led: Andy de Wit leads every program, and specialists are assembled and committed per engagement before delivery promises are made. Fee drivers are the number of systems and teams crossed, the exception variety, the data quality you start with, and the acceptance evidence your security and finance functions require.
2. Your own labor. Process owners, finance and operations experts, IT, security and the people who will review exceptions all spend time. This line is real money even when it never appears on an invoice. It is also the line most often left out of a business case.
3. Work on your systems that is not part of the fee. ERP, CRM or billing changes sometimes have to be made by your incumbent vendor or internal IT. Connectors, API access, environments and test data may carry their own charges.
4. Security, privacy and procurement. Reviews, questionnaires, legal terms and sometimes third-party assessments. These cost calendar time and money in both organizations.
5. Adoption. Training, cutover support, temporary parallel running, and the dip in productivity that precedes the gain.
6. Software, cloud and model usage. Workflow tooling, document processing, hosting and model calls. Microsoft’s adoption guidance notes that access and licensing differ by AI solution and affect budgets and security controls, so the license picture should be mapped early. Usage costs are also the line you control through design: Microsoft’s agent guidance says structured, predictable tasks are better served by regular code, which is faster, cheaper and more reliable than an agent. Every step moved from a model to a rule lowers a recurring bill.
7. Ongoing ownership. Monitoring, evaluation, exception queues, updates when models or upstream systems change, and a named owner. This line recurs every year, which is why it dominates multi-year totals.
8. Contingency. Estimates made before a hard stage has been tested are uncertain. Microsoft’s planning guidance advises adding 20-30% contingency time to initial estimates and using proof-of-concept results to refine them. Note that Microsoft’s figure is about schedule time, not money. It is not a cost percentage, and this article does not present it as one. Treat contingency as an explicit line rather than hoping it will not be needed.
What firms say they are paying for
The ECB blog published on 2 October 2026, based on its survey of about 5,000 euro-area firms, reports that 72% of firms planning AI investment expect to use internal funds. Among the investment types listed, 49% plan to spend on AI technologies and tools, 46% on employee training, 40% on data infrastructure and 12% on hiring AI specialists. The blog reports no cost figures, so it supports a point about structure and not about price: tools are the largest category, but training and data are close behind and appear in almost as many plans. The same blog notes that external financing is more closely tied to tangible, collateralizable assets. For a CFO that matters: much of a transformation budget (labor, process change, adoption) is intangible and is therefore more likely to be funded from operating cash flow than from a facility secured on an asset.
A synthetic worked scenario
The scenario below is synthetic and illustrative. It describes no Sembium client, no quote and no typical price. It exists to show the structure of a total-cost view for a customer-to-cash program (contract and order, delivery evidence, billing, deductions and disputes, credit, collections) at a mid-sized B2B company.
Assumptions, all invented for illustration:
- Program fee: $320,000.
- Your labor: 1,500 hours at $65 loaded cost.
- Integration on your side: $45,000 of ERP and billing-system work by incumbent vendor or internal IT.
- Security, privacy and procurement review: $15,000.
- Training and cutover: 40 users x 8 hours x $60 = $19,200.
- Contingency: 15% of one-off costs. This is an illustrative assumption of ours for the cost line, not a sourced benchmark and not Microsoft’s 20-30%, which applies to time; adjust it to your own risk appetite.
- Recurring, per year: licenses $36,000; cloud and model usage $2,000 per month ($24,000); internal ownership 0.3 FTE ($30,000 loaded cost); external support $40,000.
- Recurring costs are counted for all three years, which is deliberately conservative because it ignores any ramp-up.
| Cost line | Type | Amount (USD) | Share of 36-month total |
|---|---|---|---|
| Program fee | One-off | 320,000 | 33.3% |
| Your labor (1,500 h x 65) | One-off | 97,500 | 10.1% |
| Integration on your systems | One-off | 45,000 | 4.7% |
| Security, privacy, procurement | One-off | 15,000 | 1.6% |
| Training and cutover | One-off | 19,200 | 2.0% |
| Contingency (15% of one-off) | One-off | 74,505 | 7.8% |
| Recurring run costs (3 x 130,000) | Recurring | 390,000 | 40.6% |
| Total over 36 months | 961,205 | 100% |
Shares are rounded. Cumulative cost on the same assumptions:
| Horizon | Cumulative cost (USD) |
|---|---|
| 12 months | 701,205 |
| 24 months | 831,205 |
| 36 months | 961,205 |
The program fee is a third of the three-year total. Run costs are the largest single block and are the line most often absent from the initial request for approval. If a proposal quotes only the fee, ask for the other six lines.
Alternatives belong in the same comparison
A fair cost view prices the alternatives with the same lines.
| Option | Where the cost sits | Typical blind spot |
|---|---|---|
| Do nothing | Continuing operating loss, hidden queue and rework labor | Looks free because nothing is invoiced |
| Configure what you already own | Licenses, internal or partner configuration time | Cross-system gaps and exceptions remain with people |
| Buy a packaged product | License, integration, process change | The product covers its own module, not the whole flow |
| Build internally | Hiring or reallocating engineers, ongoing ownership | Run costs and key-person dependence |
| Whole-operation program | Fee plus the six other lines above | Needs a baseline and a sponsor who can change the work |
Sembium’s view is that known, predictable steps should be handled by deterministic rules and existing platform features first. A program is justified where the problem crosses teams, systems and exceptions that no single product owns. Where it is not, the right outcome of the first conversation may be “configure what you have” or “no fit”.
How to make it financeable
- Stage the commitment. Each stage should name an accountable buyer, an artifact and a falsifiable go/no-go decision. A justified stop is a valid outcome. This lets finance release money against evidence rather than a single large approval.
- Separate the one-off from the recurring. One-off lines can be budgeted as a project. Recurring lines should be owned by the operating function that benefits.
- Show all lines, including yours. Internal time, backfill and vendor work outside the program belong in the approval paper.
- Agree the horizon first. Costs accumulate over 12, 24 and 36 months differently from value. Choose the horizon before comparing.
- Ask what is excluded. Travel, third-party assessments, data clean-up, regulatory advice and license growth are common exclusions.
What this does not prove
- The figures are invented. They do not show what your operation would cost, what any Sembium engagement costs, or what a market-typical program costs.
- The ECB data describe how euro-area firms plan to fund and categorize AI investment. They do not give a price for an implementation or for what Sembium would charge.
- A cost breakdown says nothing about whether the program is worth doing. That requires a baseline and a net value model over a stated horizon.
Next step
Got a bottleneck that costs you $1M or more, and you want it solved? Book the 30-minute bottleneck call. You leave with one practical recommendation and a clear answer on fit. No quote, and no confidential data needed.
Questions buyers ask
What does a Sembium program cost?
Sembium does not publish a price. Scope and investment are set after the call, in a costed statement of work, and sized against a bottleneck worth $1M or more.
Is the program fee the whole cost?
No. In the synthetic scenario below the fee is about a third of the 36-month total. Client labor, integration work on your systems, security review, adoption effort, licenses, cloud and model usage, and ongoing ownership make up the rest.
Can you tell me what my operation would cost?
Not honestly from a website, and not in a 30-minute call. The call can show which cost drivers dominate your case and whether the bottleneck is worth $1M or more to solve. A number comes from a costed scope after the baseline is understood.
Why not just buy a packaged product?
Sometimes you should. If a product configured inside your existing stack covers the process, that can be cheaper. A program earns its cost where the work crosses teams, systems and exceptions that no single product owns. Both options belong in the comparison.
Will the savings exceed the cost?
Sembium does not promise savings, returns or timelines. The value side is a separate model with its own assumptions; see the business case article.
Sources
Sources give context. Dates show when each was last checked.