Skip to the stories
Microsoft 365 & SharePoint

HCLTech's Nano GCC Bundles AI Operations on AWS for Smaller Teams

  • Express Computer
  • 690 views

HCLTech's nano GCC model pairs small, product-focused teams with AWS agentic AI services, aiming to move enterprise AI from pilot to production.

HCLTech's Nano GCC Bundles AI Operations on AWS for Smaller Teams

HCLTech has put a smaller, AI-first spin on the Global Capability Centre model. Its new nano GCC offering runs on Amazon Web Services and is pitched at one specific problem: getting AI initiatives out of pilot projects and into production without rebuilding the whole operating model around them. For IT leaders who have watched AI proofs of concept stall, that's the part worth paying attention to.

What the nano GCC actually is

The offering sits inside HCLTech's GCC 360 solution suite. It combines the company's GCC advisory services with its AI platforms, including AI Force, and layers on AWS infrastructure and agentic AI services. In other words, HCLTech is selling the setup work, the platforms and the cloud foundation as one package.

The key difference is scale. Traditional GCCs tend to be built around broad operational mandates and large headcount. The nano model swaps that for smaller, product-focused teams running AI-enabled workflows. My read is that this is less a new type of centre and more a way of standing up a narrow capability quickly, then widening it only if the results justify the spend.

The service scope covers four areas: AI-native engineering, autonomous IT operations, data and analytics, and business operations. Responsible AI governance is built into the operating model from the start rather than bolted on later, which is a detail that matters to any team that has had to retrofit controls onto an AI deployment.

Who it's aimed at

HCLTech identifies two target groups, and they're quite different.

The first is enterprises that already run a GCC and want to introduce AI-led change without disrupting what's working. For these organisations, HCLTech plans to support a hub-and-spoke model anchored at its Lucknow campus. That suggests existing centres could route specific AI workloads or teams through a central hub rather than rebuilding their own capability from scratch. If you run a GCC today, the practical question is how much of your work would sit in the hub and how much would stay local, and that's worth mapping before any conversation with a vendor.

The second group is mid-market companies that want a presence in a new geography but don't want to commit to a large initial setup. This is the classic nano use case: a smaller footprint, lower upfront commitment, and room to grow. Mid-market firms tend to find the full GCC build-out hard to justify on a single business case, so a modular entry point changes the maths considerably.

How delivery and the AWS side fit together

The division of labour is clear. HCLTech leads the design and implementation of the GCC operating model. AWS supplies joint go-to-market support and access to services including Amazon Bedrock, Kiro and AWS Transform.

The companies describe a staged approach: start with specific use cases, assess the results, then expand deployments as requirements change. That's sensible, and it's also how most teams should approach agentic AI anyway. Agentic systems that act on IT tickets, infrastructure or data need clearly scoped permissions and measurable outcomes before anyone widens their remit. A phased model gives you natural checkpoints to review access, logging and failure handling before the blast radius grows.

Asia Pacific is the first phase of the rollout. Delivery will be supported by HCLTech's India-based operations and its Centre of Excellence in Lucknow, drawing on the country's technology and engineering workforce. The source doesn't say when other regions will follow, so treat broader availability as an open question for now.

What the executives are saying

Kiran Cherukuri, Executive Vice President and Global GCC Practice Leader at HCLTech, framed the shift this way: "The question for most organisations is no longer whether to build AI-native operations, but how to do it without the drag of legacy setup models." He said the nano GCC model reflects the growing role GCCs are playing in developing enterprise AI capabilities.

Prabhakar Appana, Senior Vice President and Global Head of the AWS Ecosystem Business Unit at HCLTech, said the offering combines HCLTech's GCC and AI capabilities with AWS infrastructure and agentic AI services. The aim, in his description, is to help enterprises move from targeted use cases to wider deployment.

Amit Anshu, Head of GSI and IT Business at AWS India and South Asia, put the emphasis on speed and confidence: "Enterprises across Asia Pacific want to build AI-native operations with speed and confidence. AWS provides cloud infrastructure, agentic AI services and DevOps capabilities that power HCLTech's nano GCC offering. This helps organisations move from pilot to production and scale as their business demands evolve."

These are vendor and partner claims, not independent measurements. The source offers no delivery timelines, pricing, customer names or performance figures, so anyone evaluating the offering will need to get those details directly.

Workplace at a global capability centre

What IT teams should check

If your organisation is weighing up a model like this, a few questions matter more than the marketing.

First, map your current AI pilots against the four service areas. If your work sits mainly in autonomous IT operations or data and analytics, the fit will look different from a team focused on AI-native engineering.

Second, look at the dependency chain. A nano GCC built on Bedrock, Kiro and AWS Transform ties your delivery to AWS services and to HCLTech's operating model. Check how workloads, data and access controls move between the hub and any spoke teams, and who owns the runbooks when something breaks at 2 a.m.

Third, ask how responsible AI governance is actually implemented. The source says it's incorporated into the operating model, but it doesn't describe the mechanics. Request specifics on logging, human review points, and how agent permissions are scoped and revoked.

Fourth, if you're a mid-market company, test whether a product-focused team of modest size can absorb your use cases, or whether you'll outgrow the model quickly. The staged expansion approach only helps if the exit and scale-up paths are clear from the start.

What to watch next

The interesting thing here isn't the nano label. It's the bet that AI capability can be packaged as a repeatable unit, rather than assembled project by project. If HCLTech and AWS can show that enterprises move from pilot to production faster under this model, other service providers will probably copy the structure. If the results stay vague, the offering will look like a smaller version of an old outsourcing pitch.

Watch for named customers, regional expansion beyond Asia Pacific, and any published detail on how the hub-and-spoke model handles data and operational ownership. Those are the signals that will tell you whether this is a practical option for your team or another well-packaged proposition to evaluate carefully.

Source: Express Computer · www.expresscomputer.in

Neighbouring cells