Choose the consultant who understands your business, shows you real work and stays after go-live. Software skill matters, but most failed projects fail because of weak communication, vague scope or no support once the system is live. A few good questions will show you more than any sales presentation.
Talk to people who have used them
Ask for references and actually call them. Do not only ask whether they were happy. Ask what went wrong and how it was handled. Every project has problems. What you want to learn is how the consultant behaves when one appears.
Good questions for a reference:
- Did the project stay within what was agreed, and if not, why?
- How fast did they answer when something broke after go-live?
- Would you hire them again for the next phase?
Be careful with a consultant who cannot give you anyone to speak to.
Look for fit with your industry
Odoo covers many industries, but the details differ. A school with several branches needs fee schedules. A workshop needs bills of materials and work orders. A retailer needs counters, stock and returns.
Ask whether they have worked on something close to your business. You do not need an exact match, but they should ask sharp questions about your trade in the first meeting. If they talk only about screens and menus, they have not understood the problem.
Check how they handle the plan
A good consultant starts with your processes, not with a list of apps. Watch for these signs.
- They ask to see how the work is done today.
- They separate what configuration covers from what needs development.
- They tell you when a request should change the process instead of the software.
- They will not promise a date or a final figure before reviewing the fit and gap.
A quick, confident quote after one call usually means the scope has not been looked at.
Ask what happens after go-live
This is the question most buyers forget. Go-live is the start of real use, and real use finds problems.
- Who will you call, and how do you reach them?
- How are problems sorted by urgency?
- Who looks after upgrades, backups and the server?
- Is support part of the agreement or a separate arrangement?
Also ask about handover. You should be able to get documentation in plain language, so you are not locked in to one person’s memory.
Questions to take to every meeting
- Who will actually work on my project, and will they stay on it?
- How will I see progress before the end?
- How do you handle data migration, and will you rehearse it?
- How do you keep custom work easy to upgrade?
- What do you need from me, and by when?
- What would make you advise against a request of mine?
The last one is useful. A consultant who never says no is not protecting your project.
Red flags
- Pressure to sign quickly.
- Everything is “possible” with no discussion of cost in upkeep.
- No written scope.
- Training treated as optional.
- Blame placed on your staff before the work has begun.
Where Teapot Techies fits
We would rather you ask these questions of us too. Our Odoo implementation page sets out how we work, and how we work explains support and escalation. If you want to test us against this list, use the contact button below.