The Custom Integration Problem: Why Indian Enterprises Overpay for Software That Doesn't Quite Fit
There is a particularly painful pattern in Indian enterprise technology adoption. A company reaches a certain size — typically ₹50 crore to ₹500 crore revenue — and decides it needs a serious ERP. The selection process runs for six months. A major vendor (SAP, Oracle, or a mid-market equivalent like Microsoft Dynamics or Ramco) is selected. Implementation begins.
Two years later, the ERP is live. It handles the standard financial workflows adequately. But the specific approval hierarchies that reflect the company's ownership structure are kludged together in a workaround. The GST treatment for the multi-entity holding structure required a paid customization. The payroll module does not handle the specific combination of statutory compliance requirements applicable to the manufacturing facility in one state and the services subsidiary in another. And nobody has figured out how to connect it to the WhatsApp-based vendor communication workflow that is embedded in how the operations team actually works.
The result: a ₹2–5 crore ERP investment that solves 60% of the problem and creates a permanent population of workarounds for the other 40%.
This is not unusual. It is the majority experience of mid-market Indian enterprise software adoption.
Why Global Off-the-Shelf Software Fails at the Indian Last Mile
Global enterprise software platforms are built on assumptions derived from their largest markets — primarily the US and Western Europe. These assumptions are embedded in the software's data model, workflow logic, and compliance modules.
Several of these assumptions break down in the Indian context:
Multi-entity corporate structures: Indian business groups frequently operate through complex holding structures — a promoter-controlled holding company, multiple operating subsidiaries, sometimes a separate trading entity for each major product line. The intercompany transactions, shared service cost allocations, and consolidated reporting requirements for these structures are far more complex than the standard ERP assumes.
TDS and GST compliance nuances: India's tax regime is sophisticated and constantly evolving. TDS deduction rates vary by transaction type, vendor category, and threshold. GST involves multiple rates, HSN classification requirements, RCM applicability, and e-invoicing mandates that apply differently to businesses of different sizes. Global ERPs require significant paid customization to handle Indian-specific compliance — and these customizations frequently break when regulations change.
Approval workflows in relationship-based organizations: Indian businesses — particularly family-run enterprises — have approval dynamics that do not map to standard organizational hierarchy charts. The promoter's approval may be required for transactions above a certain value regardless of what the formal org chart says. Certain vendors may have relationships that require a specific person to approve, independent of their position. Encoding these dynamics in a rigid ERP workflow requires custom development.
Regional language and format requirements: Business communications, vendor contracts, and customer invoices frequently need to be produced in regional languages alongside English. Standard global ERPs have limited support for Devanagari and other Indian scripts in document templates.
Cash transaction and UPI integration: Despite India's digital payments revolution, many SME and MSME transactions still involve cash or informal payment arrangements. More significantly, UPI has created a payments behavior — instant, mobile-first, with reference tracking — that global ERP payment modules were not built to handle natively.
The Real Cost of Workarounds
When enterprise software does not quite fit, the gap is filled by workarounds. And workarounds have costs that persist for as long as the software is in use.
Shadow spreadsheets: Teams maintain parallel Excel files for the data the ERP does not capture correctly. These files require manual maintenance, are not auditable, and inevitably drift from the ERP data over time — creating reconciliation events that consume significant finance team time.
Custom scripts and integrations: Technical staff (or expensive consultants) write scripts to move data between systems, transform formats, and fill data gaps. These scripts break when either system is updated. Maintaining them requires ongoing technical capacity — which the company may or may not have internally.
Tribal knowledge bottlenecks: Over time, specific individuals become essential because they understand the workarounds. "Ask Priya — she knows how to enter this type of transaction correctly." When Priya leaves, the institutional knowledge leaves with her. Onboarding new finance team members requires weeks of informal knowledge transfer that is never fully captured.
Audit and compliance risk: Workarounds that exist outside the main system are invisible to auditors. Financial data that passes through Excel before entering Tally creates an audit gap. Custom scripts that move data between systems create questions about data integrity. The workarounds that solve operational problems create compliance problems.
The cumulative annual cost of workarounds for a mid-market Indian enterprise — in staff time, consultant fees, error correction, and audit risk — often exceeds the original software licensing cost. The ERP that cost ₹3 crore to implement costs another ₹1–2 crore per year to maintain in its imperfect state.
What API-First, Composable Platforms Enable
The alternative to monolithic ERP is not no system — it is a composable system built on an API-first platform.
An API-first platform is one that exposes its data and functionality through well-documented, stable APIs — allowing any integration, any workflow, and any external tool to connect with it. Instead of buying a system that does everything, you build an ecosystem of components that do specific things excellently and connect them.
For Indian businesses, composable platforms enable:
Indian-specific compliance modules that actually work: Instead of customizing a global ERP's tax module to handle Indian GST and TDS, you integrate a purpose-built Indian compliance module (like ClearTax for GST filing or a local payroll provider for PF/ESIC) via API. These modules are built specifically for Indian compliance, updated when regulations change, and maintained by specialists.
Workflow customization without code: Modern platforms (including Akritra) allow business users to define approval workflows, automation triggers, and integration rules through configuration rather than custom development. The promoter's approval requirement for transactions above ₹5 lakh is a workflow rule, not a customization project.
Native integration with India-stack infrastructure: UPI, Aadhaar-based verification, DigiLocker document retrieval, GSTN validation, and e-invoicing APIs are all part of India's digital infrastructure. An API-first platform can connect to these natively — delivering capabilities that global ERPs require expensive customization to achieve.
Future-proof adaptability: When WhatsApp releases a new business messaging API, when GSTN introduces a new compliance requirement, when a new payment method emerges — an API-first platform can integrate the new capability in days rather than months. The monolithic ERP requires a customization project and a deployment cycle.
The Shift: From Buying Software to Assembling Operational Stacks
The most forward-thinking Indian enterprises are not asking "which ERP should we buy?" They are asking "what capabilities do we need, and what is the best combination of purpose-built components to deliver them?"
This is not just a technology question. It is a strategy question. The answer shapes how quickly you can adapt to regulatory changes, how much you pay in implementation and maintenance, and how resilient your operations are to the inevitable changes in both your business and the technology landscape.
Akritra's approach to this is deliberate: a core platform that handles the end-to-end business operations workflow natively, combined with an integration layer that connects to external systems via API — with custom integration capabilities available for enterprise clients with specific workflow requirements.
The era of the single, expensive, imperfect ERP is not over. But for businesses that want operations that actually fit how they work, the composable alternative is increasingly compelling — and increasingly accessible.
The ceiling that complex, bespoke ERP implementations seemed to require is coming down. The floor — in terms of what a purpose-built platform delivers out of the box for an Indian business — is rising. The distance between them is where the opportunity is.