The Churn Nobody Talks About
Procurement tech in India has a dirty secret. Monthly churn sits at 8-12%. Enterprise procurement platforms see it worse—15%+ in some cases. Founders know this by month 6. They stay anyway.
Why? Because they've told themselves a story. "Early days," they say. "Product-market fit takes time." But procurement isn't like SaaS distribution software. It's not like HR tech. Procurement is a trust layer masquerading as a tech problem.
The Sunk-Cost Machinery
A founder raises ₹1.5-2 crore. Hires 8-10 people. Builds for 6 months. Launches with 10-15 pilot customers. Sees 40% churn by month 9. What happens next? They don't pivot. They optimize.
They hire a sales person. Then two more. They build custom integrations for one customer—just to keep them. They add reporting features nobody asked for. They attend 50 trade shows. They're running on fumes, not data.
By month 18, they've burned ₹3-5 crore. The cap table is fractured with option grants that make new funding impossible. The team knows it's broken. The founder knows. But they keep going because walking away means admitting they misread the market.
This is the sunk-cost trap. It's not stupidity. It's psychology.
Why Procurement Resists Tech
Procurement officers in India care about three things: compliance, relationships, and speed—in that order. Not in that order of tech elegance.
A procurement officer at a mid-market manufacturer spends 60% of their time on regulatory paperwork. GST filings. Invoice matching. Vendor management. They want a system that removes friction from compliance, not one that looks pretty.
Most procurement tech founders optimize for the wrong problem. They build beautiful dashboards. They add AI-driven supplier recommendations. They integrate with 10 accounting systems. The buyer doesn't care. The buyer needs "does it talk to my tax consultant?"
The signal is brutal. If your platform doesn't solve compliance by month 3, it won't solve anything by year 2.
The Fragmentation Problem
India's procurement landscape is radically fragmented. There are 50,000+ qualified procurement officers. They work in textiles, pharma, manufacturing, agritech, construction. Each vertical has different compliance rules. Different vendor ecosystems. Different buying cycles.
A founder building a national procurement platform is building for 15 different markets simultaneously. Most founders optimize for the easiest vertical (usually manufacturing or pharma), then assume that playbook works everywhere else.
It doesn't.
A procurement app for a textile manufacturer who needs AATF compliance is not the same as one for a pharmaceutical company under DPCO rules. The founder who understands this does 80% of their work hyperlocal—building relationships, understanding specific workflows, tweaking for regulations.
The founder in denial builds a product and expects it to scale.
The India Stack Timing Lens
India's digital backbone—UPI, ONDC, Aadhaar, GST API—created a 24-month window. Procurement tech founders had real tailwinds from 2019-2022. API-first compliance became possible. Open network marketplaces looked viable.
But that window is closing. Buyers have made their choices. Tally, SAP Concur, and regional players own the compliance layer. New procurement platforms now face entrenched adoption curves.
A founder raising money in 2024 for a general procurement platform is betting against 15 years of entrenchment. That's a structural disadvantage, not a marketing one.
The Pivot That Comes Too Late
Most founders pivot after 18-24 months. By then, they've burned through Series A. The team is tired. The board is impatient. The founder is demoralized.
They switch verticals. Or move upmarket. Or add a marketplace layer. None of this matters. They're pivoting with a depleted team and depleted runway. They're optimizing for survival, not for finding the real opportunity.
The founders who win do it differently. They listen at month 2, not month 18. They see the compliance wall and accept it. They build hyperlocal motion into the go-to-market from day one. They raise enough to sustain a 24-month learning cycle—not a 6-month launch cycle.
What This Means For Investors
If you're backing procurement tech, stop asking about TAM. Stop asking about tech elegance. Ask this: "How are you solving the compliance-first problem in your first vertical by month 4?" If the answer is vague, pass. If the answer is "we're building an abstraction layer," pass harder.
Back the founder who understands that procurement is a regulatory problem with a tech wrapper. Not the other way around.