Odoo consulting services: what you get at each phase

Odoo consulting services are the project work your subscription does not buy: analysis, configuration, data import, custom development, training, and project management. As of October 2026, a new customer's first Success Pack runs from USD 493 for 4 hours to USD 21,250 for 200 hours, and companies over 50 employees usually use a partner for local project management. A proposal you can sign names the phase, the artifact, the hours by role, and the work your team still owns. Who should do the work is covered in our guide to hiring an Odoo consultant in the US.

The official phase split is the yardstick for that proposal. Odoo's Implementation Methodology assigns about 10% of the project to ROI analysis, about 5% to kick-off, about 80% to implementation, and about 5% to go-live, plus a later second deployment whose length depends on what you deferred. On larger projects the same guide says go-live can take 10% to 15% because change management is heavier. For most smaller companies the ROI step is wrapped into kick-off, and on projects under about four months it is not a separate phase at all.

What the subscription leaves for consulting to cover

Odoo's pricing page states that implementation is not in the subscription. The same page says companies under 50 employees usually buy Success Packs from Odoo, companies over 50 employees usually use a partner for local project management, and companies of 250 or more employees should contact Odoo. That split is the first line of a scope request: say which path you are on, then ask the bidder to price services separately from licenses.

What the subscription does include, as of October 2026, is Odoo Online hosting, Monday to Friday email support 24/5 in English, French, Spanish, or Dutch, free eLearning, and version upgrades. Odoo Online storage is described as unmetered up to 100GB under the acceptable-use policy. Left out are Odoo.sh hosting for custom developments, implementation or expert services, in-app credits (SMS, contact autocomplete, lead generation, and AI to scan vendor bills and expenses), and maintenance of custom code.

License figures on that page are not a single list price. As of October 2026 the Standard plan is shown as US$31.10 and US$38.90 per user per month, and also as USD 24.90 and USD 31.10. The Custom plan is shown as US$61.00 and US$76.20 per user per month, and also as USD 49.00 and USD 61.10. A footnote says the discount is valid for 12 months for the initial users ordered. The page does not say which pair is yearly billing and which is monthly billing. A Light User is listed at US$8.90 and is quoted through an Odoo advisor. One configurator line showed US$61.00 labeled "First Year Initial Discount on regular users."

Standard is Odoo Online only and cannot host custom modules. The Custom plan is the one that adds Odoo.sh or on-premise hosting, Studio, agentic AI, multi-company, and the external API. External API means a system outside Odoo calling Odoo's JSON-RPC or XML-RPC API. Calls that Odoo initiates, such as payment providers, carriers, and bank sync, stay on the Standard plan.

Assume 25 people who each need a full user, and no Light Users. You still should not multiply one of those figures by 25 and call it the annual bill. The page shows two pairs, and the discount applies for 12 months to the initial users ordered. The scope request should make the bidder write the plan name, the user count, the billing term, and the price after month 12 on separate lines from consulting hours.

What each official phase hands back

Use the methodology's stages as headings in the statement of work. If a bidder renames them, ask which artifact closes the stage. Each stage should hand back a named file, a recorded decision, and an owner. A day rate that skips those three is what a comparison should drop.

ROI analysis, when it stands alone

On a large project, ROI analysis is sold before you commit to the full budget and can take 5 to 80 days. Workshops cover the current way of working, pain points, terminology, and sample reports. A peer review follows, then a closing presentation. The deliverables named in the guide are a cost-savings and benefits analysis, a budget and implementation plan, a map linking business needs to product features, and a proof of concept built from configured flows or mock-ups.

On a project under about four months, that work is folded into kick-off. Ask for the same four outputs anyway. A short project still needs a needs-to-feature map before anyone imports a product file.

Kick-off

Kick-off exists to onboard your single point of contact on the methodology, run a quick feasibility check if ROI analysis was skipped, finalize scope and phasing, check the budget, and train that contact on the key flows with eLearning and documentation. The contact has to be available and has to have authority to decide. The guide is explicit that the customer defines why and what, and the project leader defines how.

Implementation cycles

Implementation is a series of short cycles that should deliver functionality every week. The project leader configures the apps, including Studio, with no custom code. Data import is done by the project leader or a developer after your team prepares the file. Custom development is specified by the project leader, attested by your contact, built and automatically tested by a developer, then retested and trained.

The guide tells implementers to import master data and to avoid full transaction history when possible. It also says not to hold go-live only to perfect data your team was already using. Developments that the business must have in order to operate are separated from developments that can wait. The rule in the guide is to keep custom development small and to split must-have work from later phases during peer review.

Go-live

