Should you build a custom ERP or use a SaaS ERP?

This question usually arrives when billing sits in one tool, stock in a spreadsheet and approvals on WhatsApp, and nobody agrees on the numbers. Something has to become the one system.

MyFloww builds custom ERPs, so read this knowing that — and knowing that for a business with ordinary processes, a packaged product is usually the better answer.

What an ERP actually has to do

Start with the jobs, not the products. Most small and mid-sized Indian businesses need a handful of these done well, not a full suite.

Inventory

Stock by item, batch and location, with reorder levels and the awkward states: goods on approval, in transit between godowns, or lent to a branch.

Purchase and sales orders

Purchase orders and goods received against them; quotations, orders, part dispatches and delivery paperwork.

GST-compliant invoicing

Invoices and credit notes with tax details per item and customer, the reports returns are filed from, and e-invoices and e-way bills where your turnover or the movement of goods requires them.

Accounts

Either the ledger itself, or clean entries handed to the system finance already closes the books in. For many Indian businesses that is Tally, and it is staying.

Production and job work

Bills of materials, work orders, and material sent to job workers and received back, which has GST paperwork of its own.

Approvals, locations and reports

Discounts and purchases above a limit routed for sign-off; stock per branch, with transfers recorded; margins and receivables from one set of numbers.

The packaged and SaaS options, described plainly

Names you are likely to meet on a shortlist. None is a bad product; the question is what it would take to make each fit you.

The customisation trap

The expensive mistake is rarely the wrong product. It is choosing a packaged ERP for speed, finding it does not fit, and paying a partner to customise it until it does.

Customisations are code inside a product the vendor keeps changing, so every upgrade means checking and often rewriting them. Businesses either pay for that each time or stop upgrading, and a frozen ERP falls behind on compliance changes. You pay for a licence and a custom build at once, and own neither. The signs:

• Spreadsheets have grown back around the ERP for the cases it cannot handle.
• Upgrades are postponed in case the customisations break.
• Only one consultant knows how the system is set up.

The rule is configure, do not customise. If a packaged ERP fits through its own settings and workflows, it is probably the right one. If it fits only after custom code, judge that code as what it is: a custom build.

The three-year sum, with your own numbers

SaaS ERPs are commonly priced per user, per module or by edition, with implementation charged separately. Do the sum yourself:

1. The per-user monthly price of the plan with every module you need, not the cheapest plan.
2. Times the logins you will need in three years — the counter, the godown and the branch managers, not just accounts.
3. Times thirty-six.
4. Plus implementation, data migration, training and customisation, each quoted in writing.

Compare that with a custom build quoted in phases, plus three years of hosting and the changes real use brings. For a small team with standard processes the subscription often wins; that is why you do the sum.

Who owns the data, and how it leaves

With a SaaS ERP your data leaves in the vendor's export formats, so before signing, see a complete export, transactions included, and ask what happens to the data if you stop paying. With a custom ERP the database and the code should be yours; check that the agreement says so. Either way, migrating opening stock and open balances is real work, and how clean they are decides how long it takes.

The hybrid path: keep Tally, build around it

For many Indian businesses the gap is not in the accounts: Tally already closes the books, and the accountant is quick on it. What is missing is everything before an entry reaches the ledger — orders, stock across godowns, job work, approvals, dispatch and each customer's credit.

The hybrid route builds that operational layer and nothing else. It owns the workflow and hands clean, reconciled entries to the accounting system, whether that is Tally or Zoho Books, and never tries to become a second ledger: two sets of books that disagree are worse than the problem you started with.

When a SaaS ERP clearly wins

• Your processes are standard: buy, hold stock in one or two places, sell and invoice.
• You need it running this month.
• Your team is small and will stay small.
• You have not settled how you want to work. Building a process you have not decided on is the costliest way to find it.
• You would rather a vendor absorbed compliance changes for you.

If that describes you, you do not need a custom ERP, and you do not need us. Some businesses that ask for an ERP are better served by good accounting software with inventory, used consistently.

When a custom ERP pays off

Your exceptions are your business

Stock on approval, rates agreed per customer, credit for regulars, job work moving between units: edge cases to a packaged ERP, most of the day for some businesses.

The floor needs different screens

A counter or a godown needs a few clear buttons, not screens designed for trained back-office users.

Several systems never agree

When reconciling the billing, stock and staff tools is somebody's monthly job, one system removes the job rather than speeding it up.

It is part of something larger

A dealer portal, a customer app or WhatsApp order updates on the same database are simpler to build in than to connect later.

How a phased custom build runs

A custom ERP should go live a module at a time, starting with the one whose absence costs most every day — usually billing or inventory. Map how goods, money and work move; scope the first module at a fixed price; build it with your real items, move the opening data and put it into daily use; then scope the next module from how the first is used.

That is how we approach custom ERP software development, and it is a fair standard to hold any builder to. How long each phase takes is covered in how long custom software takes to build.