·ERP
How to choose an ERP implementation vendor (without regret)
Choosing an ERP vendor matters as much as choosing the software. Even the best system fails in the hands of the wrong implementer. Here's how to judge.
What a good vendor looks like
- Discovery first, price later. A serious vendor understands your process before naming a number. A final figure without understanding your needs is just a guess.
- Scope & cost in writing. A proposal with clear modules, timeline, and cost — scope changes agreed first, not sprung on the invoice.
- Honest about fit. If your needs suit integration or another solution better, a good vendor says so.
- Post go-live support. A system needs support after launch. Make sure there's an SLA-backed support arrangement, not abandonment.
- References and portfolio. Ask for similar projects and their outcomes.
Red flags
Be wary of a vendor that:
- Quotes a final price in the first meeting, before knowing your process.
- Promises everything is possible without conditions — real projects always have trade-offs.
- Focuses on features, not your problem — they're selling, not solving.
- Is unclear about ownership of source code, data, and access.
Questions worth asking
- How do you run discovery?
- What happens if scope changes mid-project?
- How does support work after go-live, and what's the response time?
- Who owns the data and source code once the project is done?
The answers to these four already separate serious vendors from those just selling.
Want to talk to a vendor that starts from your problem, not from a product? Start with a free consultation.