AssembloERP
This is our own bias territory, so let us be plain about it: we build custom. That does not make custom right for you, and we turn down work when it is not.
Here is the framework we use, including the cases where you should buy a packaged product and ignore us.
When off-the-shelf is the right answer
- Your process is ordinary. Buy, store, sell, account. If you cannot name a workflow that differs from your competitor's, you are paying for uniqueness you do not have.
- You need it running in three weeks. Packaged software is faster to stand up, full stop.
- Your team is small and turnover is high. Widely-used software means the next hire may already know it.
- Compliance is the main driver. GST, e-invoicing and statutory reports are commodity problems, solved well by many products. Do not pay to rebuild them — see the compliance checklist for what "solved" should mean.
When custom wins outright
1. One workflow is your actual advantage
A converter who quotes in three minutes while competitors take a day. A processor whose traceability is why a large buyer stays. If a packaged system forces that workflow into a generic shape, you are paying to become average.
2. Your process is genuinely unusual
Coil-to-length conversions where the factor varies by batch. Job work with returnable scrap and multi-stage vendors. Piece-rate wages tied to inspection results. These exist in thousands of Indian businesses and in very few product roadmaps.
3. The workarounds would outlive the software
Here is the honest test. After implementation, how many spreadsheets survive next to the system? If the answer is two or more, permanently, you have bought a packaged product and kept the manual cost. That is the worst of both.
4. Integration is the point
Weighbridge, machine counters, marketplace orders, a dealer app. When the value is in the joins rather than the modules, custom is usually less painful than bending three products into each other.
The comparison people do not run
| Off-the-shelf | Custom-built | |
|---|---|---|
| Time to first use | Days to weeks | Weeks to months |
| Upfront cost | Lower | Higher |
| Fit to your process | 60-85%, configured | Designed for it |
| Cost of the gap | Permanent workarounds | Design time, once |
| Change later | Feature request, maybe never | Scoped work, on your timeline |
| Main risk | You adapt to the software | Dependency on the builder |
| Best for | Ordinary processes, speed | Differentiating or expensive workflows |
The middle path most SMBs should take
Packaged core, custom edges. Use standard modules for accounting, inventory, purchase and GST — the parts where being ordinary is a virtue. Build custom only for the two workflows that make or cost you money.
That is how we scope: a module set for the boring 80%, and a genuine build for the rest. It keeps the bill honest and puts the engineering where it earns.
A five-minute decision
- Write the one workflow that makes you money. If a packaged demo cannot do it as shown, custom is in play.
- Count the spreadsheets you would still need. Two or more, permanently? Custom is in play.
- Ask how urgent this is. Three weeks? Buy packaged now, build later.
- Ask who will maintain it in year three. If you have no answer, choose the option with more people who know it.
If you want the honest version applied to your business, describe the workflow on our contact page and we will tell you which side of this line you fall on — including when the answer is "buy something standard". Next: what an ERP really costs.
