01 The Auckland to Bengaluru Relay: Two Workdays Out of Every One
Auckland sits six and a half to seven and a half hours ahead of Bengaluru depending on daylight saving, which sounds awkward and is actually a gift: run it properly and the same project is being worked on for the better part of every 24 hours.
⏰ The geometry of the relay
Your New Zealand afternoon is Bengaluru's morning. That gives you a live window of several hours every day for standups and decisions, at the end of your day and the start of theirs. Then India runs on long after Auckland sleeps, and what they ship overnight is waiting when you open your laptop.
📝 The baton is a written note
Relays fail at the handoff, never on the straightaways. The discipline that makes this work is a short end-of-day note from each side: what moved, what is blocked, what needs a decision. Ten minutes of writing buys twelve hours of unblocked progress. Teams that skip the note end up rediscovering the time gap the hard way.
🧾 Keep the admin out of the relay
The relay only carries product work. Indian payroll, provident fund deposits and tax filings should never travel through it, because a statutory question asked at Auckland 4pm should not wait on anyone. Employment through an EOR keeps that entire layer on Indian desks, on Indian deadlines.
02 New Zealand's Talent Ceiling and the One Indian City That Clears It
New Zealand produces excellent engineers and not enough of them. A country of five million cannot staff every scale-up's roadmap, and the honest symptom is familiar: roles open for months, salaries climbing, the same candidates circulating between the same companies.
📇 What one Indian city changes
Bengaluru alone holds more software engineers than New Zealand holds workers in its entire tech sector. Depth changes the shape of hiring: instead of waiting for someone qualified to become available, a structured search returns a vetted shortlist in around nine days, across specialisms Auckland simply cannot supply at any price.
🚀 From shortlist to first payslip in days
With employment run through an EOR's Indian entity, a signed candidate is onboarded and compliant in about five days, with no New Zealand company ever registering in India. Recruitment on top works as a success fee: 12% of CTC for junior and mid roles, 15% for senior, invoiced only at day 90, so a bad hire is the provider's problem before it is yours.
⚠️ The trap: treating India as overflow
Teams hired as a spillover valve get spillover results. The New Zealand companies that win give their India engineers real product ownership and fold them into the relay rhythm the time zones already reward.
03 Pricing an India Hire in New Zealand Dollars: Four Lines and Two Traps
The full cost of an India hire fits on four lines of a spreadsheet. The overruns, when they happen, come from two places that never appear on any pricing page. Both are avoidable at contract time.
🧾 The four lines
Line one is CTC, the all-in Indian salary figure that already bundles gross pay with employer contributions. Line two makes those contributions visible: provident fund around 12%, ESI at 3.25% where applicable, gratuity accruing at 4.81%. Line three is the platform: a flat $149 per employee monthly, sliding to $129 beyond 20 heads, first month free. Line four is FX, which should convert at the RBI reference rate and nothing worse.
⚠️ Trap one: percentage pricing
Some providers charge a percentage of salary instead of a flat fee. On senior salaries the difference compounds quietly: a percentage model can double your platform cost by the time the team reaches ten people, roughly $1,490 a month in flat-fee terms.
💸 Trap two: the FX spread
A markup of even 2% on the NZD-to-INR conversion is a stealth fee on your entire payroll, month after month. Ask the question before signing, in writing, and watch how quickly the honest providers answer.
⭐ The verdict
Four lines, two traps, one page. If a quote cannot be laid out this simply, the complexity is doing a job, and it is not for you.