Chaukas — contractor-compliance gate for Indian factories

1. One-liner

Verifies every labour contractor’s PF/ESI/wage proof before a mid-size Indian factory releases their monthly bill.

2. Trend signal — why now?

India’s four Labour Codes were notified 21 November 2025 and enforcement began rolling out from 1 April 2026. The Code on Social Security’s Rule 54 unifies compliance into a single electronic return and standardized digital registers — replacing the old paper-register habit. That’s the “why now”: the register just went electronic, and the principal-employer’s vicarious liability for contractor defaults got restated and sharpened in the same codes.

The liability itself is old but brutal and non-contractual: the principal employer (the factory) is jointly liable when its labour contractor stops depositing PF/ESI, and this liability “cannot be contractually extinguished.” Practitioners on CiteHR describe the exact monthly ritual — “every month, the principal employer should compulsorily verify that the contractor is paying PF… and make this a checkpoint before paying dues on a monthly basis” — and the horror story that follows when they don’t: “Factories have been assessed for two years of unpaid PF on contract workers whose contractor had quietly stopped filing six months earlier.”

Feasibility changed too: cheap OCR + Indic-capable models (Sarvam, ~₹-scale inference) now let you read a messy scanned ECR/ESIC challan and cross-check headcount and amounts against a PO — a validation task that used to need a human auditor.

Provenance:

• Signal 1 (demand): Principal-employer monthly PF/ESI challan verification is a recurring manual headache with severe liability; practitioner discussion + “two years of unpaid PF” assessment story — https://www.citehr.com/618224-ensuring-contractor-pf-deposits-how-do-you.html and https://www.mewurk.com/blog/pf-esic-compliance-india — 2026-07-25
• Signal 2 (feasibility): Rule 54 / Section 123 mandate electronic wage registers + unified digital returns; codes enforced from 1 April 2026 — https://www.india-briefing.com/news/india-dpdp-compliance-timeline-enforcement-2026-27-44740.html (labour-code context) + https://factohr.com/labour-law-in-india/ — 2026-07-25
• Signal 3 (economic): 22-year incumbent Aparajitha/Simpliance serves 1,750+ (large) orgs on custom-quoted retainers for exactly this vendor-compliance audit — money already flows, but only up-market — https://www.aparajitha.com/services/vendor-compliance-services/ — 2026-07-25 Category: Regulatory arbitrage

3. The opportunity

The market splits into two camps and leaves a hole in the middle:

• Enterprise compliance consultancies (Aparajitha/Simpliance, Mynd, TMS, SNG, Talent Compliance) — human-audit retainers, custom-quoted, built for large principal employers with dozens of sites. Aparajitha alone cites 1,750+ orgs. Too expensive and too high-touch for a single 200-worker plant.
• Payroll SaaS (factoHR, SalaryBox) — excellent at running the contractor’s own payroll or the factory’s own staff. They do not solve the cross-vendor problem: collecting, reading, and validating statutory proof from 5–30 independent contractors every month and gating their invoices on it.

The mid-size principal employer — one factory/warehouse/facility, one overworked HR-admin, 5–30 labour contractors — falls between. Today that admin WhatsApps 15 contractors for their ECR + ESIC challan + wage register, eyeballs whether the challan headcount roughly matches the deployed workers, files the PDFs in a folder, and hopes. When a contractor quietly stops filing, nobody notices until the EPFO 7A notice lands — and by then it’s the factory’s rupees. Chaukas is the missing gate: no contractor bill clears until their statutory proof is collected, machine-verified, and green.

4. Target market

• Primary customer: HR/Admin/Compliance manager (often the only such person) at a single-site Indian manufacturing plant, warehouse, logistics hub, facility-management client site, or hospital — ₹5–50Cr turnover, 50–300 contract workers spread across 5–30 labour contractors.
• Why they buy, in their words: “If the principal employer does not ensure that the contractor has paid the ESI/PF, the ESI & PF offices will penalize the principal employer.” They buy to stop being personally the last line of defence with a highlighter and a WhatsApp thread.
• Rough TAM reasoning: India has ~250,000 registered factories plus lakhs of warehouses, FM sites and establishments that engage contract labour. Even a narrow serviceable slice — say 40,000–60,000 mid-size sites that use multiple labour contractors and can’t afford an Aparajitha retainer — at ₹3,000–8,000/mo is a multi-hundred-crore niche. We only need a sliver.
• Why now for them: Codes enforced from April 2026, registers now electronic, inspector-cum-facilitators actively issuing improvement notices. The compliance conversation is live in every plant HR’s inbox this quarter.

5. Product sketch (MVP)

