WM Signal Enterprise
Large Australian operators must cut non-core AI experiments before they consume integration capacity needed for core platform upgrades.
Enterprise teams are running multiple AI proofs while core ERP and customer platforms require major integration work. Resource contention is already visible in delayed release trains. Continuing without explicit prioritisation will extend upgrade timelines by at least one quarter.
01 · What matters
-
AI experiments drawing from the same integration teams as core upgrades
creates contention that delays revenue-critical platform work
-
Operating models still organised around project rather than product teams
slows decisions on which AI components survive into production
-
Legacy vendor contracts limit data access for new models
increases cost of any AI that touches customer or financial records
Hard call · this week
halt non-core AI experiments and reallocate integration capacity to core platform work
Watch · weak signal
release train delays exceeding two weeks
If true indicates integration capacity is already over-subscribed
Do not
- add new AI use cases without integration capacity audit
- leave AI experiments without explicit kill criteria
Questions for the room
- Which AI experiments share integration resources with the ERP upgrade?
- What operating model change is required to run AI as a product rather than a project?
Other sectors this week