← All territories
Territory 06 · Bengaluru beachhead

Territory · Substrate signal

06Bengaluru beachhead.

The Albertsons Companies Global Tech & Innovation Center is onboarding associates over 18 months under Sunil Gopinath (former Rakuten India CEO). Charter spans cloud, security, data, AI. Enmovil's India SaaS posture = same-geography deployment partner for Newton's roadmap.

Same geography · same time zone · same talent pool.

Newton + Dhanda · supply-chain technology mandate · Bengaluru build
CADDIE · India SaaS · same-geography deployment partner
Bengaluru tech center
Cloud + data + AI charter
18-month onboarding
Lower friction than US-based vendor procurement

A US Fortune 500 retailer building a tech center in India naturally pairs with a SaaS already operating at scale in India.

The new tech center · the deployment thesis.

India tech center · Aug 2025

Sunil Gopinath named CEO of Albertsons Companies India (Bengaluru). Charter spans cloud, security, data, AI; onboarding associates over the next 18 months.

BusinessWire

Charter scope

"Modernizing core systems, integrating data science and artificial intelligence." Direct fit with the supply-chain orchestration roadmap.

Grocery Dive

Enmovil deployment posture

~100K trucks per day under orchestration · India SaaS in production at multiple Fortune 500 deployments · same time-zone deployment + integration support.

Enmovil deployment baseline

Three deployment advantages.

Same-geography deployment

India SaaS, India team, India support — natural alignment with the Bengaluru tech center build.

Pre-built integration patterns

Caddie ships with pre-built integration patterns against SAP, Oracle, transportation and warehouse systems used at Fortune 500 scale.

Lower-friction proof of value

No US vendor-procurement gauntlet for the first proof of value — pilot can run inside Bengaluru's mandate before US-team handoff.

Where we have shipped this shape.

~100K

Trucks per day under orchestration across the Enmovil deployment base

~99%

Estimated delivery accuracy across multimodal deployments

18 mo

Bengaluru onboarding window · the natural pilot timeframe

Questions, fence, timeline.

  1. What's Bengaluru's charter for supply-chain technology specifically — build, run, or both? Scale of supply-chain-IT-aligned hires there?
  2. Is there an opportunity for Enmovil to engage as a Bengaluru-side deployment partner before formal US procurement?
  3. How does Newton's organisation interface with Bengaluru today — co-located teams, regular syncs, or full ownership transition?

We would touch

  • Same-geography deployment + integration support out of India.
  • Pre-built Caddie integration patterns against SAP, Oracle, TMS, WMS.
  • Pilot scoping inside Bengaluru's 18-month onboarding window.
  • Co-located team support during US handoff.

We would not

  • Replacing Bengaluru's charter scope.
  • US-team-only deployment (defeats the geography advantage).
  • Vendor-of-record positioning before proof of value.
  • Full-stack rebuild (Caddie sits above existing systems).
90-day proof · co-built with Bengaluru · one cross-system flow

First proof: one cross-system flow instrumented + co-built with Bengaluru engineers in 90 days, then formal US-team handoff for production.

← Previous05 · Inbound vendor All territories