VendorProof

1. One-liner

Verifies your labour contractors deposited PF, ESI, and minimum wage — before you release their invoice.

2. Trend signal — why now?

India switched on all four Labour Codes on 21 November 2025, consolidating 29 laws and — critically — tightening principal-employer liability for contract labour. If the manpower vendor who supplies your security guards and housekeeping staff underpays them, skips the PF challan, or falls short of the state minimum wage, the company that hired the vendor is on the hook, jointly and severally. Contractual clauses that “put it all on the contractor” do not override statutory liability under CLRA Sections 20–21.

This isn’t theoretical. The standard practitioner prescription now circulating is blunt: “Do not release contractor bills without an ECR and a paid challan, and match employee names with the muster roll,” and “monthly verification of the contractor’s ECR challan against your contract-worker headcount, with the challan filed in your records, not the contractor’s.” One cited case: a factory “assessed for two years of unpaid PF on contract workers whose contractor had quietly stopped filing six months earlier.”

Meanwhile minimum wage moves under everyone’s feet — most states revise the Variable Dearness Allowance twice a year on staggered dates (Delhi 1 Apr / 1 Oct, Maharashtra Jan / Jul, central sphere 1 Apr / 1 Oct). “An employer paying correctly today can fall out of compliance six months later simply because the state notified a revised rate and nobody updated the payroll” — and the vendor’s underpayment becomes your underpayment.

The existing answer is a manual services industry (Aparajitha/Simpliance, TeamLease, MYND, TalentPro) selling retainer-priced vendor audits to large factories. Nobody is selling a cheap, self-serve tool to the mid-market principal employer.

Provenance:

• Signal 1 (demand): Practitioner guidance — “Do not release contractor bills without an ECR and a paid challan… monthly verification of the contractor’s ECR challan against your contract-worker headcount”; cited factory assessed 2 years of unpaid contractor PF — https://futurexsolutions.com/pf-and-esic-mistakes-indian-employers-2026/ — 2026
• Signal 2 (feasibility/economic): Four Labour Codes effective 21 Nov 2025 tighten principal-employer liability; CLRA Sections 20–21 impose direct liability regardless of contract; ₹4.8L penalty cited — https://futurexsolutions.com/contract-labour-compliance-clra-act-india/ — 2026
• Signal 3 (economic): Existing paid vendor-compliance/audit market — Aparajitha “Simpliance Vendor” SaaS + manual audit services position vendor compliance as “the untapped risk area for Indian enterprises” — https://www.aparajitha.com/vendor-compliance-the-untapped-risk-area-for-indian-enterprises/ — 2026 Category: Regulatory arbitrage

3. The opportunity

Every company that outsources security, housekeeping, canteen, or facility staff carries a hidden liability: it must prove, every month, that the vendor actually deposited PF and ESI and paid at least the state minimum wage for the exact headcount deployed on its premises. The proof is a stack of documents — the vendor’s ECR (PF electronic challan-cum-return), the ESIC challan, the wage register, the muster roll, the invoice — that must be reconciled against each other. Headcounts must tie. Wage rates must clear the current state minimum. Deposits must actually be paid, not just filed.

Today this happens one of three ways: (a) it doesn’t, and the company eats a surprise assessment years later; (b) an HR generalist manually eyeballs a PDF pile once in a while; or (c) the company pays a compliance-services firm a fat retainer to do quarterly audits. The incumbents — Aparajitha/Simpliance, TeamLease, MYND — are built for large factories, priced enterprise, and heavy on human consultants. Their tools are checklist-and-workflow shells; a human still reads the challans.

The 10× move: an AI that ingests the vendor’s monthly document pile, extracts every number, cross-checks headcount/wages/deposits against the correct state minimum-wage table, and returns a one-page red/amber/green verdict before the invoice is released — for ₹X per vendor per month instead of a ₹lakh retainer. AI is load-bearing because the inputs are messy, non-standard PDFs from hundreds of small vendors, and the rules are per-state and time-varying.

