An ERP touches purchase, stores, production, sales, accounts and GST compliance at the same time. Pick the wrong partner and you lose more than the project fee. You lose a year of management attention and a good deal of staff goodwill. This guide sets out how to choose an ERP software development company in a structured way: decide what you are actually buying, score vendors on evidence rather than demos, ask the questions that expose weak partners, and sign a contract that protects your data and your code.
If a custom-built system is on your list, our ERP software development services page explains how we run discovery, phasing and go-live. The checklist below works for any vendor, including us.
Step 1: Decide whether you need a custom ERP at all
Before comparing vendors, compare options. Some businesses approach custom developers when a packaged product would serve them better. Others force a package onto processes it was never designed for. Use this as a rough fit guide:
| Option | Usually fits | Watch out for |
|---|---|---|
| TallyPrime with add-ons | Traders and small manufacturers whose needs centre on accounting, GST, simple inventory and a handful of users | Limited approval workflows, field access and multi-plant production planning; deeper changes depend on TDL developers |
| Odoo or a similar open-source ERP | Businesses with fairly standard processes that are willing to adapt to the software, with a capable implementation partner | The enterprise edition is licensed per user; heavy customisation makes version upgrades costly; GST localisation quality varies by partner |
| SAP Business One, S/4HANA and other large suites | Larger or multi-entity organisations with budget for licences, certified partners and longer rollouts | High licence and implementation cost; change requests are slow and expensive |
| Custom ERP | Processes that give you an edge or do not fit packages, heavy integration needs, or large user counts where per-user licences hurt | Higher upfront cost and full dependence on the quality of your development partner |
A common middle path is to keep accounting in Tally and build custom modules around it for orders, production, dispatch or field service, connected through an integration. If custom or hybrid looks right, the rest of this guide is for you. For budgeting, our guide to custom software development cost in India gives typical ERP ranges and the factors behind them.
Step 2: Build a shortlist of three to five vendors
Look for firms that have built ERP or ERP-like systems for businesses of your size and industry, not only websites or apps. Useful sources are peers in your industry association, your chartered accountant (who sees many systems at many clients), and vendors whose material shows real workflows rather than stock screenshots.
Write a two-page brief before the first call: business goals, number of users by department, current tools, must-have integrations and your rough budget band. Vendors who respond to the brief with specific questions are worth meeting. Drop anyone who cannot show you a working system, with realistic data, within the first two meetings.
Step 3: How to choose an ERP software development company with a scorecard
Demos reward the vendor with the best presenter. A weighted scorecard forces the decision onto evidence. Score each vendor from 1 to 5 on each row, multiply by the weight, and add up. Adjust the weights to suit your business, but agree them before the first demo so the scoring stays honest.
| Criterion | Weight | What good looks like | How to verify |
|---|---|---|---|
| Process and industry understanding | 20% | Asks how you work before talking technology; understands GST, e-invoicing, e-way bills, and batch or serial tracking in your sector | The quality of their questions in the first meeting; a walkthrough of a similar module they have built |
| Discovery and documentation | 15% | A structured discovery workshop, process maps, and a signed-off scope with acceptance criteria | Ask for a redacted sample scope or requirements document |
| Architecture and integrations | 15% | A clear technology stack, documented APIs, and experience with Tally, GST e-invoicing, payment gateways and WhatsApp | An architecture diagram for your project; a demo of a live integration |
| Data migration and go-live plan | 10% | Trial migrations, reconciliation reports, a parallel run and a cut-over checklist | Ask for their migration plan template |
| Security and quality | 10% | Code reviews, automated tests, security testing before go-live, a documented information security process | Certificates such as ISO/IEC 27001; a sample test or VAPT report |
| Team and continuity | 10% | A named in-house team, little reliance on subcontractors, documentation that survives staff changes | Meet the actual project lead and senior developer |
| Commercials and contract | 10% | Milestone payments, clear change-request rates, source code and IP ownership | Review their standard contract before final pricing |
| Support and SLA | 10% | Response and resolution times by severity, a defined warranty period, a sensible annual support fee | The SLA document; a reference call with a client in their second year or later |
A vendor that scores below 3 on process understanding or data migration should usually be dropped, whatever its total. Weaknesses in those two areas are the hardest to fix once the project is underway.
Step 4: Ask questions that reveal how a vendor really works
Use open questions and listen for specifics. A vague answer is information too.
About your business
- How would you run discovery for us? Who do you need from our side, and for how many hours?
- Which of our processes would you change rather than automate as they are?
- What would you put in phase one, and what would you leave for later?
About delivery
- Who exactly will work on our project, and are they employees or subcontractors?
- How often will we see working software? Two-week sprints with a demo are a good sign. A single demo near the end is not.
- How do you handle a change in requirements in the middle of a phase?
- How will you migrate our masters, open orders, stock and outstanding balances, and how will we verify the numbers?
About ownership and support
- Who owns the source code and the database design, and when do we get repository access?
- What does annual support cost after the warranty, and what does it include?
- What happens if we later move support to another vendor or an in-house team?
- How do you keep the system current when GST rules or e-invoice schemas change?
Red flags to watch for
- A firm price before discovery. A vendor who fixes an ERP price after one call has either padded it heavily or plans to recover the difference through change requests.
- "Our ERP is ready, we only customise it", with no clarity on licensing. Ask whether you are buying a licence, a customisation or ownership. These are very different things.
- No access to the code until the end of the project, or none at all.
- Large advance payments not tied to delivered, working modules.
- No data migration plan, or a plan that only says the client will provide data in the vendor's Excel format.
- No test environment separate from production.
- Stale references, or no client who is still using the system today.
- Everything promised in phase one. An honest partner pushes back on scope.
Step 5: Contract points that protect you
Most ERP disputes trace back to something the contract left vague. Make sure yours covers these clearly.
- IP and source code ownership. The contract should assign the source code, database design and documentation to you on payment, with access to a repository you control during development. If the vendor builds on its own framework, get a perpetual licence to that portion.
- Source code escrow. Where the vendor keeps ownership of a core product, ask for the code to be deposited with a neutral escrow agent and released to you if the vendor shuts down or stops supporting it.
- Scope and acceptance criteria. Attach the signed scope document. Define how each module is accepted and what counts as a defect rather than a change.
- Data migration. List what moves (which masters, how many years of transactions, opening balances), who cleans the data, how many trial runs happen and who signs off the reconciliation.
- Parallel run. Run the old and new systems side by side for at least one period close, usually a month-end, and reconcile stock and ledger balances before switching off the old system.
- SLA and warranty. Define severity levels with response and resolution times, a warranty period during which defects are fixed at no charge, and the annual support fee after that.
- Change requests. State the hourly or daily rate and the approval process.
- Exit and transition. Require handover of code, credentials, documentation and a database export in a usable format if the relationship ends.
- Confidentiality and data protection. An NDA, plus clear obligations on handling personal data in line with the Digital Personal Data Protection Act.
A realistic selection timeline
For a mid-sized business, a careful selection takes four to eight weeks:
- Weeks 1–2: write the brief and build the shortlist.
- Weeks 2–4: first meetings and demos, using the questions above.
- Weeks 4–6: paid discovery with your top one or two vendors, scoring and reference calls.
- Weeks 6–8: proposal comparison, contract review and kick-off.
Paying two vendors for discovery costs a little more up front, but it is the best preview you will get of how each one behaves once the real project starts. Knowing how to choose an ERP software development company is mostly about this: judging partners on what they do, not on what they promise.
How we answer this checklist at EthicsComputer
For transparency, here is where we stand on the points above. EthicsComputer is certified to ISO 9001:2015, ISO 20000:2018 and ISO/IEC 27001:2022, and is MSME Udyam registered. Every ERP engagement starts with a discovery workshop, followed by a fixed-scope proposal or a dedicated team. We deliver in two-week sprints, hand over 100% of the source code and IP to the client, and run in-house VAPT before go-live. Integrations with Tally, payment gateways and WhatsApp are built by our API development team.
FAQs
How long does it take to choose an ERP development company?
For a mid-sized business, four to eight weeks is realistic. That allows time for a written brief, demos with three to five vendors, paid discovery with the top one or two, reference calls and contract review. Rushing the selection usually costs more time later in rework.
Should I choose a custom ERP or a packaged ERP like Odoo or SAP?
Choose a packaged ERP if your processes are fairly standard and you are willing to adapt to the software. Choose a custom ERP when your processes give you a competitive edge, need heavy integration, or when per-user licence costs grow too high. Many Indian businesses use a hybrid: Tally for accounts plus custom modules for operations.
What should an ERP development contract include?
At minimum: source code and IP ownership, repository access during development, a signed scope with acceptance criteria, a data migration plan, a parallel run before switch-over, an SLA with severity levels, a warranty period, change-request rates, and exit terms covering handover of code, credentials and data.
What is source code escrow and do I need it?
Source code escrow means the vendor deposits the code with a neutral third party, which releases it to you if the vendor closes down or stops supporting the product. You need it when the vendor keeps ownership of the core software. If the contract already assigns the full source code to you, escrow is usually unnecessary.
Why is a parallel run important in an ERP go-live?
Running the old and new systems side by side for at least one period close lets you compare stock, receivables and ledger balances before you depend on the new system. It catches migration and configuration errors while you can still fall back to the old one.
Talk to us
If you are shortlisting partners for a custom or hybrid ERP, we are happy to be scored against this checklist. See how we approach custom ERP software development, or book a discovery call with our team.
