<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>Altacent Partners Insights</title><subtitle>Practical notes on GCC, offshoring, SAP and enterprise AI.</subtitle><link href="https://altacentpartners.com/insights/feed.xml" rel="self"/><link href="https://altacentpartners.com/insights/"/><id>https://altacentpartners.com/insights/</id><updated>2026-10-30T00:00:00Z</updated><entry><title>Anatomy of a failing capability center, and how to rescue one</title><link href="https://altacentpartners.com/insights/failing-capability-center-rescue/"/><id>https://altacentpartners.com/insights/failing-capability-center-rescue/</id><updated>2026-10-30T00:00:00Z</updated><summary>A failing capability center usually has one of three failure modes. How to tell which, and the rescue sequence the book says must not be shortcut.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>Why the cost case alone fails: what a GCC business case misses</title><link href="https://altacentpartners.com/insights/why-the-gcc-cost-case-fails/"/><id>https://altacentpartners.com/insights/why-the-gcc-cost-case-fails/</id><updated>2026-10-30T00:00:00Z</updated><summary>A GCC business case built only on cost measures what a center will cost, not what it could become. What that misses, and the one decision that matters.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>Why so many companies still run legacy SAP</title><link href="https://altacentpartners.com/insights/why-companies-stay-on-legacy-sap/"/><id>https://altacentpartners.com/insights/why-companies-stay-on-legacy-sap/</id><updated>2026-10-22T00:00:00Z</updated><summary>Tens of thousands of enterprises still run SAP ECC or R/3. The five structural reasons they stay, and why staying is often a rational decision.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>AI on legacy SAP before migration: five options compared</title><link href="https://altacentpartners.com/insights/ai-on-legacy-sap-before-migration/"/><id>https://altacentpartners.com/insights/ai-on-legacy-sap-before-migration/</id><updated>2026-10-22T00:00:00Z</updated><summary>Companies on SAP R/3 or ECC can add conversational AI before moving to S/4HANA. The five realistic options, when each fits, and a bounded 26-week first project.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>The pre-IPO governance gap: IT controls before the audit</title><link href="https://altacentpartners.com/insights/pre-ipo-governance-gap/"/><id>https://altacentpartners.com/insights/pre-ipo-governance-gap/</id><updated>2026-10-22T00:00:00Z</updated><summary>Why IT controls are often not audit-ready before an IPO or carve-out, and the practical steps to close the gap on access, change control and evidence.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>Ten rules for delivering any project, from SAP rollouts to new GCCs</title><link href="https://altacentpartners.com/insights/ten-rules-for-delivering-projects/"/><id>https://altacentpartners.com/insights/ten-rules-for-delivering-projects/</id><updated>2026-10-22T00:00:00Z</updated><summary>Ten plain rules that keep projects on track, drawn from a practitioner&#x27;s project delivery method: scope, constraints, risk, honest tracking and a proper close.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>Build, fix or walk away: deciding what to do with a GCC</title><link href="https://altacentpartners.com/insights/build-fix-or-walk-away-gcc/"/><id>https://altacentpartners.com/insights/build-fix-or-walk-away-gcc/</id><updated>2026-10-22T00:00:00Z</updated><summary>Three questions, asked in order, decide whether to build a capability center, fix the one you have, or close it. Includes the walk-away conditions.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>Micro GCC or agency staff: what the numbers say</title><link href="https://altacentpartners.com/insights/micro-gcc-vs-agency-staff-costs/"/><id>https://altacentpartners.com/insights/micro-gcc-vs-agency-staff-costs/</id><updated>2026-10-22T00:00:00Z</updated><summary>A 12-person micro GCC in Bengaluru is modelled at USD 310,000 to 430,000 a year against 504,000 to 672,000 for agency staff, a saving of 24 to 38 per cent.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>How a micro GCC is set up in seven days</title><link href="https://altacentpartners.com/insights/micro-gcc-in-seven-days/"/><id>https://altacentpartners.com/insights/micro-gcc-in-seven-days/</id><updated>2026-10-22T00:00:00Z</updated><summary>A micro GCC can start in about seven days with an employer of record, or in four to six weeks with its own subsidiary. Legal, talent and governance run in parallel.</summary><author><name>Anupam Shrivastav</name></author></entry><entry><title>What is a micro GCC, and when does it make sense?</title><link href="https://altacentpartners.com/insights/what-is-a-micro-gcc/"/><id>https://altacentpartners.com/insights/what-is-a-micro-gcc/</id><updated>2026-10-22T00:00:00Z</updated><summary>A micro GCC is a wholly controlled offshore team of five to 25 people, employed directly by the company. How it differs from outsourcing, and when it fits.</summary><author><name>Anupam Shrivastav</name></author></entry></feed>