What an India-based partner actually changes
The honest version of the offshore argument is about capacity, not price. At Indian
rates a project that would fund two engineers in the US funds a team with a senior
architect, and in AI work seniority is what separates a system that survives
production from one that does not.
The dishonest version is a rate comparison. Chasing the lowest hourly cost in this
field reliably produces a working demo, a thin evaluation story, and a rebuild in
month six. If you are comparing vendors, the question worth asking is not the rate —
it is to see an evaluation methodology and a system they have operated for a year.
The timezone is a discipline problem, not a geography problem
Distributed delivery across a nine-and-a-half-hour gap works when the async discipline
is genuine and fails when it is claimed. What makes it work in practice:
- A fixed overlap window agreed at the start, not negotiated weekly.
- Decisions written down, so an unanswered question does not cost a day.
- A named escalation path with a response time outside the window.
Done properly, the gap is an advantage: work continues while your team sleeps and
lands before their morning. Done carelessly, every question costs twenty-four hours.
Designing for more than one privacy regime
Almost none of our clients operate under a single regime. An Indian lender has DPDP
obligations; its European customers bring GDPR; a US healthcare client brings HIPAA
and state privacy law on top.
So the design question during scoping is which regimes apply and what the strictest
constraint is on each dimension — where processing may happen, what may be retained
and for how long, what the audit trail must contain, how a deletion request
propagates. Designing to that from the start is straightforward. Retrofitting it after
a security review is usually a rebuild.