Skip to main content
Global capability centres · Kolkata

IT services for global capability centres in Kolkata

Kolkata's capability centres cluster in Salt Lake Sector V and New Town, and they tend to be delivery and back-office operations rather than the strategic functions concentrated in Bangalore or Gurugram. The estates are large, the parent standard applies as it does everywhere, and the local IT layer is frequently thinner than the headcount would suggest because investment has followed the delivery function rather than the infrastructure. That produces a specific gap: group IT owns the endpoints, nobody locally owns the network, the meeting rooms or the physical infrastructure, and it shows. We take that layer, agree the boundary with group IT in writing first, and align cover to the overlap hours with the parent rather than to Indian office hours. Delivery is remote-first with engineers travelling for scheduled work.

30 min
Managed response SLA
24/7
Monitoring and cover
Remote-first
Plus scheduled visits to Kolkata
Microsoft
Partner-led 365 and security

global capability centres in Kolkata, and where it sits

Kolkata splits cleanly between its newer technology districts and its historic commercial core. Salt Lake Sector V and New Town carry the IT and ITES campuses; BBD Bagh and Dalhousie hold government offices, banks and long-established trading houses; Park Street and Camac Street carry corporate and professional offices; and the EM Bypass corridor has drawn healthcare and newer commercial development.

Kolkata businesses skew older and more established than in the newer metros, particularly around BBD Bagh and the trading houses, which means IT estates frequently carry a decade or more of accumulated decisions nobody currently employed made. The first job is usually documentation rather than improvement, because you cannot safely change what has never been mapped.

What we find going wrong

Across GCCs, captive centres and offshore delivery teams we support, the same handful of issues come back. If two or three look familiar, the pattern is more common than it feels.

  • Escalation paths that work in local office hours and quietly do not during the overlap window
  • Meeting-room technology failing at scale, which is disproportionately visible to the parent
  • Local network treated as out of scope by group IT and unowned by anyone else
  • Gaps and overlaps between the group IT function and local providers, where each assumes the other owns a system

What constrains the work

These decide what can be changed and when. They are not obstacles to work around, they are the shape of the engagement.

Time-zone overlap. Handovers and overlap windows mean the local working day extends well past office hours, and support has to reflect that.

The parent sets the standard. Security baselines, tooling and reporting are mandated from the group. The local requirement is to meet them and prove it, not to design an alternative.

What an engagement here involves

Kolkata captive centres are usually delivery and back-office operations, and the recurring gap is that investment has followed the delivery function rather than the infrastructure underneath it. Group IT owns the endpoints; nobody locally owns the network, the meeting rooms or the physical layer, and it shows in exactly those places. Our engagement is taking that layer with the boundary agreed in writing first. Meeting-room reliability gets early attention because a failed call with the parent is the most visible failure the site can have. Support hours align to the overlap window with the parent rather than Indian office hours.

Every sector has work that can be done from anywhere and work that cannot. For GCCs, captive centres and offshore delivery teams the split looks like this.

Local exceptions to the global baseline that were granted informally and never reviewed. That is remote work: configuration, policy and monitoring, with nothing gained by being in the room. Across Kolkata we see it often enough in global capability centres that it is part of the standard onboarding audit rather than something we wait to be told about.

Escalation paths that work in local office hours and quietly do not during the overlap window. That one needs an engineer in the building, so it goes into a scheduled visit rather than waiting for a call-out. Across Kolkata we see it often enough in global capability centres that it is part of the standard onboarding audit rather than something we wait to be told about.

Meeting-room technology failing at scale, which is disproportionately visible to the parent. That is diagnosed and fixed remotely, and monitoring catches it rather than a user reporting it. Across Kolkata we see it often enough in global capability centres that it is part of the standard onboarding audit rather than something we wait to be told about.

Where global capability centres sits in Kolkata

We work across Kolkata, and for GCCs, captive centres and offshore delivery teams the concentration is usually around Salt Lake Sector V, New Town and Rajarhat, Park Street and the EM Bypass corridor.

Location matters less than it would for an on-site provider, but it still shapes the engagement: building management, landlord-controlled connectivity and riser access differ by district, and those are the constraints that decide what is physically possible.

How delivery to Kolkata actually works

Kolkata is served remote-first from Hyderabad. Support, monitoring and administration are delivered remotely, with engineers travelling for scheduled projects and reviews. That model suits the market: local providers are plentiful for break-fix, and what Kolkata businesses more often lack is depth in Microsoft 365, security and compliance.

Remote-first is not a euphemism for remote-only. Rollouts, refreshes and physical infrastructure work are done on site in Kolkata, they are simply planned rather than reactive.

Managed clients have a 30-minute response target for critical issues. For a first enquiry, we reply within 4 business hours.

When we can touch your systems

Planned around your overlap hours and the group change calendar, so local work does not collide with a global change freeze.

Scheduling is agreed with you rather than assumed, and anything disruptive is planned into a window you have approved.

Questions

IT for global capability centres in Kolkata, answered

Global capability centres, Kolkata

Get a fixed-scope quote for global capability centres in Kolkata

Tell us what you run and how you operate, and we will come back within 4 business hours. Managed clients get a 30-minute response SLA.