Go-live in the guide is mainly end-user training and bug fixes. Your single point of contact gives the green light after final tests. End-user training is run by that contact or by key users. The guide assigns the user manual to your team. The two failure modes the guide names are a database that key users have not fully tested, and training that happened too early or without practice on the live flows.

Second deployment

Second deployment is a later phase to widen scope or to add custom features that are not required to operate. A proposal that puts every requested report, portal, and carrier rule into phase one has skipped the peer-review split the methodology calls for.

• ROI analysis: About 10%. Wrapped into kick-off for most SMEs. Not a separate phase under about four months. On large projects, 5 to 80 days, sold before the full budget.
• Kick-off: About 5%. Scope, phasing, budget check, and training of your single point of contact.
• Implementation: About 80%. Weekly cycles of configuration, import, and only the custom work required to operate.
• Go-live: About 5%, or 10% to 15% on larger projects. End-user training and bug fixes.
• Second deployment: Variable. Deferred scope and custom features that can wait.

Those shares are Odoo's, from the Implementation Methodology, as reviewed in October 2026. They are a way to test whether a quote spent its hours in configuration or in status meetings. Your project can land on different shares once change management or custom work grows.

What your team still owns after you hire help

Consulting does not take the operating decisions. On a large project the guide adds a steering committee, department key users who test each deliverable, and a sponsor such as the CEO or CFO. On a smaller project the same duties collapse onto one person. If that person cannot approve a field, a price list, or a go-live date, the project leader has nobody to attest a specification.

Four pieces of work stay with you even when the statement of work is thick:

1. Your team prepares the import files and the consultant loads them, after you extract customers, vendors, products, and opening balances in the shape the import expects.
2. Test as key users before anyone trains the wider staff. An untested database is one of the two go-live failures the guide names.
3. Write the user manual and run end-user training, using the contact or key users. The consultant trains that contact during kick-off and implementation. The contact trains the floor.
4. Decide to go live. The single point of contact gives that green light after final tests.

Hours cannot invent a scope your operators have not named. Before you ask for a price, list the apps that must run at cutover, the files your team can extract, and the decisions the contact is allowed to make without a second meeting. Firms price what is written down. A missing product file or an unnamed approval becomes a change request in month two, after the pack you bought is already partly used.

Official Success Pack prices versus a partner statement of work

Odoo publishes Success Packs as hour blocks with a dedicated consultant. As of October 2026, the pack page lists Starter, Basic, Standard, Custom, and Pro. Returning-customer prices and the new-customer first-pack prices (15% off once) are below. Travel is extra when a higher pack includes onsite work: travel time is billed and travel expenses are billed separately.

• Starter (Hours: 4 · Returning customer (USD): 580 · New customer, first pack only (USD): 493 · Pack price divided by hours (returning): 145)
• Basic (Hours: 25 · Returning customer (USD): 3,600 · New customer, first pack only (USD): 3,060 · Pack price divided by hours (returning): 144)
• Standard (Hours: 50 · Returning customer (USD): 7,000 · New customer, first pack only (USD): 5,950 · Pack price divided by hours (returning): 140)
• Custom (Hours: 100 · Returning customer (USD): 12,500 · New customer, first pack only (USD): 10,625 · Pack price divided by hours (returning): 125)
• Pro (Hours: 200 · Returning customer (USD): 25,000 · New customer, first pack only (USD): 21,250 · Pack price divided by hours (returning): 125)

The last column is arithmetic on Odoo's published pack prices as of October 2026. It is not a published hourly rate. Dividing USD 580 by 4 hours is USD 145. Dividing USD 12,500 by 100 hours, and USD 25,000 by 200 hours, is USD 125. Use it to see how the block is built. Use the statement of work to see what the hours produce.

The pack table includes project management, email and phone support, training and coaching, configuration, and data-import assistance on the packs that list them. App customization, form, report, and workflow customizations, and developments appear on the Custom and Pro columns. Odoo says consultants will use best efforts to get you started within the pack hours. That is a different commercial promise from a fixed list of finished workflows. The pricing configurator states that Success Pack hours expire after one year. The same page's default line recommended a pack of 25 hours. That was the unloaded default, not an estimate of your apps.

Performance work sits outside free support. Odoo says most performance issues are not in standard code and that analysis requires a Success Pack of at least 50 hours. For custom development, Odoo says its own developments are charged per day of consulting, and that partners usually charge per day of consulting or development. Extra monthly charges apply for maintenance of extra modules or lines of code.

Odoo states "98% implementation success rate, vs 65% without success pack (self)" on the pack page. The methodology document says that over the prior five years more than 95% of Odoo's implementations were successful. Those are Odoo's claims. The documents do not cite an independent study, so keep the scorecard on named artifacts and named people.

