Q1. Could you start by giving us a brief overview of your professional background, particularly focusing on your expertise in the industry?

My career spans nearly three decades and four very different organisational contexts — TCS, Cognizant, Accenture, Novartis, and now as a freelance consultant and each chapter added a layer, perspective and an experience that the previous one simply could not have given me. I started as a hands-on technologist in the late nineties, got deep into test engineering and quality assurance when nobody was calling it "strategic," and then progressively moved into running large global delivery organisations.

At Accenture, I was operating at VP level, leading testing and technology programme delivery across some of the most complex enterprise transformations in telecom and financial services. I turned around a 220-person Testing Centre of Excellence that was running at a minus five percent margin and brought it to a sustained thirty percent-plus.  That experience is probably the one that shaped how I think about delivery discipline and commercial accountability more than any certification or MBA could teach you.

Moving into a Pharma giant, when I was reached out to, was a deliberate pivot toward industry, and it is where my thinking about GCCs, regulated digital transformation, and the intersection of data and pharma has deepened considerably. I was a part of the core team that helped setup innovation hub - Biome for Hyderabad, contributing to the Operating Model and the playbook for the setup. I also helped scale our Shared Services IT delivery function unit from a small operation to a four hundred-plus-person organisation over several years. In parallel, I have maintained a practitioner habit: I am a Kaggle Legacy Grandmaster, I have authored books on Python data visualisation, Test automation, and testing, and published white papers on DevOps, intelligent testing, and model-based testing. I was recognised as a CIO Next100 Future CIO in 2022 and have been ranked among the top-ten global thought leaders on Thinkers360. I say all that not to rattle credentials, but because these are the experiences I actually draw on when I talk about transformation and not frameworks borrowed from consultants, but things I have built, broken, and fixed myself. Such an experiential learning can go a long way and this wisdom needs to be shared to the wider forum, I think.

Q2. How is the role of Global Capability Centers evolving in the pharma industry as companies move from cost optimisation to capability and innovation-led models?

Let me be direct about where we were five years ago: most pharma GCCs including honest conversations inside the large pharma GCC I was part of - were being justified almost entirely on the labour arbitrage story. The pitch was straightforward: offshore the work, reduce cost per FTE, hit your efficiency targets, keep headquarters happy. And for a while, that was fine because the work being offshored was transactional enough that pure labour cost was a legitimate metric.

What has changed, and I have watched this shift happen in real time, is that pharma has started asking a fundamentally different question. Not "how cheaply can we do this?" but "can our GCC own this?" Those are entirely different organisational challenges. Owning something in pharma means GxP accountability, means decision-making authority, means domain experts sitting in Bengaluru, Pune, Chennai or Hyderabad who can actually influence how clinical trials are designed or how pharmacovigilance workflows are structured.

The GCCs that do this well are those where leadership has genuinely distributed decision rights, not just headcount. I have written about this before. If every significant decision still travels back to the global HQ for sign-off, you do not have a capability hub; you have an expensive managed service with good branding. The transformation from cost-to-capability is not automatic. It requires intentional investment in senior talent, proximity to strategy, and leaders at the GCC level who are empowered to push back on headquarters when the business case demands it. The companies that are serious about this are now investing in computational biology, bioinformatics, clinical data engineering, and regulatory intelligence automation capabilities that genuinely move the science forward, not just the spreadsheet.

Q3. Where are AI, automation, or data platforms materially improving efficiency across pharma operations, and where have these investments struggled to deliver meaningful returns?

I think about this constantly, and I have lived both sides of it. The wins and the uncomfortable post-mortems. The places where AI is delivering real, measurable value in pharma are fairly specific: adverse event detection and signal identification in pharmacovigilance, where the volume of incoming case data is simply too large for manual review at acceptable speed; medical imaging analysis, where models have demonstrably outperformed clinicians in narrow, well-defined tasks; supply chain demand sensing, where ML-driven forecasting is reducing wastage in temperature-controlled logistics; and clinical trial protocol optimisation, where pattern recognition across historical trial data is helping design teams avoid known failure modes.

What I have seen consistently fail is the platform-first, use-case-later approach. Large data lake programmes that consumed tens of millions in infrastructure investment but never got past the governance layer. RPA deployments that automated broken processes; I have seen this repeatedly, rather than fixing the underlying process design and then automating it. Chatbots and automation initiatives launched with enthusiasm but now sit unused because they were designed around what the technology could do rather than what users actually needed.

The ROI gap almost always comes down to three things: data quality foundations that were never properly laid before model development started; the absence of domain experts sitting alongside data scientists during solution design; and change management that was treated as a communications task rather than an organizational transformation. Being a Kaggle Grandmaster means I can design solutions, develop algorithms, and build models. But I have learned, often the hard way, that the model is the smallest part of the problem. Getting the data, the workflow, and the human adoption right is where the value is either created or destroyed. Just like how skilled plumbers make a ton of money, equivalent to or more than professional white-collar workers in developed nations, data plumbers are the key to the success of an enterprise product. They are the ones who make the top tech firms succeed in a big way.

Q4. Where do regulatory and compliance requirements most significantly influence digital transformation priorities in pharma organisations?

This is the question that separates people who have actually worked inside regulated pharma environments from those who have advised from the outside. Regulation in pharma is not a friction factor you manage around. It is literally the architecture of how you build systems. GAMP 5, 21 CFR Part 11, GxP validation requirements, audit trails, electronic signatures, CSV documentation - these are not box-ticking exercises. They shape your cloud vendor selection (TPRM is a concept widely leveraged), your deployment pipelines, your access management design, your change control processes, and, increasingly, your AI model governance.

