Multi-buyer working-capital cockpit for Indian suppliers that forecasts, routes, and funds approved invoices before cash gaps hit.

1. This is no longer a greenfield category: Mynd acquired C2FO India outright, adding about 100 employees and nearly 140 enterprise clients under one owner.
2. A combined run-rate of about ₹60,000 crore annually means supplier-side workflow software can attach to real financing volume, not pilot spend.
3. With nearly 50% of Nifty50 companies already served, suppliers to large Indian buyers can increasingly expect buyer-led finance programs as a standard part of doing business.
4. Around 200,000 suppliers on C2FO India create enough multi-buyer complexity that a neutral supplier-side operating layer can be valuable on day one.

Catalyst. Mynd's takeover of C2FO India concentrates 140 enterprise clients, about 200,000 suppliers, and roughly ₹60,000 crore of annual financing flow onto scaled digital rails, making a supplier-side orchestration layer newly integrable and urgent.

Supplier Liquidity Cockpit ingests ERP or accounting invoice data, buyer portal approvals, and lender statements to build one cash-eligibility ledger across programs. It shows which approved invoices can be financed today, when future receivables will become eligible, what each option costs, and whether drawing now reduces or worsens the next 13 weeks of liquidity. Finance teams can launch a draw, defer, or split utilization across buyers from one workflow instead of checking multiple portals and calling relationship managers. The first release stays balance-sheet-light: software plus orchestration, not a lender. Over time the company can add automated collections planning, dynamic discount routing, lender routing, and supplier health benchmarks built from cross-program usage data.

What's different. Buyer-led SCF platforms optimize onboarding for the anchor enterprise, while banks optimize yield and risk for one funding line at a time. ERP and accounting systems know the invoice but not the financing menu, eligibility timing, or comparative cost across programs. This company becomes the supplier's neutral control plane across every buyer-led program, and its defensibility compounds through normalized data on utilization, pricing, drawdown behavior, and cash outcomes that no single bank or platform sees alone.

Jobs to be done

flowchart LR
  Buyer[Supplier CFO] --> Pain[Approved invoices trapped across multiple finance portals]
  Pain --> Product[Liquidity cockpit]
  Product --> Outcome[Predictable cheaper cash and fewer missed draws]

Executive takeaways

• India’s receivables-finance rails are no longer early-stage: TReDS financed ₹329.2 billion in May 2026, up 38.1% YoY from May 2025, while Mynd’s acquisition of C2FO India consolidated another buyer-led network with 140 clients and about 200,000 suppliers.[1][2][3]
• Supplier pain remains acute even as rails scale: delayed MSME receivables were still estimated at ₹7.34 lakh crore as of March 2024, and real suppliers report vendor-portal changes resetting collections cycles and trapping cash.[7][8]
• The strongest wedge is workflow neutrality, not a new balance sheet: incumbents optimize a buyer program, a TReDS venue, or a lender stack, but none gives the supplier one cockpit across multiple buyers, approved invoices, and weekly cash plans.[13][14][15][16][18][20]
• Buildability is plausible because GST e-invoicing, Account Aggregators, OCEN, and ERP developer tooling all exist; the gating risk is still practical access to buyer-portal and financier data, especially for write actions.[5][25][26][27][28]

Market definition

This market is not generic lending software; it is supplier-liquidity orchestration for Indian suppliers already operating on approved-invoice financing rails such as TReDS, buyer-led early-pay programs, and bank/NBFC supply-chain-finance lines, but lacking one operating layer for eligibility, cost comparison, and cash forecasting.[2][4][14][15][16]

Customer and buyer

The initial buyer is the supplier CFO, head of treasury, or controller inside organized auto-component and industrial-input firms. ACMA says it represents 1,155 companies and FY25 industry turnover of $80.2B, while ICRA’s tracked sample of 46 auto ancillaries already covers more than ₹3 lakh crore of FY2024 revenue—large enough to support software spend, but still exposed to inventory, freight, and working-capital shocks.[11][12]

Buying triggers

• Winning a new large-buyer contract or absorbing another payment-term extension adds one more approved-invoice workflow and raises short-term cash volatility. [7][8][11]
• Mandatory onboarding of buyers above ₹250 crore onto TReDS expands the number of finance-eligible invoices suppliers must monitor across platforms. [4][15][17]
• Commodity, freight, and inventory buffers in auto components increase the cost of missing low-friction drawdown windows. [11]

Willingness to pay

Pain is close to cash and frequent enough to justify software if ROI is framed against avoided overdraft, fewer missed discount windows, and reduced manual chasing: delayed receivables remain massive, TReDS usage keeps expanding, and buyer-led platforms explicitly position early payment as a cheaper alternative to factoring or borrowing. [6][7][14][29]