A partner can sell an hour bundle under a similar name and mean a different product. TechUltra Solutions, for example, publishes its own packs at USD 750 for 25 hours, USD 1,300 for 50 hours, USD 2,300 for 100 hours, and USD 4,000 for 200 hours, with a custom-scope implementation listed from USD 9,000 after discovery. Those figures are that firm's menu, seen in October 2026, and the firm presents them as its own packs, not as Odoo S.A. prices and not as a US rate card. If a proposal says Success Pack, ask whether the hours, the expiry, and the invoice come from Odoo or from the bidder.

One public comment put a typical implementation from about 25 hours into the hundreds: "An implementation can go typically anywhere between avg 25 hours into hundreds of hours. Start with an analysis with a partner first." The line is from a thread on implementation cost. It is one comment, not a verified price. The official packs start at 4 and 25 hours and run up to 200.

Assume a 40-person distributor with Sales, Inventory, and Accounting in phase one, and a new-customer Basic pack of 25 hours at USD 3,060. Those 25 hours are the entire Basic allotment. They have to cover every activity that pack includes before anyone treats the block as the project. Tie the 25 hours to the three apps, the files, and the test pass in the statement of work before you treat the pack as the project. A new-customer Standard pack is 50 hours at USD 5,950 (USD 7,000 for a returning customer). Fifty hours still has to be tied to named apps and named files before you treat the pack as the project.

For a company over 50 employees, the pricing page says companies usually use a partner for local project management. The statement of work should still show the methodology's artifacts. The commercial shape changes from an Odoo hour block to a partner phase plan. How fixed price differs from time and materials is laid out in our note on ERP consultant rates.

How to compare two Odoo proposals

Put both proposals on the same grid. A lower total that omits history, travel, or custom-code maintenance is not a lower project.

• Apps in phase one: Sales, Inventory, Accounting, or whichever set you will run. Later apps sit in second deployment.
• Hours by role: Project leader hours for configuration and specifications. Developer hours only where code is required.
• Configuration versus development: Studio and settings versus modules and custom code. The project leader configures. A developer builds attested specs.
• Data objects: Customers, vendors, products, opening balances. Transaction history called out as in or out.
• Integrations: Which system calls which. Outside systems calling Odoo sit on the Custom plan. Odoo-initiated carrier, bank, and payment links can stay on Standard.
• Tests: Scenarios for key users, who writes them, and the rule that training waits until those users have practiced.
• After go-live: A stated window for bug fixes. The guide does not publish a standard number of days, so the proposal has to.
• Hours running out: What a change request costs, whether unused hours expire, and the date they expire. Official pack hours expire after one year.
• Travel and maintenance: Onsite time and expenses outside the professional-fee number. A monthly fee for extra modules or lines of code.
• Code after the project: Who holds the custom modules, and whether you can move them if you change firms.

A day rate with none of those lines tells you the price of a person for a day. It does not tell you whether week six produces a configured sales order, a cleaned product file, or a status meeting. Ask each bidder to price data migration as its own line, with the objects listed, so a cheap quote cannot hide history, open orders, or a second system inside one vague import line.

Questions that show a proposal is thin

Read the proposal with the methodology open. These questions come from the duties the guide already assigns. If a bidder will not answer them in writing, you cannot tell what the fee buys.

1. Who is the named project leader, who configures, and who writes code? A buyer question worth copying into the email is "Who exactly will be doing the work, you or a team member we haven't met?" That wording is from a 2026 note on consultant roles. Another buyer put the staffing risk more bluntly: "A lot of partners are just fronts for code farms offshore." The line is from a thread on partner pricing. Named people, and a split between who configures and who writes code, are the answers that make both of those worries concrete.
2. Does our single point of contact have the authority to decide, and how many hours a week will that person give during implementation? If the answer is whoever happens to be free that week, kick-off cannot finalize scope.
3. Which developments are required to operate before go-live, and which wait for second deployment? Peer review in the guide is where that split is supposed to happen.
4. Will you import transaction history, or only master data? The guide's default is master data, and go-live is not held for a perfect history load.
5. Who writes the test scenarios, and who writes the user manual? Key users test. Your team writes the manual. If both are silently in the consultant's hours, the hour total is doing two jobs the methodology gives to you, or the jobs will not get done.
6. What happens when the hours run out, and do unused hours expire? Official Success Pack hours expire after one year. A partner block needs its own expiry and its own change-request rate in the contract.
7. Is onsite travel inside the number? On Odoo packs, travel time is billed and travel expenses are separate.
8. Who maintains custom modules after go-live, and what is the monthly fee? Odoo applies extra monthly charges for maintenance of extra modules or lines of code. A partner quote needs the same line.

