Contact Info
How does an ERP selection consultant help Indian companies choose?
An ERP selection consultant runs the decision for you: building a shortlist that matches how big you are and what you make or trade, making each Indian partner demonstrate GST, e-invoicing and e-way bill scenarios on your own data, putting partner proposals on a common basis and checking licensing and contract terms before you sign. I do this remotely from India, with no vendor commissions or referral fees.
Last reviewed by Vikas Saroj
Ask five Indian implementation partners whether their system handles GST, branches and your industry, and you will get five confident yes answers. The difference shows up later, in a demo that skipped the hard cases or a quotation that left out the e-invoicing connector. My role as an ERP selection consultant is to make those differences visible before you commit.
I am based in India, but the work is still delivered remotely: discovery calls, requirement reviews, demo sessions and scoring all happen online, so plants and branches in different states can take part without travel. A visit can be planned by arrangement when a site walk-through genuinely helps.
You end with a written recommendation, the evidence behind it and the open contract questions to close with the chosen partner.
Each step is designed to separate what a platform and its partner can actually deliver from what a sales presentation promises.
I narrow the field to options that suit your scale and processes, from a Tally-centered setup with connected tools to Zoho, Odoo, ERPNext or Dynamics 365 Business Central, with the reasons for each exclusion written down.
Most platforms in India are sold and delivered through partners of very different size and depth. I help you decide which partners to invite and what evidence to ask each one for.
Scenarios that make each partner show GST invoicing, e-invoice generation and cancellation, e-way bills and TDS on your sample data, instead of a polished standard tour.
Quotations arrive per module, per user or per man-day, with annual maintenance quoted in different ways. I put them on one sheet with the same scope assumptions so the numbers can be compared.
User types, edition limits, renewal terms, cloud or self-hosted options and where data will sit, reviewed for each shortlisted option so the running cost and control are clear.
A written recommendation with scores, risks and a runner-up, plus the clauses to settle before signing: scope, customization ownership, support terms and how you get your data out.
Agree what the system must do
Make partners prove fit
Choose and contract with care
There is no single Indian shortlist, because a trading company with one warehouse and a multi-plant manufacturer are solving different problems. I build the shortlist from your requirements, but some patterns come up often enough to describe.
These are starting points, not answers. Each option stays on the list only while it can meet your must-have requirements, and anything removed gets a short written reason. That record matters later, when a promoter or board member asks why a familiar name was not chosen. If you are still unsure whether you need an ERP at all, my ERP evaluation work starts one step earlier.
In India, the partner often shapes the outcome more than the platform. The same software can be delivered by a small team that knows your industry well or by a large firm that staffs the project with juniors. Proposals also arrive in very different shapes, which makes a quick comparison misleading.
Before reading prices, I check that every proposal covers the same scope. Typical gaps I look for include:
I then lay each proposal out against your requirement list, mark what is included, excluded or assumed, and turn vague lines into clarification questions. You see the real difference between partners rather than the difference between their writing styles. My vendor proposal review page describes the method in general terms.
A standard demo shows a clean sales invoice with tax calculated correctly. That proves very little. Indian compliance problems sit in the exceptions, so the scripts I write ask each partner to walk through the cases your accounts team actually handles.
Depending on your business, a script might ask the partner to:
Where a partner demonstrates on a test connection rather than a live one, I record that and ask how the production link is set up and who maintains it. The tax treatment behind each scenario should be confirmed by your chartered accountant; the demo only shows whether the system can carry it out. Scores are recorded per scenario, with notes on what was standard and what needed custom work.
License price is the easiest number to compare and the least useful on its own. During selection I look at how each option is licensed and hosted, because that decides your running cost and how much control you keep.
For subscription products, I check user types, which features sit in higher editions, how prices change at renewal and whether billing is in rupees or a foreign currency. For open-source options such as Odoo Community or ERPNext, the question shifts to who hosts the system, who applies updates and who maintains any India-specific apps. Where data location matters to your business or your customers, I ask each vendor directly where data is stored and what options exist, rather than relying on a brochure.
The contract deserves the same attention. Points I usually raise include:
These points are much easier to settle before signing than after. For a structured view of total cost, see my guide to ERP implementation cost.
Because I am based in India, scheduling is simple: every workshop, demo and review sits inside the normal Indian working day. Even so, the engagement is remote by design. Promoters, finance heads and plant managers in different states can join the same session, recordings let anyone who missed a demo catch up, and scores are kept in one shared workbook visible to every evaluator. If a plant visit or an in-person steering meeting would genuinely help, it can be arranged.
A typical selection moves through a short discovery, a written requirement list, partner invitations, scripted demos, reference calls and a final scoring session with your leadership. I keep the number of shortlisted options small, so each one is tested properly rather than skimmed.
No vendor or partner pays me, whether through commission, referral fee or margin, and I do not sell licenses. That lets me tell you plainly when a cheaper option fits better, or when the honest answer is to fix processes before buying anything. After the decision, I can continue on your side during the build as your ERP implementation consultant in India so the project delivers what the selection promised. For a wider view of my work here, see the India overview or the ERP consultant page for India.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
It can, and sometimes it should. If accounting works well in Tally and the real gaps are in sales, stock or approvals, a connected setup may be cheaper and less disruptive than a full ERP. I score that option against the same requirements as Zoho, Odoo, ERPNext or Business Central, so the comparison is fair rather than assumed.
Usually only a few. Enough to create real competition and a meaningful comparison, few enough that each partner can run a full scripted demo and answer follow-up questions properly. Inviting too many leads to shallow demos and tired evaluators. I help you choose which partners to invite based on platform, industry experience and team size.
No. I take no commissions, referral fees or margins from any vendor or partner, and I do not resell licenses. My fees come only from the client. That is what lets me recommend a smaller partner, an open-source option or no new system at all when that fits your business better.
The work is designed to run remotely, and most selections never need a visit: plant teams join video sessions and share short recordings of their processes. Where seeing a site in person would genuinely improve the requirements or the demo scripts, a visit can be planned by arrangement and agreed in advance.
No. Tax treatment is for your chartered accountant to confirm. I turn their guidance into demo scenarios and scoring criteria, so you can see whether each platform and partner can apply it consistently. Points still awaiting your accountant's view are logged, so they are settled before the contract is signed.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.