After enough ERP vendor evaluations, the patterns become predictable. Vendors that produce successful implementations behave differently from vendors that produce expensive failures. The differences show up in the first conversation, the proposal, the demo, and the reference calls.
This is the list of ten warning signs Singapore manufacturers should watch for. None of them are automatic disqualifications — context matters — but each one is a signal that warrants harder questions before signing.
1. Vague Pricing After Paid Discovery
A reputable ERP vendor commits to a fixed scope and fixed price after a proper discovery. The discovery output should include a single number (or narrow band) the manufacturer can budget against.
Red flag: The vendor offers "time and materials" billing, or pricing "subject to detailed design phase," or "approximately S$X but final cost depends on scope." This is the vendor protecting themselves at the manufacturer's expense.
What to ask instead: "What is the fixed-scope, fixed-price quote? What does it include? What is explicitly excluded? What triggers a change request?"
2. No Singapore-Based References
ERP that works in the US, EU, or Australia does not automatically work in Singapore. The compliance gaps (InvoiceNow, GST, regulatory regimes) and the operational patterns differ enough that experience elsewhere is not a substitute.
Red flag: The vendor cannot provide 2-3 reference customers in Singapore who have been live for 12+ months. References from other countries or recently-live customers do not count.
What to ask instead: "Can you connect me to three SG manufacturers you have implemented for, who have been live for at least a year?"
3. Demo Uses Their Generic Database
A vendor demo using a generic demo database tells you the product can run. It does not tell you the product fits your operation.
Red flag: The vendor refuses to demo with a sample of your data, or insists "we can configure that later." If the demo cannot model your specific workflow at the evaluation stage, the post-purchase reality will be a customisation project.
What to ask instead: "Can the demo use a small sample of our actual data (pricing structure, BOMs, suppliers)? Show me how a quote for our Customer A would be built in your system."
4. "We Can Customise That" Without Quoting
Every vendor will say their product can be customised. The question is: at what cost, on what timeline, with what risk to future upgrades?
Red flag: The vendor responds to gap questions with "we can customise that" without immediately quoting the customisation. Or proposes 20%+ of total cost in customisation line items — which means you are paying for both the off-the-shelf product and a custom system built on top of it.
What to ask instead: "For each of these 10 specific workflows I need, will the standard product handle it, or does it need customisation? If customisation, what is the cost and what happens during future upgrades?"
5. Partner Has Just One Successful Implementation
ERP vendors sell software; implementation partners deliver projects. The partner's track record matters more than the product's.
Red flag: The partner can only point to one successful implementation in your industry — or worse, the same implementation they keep referring multiple prospects to. This signals either inexperience or that successful implementations are rare.
What to ask instead: "How many similar implementations has this specific partner team completed? Not the product's install base — this team's delivery history."
6. Aggressive Discounts at Quarter End
ERP sales cycles run on quarters. End-of-quarter discounts can be legitimate — vendors close pipeline to hit targets — but they can also signal a vendor sales team prioritising the close over the fit.
Red flag: Significant discount (20%+) appears suddenly, paired with pressure to sign before quarter end. The implicit message is "buy now or pay more later," which compresses the evaluation timeline below what good due diligence requires.
What to ask instead: "If this is the right product for our operation, will the price still be available next month? If not, why not?"
7. Long Implementation Timeline With Vague Milestones
A 12-month implementation is normal for enterprise ERP. A 12-month implementation without weekly demonstrable milestones is a warning sign.
Red flag: The implementation plan has long stretches between milestones, or milestones described in process terms ("requirements analysis complete") rather than output terms ("staging environment shows your top 5 workflows working").
What to ask instead: "What can I see working in week 4? Week 8? Week 12? What does 'on track' look like at each checkpoint?"
8. Hidden Ongoing Costs
The upfront cost is what gets quoted. The ongoing costs are often what surprise.
Red flag: The proposal is vague on annual licence, maintenance fees, support tier costs, customisation maintenance fees, training costs for new staff, integration maintenance, or infrastructure pass-through fees.
What to ask instead: "What is my total cost over 5 years, including all annual fees, expected customisation, expected training, and expected infrastructure? Put it in writing."
9. Cannot Articulate Their Limitations
Every ERP product has limitations. A vendor who cannot articulate where their product struggles is either inexperienced or being dishonest.
Red flag: When asked "where does your product not fit well?", the vendor answers "we can handle anything" or only gives marketing-friendly answers.
What to ask instead: "What types of manufacturers should NOT use your product? What are the three most common reasons your implementations fail or get extended?"
10. Code or Data Ownership Is Vague
For off-the-shelf SaaS, you do not own the code — that is fine. But you should always own your data, with a clear export path.
Red flag: The contract or proposal does not explicitly address: (1) your right to export your data at any time in usable formats, (2) what happens to your data if the vendor exits the SG market or goes out of business, (3) for customisations, who owns the customisation code.
What to ask instead: "If I terminate the contract in year 3, what is the data export process? How long do I have access? Is the export format usable by another system?"
How to Use This List
Do not treat any single red flag as automatic disqualification. Use them as triggers for harder questions. A vendor who responds to harder questions with good answers earns more confidence; a vendor who gets defensive or vague reveals more about the partnership than the product itself.
The pattern that successful implementations share: a vendor who is honest about limitations, specific about deliverables, and confident enough to commit to fixed scope and price. The pattern that failed implementations share: a vendor who promises everything, prices vaguely, and treats the evaluation as a sales obstacle to overcome rather than a fit assessment to participate in.
Start Canyon's Vendor Selection Support engagement (S$3,000-S$8,000) runs this red-flag evaluation systematically for prospects evaluating multiple ERP vendors. The output is a scorecard and recommendation — including build-vs-buy guidance if no vendor scores well. Independent advisory, no vendor affiliations.