Last updated: 9 November 2026
Short answerBuy a ready-made ERP when your process is standard, a handful of people will use it and you want to be live soon. Build a custom ERP when a rule that matters to your business does not fit any ready product, when per-user fees would keep growing, or when you must hold the code and data yourself. Most small businesses in India should start with the ready-made option, and some should stay there for good. The middle path is a ready-made core for accounts and stock with a small custom layer for the one part that is unique to you. This page gives a decision table, a 12-point checker, the prices three ready-made options publish (read on 9 November 2026) and a worked example of how the cost curves differ. If you are not sure, tick the boxes first.
This guide is for owners and managers of trading, distribution, manufacturing and service businesses in India who are choosing between a ready-made ERP (Odoo, ERPNext, TallyPrime and similar) and a custom-built one. We are Coded Idea, a software company in Sector 127, Mohali, with 100+ projects since 2020, and we build custom CRM and ERP systems, so we gain if you choose custom. That is why this page also says when you should not. For how a custom ERP is priced, read our ERP implementation cost guide. For our service, see CRM and ERP development.
Your steps are standard, the team is small, you need speed, and someone can set the product up and keep it running.
A rule that matters has no ready equivalent, many users would make fees grow, or you need code, data and hosting in your name.
Accounts and stock are standard but one workflow, portal or machine link is not. Keep the core ready-made and build only that part.
Checker: which way does your business lean?
Tick every line that is true for your business today. The checker counts how many point to a ready-made ERP and how many to a custom build, and shows which way you lean. It is a first lean, not a decision, and it never gives a price. Your answers stay on this page until you choose to send them.
Lines marked Heavy are the ones most likely to rule out a ready-made product.
1. The decision table
| Question | Ready-made ERP | Custom ERP | Mix of both |
|---|---|---|---|
| How fast can you start? | Fastest. You configure, import data and train. | Slowest. Scope, build, test and a parallel run come first. | Middle. The core starts early; the custom part follows. |
| What do you pay first? | Subscription or licence, plus set-up help if you need it. | The build, as a written quote for a fixed scope. | Both, but the custom part is smaller. |
| What do you pay every year? | Per user or per licence, again every year, and it grows with headcount. | Hosting, support and changes. No per-user licence. | The ready part’s fee plus a smaller support bill. |
| How well does it fit your process? | Good if your process is common. Odd rules need configuration or add-ons. | Built around your steps, forms and approvals. | Ready where you are standard, custom where you are not. |
| GST, e-invoicing and e-way bill | Usually part of the product. Ask exactly which features and which edition. | Scope items you must write into the quote and test on the government portal. | Take the ready part’s GST features and build only the extras. |
| Who owns the code and data? | The vendor owns the software. Check data export and where it is hosted. | Agreed in the contract. Make code, data and hosting accounts yours in writing. | Split: ready part is the vendor’s, custom part is agreed. |
| Main risk | You bend your process to the product, or pay for every change. | A long project, and depending on one vendor for years. | Two suppliers to coordinate, and the link between them to maintain. |
2. What three ready-made options publish (read 9 November 2026)
We opened each vendor’s own page on 9 November 2026. These are the figures and conditions they state, for their stated scope. Prices change, scopes differ, and none of this is a quote for your business. We did not test these products; we only report what the pages say.
| Product | What the page says | Conditions the page states | Source |
|---|---|---|---|
| Odoo | Standard plan Rs 580 per user per month (struck-through Rs 725) and Custom plan Rs 1080 per user per month (struck-through Rs 1,350) on the yearly view, with a Light User at Rs 195. The discount is valid for 12 months for the initial users ordered. All plans include support, hosting and maintenance. Standard runs on Odoo Online; Custom can also be self-hosted or run on Odoo.sh and adds Odoo Studio and the external API. | Odoo.sh hosting is not included. The page treats implementation as a separate service, with Success Packs, a project estimator or a partner, depending on company size. It does not state whether tax is included. | odoo.com/pricing, no date shown |
| Odoo India set-up | The India documentation (version 19.0) lists e-invoicing, e-way bill and GST return modules. It says set-up needs a GST suvidha provider (GSP) to be configured, plus API users created on the government e-invoice and e-way bill portals. | The page gives no price for this set-up. Ask what it costs. | odoo.com documentation, version 19.0 |
| ERPNext (Frappe) | ERPNext is described as free and open source, with self-hosting offered. Managed hosting on Frappe Cloud starts at Rs 410 a month for a single site, and the page says you pay for hosting, not per user. It says your cost has two parts: hosting and implementation. | Implementation: the page says you can start with the default setup or hire a Frappe partner for it. Hosting is billed separately from the software. | frappe.io/erpnext/pricing, no date shown |
| TallyPrime (Silver, single user) | Rs 22,500 for a lifetime licence, or Rs 9,000 for 12 months (shown as Rs 8,100 after a 10% discount). Both are shown plus 18% GST. There is also a multi-user Gold edition. | Prices exclude 18% GST. The periodic plans auto-renew until cancelled. | tallysolutions.com, no date shown |
Two things stand out. The cost of getting a ready-made ERP running is mostly outside the headline price: both Odoo and Frappe treat it as separate on their own pages. And the three price models differ in kind: a fee per user (Odoo), a fee for hosting that does not depend on users (ERPNext) and a licence per computer or user (Tally). Which is cheaper for you depends on how many people use it.
3. A worked example (illustrative, not a client and not a quote)
A small distributor that adds users as it grows
Imagine a distributor with one warehouse that starts with 10 ERP users and adds staff over three years. The user counts are made up to show the method. They are not data from any business. The table uses Odoo’s published Standard rate from the section above, for licence fees only.
| Users | Per year at Rs 580 per user per month | Per year at Rs 725 per user per month |
|---|---|---|
| 10 | Rs 69,600 | Rs 87,000 |
| 25 | Rs 1,74,000 | Rs 2,17,500 |
| 50 | Rs 3,48,000 | Rs 4,35,000 |
The sums are users × rate × 12 months. Odoo’s page says the discount is valid for 12 months for the initial users, so the second-year figure may be the higher rate; confirm it with the vendor. The licence is only one line: implementation, data migration, training and any custom add-on come on top, and Odoo’s page lists implementation as a separate service.
How to compare with a custom build. Ask the custom vendor for a written quote B for your scope and a yearly running cost R for hosting, support and changes. Then compare three-year totals: ready-made = licence for three years + implementation + add-ons; custom = B + 3 × R. At a small user count the ready-made product usually has the lower first bill. As the user count climbs, the licence line grows every year while R does not grow with users, so the two lines can cross. Where they cross depends on your quote, which is why we cannot give you a number without a scoping call.
4. When a ready-made ERP is the right answer
- Your process is common. If you sell, buy, stock and invoice the way most firms in your trade do, a product used by many firms has usually already solved it.
- You need to start soon. Configuring a product is quicker than designing, building and testing one.
- The team is small. Per-user fees stay modest for a handful of users.
- You only need accounts and GST. A product built for that job, such as TallyPrime, may be all you need. An ERP can be more than the business asks for.
- You have someone to own it. A ready product still needs a person or partner to set it up, train staff and handle upgrades.
5. When a custom ERP is worth considering
- A rule that matters has no ready equivalent. Examples: batch or serial tracking that follows your own scheme, dealer-wise pricing or approval chains that differ by product.
- The workflow is your edge. If you win customers by how you work, fitting a generic product can remove the advantage.
- The user count will grow. A custom build has no per-user licence, so growth does not raise a licence bill.
- You must connect unusual systems. Machines, a dealer app, a marketplace or a portal that ready products do not connect to are work for a custom integration. See our RPA vs API integration vs AI automation guide for the options.
- You need control. Code, data and hosting in your own name, agreed in writing, give you a way out if you change vendor.
6. When not to hire us
Do not hire a custom build if your process is standard, a handful of people will use the system, you need it running in weeks, and nobody inside your business has time to answer the vendor within a day. In that case buy a ready-made product, use an implementation partner for it, and keep your money. If you only need GST accounting, start with an accounts product. This page does not claim that we resell or implement any product named here. We can help when a ready-made ERP is nearly right and one part is not, and when the gaps are the business itself.
7. Ten questions before you choose
- Which five workflows must work on day one, and has each been tried with our own data?
- What does the ready product cost per year at our user count today and in three years?
- Is set-up and data migration inside the price, or a separate bill?
- Who holds our data, where is it hosted, and can we export all of it?
- Which GST, e-invoicing and e-way bill features are included, and in which edition?
- For a custom quote: what is in the scope, what is out, and how is a change priced?
- Who owns the code, the data and the hosting accounts?
- Who fixes problems after go-live, and how fast?
- Who inside our business will own the project and answer within a day?
- Can we start with a smaller first phase and decide again after it?
For the cost side of a custom ERP, see our ERP implementation cost guide. If your real need is sales follow-up and not back-office control, a CRM may be enough: read the custom CRM cost guide. For the GST e-invoicing rules, check the current position on the official e-invoice portal.
Frequently asked questions
Is a custom ERP better than a ready-made ERP for a small business in India?
Not by default. A ready-made ERP is usually the better start when your process is standard, only a few people will use it and you need to be live soon. A custom ERP is worth considering when you need rules a ready product does not have, when many users would make a per-user fee grow every year, or when you need the code, data and hosting in your own name. Many businesses end up with a mix: a ready accounts and stock core, plus a custom layer for the part that is unique to them.
How do I decide between Odoo, ERPNext, Tally and a custom build?
Write down your five most important workflows and try each of them in a free trial or demo of the ready product, using your own data. If a ready product handles all five with configuration, buy it. If it fails on one that matters, ask what the fix costs, who maintains it after every upgrade, and whether a small custom add-on is enough. Move to a full custom build only when the gaps are central to how you work. The checker on this page gives a first lean, not a decision.
Does a custom ERP cost more than Odoo over three years?
It depends on the number of users, the scope and what you ask the ready product to do. A subscription grows with every user and is paid every year. A custom build has no per-user licence but a larger first bill, plus hosting, support and changes. Odoo’s page treats implementation as a separate service from its per-user price, and Frappe’s page says an ERPNext cost has two parts, hosting and implementation, so compare totals for the same scope over three to five years. We do not publish a price list for custom ERP: you get a written quote after a scoping call.
Does a custom ERP handle GST e-invoicing?
Only if it is built to. In a ready product the GST features are usually part of the package, and you should check which ones with the vendor. In a custom build, e-invoicing and e-way bill connections are scope items that must be written into the quote and tested against the government portal. Check the current rules on the official e-invoice portal and ask your chartered accountant what applies to your turnover.
Want a second opinion on buy or build?
Send us your checker answers and a few lines on your business. We reply with an honest view, including when a ready-made product is the better choice, and a written scope and quote if a custom build fits. Meet us in Sector 127, Mohali, or talk on video from anywhere in India.