Category dynamics

Growth signal 38.1% YoY growth in TReDS financed value (May 2026 vs May 2025)

Validation signals

• TReDS financed value reached ₹329.2B in May 2026 across 152,789 financed factoring units, up 38.1% YoY from May 2025.
• Mynd’s acquisition of C2FO India shows buyer-led SCF distribution is consolidating around scaled local platforms with 140 clients and about 200,000 suppliers.
• CredAble says its platform hosts 100+ corporates, 35+ banks and NBFCs, and 250,000+ SMB borrowers, confirming adjacent demand for working-capital infrastructure.
• ACMA’s 1,155-member base and FY25 turnover of $80.2B provide a concentrated beachhead for vertical go-to-market.
• Treasury teams still report rising expectations, multi-bank complexity, and gaps between desired and actual cash visibility, which supports the cockpit narrative.

Regulatory & technical constraints

• If the product crosses from orchestration into loan intermediation, RBI digital-lending rules limit how an LSP can handle funds and complaints.
• TReDS is formally defined as a digital platform for factoring MSME trade receivables through multiple financiers, so the startup must avoid being mistaken for an unlicensed platform operator or financier.
• Direct GST e-invoice API integration is best suited to taxpayers with internal IT teams and high transaction volumes, which may exclude smaller suppliers at first.
• Account Aggregator data access is consent-based and depends on ecosystem coverage, so AA can enrich reconciliation but cannot be the only data pipe on day one.

Competition fragments into four buckets: buyer-led SCF and early-pay networks (Mynd/C2FO, Taulia), regulated TReDS venues (M1xchange, RXIL), working-capital infrastructure players that sell into banks or corporates (CredAble, Veefin), and treasury/AR systems that improve visibility but not invoice-financing execution (HighRadius and similar suites). The startup only wins if it becomes the neutral supplier control plane across several of those rails at once.[13][14][15][16][18][20][22][30]

Why incumbents do not win by default

• Buyer-led SCF platforms. They win anchor-buyer distribution, but they still optimize a single buyer program at a time; suppliers with several buyers still need a cross-program cockpit.
• TReDS exchanges. They digitize invoice discounting and rate discovery, but they are marketplaces for receivables rather than daily liquidity-planning systems for the supplier CFO.
• Bank and fintech working-capital infrastructure. Infrastructure players help lenders and corporates launch programs, but their orientation is distribution and credit plumbing, not neutral orchestration across competing financing rails.
• ERP and treasury suites. Treasury software can improve visibility, yet it still needs India-specific invoice, AA, GST, and TReDS context to know what financing is actually available on an approved invoice today.

Supplier Liquidity Cockpit should launch as India-first orchestration software for ₹50-250 crore auto-component and industrial-input suppliers that already sell into several listed buyers and juggle multiple approved-invoice financing programs. Mynd's acquisition of C2FO India, the combined reach of 140 enterprise clients and about 200,000 suppliers, and TReDS financed value of ₹329.2 billion in May 2026 show that the financing rails are scaling even as supplier-side workflow remains fragmented. The first customer is a ₹75-200 crore supplier in Pune or Chennai that adds a new OEM contract or accepts longer payment terms and suddenly has one more portal to manage against weekly payroll and raw-material needs. The product should start as a read-heavy cockpit that unifies ERP, statement, and portal data into one eligibility ledger, 13-week liquidity forecast, and best-action recommendation, not as a lender or TReDS operator. Go-to-market should begin with founder-led sales and ERP-integrator referrals around trigger events, with pricing tied to connected programs, financed volume, and measurable savings versus overdrafts or missed discount windows. The beachhead is intentionally narrow because auto-component suppliers offer concentrated buyer networks, repeatable Tally/SAP workflows, and enough working-capital stress to prove ROI quickly. Research models the India-only TAM at about $223M and the initial SAM at $14.6M, so the company must earn the right to expand into adjacent sectors and working-capital products rather than overbuild on day one. The main strategic risk is that buyer portals, banks, or suppliers may not support reliable data access or standalone budget ownership, which would turn the product into services or a partner-bundled feature rather than a software category. The missing diligence item is direct proof that enough target suppliers use two or more rails concurrently and will pay a neutral vendor for orchestration, which keeps the opportunity in Watch territory until pilots prove multi-rail prevalence, data access, and paid conversion.

Problem

• Approved-invoice liquidity is fragmented across buyer-led SCF portals, TReDS venues, and bank lines, so supplier finance teams cannot see what cash is available this week without manual reconciliation.
• Missed drawdown windows force suppliers back to overdrafts or ad hoc discounting exactly when new buyer contracts, longer payment terms, and raw-material purchases increase working-capital strain.

