Start Canyon
7 min read·2026-05-29

When NOT to Build a Custom ERP in Singapore: Six Honest Reasons to Stay With Off-the-Shelf or Excel

When not to build a custom ERP in Singapore — six honest scenarios where off-the-shelf or even Excel is the right answer. Written by a custom ERP developer who turns down 30% of inquiries.

Manufacturing strategy desk with laptop analytics, notebook, reference material, and sample components
Operational view

Read this as an operating decision

Each guide is written to help a manufacturer decide what to fix first, what to defer, and what to avoid.

Custom ERP is not the right answer for every Singapore manufacturer. About 30% of the prospects who reach out to Start Canyon should not work with us. The honest answer in those cases is "use Excel a little longer," "buy Katana," or "talk to SAP."

This article is the disqualification list. It is written so that prospects who would be a poor fit can recognise themselves before booking a paid discovery — and so that prospects who ARE a fit can read it and feel more confident that the engagement we offer is grounded.

1. You Are Under 30 Staff

Operations under 30 staff almost always have simpler workflows than a custom system needs to model. The marginal value of custom is low — the master Excel still works, the senior estimator knows everything, the communication channels are short enough that gaps are caught informally.

A custom system at this scale is over-engineering. The S$10,000-S$30,000 build cost is real money. The 6-12 week implementation displaces operational attention. The post-go-live adoption requires bandwidth the team probably does not have.

What fits instead:

  • Xero or MYOB for accounting (probably already running).
  • Structured Google Sheets with formulas and validation for quoting and tracking — formalising what already works.
  • Katana, MRPeasy, or inFlow if inventory specifically is breaking and a SaaS at S$200-500/month would solve it.

Revisit custom when you cross 50 staff or when a specific workflow becomes the bottleneck regardless of size.

2. Your Workflow Fits Standard Modules

If your pricing is a price list (no per-customer rates), your production is make-to-stock with stable BOMs, your supplier base is small and stable, and your quality requirements are generic — your workflow fits an off-the-shelf ERP product. Standard modules will handle it.

In this case, an off-the-shelf product is faster (3-6 months vs 6-12 weeks plus longer ramp), lower-risk (the vendor handles updates), and has a proven track record across hundreds of similar businesses.

What fits instead:

  • Odoo with a reputable local partner — for standard mid-market workflows.
  • SAP B1 — if you have an enterprise track record and budget.
  • Synergix — if you want a Singapore-built mid-market option.

The diagnostic question: of your top 5 workflow surfaces, how many need customisation beyond configuration? If 0-1, buy off-the-shelf. If 4-5, build custom. If 2-3, do a Workshop or RFP Support engagement to validate before committing.

3. The Pain Is Accounting, Not Operations

If your operational systems work fine (production runs, quoting is acceptable, suppliers are managed) but accounting is painful (GST returns, bank reconciliation, financial reporting), the right answer is a better accounting system — not a custom ERP that wraps the accounting.

What fits instead:

  • Switch from Excel-based bookkeeping to Xero or MYOB.
  • Outsource to an accountant who manages the books on your behalf.
  • Upgrade to a more capable accounting tool if you have outgrown your current one (Sage 300 from MYOB, NetSuite if multi-entity).

A custom ERP would add operational complexity for a problem that already has a clean off-the-shelf answer.

4. You Have Budget Below S$10,000

We cannot deliver a useful custom manufacturing ERP for under S$10,000. The minimum scope — paid discovery, focused build, deployment, and parallel-run adoption — costs more than that to deliver well. Engaging anyway would set both sides up for disappointment.

What fits instead:

  • Free tier of Notion, Airtable, or Google Sheets for lightweight workflow tracking.
  • Katana or Cin7 starter plans (S$200-500/month) for inventory and basic manufacturing.
  • Zoho One (S$50/user/month) for an all-in-one SMB stack.

When your budget grows or when a specific high-value workflow justifies the S$10k+ investment, the conversation can restart.

5. You Want a Specific Vendor (Not Custom)

If you have already evaluated and decided on a specific vendor — SAP B1, Microsoft Dynamics, Oracle NetSuite — then engaging Start Canyon for a custom build is the wrong path. We are not an implementation partner for those products.

What fits instead:

  • Vendor Selection Support (S$3,000-S$8,000) if you want a neutral second opinion before committing to a specific product.
  • The chosen vendor's certified partner network for implementation.
  • An independent implementation consultant if the vendor partner is also the developer and you want a check on that conflict of interest.

We will happily decline the engagement and recommend the right path.

6. Your Operation Is in Active Crisis

If your operation is in active crisis — major delivery failures, key staff departure, customer threatening to walk — a custom ERP build is not the answer. A 6-12 week build is too slow for crisis response.

What fits instead:

  • Stabilise first. Address the immediate crisis with manual processes, temporary staffing, or customer-level damage control.
  • Diagnose root cause. The crisis may be symptom of operational gaps that a system would help — but only after the immediate fire is out.
  • Run a Sprint (S$1,500-2,500) for a single targeted decision once stable.

A custom build started during crisis usually becomes another problem the team has to manage. Better to come back when the operation is stable enough to absorb a system project.

The Pattern

The honest pattern: custom ERP is the right answer when (1) you are 30+ staff with operations complex enough to need a system, (2) your workflow has 2+ surfaces that off-the-shelf cannot model, (3) you have S$10k+ budget and 9-13 week runway, (4) accounting is solved separately, (5) you have not pre-committed to a vendor product, and (6) your operation is stable enough to absorb the project.

When all six conditions are met, custom is often the highest-leverage investment a manufacturer can make.

When any are not met, the right answer is something else — and we will tell you what.

The free diagnostic at startcanyon.com/diagnostic is the fastest way to discover which side of this you are on. If it returns "not a fit," that is a useful answer.

FAQ

Practical questions before you buy.

Why would a custom ERP developer recommend against custom?

Because mismatched engagements waste everyone's time and produce bad outcomes. When a manufacturer's workflow fits an off-the-shelf product, recommending custom anyway leads to a more expensive system that does the same job — and damages our reputation when prospects discover the easier path months later. Honest qualification is the long game.

How often does Start Canyon turn down inquiries?

Roughly 30%. The common disqualifications: under 30 staff (operations too small to justify custom), workflow fits standard modules (off-the-shelf is faster and cheaper), accounting-only need (the accounting system already handles it), or budget below S$10k (we cannot deliver a useful custom system in that range and would rather say so).

What does Start Canyon recommend when custom is not right?

Specific products by use case: Xero or MYOB for accounting, Katana or Cin7 for inventory-led SaaS manufacturers, Odoo for standard mid-market workflows, SAP B1 for enterprise-track companies, Excel + structured templates for very small operations. We name the alternative — we do not just say "not us."

Next step

If the master Excel is the bottleneck, let’s talk.

Reply within one Singapore business day. WhatsApp for faster routing.