Acquired-AI Platform GCC Spin-Up Leader

The mandate

The acquired evaluation platform passed startup customer tests but failed its first parent deployment when identities crossed tenant boundaries and evidence retention did not meet the contracted enterprise workflow. Parent security applied emergency controls, while founders argued those controls made the product unusable. The integration vice-president exited as customer commitments and the proposed India GCC charter became inseparable.

The interim will begin in San Francisco within two weeks and lead the eighteen-month spin-up across parent and India teams. Search for a permanent global platform executive opens after four services complete parent control integration and two enterprise customers accept the new operating model, expected by month eleven. The successor will lead a customer release and isolation-incident exercise during an eight-week overlap.

Handover requires evaluation orchestration, dataset handling, evidence retention, tenant isolation and platform reliability to have one product charter, accountable Bengaluru owners, parent control interfaces, customer obligations and tested recovery. Two customer migrations and three isolation or evidence scenarios must be complete. The successor receives service dossiers, founder dependencies, contract exceptions, integration debt, talent decisions and value commitments.

The interim may stop a customer migration, freeze a platform release, assign service-product authority, require isolation testing, restructure the integration backlog and commit up to USD 45 million within the approved portfolio. Contract amendment, customer pricing, acquisition earn-out, legal-entity change, workforce termination and enterprise risk acceptance require existing executives. Bengaluru owners gain roadmap and service decisions within defined customer and control limits.

Foundation-model selection, parent-wide identity redesign, general sales integration, corporate legal merger and AI products outside the acquired platform remain out of scope. The seat owns GCC spin-up, platform-product authority, control integration, enterprise acceptance, founder-to-leader transition and succession. It cannot turn one acquisition into authority over the company’s broader AI strategy.

Why this seat is open

The failed deployment exposed a gap between startup product success and enterprise operating accountability, then the integration leader departed. Founders and parent control teams hold opposing but incomplete views of acceptable operation. A temporary platform executive can make product and control decisions through customer evidence and leave a durable Bengaluru capability.

What you will own

• Reconstruct the failed deployment across identity flow, tenant isolation, evaluation evidence, retention, SRE response and customer obligation.
• Define complete product envelopes for five acquired platform services with named Bengaluru and parent interfaces.
• Reconcile startup release speed with enterprise access, segregation, evidence, incident and change-control requirements.
• Transfer customer, roadmap and service authority while reducing founder and parent shadow approvals through exercised decisions.
• Build India product, platform, security and reliability leaders with two-deep cover and direct customer exposure.
• Command migration, cross-tenant, evidence-loss, degraded-service and urgent model-change scenarios before scale.
• Transfer service dossiers, customer exceptions, founder knowledge, integration debt and talent commitments through successor-led governance.

Candidate qualifications

• Held executive product and platform authority integrating an acquired AI or developer-tools company into an enterprise portfolio.
• Converted a founder-led India engineering hub into a GCC with customer, roadmap, service and control accountability.
• Recovered tenant-isolation, identity or evidence-retention weakness during a consequential enterprise platform deployment.
• Balanced acquired-product speed with security, reliability and contracted customer controls without smothering differentiation.
• Transitioned founder-held relationships and technical judgment into durable product leadership and service artefacts.
• Handed an acquisition spin-up to permanent leadership after observed migrations, incidents and portfolio choices.

Non-negotiables

• Can start in San Francisco within two weeks and travel monthly between parent and India platform teams.
• Will accept exclusive executive accountability and continuous escalation for the five acquired platform services.
• Brings AI-platform acquisition integration plus India GCC spin-up; generic post-merger management is insufficient.
• Must disclose relationships with the acquired company, competitors, model providers, customers, investors and advisers.

1. 49 words maximum. Describe an acquired platform deployment where enterprise controls exposed a product-operating gap.
2. 49 words maximum. Which founder-held decision must transfer before Bengaluru becomes an accountable GCC capability?
3. 49 words maximum. State your San Francisco start and the largest acquired platform integration you directly led.