4. Target market

• Primary customer: The compliance/HR/finance owner (HR manager, plant admin, or “manager – statutory compliance”) at a mid-market principal employer in India — a 200–1,500-headcount office park tenant, hospital, hotel, mall, IT campus, mid-size factory, or facility-management company — that engages 3–30 outsourced manpower vendors (security, housekeeping, canteen, drivers, packers).
• Why they buy: In their words — “when the contractor stops depositing PF, the EPFO comes after us, and we find out two years too late.” They are terrified of a joint-and-several assessment and currently have no reliable way to confirm a vendor’s challan is real, paid, and covers the right headcount before they clear the invoice.
• Rough TAM reasoning: CLRA registration bites at 20+ contract workers. India has well over a hundred thousand establishments above that line (factories, hospitals, hotels, malls, large offices, FM companies). Even a serviceable niche of 30,000–50,000 mid-market principal employers at ₹6,000–₹40,000/mo is a multi-hundred-crore serviceable market. I don’t need the whole thing — a few thousand accounts clears $5M ARR.
• Why now for them: The 21 Nov 2025 codes made the liability sharper and better-known; every labour-law newsletter and their auditor is now warning them about contractor exposure. The fear is fresh and top-of-mind this year.

5. Product sketch (MVP)

• Vendor document inbox: the vendor (or the HR team) uploads the monthly pack — ECR, PF paid-challan, ESIC challan, wage register, muster roll, invoice — as whatever PDFs/photos they have.
• Auto-extraction + reconciliation: pulls headcount, UAN rows, wages, and deposit amounts from each document and cross-checks them against each other and against the invoice.
• State minimum-wage check: validates each worker’s wage against the current minimum wage for that state, skill category, and scheduled employment — with the VDA revision baked in.
• Deposit-actually-paid check: flags “filed but not paid,” headcount mismatches (ECR rows ≠ deployed headcount), and wage shortfalls.
• Red/amber/green invoice gate: a one-page verdict per vendor per month — “clear to pay” or “hold: 4 workers missing from PF challan” — with the exact deficiency spelled out for the follow-up email.
• Evidence vault (Form XII, Form V, registers): keeps the challans and registers filed in your records, timestamped — the exact documentation an EPFO/labour inspector demands.
• Rate-change alerts: notifies when a state you operate in notifies a new minimum-wage/VDA, so you know which vendors need to raise wages next cycle.

6. AI angle — what’s load-bearing

The inputs are non-standard: hundreds of small vendors each produce ECRs, challans, and wage registers in different layouts, quality, and languages, often as scanned photos. Extracting a clean, reconcilable set of numbers from that mess — then judging “does this UAN count match the deployed headcount, is this wage above the current Chhattisgarh unskilled rate, is this challan paid or merely generated” — is exactly document-intelligence + rules reasoning that got cheap in the last 18 months. Remove the AI and you’re back to an HR person squinting at PDFs, which is the status quo I’m displacing. The rules engine (per-state, time-varying minimum-wage tables; PF/ESI deposit logic) is the domain moat; the extraction is the labor-saver.

7. Localization angle

This is the localization play — it exists only because of Indian statute (CLRA, EPF Act, ESI Act, Code on Wages), Indian filing artifacts (ECR, UAN, ESIC challan, Form XII/V), and India’s state-by-state, twice-yearly minimum-wage machinery. Pricing is India-native (₹6,000–₹40,000/mo tiers work where a $500/mo global tool never would). No generic global product can touch it; the entire value is encoded local rules. Distribution leans on Indian channels — CiteHR/HR practitioner communities, compliance-consultant referral, LinkedIn HR groups.

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

