Problem
India's Code on Social Security 2020 legally obligates gig platform aggregators — delivery, beauty, logistics, and freelance marketplaces — to register every gig worker on the e-SHRAM portal and make monthly social security contributions on their behalf. Rajasthan and Karnataka have already passed enforcement legislation, and central-government audits are escalating. Yet most platforms are still tracking obligations in spreadsheets, risking ₹10,000-₹1,00,000 per-worker fines.
Solution
A B2B SaaS that plugs into a platform's existing HR or workforce-management system via REST API, ingests active-worker rosters and monthly earnings data, calculates the correct ESIC and welfare-fund contributions per worker per month, generates the government-mandated XML/JSON filing reports, and pushes them to the e-SHRAM and ESIC portals — with an audit trail and deadline-alert dashboard. V1 covers registration, monthly calculation, and report generation; V2 adds direct UPI-based contribution disbursement.
Why Now
The Code on Social Security 2020 notified the gig-worker provisions in 2021, but state-level enforcement and audits only became aggressive from late 2025 as Rajasthan and Karnataka operationalised their Platform Worker Acts. The 2026 Union Budget allocated ₹200 crore for gig-worker welfare schemes, signalling that central enforcement will follow — creating a hard compliance deadline for 5,000+ gig platforms that have so far been non-compliant.
Target User
First 1,000 customers are mid-size gig platforms in Bengaluru, Delhi-NCR, and Mumbai with 100–10,000 active workers: urban hyperlocal logistics companies, beauty/wellness service aggregators (Urban Company clones), and staffing firms supplying blue-collar gig workers to warehouses and retail. Their HR or finance head is the decision-maker; purchase trigger is a government audit notice or a VC insisting on compliance before the next funding round.
Business Model
SaaS subscription priced per active worker per month: ₹60/worker/month for platforms under 1,000 workers, ₹40/worker/month above 1,000 (volume discount). A platform with 5,000 active workers pays ₹2L/month (₹24L/year ARR). Gross margin is 80%+ — costs are cloud infrastructure and compliance expert time for rule updates. Annual contracts with NACH auto-debit reduce churn and lock CAC economics at less than 2 months of revenue.
Competitive Landscape
- Direct (India): Keka, Darwinbox, and Greytip cover salaried-employee PF/ESIC but have no gig-worker module (different data model — earnings vary monthly, no fixed CTC); SpringVerify does background checks, not social-security compliance
- Direct (global reference): Deel and Remote.com handle cross-border contractor compliance in the US/EU; no India-specific gig-worker social-security analog exists
- Why we win: First-mover in a mandatory compliance category with a narrow, high-urgency problem; integration with e-SHRAM and ESIC portals creates data moats and switching costs since migrating compliance history is painful
6-Month Plan
- Month 1 (₹2L): Hire compliance consultant part-time (ex-ESIC officer); reverse-engineer e-SHRAM API and ESIC filing format; set up cloud infra
- Month 2 (₹2L): Build worker-roster ingestion API, contribution calculation engine, and report generator; internal testing with sample dataset
- Month 3 (₹2L): Alpha with 2 pilot platforms (use existing network); iterate on edge cases (variable earnings, worker exits mid-month, rejoining workers)
- Month 4 (₹2L): Launch to 10 paying customers via LinkedIn and compliance-event outreach; close first annual contracts; implement audit-trail dashboard
- Month 5 (₹2L): Build Keka/Darwinbox/Zoho People integrations for partner-channel sales; reach ₹5L MRR milestone
- Month 6 (₹2L): File patents on calculation algorithm; hire 1 sales person; begin V2 scoping (UPI contribution disbursement)
Risks
- Regulatory complexity fragmentation (High): Each state may pass its own rules on top of the central Code, requiring rapid rule updates — mitigate by hiring a compliance expert full-time by month 4
- Long sales cycles at larger platforms (Medium): Enterprise HR decisions take 60-90 days; mitigate by targeting mid-market first and using penalty-risk framing to compress timelines
- E-SHRAM/ESIC API instability (Medium): Government portals change schemas without notice; mitigate by building a versioned abstraction layer and monitoring filing endpoints daily
Score Breakdown
Market (15/20): ~10M active gig workers on 5,000+ platforms; at ₹60/worker/month, reachable TAM is ₹3,600 crore annually — well above ₹1,000 crore threshold, but realistic 3-year capture is ~₹100-200 crore, scoring mid-range.
Capital (12/15): ₹12L covers 2 devs + 1 part-time compliance consultant + cloud for 12 months; MVP feasible in ₹4-6L; leaves buffer for sales. Scores just below maximum because compliance expert adds cost vs. pure-software play.
Team (7/10): 2 backend devs plus 1 compliance expert = 3 people, ships v1 in 10 weeks. Government portal integration adds complexity over a pure API product, hence 7 not 10.
Trend (13/15): Strong regulatory tailwind — Code on Social Security 2020 enforcement, state-level platform worker acts (Rajasthan, Karnataka), Budget 2026 welfare allocation. Near-max because the deadline pressure is real and imminent.
Moat (13/15): Deep moat: compliance-data switching cost (migrating history is painful), government portal integration know-how, and network of compliance experts building proprietary rule library. Not a 15 because a well-funded payroll incumbent could build this in 6 months if they chose to.
Economics (13/15): 80%+ gross margin SaaS, annual contracts, NACH auto-debit, low churn (compliance tools are sticky). CAC is low via penalty-anxiety-driven inbound. Near-maximum score.
Speed (6/10): Government portal integrations and compliance testing add 4-6 weeks vs. a pure SaaS product; realistic first-paying-user timeline is 10-12 weeks. Scores 6 (between 5 for 12 weeks and 10 for ≤6 weeks).