01
Normalise the scope
Give every vendor the same process list, data sample, user population and integration inventory. Record exclusions in the same format.
Plan / ERP buyer series
Odoo partner proposal checklist: what to ask before you sign
Before you sign with an Odoo implementation partner, make every proposal answer the same questions: which workflows, data and integrations are delivered, who on a named team does the work, how change requests are priced, who owns the custom code and who upgrades it. Compare quotes only after those boundaries match. A lower total may simply leave that work out.
Discuss my ERP scope See the buying checklist
No purchase commitment. Submitting an enquiry does not book a meeting.
Which path fits your situation?
02
Price the dependencies
Customer data cleanup, third-party access, hosting and user testing still need owners even when the vendor does not charge for them.
03
Agree acceptance first
Define evidence for completion before negotiating the last discount. Tie the review to working scenarios rather than a count of installed modules.
Put the decision in writing
Use the same requirements for every proposal. Record what is included, what needs validation and who owns unresolved work.
| Proposal line | What to ask for | Warning sign |
|---|---|---|
| Configuration | Named workflows, roles and reports. | A list of app names without operating requirements. |
| Migration | Objects, history depth, rehearsals and reconciliation. | “All data” without a sample or volume assumption. |
| Integrations | Systems, directions, failures and support owners. | “API available” treated as a finished connector. |
| Support | Hours, channels, severity definitions and exclusions. | An unqualified support promise without response commitments. |
Swipe the table sideways to compare all columns.
Separate fixed delivery from change requests
Ask which requirements were demonstrated and which remain estimates. For custom work, record the behaviour, test data and acceptance result rather than only developer hours. Agree how new requests will be assessed, approved and priced. The change process should protect both sides from treating an untested assumption as an unlimited obligation.
Make the commercial comparison repeatable
Create separate one-time and recurring totals. Include licences, deployment, integrations, migration, training, travel where relevant and support. State the currency, tax treatment and payment milestones on each quote. Model the same evaluation period and renewal assumptions. Do not compare a first-year promotional subscription price with another vendor’s full renewal cost.
Include an exit and handover plan
Identify who holds administrative access, where documentation is stored and how backups can be restored. Ask for data export formats and source-code rights where applicable. Clarify how another support team would take over and which third-party licences remain necessary. On Odoo, also ask who upgrades the custom modules: Odoo’s own upgrade service covers standard apps, Studio customisations and code under a maintenance-of-customisations subscription, not modules a partner wrote outside such a contract. A practical handover plan is valuable even when you expect to keep the same partner.
From comparison to a scoped proposal
Bring one workflow.
Ask better questions.
Braincuber offers Community-based custom ERP and Odoo Enterprise implementation. We will review fit, gaps and responsibilities before proposing delivery. Bring anonymised examples—not confidential records.
Request a scoped discussion
Questions before you commit
Is the partner listed on odoo.com/partners, and does the listing match the proposal?
Search the Odoo partner directory for the company named on the proposal. The listing shows its grade (Gold, Silver or Ready), the number of published customer references, certified experts by Odoo version and typical project size. A good answer is a listing under the same legal entity that will sign the contract. Treat the grade as one input, not proof of fit for your project.
Can we speak to a live customer on a comparable project?
Ask for one reference in your industry, at a similar user count, using the same core apps and live on a supported Odoo version. A good answer is a named contact you can call. Ask that customer what changed after go-live, what was delivered late and who supports them now. A logo slide or an anonymous case study does not count.
Who exactly will deliver our project?
Ask for the project manager and functional lead by name, the share of their time on your project, and whether any part is subcontracted. Odoo certifications are version-specific, so check which version each person is certified on. A good answer names people and commits to notice and approval before anyone on the core team is replaced.
Which requirements are standard, configured, Studio or custom code?
Ask the partner to label every requirement in the proposal with one of those four types. Standard and configured items should be shown working in a demo on your own sample data before you sign. Custom code is where estimates, testing effort and upgrade cost grow, so it deserves the most detail in the quote.
Which Odoo edition, plan and hosting does the quote assume?
Odoo Online, Odoo.sh and on-premise hosting change what the partner can deploy. Odoo’s pricing page states that the Standard plan is hosted on Odoo Online without custom modules, so any custom or third-party module needs the Custom plan. A good answer names the plan, the hosting, and who pays for Odoo.sh where it is used.
How are change requests estimated, approved and priced?
A good answer is a written process: how a new request is estimated, who approves it, the rate or method used to price it, and that no chargeable work starts before approval. Ask for one past example of a change request and its approval record, with the client’s details removed.
Who owns the custom modules, and where is the source code kept?
Ask the contract to state who owns code written for you and under which licence, and to give you access to the repository during the project, not only at handover. A good answer lets another partner read, build and maintain the modules if you change suppliers. Verify by asking for read access to the repository at kickoff.
Who upgrades our customisations when we move to a new Odoo version?
With Odoo Enterprise, Odoo’s upgrade service covers standard apps, customisations made with Studio while Studio and the subscription stay active, and developments under a maintenance-of-customisations subscription. It excludes modules built in-house or by third parties, including Odoo partners, without such a contract, plus data cleanup and training. Ask the partner to price those upgrades in writing.
Should we always choose a fixed-price proposal?
Not necessarily. Fixed pricing needs a stable scope. For uncertain work, a bounded discovery or phased agreement can make assumptions explicit before a larger commitment.
Is a promised go-live date enough?
No. Ask for dependencies, acceptance conditions and a cutover plan. Dates without those assumptions cannot be compared meaningfully.
What should we send Braincuber?
A non-confidential process summary, required interfaces, approximate users and locations, and the decisions you need the proposal to resolve.
Sources and how to use this guide
Braincuber sells ERP implementation services. Product statements refer to the vendor sources below; the evaluation scenarios and recommendations are our analysis. Verify the current edition and commercial terms in your written quote. We have not assigned independent ratings, tested every configuration or invented customer results.
- Odoo plans and exclusions
Check your country, billing term, renewal terms and implementation exclusions before budgeting.
- Odoo partner directory
Lists each partner’s grade, published references, certified experts by version and typical project size (reviewed 25 October 2026).
- Odoo upgrade service scope (Odoo 19 documentation)
Defines which standard apps, Studio customisations and maintained developments the upgrade service covers, and what it excludes (reviewed 25 October 2026).