• Contractor roster + monthly checklist: each contractor’s required docs for the month (ECR/PF challan, ESIC challan, wage register, CLRA licence validity, attendance) with due dates.
• WhatsApp-first collection: the tool nudges each contractor on WhatsApp/email, they reply with the PDF/photo; it lands in the right slot automatically. No portal login required for the contractor (the adoption killer).
• AI verification, not just storage: reads the scanned challan, extracts TRRN/period/headcount/amount, and cross-checks: does the PF challan headcount match the contract-worker headcount on-site? Is the period the current month? Does the wage register total reconcile? Flags mismatches and non-filers.
• Invoice-clearance gate: a per-contractor red/amber/green status the finance team sees before releasing the monthly bill. Green = safe to pay; red = withhold.
• Defaulter alert: the moment a contractor skips a filing, HR gets pinged — not six months later.
• Inspection pack: one-click export of the full month’s verified registers, challans and attendance in the shape an inspector-cum-facilitator or 7A notice asks for.
• Recovery trail: logs that you verified before paying, so if a contractor still defaults you have the paper to recover from their bills under Section 8A.

6. AI angle — what’s load-bearing

Remove the AI and this collapses back into a shared folder. The load-bearing work is reading heterogeneous, messy statutory documents — scanned EPFO ECR receipts, ESIC challans, hand-adjusted wage registers, each contractor in a different format — and validating them against expected headcount, period, and amount. That’s OCR + structured extraction + rule-checking, exactly the 2-hour-to-2-minute collapse the operator wants. The verification judgement (does this challan actually cover these workers for this month?) is the product; the storage is table stakes.

7. Localization angle

This is India-first by construction — the entire product is the Indian labour-code / EPFO / ESIC / CLRA regime, WhatsApp as the contractor channel, and rupee pricing that a single plant can expense without a procurement cycle. A generic global vendor-compliance tool cannot serve it; the value is the local regulatory encoding. Indic-language wage registers (Hindi/Tamil/Marathi) handled by Indic-capable models. ₹3,000–8,000/mo tiers work where a $500/mo global tool would never land.

8. Business model — path to $1M–$5M ARR

• Pricing: ₹3,000/mo (up to 10 contractors) → ₹8,000/mo (up to 30) → custom above. Per-site, self-serve, annual discount.
• ACV: ₹60,000 ($720) blended.
• Rough math to $1M ARR: ~1,150 sites × ₹6,000/mo × 12 ≈ ₹8.3Cr ≈ $1M. ~1,150 mid-size plants in a country with 250k factories is a rounding error of the TAM.
• Rough math to $5M ARR: ~5,000–6,000 paying sites, plus an upsell to multi-site groups and a per-verified-document usage tier for high-volume FM/staffing clients. Would need a real inside-sales motion by then, not just founder-led.
• Expansion path: more contractors per site → higher tier; add adjacent statutory verifications (BOCW cess for construction, PT, LWF); a “contractor-side” free app that becomes a distribution wedge (contractors onboarded on one site get pulled to others).

9. Go-to-market wedge — first 100 customers

• CiteHR + plant-HR WhatsApp groups: the exact audience lives on CiteHR and in dozens of “Factory HR / Statutory Compliance” WhatsApp/Telegram groups. Answer the recurring “how do you verify contractor PF challans” threads with a genuinely useful checklist + a free “single-contractor verifier.” Convert.
• Compliance-consultant channel (partner, don’t fight): small regional labour-law consultants who currently do this by hand for 10–20 clients each are the perfect resellers — the tool makes them faster and they bring the trust. Sign 5 consultants → 50–100 sites.
• Industrial-estate cluster sales: MIDC/GIDC/SIPCOT estates cluster hundreds of mid-size plants. Walk one estate, land 3–5 anchor plants, use them as reference for the estate’s HR WhatsApp group.
• The inspection-notice moment: run tightly-targeted content (“got a 7A notice on contract-worker PF?”) — searchers in that moment convert fast and pay immediately.
• Contractor-side viral loop: every contractor onboarded to submit docs for Plant A is a warm lead for Plants B and C they also serve.

10. Build complexity — justification

