The build vs buy decision is the most consequential choice a Singapore manufacturer makes when evaluating ERP. Get it right and the system accelerates the business for years. Get it wrong and the manufacturer spends S$150,000 and eighteen months on a system that requires workarounds for every non-standard process.
The decision is harder than it should be because both sides have strong advocates with financial incentives. Off-the-shelf vendors sell licences and implementation services. Custom developers sell build hours. Neither has an incentive to recommend the other. The manufacturer is left to evaluate competing pitches from parties who benefit from the outcome.
This guide is written by a custom developer (Start Canyon), so take the appropriate discount. But the framework is honest: there are genuine cases where off-the-shelf wins, and a custom developer who recommends custom for every situation is not being truthful.
When Off-the-Shelf Wins
Off-the-shelf ERP wins when the manufacturer's workflow is standard:
Standard pricing. If you sell from a price list — same price for every customer, standard quantity breaks, no per-customer negotiated rates, no product-form multipliers — an off-the-shelf quoting module handles this natively.
Standard production. If your production is make-to-stock with simple BOMs (assemble components A, B, C into Product X), standard production modules handle the BOM, work order, and inventory deduction workflow.
Standard quality. If your quality requirements are generic (incoming inspection, in-process check, final inspection) without industry-specific documentation (no PPAP, no DHR, no GMP batch records, no material data books), standard quality modules suffice.
Standard compliance. If your regulatory requirements are handled by the accounting system (GST, InvoiceNow) and you do not have industry-specific compliance needs (CAAS, HSA, SFA, ISO 13485), the off-the-shelf system covers it.
Strong local partner. If a reputable local partner exists for the product (SAP B1 has several strong SG partners; Odoo has variable partner quality), the implementation risk is manageable.
When all five conditions are met, an off-the-shelf system is faster to implement, lower risk to adopt, and comes with a proven track record. The manufacturer benefits from a product that has been tested across hundreds of similar businesses.
When Custom Wins
Custom ERP wins when the manufacturer's competitive advantage lives in a workflow that standard software cannot model:
Non-standard pricing. Per-customer negotiated rates with quantity breaks, product-form multipliers, substrate-based pricing, or any pricing logic that exceeds a simple price list. This is the most common trigger for custom builds among Singapore manufacturers.
Non-standard production. Job shop workflows, engineer-to-order processes, multi-stage subcontractor coordination, or production processes where the sequence varies by product type. Standard production modules assume a fixed routing; custom production varies by order.
Industry-specific quality. PPAP documentation for automotive. GMP batch records for food and pharma. Device History Records for medical devices. Material data books for marine fabrication. These are not "quality module configurations" — they are entire workflow surfaces that standard quality modules do not cover.
External-facing portals. Customer portals where buyers check order status and download documentation. Supplier portals where vendors acknowledge POs and update delivery schedules. These are not features of most off-the-shelf ERP systems — they require custom front-end development even when the back-end is off-the-shelf.
Integration-first architecture. When the manufacturer wants to keep their existing accounting system and build the operational layer around it, a custom system is designed for integration from the start. Off-the-shelf systems are designed to replace everything — and their integration capabilities are often an afterthought.
The Customisation Trap
The most expensive outcome is buying off-the-shelf and then customising it into a custom system.
This happens when the manufacturer's workflow does not fit the standard modules, but the vendor proposes customisation rather than acknowledging the poor fit. The result:
- Base licence cost: S$30,000-S$80,000
- Customisation cost: S$50,000-S$150,000 (often exceeds the base cost)
- Implementation timeline: 12-18 months (instead of 3-6 months for vanilla)
- Upgrade path: blocked (customisations break with each vendor update)
- Partner dependency: high (only the implementing partner understands the customisations)
The total spend often exceeds what a purpose-built custom system would have cost, and the result is worse — because the customised off-the-shelf system carries the complexity of the base product plus the fragility of the customisations.
The signal that you are heading into the customisation trap: the vendor's proposal includes more than 20% of the total cost in "customisation" line items. At that point, you are paying for a custom system built on top of a product you are also paying for.
The 5-Year Cost Comparison
| Cost element | Off-the-shelf (SAP B1 / Odoo) | Custom build (Start Canyon) | |---|---|---| | Year 1: implementation + licence | S$80,000 - S$300,000 | S$10,000 - S$30,000 | | Years 2-5: licence / maintenance | S$15,000 - S$40,000 / year | S$200 / month infra | | Years 2-5: customisation / extensions | S$10,000 - S$30,000 / year | S$5,000 - S$15,000 / year (scope-priced) | | 5-year total | S$140,000 - S$460,000 | S$22,000 - S$60,000 |
The custom build has a dramatically lower 5-year TCO for most Singapore SMB manufacturers. The caveat: if the custom system needs major extensions (new modules, new portals, new integrations), the extension cost narrows the gap. But the extension is scope-priced and optional — you choose what to build and when.
How to Decide
1. List the 5 workflows that cause the most operational pain. Not features. Workflows — the end-to-end process from trigger to outcome.
2. For each workflow, ask: does a standard module handle this as-is? Be honest. "Handle" means without customisation, without workarounds, without the vendor saying "we can configure that."
3. Count how many of the 5 workflows need customisation. If 0-1: buy off-the-shelf. If 2-3: evaluate both. If 4-5: build custom.
4. Check the 5-year TCO. Include implementation, licence/subscription, customisation, and ongoing support for both options. The upfront cost difference is misleading — the lifecycle cost is what matters.
5. Ask about code ownership. Off-the-shelf: you licence the software; the vendor owns the code; you leave when the contract ends. Custom: you own the code in a Git repository; any developer can extend it; the vendor relationship is optional after the build.
Start Canyon helps Singapore manufacturers make this decision as part of the free diagnostic. If your workflow is standard, we will tell you — and recommend an off-the-shelf system that fits. If your workflow is non-standard, we will scope the custom build.