Most Odoo implementations that go badly do not fail on the software. They fail because the customer side of the project was staffed with whoever happened to have time, rather than with the people who own the decisions. A partner brings configuration, development and process advice. What a partner cannot do is decide how your company approves a purchase order, or which of three conflicting item codes is the real one.
Here is the internal team an Odoo project actually needs, what each role does, and roughly what it costs in hours.
An executive sponsor who can settle arguments
The sponsor is usually a managing director, CFO or COO. Their job is not to sit through workshops. It is to break ties. Every implementation reaches a point where two departments want incompatible things: sales wants to invoice on delivery note, finance wants to invoice on confirmed quantity, and both are defensible. Without someone senior enough to choose, that question sits in an email thread for three weeks and the whole configuration waits behind it.
Realistic time cost: a couple of hours a month, plus genuine availability for the three or four decisions that stall everything.
A project manager on your side
Your partner will have a project manager. You need a counterpart. This person chases internal answers, gets the right people into the right workshops, keeps the open-issue list, and protects the schedule from the slow erosion of "we will confirm that later." They do not need to be technical. They need to be organized and senior enough that people reply to them.
This is the one role that should be at least half time during the build. If it is a spare-hours job, the project runs at the speed of whoever is slowest to answer.
One process owner per functional area
Finance, sales, inventory, manufacturing, HR: each live area needs a named person who knows how the work is actually done today, not how the procedure manual says it should be. They answer configuration questions, review the design, and sign off on their area during testing.
The important qualification is authority. A process owner has to be able to say "we will change how we do this" without going back up the chain for every detail. Someone who can describe the process but cannot agree to change it produces a design full of unnecessary customization, because every awkward habit gets preserved by default.
A data owner
Master data is the most underestimated part of an implementation. Someone has to own the customer and supplier lists, the item master, the chart of accounts and the opening balances, and decide what moves, what gets cleaned first, and what stays behind in the old system as a read-only archive. This is rarely a full-time role on its own, but it is the one most often left unassigned, and the cost shows up as a scramble in the final two weeks.
An IT contact, even if IT is one person
User accounts, email delivery, label and receipt printers, network access at branches, credentials for a bank portal or an online store: these are small items that block big ones. On managed hosting the infrastructure layer itself is not your problem, since backups, monitoring and staging environments come with the service, but access and endpoint questions still need someone in-house who can act.
What a missing role looks like
- No sponsor: decisions escalate into email and stay there. The timeline slips a week at a time and nobody can point to a single cause.
- No internal project manager: the partner chases individuals directly, each one answers on their own schedule, and status meetings turn into progress reports about waiting.
- No process owner in an area: that module gets configured from assumptions. The gap surfaces during testing if you are lucky, and after go-live if you are not.
- No data owner: migration becomes a last-minute exercise, and the first month of live operation is spent correcting balances and duplicate records.
Be honest about capacity
The most common planning mistake is not choosing the wrong people. It is choosing exactly the right people and then giving them no time. Your best inventory manager is already fully booked; that is why they are your best inventory manager. An ERP project is real work stacked on top of a full-time job.
There are three honest responses: free up their time, backfill part of their day job, or accept a longer schedule that fits around their real availability. All three work. Assuming the project is free of load is the option that does not.
What this looks like in a small company
Not every organization can field six people. In a company of forty, the finance manager is often the sponsor and the data owner, the operations manager is the internal project manager and the inventory process owner, and IT is an external provider on call. That is fine. The roles still need to be named out loud, because the failure mode is not "we combined roles," it is "we assumed someone was doing it."
If you are scoping an implementation now and want a view of how the work is split between your team and the partner across each phase, our Odoo implementation service page sets out the phases and the deliverables that go with them.