Over the past three years, as an independent cloud and AI consultant, advisor, and industry influencer, I have worked with numerous companies seeking my expertise. I have helped evaluate, optimize, coach, and support their generative and agentic AI initiatives.
Over the past three years, as an independent cloud and AI consultant, advisor, and industry influencer, I have worked with numerous companies seeking my expertise. I have helped evaluate, optimize, coach, and support their generative and agentic AI initiatives.
Some organizations sought a second opinion before scaling an AI platform. Others had pilots that performed well in demos but collapsed when connected to real systems. Some needed help selecting models, cloud services, vector databases, or orchestration tools. Others wanted to understand why their expensive AI investments were generating activity but not measurable value.
Because most of my work is covered by non-disclosure agreements, I cannot discuss the companies, vendors, architectures, budgets, or internal decisions involved. That is expected and appropriate. However, I can talk about patterns I have seen across varying industries, company sizes, cloud environments, and maturity levels.
The biggest lesson is simple: Most enterprise AI projects don’t fail because the model is weak. They fail because the enterprise surrounding the model isn’t ready.
The first failure pattern is the most common. Organizations start with a model, platform, copilot, agent framework, or cloud service before defining the business outcome they aim to improve. They start with “We need generative AI,” rather than “We need to reduce claims processing time by X percent” or “We need to improve first-contact resolution in customer service by a factor of X.”
The distinction matters. AI is not a business strategy. It is a technology capability that may or may not support a business strategy. When companies skip the business problem and go straight to the tool, the typical result is a polished demo seeking a reason to exist.
In context
- Topic: Cloud y Arquitectura — Nube pública, híbrida, costos y decisiones de infraestructura.
- Source: InfoWorld
- Published: 28/08/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
After a few years, nearly every organisation that migrated discovers the same thing: the bill grows faster than the business. Not because the cloud is expensive, but because nobody switches off what is no longer used and nobody has the incentive to check.
My reading goes through who sees the bill. In organisations where cloud cost reaches the team that generates it, spend organises itself. Where only finance sees the bill, spend grows and the discussion becomes a blind cut every year end.
What usually goes wrong
Where it usually breaks is team capability. The platform is new but people learned on the fly, with no time and no support. They end up replicating data-centre practices in the cloud, which means paying cloud prices for benefits that never arrive.
What to watch
- How hard it would be to leave or move a piece to another provider, which is future negotiating power.
- Who sees the bill and in what detail: with no owner for the spend, the spend grows on its own.
- Where the data physically sits and what local regulation demands about that.
How I read this entry
What I would install alongside any move to the cloud is the discipline of switching things off. Tag everything by owner, review monthly what is running unused, and give somebody the authority to turn it off. Without that, waste eats the promised savings within two years.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
