Pricing

Scoped pricing, not a generic number

Every engagement starts with a free discovery call. You get a fixed-price proposal once we understand your actual scope, not a rate card that doesn't reflect your business.

Starter

Single-entity businesses, core operations

A single business running core operations on spreadsheets or a basic tool, ready for one connected system.

Discover & Design for core modules (Sales, Accounting, Inventory or Project)
Single-entity configuration
Data migration from your current system
Role-based training for your team

Growth

Multi-department or multi-entity operations

A growing business needing operational and financial visibility across departments, or more than one legal entity.

Everything in Starter
Multi-company or multi-department configuration
Custom workflows and approval flows
Ongoing support included for the first quarter

Enterprise

Complex, multi-site, or highly customized needs

Multiple entities, custom integrations, or requirements that go beyond native Odoo configuration.

Everything in Growth
Custom development where configuration isn't enough
Third-party integrations
Dedicated ongoing support plan

Fees are agreed in writing after the Discover and Design phases, before any Build work starts.

Request Pricing

Get a scoped proposal

Tell us about your business and we’ll come back with next steps for a scoped proposal.

FAQ

Pricing questions

Odoo implementation cost depends on module count, entity structure, customization depth, and data complexity, none of which we know before a discovery call. We quote a fixed price after scoping, not a generic number that doesn't reflect your actual project.

Yes. We map your current operation and tell you honestly what a good Odoo setup looks like, and roughly what it would take, before you commit to anything.

No. Implementation and migration projects are quoted as a fixed price agreed before work starts, based on the scope from the Discover and Design phases. Ongoing support is typically a fixed monthly arrangement.

Number of modules and entities, depth of customization required, data migration complexity, and training scope. A single-entity business on core modules costs meaningfully less than a multi-entity operation with custom integrations.