Solution

• A neutral liquidity cockpit ingests ERP, bank-statement, GST, and partner file-feed data to build one eligibility ledger, compare financing options across programs, and forecast the next 13 weeks of cash.
• The first release stays read-heavy and operator-assisted, so customers can act on the best drawdown recommendation without the startup becoming a lender, moving funds, or depending on full portal write access.

Why we win

• Incumbents such as Mynd/C2FO, M1xchange, CredAble, and Taulia optimize one buyer program, marketplace, or lender stack at a time, not the supplier's neutral decision layer across several rails.
• The beachhead shares a concrete workflow and data spine: Tally or SAP invoice exports, bank statements, and recurring approved-invoice decisions tied to a small number of large buyers.
• Each deployment compounds a proprietary dataset on eligibility timing, discount rates, drawdown behavior, and approval-to-cash performance that no single platform or bank sees in full.

Milestones

flowchart LR
  Wedge[Auto-component multi-rail wedge] --> MVP[Read-only liquidity cockpit MVP]
  MVP --> Proof[Paid pilots with captured savings]
  Proof --> Expansion[Partner-led working-capital operating system]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 40% of qualified ICP suppliers already use two or more approved-invoice rails concurrently.
• The first 3 deployments reconcile at least 80% of eligible invoices without scraping or manual rekeying.
• At least 2 banks or platforms permit stable file or API access that keeps onboarding below 30 days.
• Paid pilot to annual production conversion reaches 50%+ because avoided overdraft or captured discounts exceed 3x software cost.
• By month 18, at least 30% of ARR comes from second-program, second-entity, or benchmark-module expansion rather than one-time setup.

Open diligence questions

• How common is concurrent use of two or more approved-invoice rails inside the ₹50-250 crore supplier base?
• Which buyer-led platforms and banks will share approval, pricing, and repayment data without brittle scraping?
• Who actually owns budget when the controller uses the tool daily but the CFO signs the contract?
• How much reconciliation work remains after Tally or SAP, GST, and bank-statement ingestion goes live?
• Does auto components convert faster than industrial, pharma, or construction-adjacent suppliers with similar buyer concentration?

Model sanity

• Revenue engine. Base revenue is mostly a customer-count story: 4 paying suppliers by M12, 18 by Q4Y2, and 55 by Q4Y3, with mature ARPU moving toward the top half of the BP pricing band as usage and expansion attach.
• Must go right. The company must keep onboarding below 30 days through partner data feeds and templates so the 9-FTE base case can absorb the Q4Y2-to-Q4Y3 ramp without crushing gross margin.
• Model breaks if. If sales cycles stretch and blended ARPU falls back toward the research ₹1.5M spend assumption, the downside case ends Y3 at about $0.47M cash and still negative EBITDA.
• Next-round proof. The next financing story is 32 paying suppliers by Q2Y3 with 30%+ of ARR from expansion or usage, partner-sourced pipeline working, and positive EBITDA in H2Y3.

Scenarios

Sensitivity

flowchart LR
  Pipeline[Founder + partner pipeline] --> PaidPilots[Paid pilots]
  PaidPilots --> Production[Production suppliers]
  Production --> Expansion[Second programs + usage fees]
  Expansion --> Revenue[Revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash runway]

Flags: The base case assumes mature customers land near the upper half of the BP annual software range plus usage fees, which is above the research ₹1.5M per supplier-year sizing proxy. · Revenue per FTE remains modest for software because the wedge is low-ACV and onboarding-heavy; partner-led onboarding must keep the business from looking services-like. · Gross margin depends on repeatable file or API access; if portal and financier data stay bespoke, either COGS or headcount will need to rise. · customersEop includes paid pilots in Y1, so true production customer count is slightly lower than the headline paying-customer count until later Y2.

• Portal access risk. If buyer-led SCF platforms or banks do not expose reliable approval and pricing data, the product could collapse into a glorified spreadsheet. Mitigation: Start with ERP plus statement or file ingestion, secure one design-partner platform and bank API, and prove ROI before broadening integrations.
• Incumbent channel squeeze. Mynd, C2FO-style platforms, banks, or ERP vendors could copy basic cockpit features or discourage integrations once the category proves attractive. Mitigation: Own the neutral multi-buyer cash workflow, launch across several funding partners, and build sticky forecast and benchmarking features beyond raw drawdown.
• Weak supplier budget ownership. Suppliers may admit the pain but still expect banks to solve it for free, slowing standalone SaaS adoption. Mitigation: Price against financed volume or interest savings, target suppliers already juggling multiple programs, and sell around new-contract or term-extension events with hard cash ROI.