Swiggy-class. Scaled past 30.

Swiggy is India's most ambitious consumer marketplace. The company runs food delivery (the namesake Swiggy app), grocery delivery (Instamart), and a stack of adjacent commerce surfaces. Headquartered in Bengaluru, founded in 2014, listed on BSE and NSE in November 2024 (ticker: SWIGGY), the company operates across hundreds of Indian cities with a delivery network in the hundreds of thousands.

What this means for engineering scale is well-documented in Swiggy's S-1 filings and post-listing earnings disclosures. The technology organisation is among India's largest. The teams behind order routing, restaurant onboarding, dispatch optimisation, Instamart catalog management, and the dozen surrounding services collectively ship the operating system that India's quick-commerce economy runs on.

Inside that scale, there are specialised contract engagements that an Employer of Record vendor is best positioned to serve. Niche specialisations where the direct hiring loop would add a quarter. Project-shape engagements where the duration is bounded. Contract-to-hire conversions where Swiggy wants to validate the specialist before transitioning to direct payroll. Versatile's engagement with Swiggy sits in this operational slot.

When the engagement began in March 2024, Swiggy was operating its India team on three legacy placement vendors. The cumulative headcount across the three vendors was twelve specialists, but the operational reality was a procurement and compliance nightmare: three sets of payslip formats, three TDS reconciliations, three compliance documentation pipelines, three audit response windows. Swiggy was approaching its IPO. The audit posture was about to escalate. Three vendors was not going to survive a listed-entity audit.

The pre-IPO holding entity was BUNDL TECHNOLOGIES PRIVATE LIMITED. The Engineering Manager who owned the India platform operations function asked Versatile to absorb all three vendors and become the single Employer of Record across the cohort. The consolidation completed across two payroll cycles in April-May 2024. By July, the audit documentation was unified.

Five months later, Swiggy listed. The holding entity transitioned to Swiggy Limited, the post-IPO listed entity. The transition affected GST registration, employment contracts, statutory filings, and the legal counterparty on every Versatile invoice. Versatile handled this transition without breaking a single payroll cycle, without affecting UAN continuity for any specialist, and without triggering a single compliance query during the audit window that followed.

That month is what the case study is built around. The rest of the engagement is operational rhythm at scale.

Swiggy's challenge stack was the most operationally complex of any Versatile engagement, by a wide margin.

The first challenge was vendor consolidation. Twelve specialists across three placement vendors meant three different employment contracts, three different compliance regimes, and three different audit response windows. The Engineering Manager wanted one Employer of Record, one payroll register, one compliance pipeline. The consolidation had to happen without a payroll gap and without affecting any specialist's UAN, PF balance, or gratuity accrual.

The second challenge was the audit escalation. Swiggy was on a clear path to an IPO listing through 2024. Listed-entity audits in India operate at a different documentation depth than private-company audits. SEBI, the stock exchanges, the listed-entity auditors, and the statutory auditors all overlap on payroll documentation. Every Versatile-employed specialist's compliance footprint had to survive that escalated audit. There was no room for a 'we will fix that next cycle' answer.

The third challenge was the entity transition itself. Around the November 2024 IPO listing, BUNDL TECHNOLOGIES PRIVATE LIMITED transitioned to Swiggy Limited as the operating counterparty. The transition meant a new GST registration, a new vendor record in Swiggy's accounts payable system, a new MSA, and updated employment contracts for every Versatile-employed specialist (because the client counterparty on the work direction changed). Versatile had to execute all of that without any payroll disruption.

The fourth challenge was scale. The team grew from twelve specialists at engagement start to past thirty by Q3 2025. Versatile's compliance pipeline had to scale without process drift. Every additional specialist added pure operational load: an additional payslip, an additional PF challan reference, an additional TDS computation, an additional Form 16 cycle. The discipline that holds at twelve does not automatically hold at thirty. Most India placement vendors lose the discipline somewhere between twenty and thirty.

