Most Indian businesses run on Tally, then outgrow it, then face a choice: buy a bigger product such as Zoho, Odoo, Busy or SAP Business One, or have an ERP built around how the business actually works. Both routes can be right. Both are sold by people with an interest in one answer. This is the comparison we give clients before they decide, including the cases where we tell them not to build.
What "off-the-shelf" covers
The products a mid-size Indian company is usually choosing between fall into three bands.
- Accounting-first tools. Tally, Busy, Marg. Excellent at GST, invoicing and books. Thin on operations such as multi-godown stock, production, dispatch or field sales.
- Cloud suites. Zoho, Odoo and similar. Broad module coverage at a per-user monthly price, configurable within limits, with a marketplace of add-ons.
- Mid-market ERPs. SAP Business One, Microsoft Dynamics Business Central and the like. Strong, mature, expensive to licence and to implement, and usually sold through a partner who does the configuration.
A custom ERP is a system written for you, owned by you, and shaped by your process rather than the vendor's idea of a generic company. It might cover everything or only the operational part, with Tally still doing the books.
What "custom" does not mean
Custom does not mean starting from a blank page. A competent team builds on established frameworks, reuses tested modules for logins, roles, audit logs, GST invoice formats and reports, and sometimes starts from an existing product base and changes the parts that are specific to you. Our own RightSutra modules are often that base. What is custom is the process: your order flow, your scheme logic, your costing, your screens. That is where the time and money go, and it is why a custom quote should be itemised by module rather than given as one round figure.
The comparison
| Factor | Off-the-shelf | Custom ERP |
|---|---|---|
| Time to first use | Days to weeks | Typically 3–6 months to first module |
| Upfront cost | Low to moderate; licence plus setup | Higher; roughly ₹3–12 lakh for an MSME ERP |
| Ongoing cost | Per-user licence every month or year, forever | Hosting plus a support contract; no per-user fee |
| Fit to your process | You adapt to the software | The software adapts to you |
| Changing it later | Limited to configuration and add-ons | Anything, at development cost |
| Who owns the data and code | Vendor owns the product; you can export data | You own both |
| Support | Vendor or partner help desk | The team that built it |
| Risk of vendor disappearing | Low for large vendors | Real; insist on source code and documentation |
| GST, e-invoicing, statutory | Kept current by the vendor | Must be maintained, or left to Tally |
Where off-the-shelf wins
Your process is ordinary. A trading company buying, stocking and selling standard goods, a service firm invoicing by the hour, a single-location retailer. The generic model fits, and paying to rebuild it would be waste.
You need it next month. A cloud suite can be live in weeks. Custom work cannot.
Statutory compliance is most of the job. GST returns, e-invoicing, e-way bills and TDS change every year. Tally and its peers absorb those changes for you. We nearly always recommend keeping accounts on such a product even when the operations system is custom.
You have fewer than ten users and no operational complexity. The per-user licence is cheap at that scale and the fit is good enough.
Where custom wins
Your process is your advantage. A manufacturer with a particular way of costing jobs, a distributor whose scheme and credit logic is more complicated than any product handles, a cold-storage operator, a college with a fee structure nobody else has. Forcing that into a generic product means daily workarounds, and workarounds mean Excel, and Excel means the ERP is not the truth any more.
Per-user licences would run into lakhs a year. A business with 60 field staff, godown workers and counter staff who each need a login pays that multiplied every month on a cloud suite. A custom system has no per-user fee, so the maths flips somewhere between 20 and 50 users, depending on the product.
The product's mobile experience is poor for your staff. Cloud suites are designed for office desktops. If your users are dispatch staff on a ₹8,000 Android phone in a godown with weak signal, a screen built for exactly that job, in Marathi or Hindi, will be used; a generic app will not.
You need hardware in the loop. Weighbridges, barcode scanners, RFID gates, IoT sensors, biometric attendance. Products can sometimes be integrated; custom systems are built around it.
You have already tried to configure a product and failed. This is the most common reason clients come to us. They bought a suite, spent a year and several lakh on partners configuring it, and still run the real business on Excel.
Total cost of ownership over five years
The upfront figure is the least useful number. Compare five-year cost.
For a cloud suite with 30 users at roughly ₹1,500 per user per month, licences alone are about ₹5.4 lakh a year, or ₹27 lakh over five years, before implementation, add-ons and the partner's fees for changes. Prices vary widely by product and plan, so use your own quote.
For a custom MSME ERP at roughly ₹6 lakh to build, plus hosting of a few thousand rupees a month and a support contract of perhaps 15 to 20 percent of the build cost per year, the five-year figure is roughly ₹11 to 13 lakh, and it does not rise when you add users. Every figure here is an estimate and the real number depends on scope. The point is that the comparison changes completely once you count the years after go-live.
The custom route carries costs that do not appear on the invoice: your time in requirements meetings, the risk of a vendor who disappears, and the fact that statutory changes are your problem. Price those honestly.
A hybrid that usually works
The pattern we see succeed most often in Indian MSMEs is a split.
- Accounts, GST and statutory on Tally or a similar product, maintained by the vendor.
- Operations, the part that is specific to the business, on a custom system with mobile entry.
- A one-way or two-way sync so invoices, receipts and stock values flow into accounts without retyping.
This keeps the compliance burden with people whose job it is, and puts the custom money where the business is different. The sync between the two is the item most often missing from quotes, so ask for it explicitly: which records flow, in which direction, how often, and what happens when an entry is edited on one side after it has already crossed to the other. Our guide to ERP for small manufacturers goes into the module-by-module detail, and our cost guide for custom software in India explains what drives the price.
Questions to ask before you decide
- Write down the ten things your staff do most often. Can the product do each one in fewer clicks than the current way? Try it, do not take the demo's word.
- What does it cost with the number of users you will have in three years, not today?
- If you build, who owns the source code, and is it documented well enough for another developer to take over?
- If you buy, what happens to your data if you leave? Can you export everything, in a usable format?
- Who supports it after go-live, at what response time, at what price?
- How does it work on the phones your staff actually carry, on the connectivity you actually have?
Where SailRight fits
We build custom ERP and business software for businesses whose process does not fit a product, and we tell clients plainly when we think they should buy instead. Our RightSutra suite is our own product for billing, stock, payroll and analytics when a ready system is the better answer. Tell us what you run today and we will say which route we would take.
- ERP
- Custom software
- Tally
- Zoho
- Total cost of ownership
- MSME