References belong next to the names. Ask for two recent projects with a similar app list, and ask what the customer prepared versus what the project leader configured. Partner tier is a label you can note after those answers. It does not replace them.

Hosting, credits, and custom work the hours do not buy

Custom modules need a place to run. Standard plan hosting will not take them. The pricing configurator, license excluded, showed these Odoo.sh figures as of October 2026. Each line is a pair. The lower figure is the discounted amount. The page does not label which figure is an annual commitment. It says to contact Odoo above 16 workers or 512 GB. The dedicated-server line is listed for environments above 8 workers.

• Worker (Higher figure (USD): 72.00 · Lower figure (USD): 57.60 · Basis: Per worker per month, license excluded)
• Storage (Higher figure (USD): 0.25 · Lower figure (USD): 0.20 · Basis: Per GB per month)
• Staging environment (Higher figure (USD): 18.00 · Lower figure (USD): 14.40 · Basis: Per environment per month)
• Dedicated server (Higher figure (USD): 600.00 · Lower figure (USD): 480.00 · Basis: Per month, for environments above 8 workers)

Assume 4 workers, one staging environment, and 100 GB, with no dedicated server. At the higher figures that is 4 times USD 72.00 (USD 288), plus USD 18.00, plus 100 times USD 0.25 (USD 25): USD 331 a month before licenses. At the lower figures it is 4 times USD 57.60 (USD 230.40), plus USD 14.40, plus USD 20: USD 264.80 a month. Put both calculations in the comparison until the order form names the commitment. Four workers sit under the 8-worker dedicated-server line and under the 16-worker contact line, so this sketch does not add a dedicated server.

In-app credits are a second bill the subscription does not cover. SMS, contact autocomplete, lead generation, and AI that scans vendor bills and expenses are called out on the pricing page as excluded. A warehouse that texts customers at ship confirmation, or an accounts team that wants bills read into draft entries, should see a credit estimate in the proposal. The consultant can configure the flow. The credit price is still yours.

Custom code has a third bill. Build cost is consulting or development days, from Odoo or from the partner. Upkeep is the monthly maintenance charge for extra modules or lines of code. If phase one is standard apps plus Studio and no custom module, say that in the scope so nobody prices a maintenance retainer against work you did not buy. If a carrier, a bank feed, or a payment provider is the integration, confirm it is an Odoo-initiated link that can stay on Standard. If your web store or your warehouse system will call Odoo, the license conversation moves to the Custom plan and to Odoo.sh or on-premise hosting.

What to put in the scope request you send out

Write the request so two firms have to answer the same grid. Open with headcount, the legal entities, and whether you are under or over 50 employees, because that is the fork Odoo prints between its packs and a partner. List the apps that have to run when you cut over, the systems that will feed master data, and the developments that operations cannot live without. State that transaction history is out unless a line item brings it in. Name the internal single point of contact and the sponsor. Ask for hours by role, a change-request rule, hour expiry, travel, hosting, in-app credits, and the monthly fee for custom code.

We scope that first phase as a written set of artifacts: the needs-to-feature map, the configured apps, the import files you prepare, the must-have developments attested by your contact, and a go-live decision your contact still owns. The Odoo implementation page is where that phased delivery is described. When the scope also has to cover finance, inventory, and the cutover across the operation, the same request sits inside our ERP implementation service.

Send the grid to every bidder before you compare totals. The firm that prices each line, names the project leader, and marks what your team still owns is the firm you can hold to the phase. Bring the drafts to a call if you want them ordered against a first phase your team can staff.

How Flectic can help

Flectic implements Odoo one app at a time on a single database, and each phase hands back working apps and a written plan with a price. Connected business (accounting, inventory or manufacturing, historical data, one or two integrations, Studio) has a planning range of $19,000 to $60,000, not a quote. Check each phase against our Odoo implementation scope, then Book a free discovery call with Flectic before you compare proposals.

Sources

Implementation Methodology, Odoo, October 2026

Odoo Pricing | Discover Odoo Packs, Odoo, October 2026

Odoo Pricing | Discover Odoo Plans, Odoo, October 2026

Odoo Pricing Configurator, Odoo, October 2026

Odoo Success Pack: Cost, Hours & What's Included, TechUltra Solutions, October 2026

What Does an Odoo Consultant Do? Roles & Rates 2026, Odoo-lab / OmiSoft, October 2026

Implementation and cost, Reddit r/Odoo, October 2026

Odoo partners pricing, Reddit r/Odoo, October 2026