Medium. The web app, WhatsApp collection, roster and status-gate are standard stack. The real work is the extraction/validation layer across many messy document formats — solvable with off-the-shelf OCR + Indic models plus a rules layer, but it needs iteration on real challans to get precision high enough to trust for a payment gate. No custom model training, no EPFO API dependency required for v1 (verification is doc-vs-expectation, not portal-scraping). Small team, ~4 months to a credible v1.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Compliance-assist tool; no licence needed. Must avoid claiming to file on EPFO’s behalf.
Ethical — no harm / dark patterns	✅	Helps workers actually get PF/ESI deposited; pro-worker outcome.
Market exists (evidence above)	✅	Incumbent retainers, forum pain, hard liability.
1–5 person team can build this	✅	Medium build, no research risk.
Launchable with <$50K / ₹40L	✅	Bootstrappable; main cost is founder time + inference.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Real liability, felt monthly, current workaround is WhatsApp + highlighter. Not quite daily hair-on-fire, but the 7A-notice tail risk is severe.
Demand evidence	15	12/15	Multiple independent signals: retainer incumbents, forum threads, case law, hard penalties. Docked because the mid-size self-serve buyer’s willingness-to-pay is inferred, not yet observed.
Build feasibility	15	11/15	Standard stack + a document-validation layer that needs precision tuning on real challans.
Distribution clarity	15	11/15	Named channels (CiteHR, consultant resellers, industrial estates), but conversion math still estimated.
Revenue mechanics	15	12/15	Pricing sits cleanly between free-folder and enterprise retainer; ACV realistic; $1M path needs only ~1,150 sites.
Time to first revenue	10	7/10	Consultant partners and inspection-moment buyers can pay within 4–8 weeks of a working verifier.
Defensibility	10	5/10	Execution + accumulating contractor-network data + workflow lock-in on the payment gate. Copyable, but incumbents are up-market and slow.
Total	100	74/100

13. Qualitative modifiers

Founder-fit tags

domain-expertise-required · operations-heavy

Key assumptions to validate (3–5)

1. Assumption: Mid-size single-site plants will pay ₹3–8k/mo self-serve rather than lean on a human consultant. How to test: 30 plant-HR interviews across two industrial estates; pre-sell 10 at ₹6k/mo.
2. Assumption: AI verification of scanned ECR/ESIC challans hits precision high enough to gate a payment (few false “greens”). How to test: run 200 real challans collected from consultant partners; measure extraction + mismatch-detection accuracy.
3. Assumption: Contractors will actually submit docs via WhatsApp when the principal employer’s payment is the stick. How to test: pilot one plant with 10 contractors; measure submission rate over two months.
4. Assumption: Small labour-law consultants will resell rather than see it as a threat. How to test: pitch 5 regional consultants; get 2 signed as channel partners.

Risk flags

1. Regulatory drift: state rules and exact register formats vary and are mid-transition under the new codes; the validation logic needs per-state upkeep. Ongoing content cost.
2. Incumbent-down-market risk: Aparajitha/Simpliance or factoHR could ship a self-serve mid-market tier. Head start + focus is the only moat early.
3. Liability optics: must be crisp that Chaukas assists verification and does not assume the principal employer’s statutory liability — a wrong “green” that leads to a penalty is a trust-and-legal risk. Keep it an evidence tool, not a guarantee.
4. Channel dependency: WhatsApp Business API terms and pricing shifts could raise collection costs.

14. Structured verdict

Score:                  74/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Founder with Indian labour-compliance/HR-ops domain depth + one engineer
Time to revenue:        6–10 weeks (via consultant partners + inspection-moment buyers)
Capital to launch:      ₹8–15 lakh ($10–18K)
Top 3 assumptions to validate first:
  1. Self-serve willingness-to-pay at ₹6k/mo — 30 interviews + 10 pre-sells
  2. Challan-verification precision high enough to gate payments — 200 real docs
  3. Contractor WhatsApp submission rate under a payment-stick — one live plant pilot
Kill criteria:
  - Abandon if <8 of 30 interviewed plants will pre-pay after seeing a working verifier
  - Abandon if verification precision can't clear ~95% without unsafe false-greens on real challans
  - Abandon if a payroll incumbent ships an equivalent self-serve mid-market gate before v1

15. Next step — 1-week validation sprint

• Day 1–2: Collect 30–50 real (redacted) contractor challans + wage registers from 3 friendly plant-HRs / one consultant. Hand-run them through an off-the-shelf OCR + model prompt to gauge extraction and mismatch-detection accuracy. Falsifiable target: ≥90% correct extraction, catches every planted “wrong month / wrong headcount” case.
• Day 3–4: Interview 15 plant-HR managers on two industrial estates. Show a clickable mock of the invoice-clearance gate. Ask the money question: “₹6,000/mo to never chase a contractor challan or eat their default again — yes/no, and would you pre-pay?”
• Day 5: Go/no-go. Go only if ≥5 of 15 say they’d pre-pay and the Day-1–2 verifier cleared the accuracy bar. Anything less = the pain is real but the self-serve wedge isn’t proven — revisit as a consultant-tool play instead.