ERP Platforms technologies
ERP platforms,and when to build instead.
We implement and integrate these, and we'll tell you when one of them beats a custom build.
Implementing an existing ERP is usually cheaper and faster than building one. We recommend custom only when your operating model is genuinely your advantage, or when the standard product's gaps would force daily manual work.
What we use
And why we picked each one.
Odoo
Modular open-source ERP.
WhyStrong coverage across sales, inventory, accounting and manufacturing. Frequently the right answer for a conventional SME.
ERPNext
Open-source ERP built for Indian businesses.
WhyGST handling out of the box and no licence cost. Genuinely underrated for Indian manufacturing and trading.
SAP
Enterprise ERP.
WhyWe integrate with it rather than implement it. Where you already run SAP, we build the surrounding systems that talk to it.
Dynamics 365
Microsoft's ERP and CRM suite.
WhySensible where you're already committed to Microsoft licensing and Azure.
Tally
The dominant Indian accounting system.
WhyWe integrate with it on nearly every ERP project. Replacing Tally is rarely worth the retraining — syncing to it usually is.
Zoho
Integrated business application suite.
WhyExcellent value for small businesses. We build the integrations and customisations around it.
How we choose
Four criteria, in this order.
Fit
Does it solve your actual problem, or a more interesting one?
Hiring pool
Could you hire for it in India if you took the project in-house?
Total cost
Licences, hosting and the operational time to run it — not just build cost.
Exit risk
How hard would it be to leave? We don't build things you can't walk away from.
Services
What we build with it.
Odoo if your processes are broadly conventional — it's faster and cheaper, and we'll say so. Custom when your operating model is your advantage, when licence costs scale painfully, or when the gaps force daily workarounds.
Yes, through standard interfaces and middleware. Most of our SAP work is building the systems around it rather than changing SAP itself, which is usually the pragmatic path.
No, and usually you shouldn't. Keep Tally for statutory accounting — it's genuinely good at that — and sync operational transactions across.