• Pricing: tiered by vendor count. Starter ₹6,000/mo (up to 5 vendors), Growth ₹18,000/mo (up to 15 vendors), Pro ₹40,000/mo (up to 40 vendors + multi-location + inspector-ready exports). Roughly ₹1,200–₹1,500 per vendor per month at the margin.
• ACV: ₹1.8–2.4L ($2,200–2,900) blended.
• Rough math to $1M ARR: ~400 mid-market accounts × ₹1.8L/yr ≈ ₹7.2Cr ($870K). Round to ~450 accounts for $1M. Reachable — there are tens of thousands of eligible principal employers.
• Rough math to $5M ARR: ~1,800–2,200 accounts, or fewer accounts + upsell into FM companies and staffing firms who resell VendorProof to their clients as a compliance guarantee. That channel (FM/staffing partners with 50–500 client sites each) is the real $5M lever.
• Expansion path: more vendors per account → multi-location → add adjacent verticals (gratuity/bonus checks, LWF, PT, S&E renewals) → white-label for compliance consultants who currently do this by hand.

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

• Compliance-consultant channel (primary): India’s thousands of small labour-law consultants and CA firms already do vendor audits manually and hate it. Sign 15–20 as resellers/white-label; each brings 5–15 client accounts. This is the fastest path to 100 and doubles as distribution + credibility.
• CiteHR + HR LinkedIn groups: the exact audience (HR/compliance managers) argues about contractor PF liability on CiteHR and in LinkedIn HR-compliance groups daily. Post a free “Contractor Liability Exposure Check” — upload one vendor’s last challan pack, get a red/amber/green report. Lead magnet → paid.
• FM/staffing-firm partnerships: facility-management and manpower-staffing companies want to sell compliance assurance to win contracts. Offer VendorProof as a co-branded “verified compliant” badge across their client sites — one signed FM partner = dozens of principal-employer accounts.
• Targeted outbound: scrape recently-registered principal employers and CLRA-licensed establishments by industrial-area directory; email the plant-admin/HR contact a 90-second Loom showing a real challan being caught as “filed but not paid.” Expect 3–5% reply among the freshly-scared post-code cohort.

10. Build complexity — justification

Medium. Document extraction from ECR/challan/wage-register PDFs runs on off-the-shelf vision+LLM APIs; the web app is a standard stack. The real work is the domain rules engine: a maintained, per-state, time-versioned minimum-wage/VDA table plus PF/ESI deposit and headcount-reconciliation logic, and correctly modeling ECR/UAN/ESIC artifacts. That’s a few months of careful build plus ongoing rule maintenance — hence Medium, not Low. A technical founder with a labour-compliance advisor (or ex-Aparajitha/TeamLease operator) ships a credible v1 in ~4 months.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Helping principal employers meet statutory duties; no PII beyond what employer already holds.
Ethical — no harm / dark patterns	✅	Surfaces underpayment of workers; net-positive for the workers too.
Market exists (evidence above)	✅	Paid manual-audit market + fresh code-driven liability + practitioner prescriptions.
1–5 person team can build this	✅	Doc-AI + rules engine + web app, small team.
Launchable with <$50K / ₹40L	✅	No capex; API + hosting + one domain advisor.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Hair-on-fire for the exposed buyer — surprise multi-year assessments, ₹lakh penalties, personal accountability. Not daily pain (monthly), so not a full 17+.
Demand evidence	15	12/15	Existing paid audit market + explicit practitioner “do not release bills without a paid challan” prescriptions + fresh 2025 code. Strong, but couldn’t pull verbatim buyer quotes (forums JS-gated), so short of 13+.
Build feasibility	15	11/15	Extraction is easy; per-state time-varying rules engine + artifact modeling is real work and needs maintenance. ~4 months.
Distribution clarity	15	11/15	Consultant/FM reseller channel is concrete and warm; outbound is plausible; but reseller-led GTM has a ramp.
Revenue mechanics	15	11/15	Pricing benchmarks against retainer audits; per-vendor unit economics clean; $5M needs the partner channel to fire.
Time to first revenue	10	8/10	Fear is acute and monthly cycle recurs; a compliance consultant can resell within weeks of a working v1.
Defensibility	10	7/10	Moat = maintained per-state rules library + reseller relationships + evidence-vault lock-in. Copyable, but the rules maintenance and channel are a real head start.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