The emerging AI guidance is particularly significant. There is active regulatory attention globally. From the FDA, EMA, and others 0 on how AI systems used in drug development or manufacturing should be validated, monitored, and updated. In practice, this means that any model touching GxP-relevant data needs a validation strategy from day one, not retrofitted after engineering is complete. I have heard many stories from industry peers who were in the room seeing entire (multi-year, multi-million $) programs to be re-scoped because compliance was not embedded in the design phase.

The organisations that move fastest in this environment are not cutting corners. These organizations are building compliance thinking into their sprint design from the beginning, treating their regulatory colleagues as architects rather than auditors. There is a real competitive advantage available for pharma companies that treat validated cloud environments and regulatory-aware data platforms as strategic assets rather than cost centres. The compliance burden is real, but it is also a moat. Not many organisations can do this well, and the ones that can move significantly faster when the architecture is right from the outset.

Q5. Which markets appear most attractive for pharma GCC expansion but present the greatest operational or talent challenges in practice?

India remains, and will continue to be for at least the next decade, the most compelling destination for pharma GCC expansion. The growth of Pharma GCCs (especially in Hyderabad) is a telling example for this. The talent depth is real. We are not just talking about generalist software engineering, but increasingly about a growing cohort of professionals with genuine pharma-domain experience: people who have spent five or more years in clinical data management, validated systems engineering, biostatistics, and regulatory submissions. That cohort is smaller than vendors will tell you, and competition for it is intense, but it exists, and it is growing.

What the location analysis spreadsheet does not always capture is how quickly the talent war for specialised profiles has intensified. The same names - Novartis, AstraZeneca, Sanofi, Novo Nordisk, BMS, Takeda, Amgen, GSK, Pfizer etc., are all hiring for broadly similar roles in Hyderabad and Bengaluru simultaneously. Average compensation for senior clinical data engineers or bioinformatics specialists has moved sharply, and attrition in those profiles runs well above industry average. You cannot build a sustainable GCC on a talent model that constantly rebuilds the top of the pyramid.

Eastern Europe - Poland, Romania, and Slovakia offers a different value proposition. A strong technical talent, EU regulatory familiarity, cultural proximity to Western headquarters, and time zones that make real-time collaboration more practical. But scaling beyond three or four hundred people is operationally difficult, and the talent pool for pharma-specific profiles is considerably thinner. Southeast Asia is emerging, particularly Malaysia and Singapore, but lacks the critical mass today for full-scale pharma GCC build-outs. The honest answer for most pharma companies is a multi-hub model with India as the anchor and Eastern Europe or Singapore as a complementary layer - which is, roughly, what the smarter organisations are actually building.

Q6. How is the competitive landscape evolving between consulting firms, technology providers, and specialised life sciences service companies in driving pharma digital transformation?

The traditional boundaries have blurred significantly, and we are in a genuinely interesting competitive moment. The large consulting firms - the Accenture, Deloitte, Capgemini of the world are responding to the disintermediation threat by building proprietary accelerators, industry-specific platforms, and life sciences AI assets. They are trying to transition from being purely implementation partners to platform and IP owners. That is a credible strategy, but it requires a very different talent model and commercial structure, and the organisations doing it well are still the exceptions.

The hyper-scalers are making direct, increasingly sophisticated moves into regulated pharma. Microsoft, AWS, and Google have all invested in validated cloud environments and pre-built frameworks for GxP compliance. These are no longer generic cloud propositions. They are designed to reduce the compliance overhead of cloud adoption in pharma. That changes the build-versus-buy calculus for every pharma IT leader.

What I find most interesting is the category of specialised life sciences service companies carving out durable positions in very specific niches. Niche areas such as clinical data engineering, regulatory submissions automation, and pharmacovigilance workflow technology. These organisations are winning because depth beats breadth in regulated environments. A firm that has executed 50 pharmacovigilance automation implementations understands the edge cases, validation pitfalls, and regulatory interpretation nuances in ways that a generalist systems integrator simply cannot replicate at scale. The smart pharma CIOs I know are building vendor portfolios that deliberately mix large partner scale with specialist depth, and becoming genuinely uncomfortable when they are too concentrated in either direction.

Q7. If you were an investor looking at companies within the space, what critical question would you pose to their senior management?

There is one question I would pose, and I would watch very carefully how it was answered: When your GCC or delivery hub last pushed back on a strategic decision from headquarters and won a favourable outcome - what was it, and how did it happen?

That question does two things simultaneously. It tests whether the centre has genuine decision rights or is operating as an execution arm with nice office furniture. And it tests whether leadership has the intellectual honesty to even have an answer, because if they struggle to name a specific instance, you have learned something important about the organisational reality versus the investor narrative.

The companies that have genuinely distributed authority alongside capability are building something defensible and hard to replicate. The model where a thousand engineers sit in Hyderabad/Bengaluru/Chennai/Pune executing tasks designed in the US, UK, Japan, Germany, or Switzerland, with all substantive decisions traveling back to headquarters, is cost-efficient but fragile. It looks good in a pitch deck right up until the moment when a key client renegotiates, or a regulatory change requires rapid architectural decisions, or the talent market shifts and the cost arbitrage narrows. What survives those moments is a centre that owns outcomes, not just outputs, and that distinction is visible in the answer to my question long before it shows up in the financial results.