The Engineering Manager at Swiggy who took the discovery call with Sagar Chainani in early 2024 had been through these failure modes at peer organisations. The questions she asked on the first call were the questions of someone who had already been burned: how does Versatile structure its PF Trust governance, what is the documentation depth on Form 16 issuance, how does Versatile handle entity transition mechanics. The answers had to be specific, technical, and verifiable. They were. The engagement began the following month.

Every Swiggy placement on Versatile follows the same five-business-day Employer of Record onboarding SLA. The discipline holds at thirty specialists for the same reason it holds at six: the entity, the compliance team, and the payroll pipeline are all the same operation in the same building.

The most operationally interesting moment in the Swiggy engagement was not a single onboarding. It was the bulk migration in April-May 2024, when Versatile absorbed twelve specialists from three legacy vendors across two payroll cycles. The five-day SLA held across all twelve simultaneously, because the operational pipeline is designed to scale to that load without process drift.

The Engineering Manager has measured this SLA across thirty-plus placements. Every onboarding has completed inside the five-day window. The audit reviewers at Swiggy's listed-entity audit cycle reviewed sample onboardings in Q1 2026 and accepted the documentation without queries.

Compliance for Swiggy is compliance for any India-employed specialist, with the additional discipline that listed-entity audit posture requires. Every payslip cross-referenced to its underlying PF challan ID. Every TDS deduction traceable to a Form 12BB declaration. Every Karnataka professional tax payment evidenced by a commercial taxes portal acknowledgement.

The Q1 2026 listed-entity audit was the engagement's biggest test. The audit reviewers asked for sample cross-references across the thirty-plus specialists. Every cross-reference resolved cleanly. The audit closed inside its standard four-week window without any follow-up rework. The pass rate held at 100%.

Across 26 months and 36 invoices, Swiggy's engagement with Versatile has produced zero compliance notices, zero rectification orders, zero penalty assessments, and zero audit queries that required process change. That track record is the value proposition.

Twenty-six months in, Swiggy's engagement with Versatile is in a steady-state operational rhythm at scale. The measurable outcomes are:

The biggest single value moment was the IPO transition month. The biggest cumulative value is the absence of compliance notices across 26 months of operational scale. The biggest reputational value is the recommendation that flows from this engagement into Swiggy's network of peer companies, several of which have evaluated Versatile based on the documented track record.

Swiggy taught us three things about scaling an Employer of Record discipline past thirty specialists.

First: vendor consolidation is the most under-rated value of an India-native EOR. Going from three vendors to one is procurement value. It is also audit risk reduction, operational time reduction for the customer's engineering manager, and a meaningful improvement in specialist experience because the payslip format stops varying month-to-month. We now lead with this value in our positioning to mid-stage Indian companies.

Second: entity transitions are not edge cases. They happen at every IPO, every restructuring, every spin-off. We have built the entity-transition playbook from the BUNDL → Swiggy Ltd execution and we run it as a standing capability now. Other listing-stage Indian companies have engaged us specifically for this capability.

Third: the operational discipline that holds at thirty does not auto-scale to a hundred. We are building the next-stage scale-out playbook based on what we are learning at Swiggy. The pipeline that holds at thirty is the pipeline that the next twenty placements will use. We are designing for it explicitly.

If you are a high-growth Indian company approaching a listing, a global enterprise consolidating India placement vendors, or any organisation whose India hiring needs to scale past thirty specialists on a single Employer of Record, the Swiggy engagement pattern is the right evaluation lens.

What it looks like in practice: vendor consolidation across two payroll cycles. An audit-grade documentation pipeline that holds through your listed-entity audit cycle. An entity-transition playbook ready to run if your corporate structure changes mid-engagement.

What you should expect from us inside a serious evaluation: the specific entity transition playbook from the BUNDL → Swiggy Limited execution, walked through with you in detail. If a provider cannot walk you through their entity transition mechanics at this depth, they have not done it in production yet.