domain-expertise-required · technical-heavy — needs someone who genuinely understands CLRA/EPF/ESI mechanics (or a co-founder/advisor who does) plus doc-AI engineering.

Key assumptions to validate (3–5)

1. Assumption: Mid-market principal employers will pay ₹6K–40K/mo for pre-invoice verification rather than keep eating rare assessments. How to test: 25 discovery calls with HR/compliance managers at 200–1,500-headcount establishments; ask what a surprise contractor-PF assessment last cost them and whether they’d pre-pay to prevent it.
2. Assumption: Compliance consultants will resell rather than see it as a threat to their audit revenue. How to test: pitch 10 small labour-law consultants a white-label deal; measure how many sign an LOI.
3. Assumption: Vendor document packs are extractable at high enough accuracy to trust the red/amber/green verdict. How to test: collect 50 real ECR/challan/wage-register packs and measure extraction+reconciliation accuracy against a human auditor.
4. Assumption: The per-state minimum-wage/VDA table is maintainable by a small team. How to test: build the table for 6 high-density states and time how long a monthly notification-update cycle actually takes.

Risk flags

1. Incumbent-bundling risk: Aparajitha/Simpliance or a payroll giant (Keka/greytHR) could ship a mid-market vendor-verification module. Mitigation: move fast, own the consultant channel, price below their enterprise reflex.
2. Rule-maintenance risk: miss a state VDA notification and you hand a customer a false “green.” Mitigation: notification-monitoring discipline is a core product function, not an afterthought.
3. Document-trust / fraud risk: a vendor can submit a filed-but-unpaid or forged challan. Mitigation: verify against payment status where the EPFO/ESIC surfaces it; flag anything unverifiable as amber, never green.
4. GTM ramp risk: reseller-led distribution is warm but slower than self-serve viral; first-revenue is weeks, but scaling to hundreds of accounts leans on partner enablement.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder + labour-compliance domain advisor (ex-Aparajitha/TeamLease/greytHR type)
Time to revenue:        6–10 weeks (via a reselling compliance consultant)
Capital to launch:      ₹8–15 lakh ($10–18K)
Top 3 assumptions to validate first:
  1. Mid-market principal employers will pre-pay to prevent rare-but-large assessments — 25 discovery calls
  2. Compliance consultants resell rather than resist — 10 white-label pitches, count LOIs
  3. Real vendor doc packs extract+reconcile accurately enough to trust the verdict — 50-pack accuracy test
Kill criteria:
  - Abandon if <5 of 25 discovery-call buyers say they'd pay to prevent contractor exposure
  - Abandon if extraction+reconciliation accuracy on 50 real packs stays below ~90% after tuning
  - Abandon if a payroll incumbent ships an equivalent mid-market vendor-verification module before your v1

15. Next step — 1-week validation sprint

• Day 1–2: Line up and run 12–15 discovery calls with HR/compliance managers at mid-market principal employers (offices, hospitals, malls, factories). One question decides it: “What would a surprise contractor-PF assessment cost you, and would you pay ₹X/mo to catch it before you release the invoice?” Also DM 10 labour-law consultants about white-labeling.
• Day 3–4: Collect 20–30 real vendor document packs (ECR, challan, wage register, muster roll) from 2–3 friendly companies or a consultant. Run them through an off-the-shelf doc-AI + a hand-built 3-state minimum-wage table. Measure: can I correctly flag the headcount mismatches and wage shortfalls a human auditor finds?
• Day 5: Go / no-go. Go only if ≥40% of buyers say they’d pay and the prototype correctly catches the deficiencies in ≥90% of the 20–30 packs. Otherwise, re-scope (e.g. narrow to a single vertical like hospitals) or shelve.