AI implementation platform for Odoo

Deliver more Odoo with the team you already have.

Odoo Pilot helps Odoo teams understand requirements, plan the work, configure Odoo, build customisations and control how AI-driven changes reach their environment. It works from your project’s Odoo context, and nothing supported goes live without approval.

More capacity. More context. More control.

7-day trial · 300 Pilot Credits · Cancel any time inside the trial

For Odoo partners, agencies, consultants, freelancers, developers, administrators and in-house ERP and IT teams.

Real implementation benchmark

One implementation. Same people. Different workflow.

A scope estimated at ~16 hours. Completed with Odoo Pilot in ~1 hour.

Measured on an Odoo 19 Enterprise implementation using the same implementation team. Actual time savings vary by scope, environment and complexity.

Bars are drawn to scale. The benchmark answers “does it save time?” The controls further down answer “can I trust it?”

Already used by paying Odoo teams.

The work behind every Odoo change

Odoo is flexible. Getting it right is a lot of work.

Whether you deliver Odoo for customers or run it for your own company, the same three pressures show up.

  1. Requirements get complex.

    One business need can be met by a setting, a Studio-style change, a custom module or a different process. Working out which takes discovery, Odoo knowledge and time.

  2. Context gets scattered.

    Requirements, decisions, the state of the environment and its history end up in documents, chats, tickets and people’s heads. The next person starts by rediscovering them.

  3. Execution takes time, and needs control.

    Configuring, customising and building is repetitive work. And every change to a live database is one you’ll need to review, explain and sometimes undo.

Odoo Pilot is designed to remove repetitive work without removing expert judgement.

How Odoo Pilot fits together

Scope it. Deliver it. Keep control.

Odoo delivery starts with the requirement. Begin in Presales and Discovery, move into the delivery mode that fits the work, and keep review and approval around every supported change. Ask Odoo and Pilot Health are supporting information tools you can use whenever you need an answer or a diagnostic view.

  1. Every planScope

    Start from the requirement

    Use Presales and Discovery to understand the requirement, identify gaps and open questions, and build the scope and estimate before configuration or customisation starts.

    • Requirements
    • Gap analysis
    • Estimate
    • Discovery
    Start with Discovery
  2. Every planDeliver

    Use the right delivery mode

    Move the scoped work into Implementation Mode, Pilot Studio, Module Builder or Website Builder depending on whether it is configuration, in-database customisation, development or website work.

    • Implementation Mode
    • Pilot Studio
    • Module Builder
    • Website Builder
    See the five modes
  3. Every changeControl

    Keep control of execution

    Proposed work is explicit, a person approves supported live changes, and every run leaves a record. Eligible changes can be rolled back.

    • Review
    • Approval
    • Mode boundaries
    • Run history
    How control works
The Pilot toolkit

Five modes that follow the work, from requirement to running Odoo.

Start with Discovery to understand and scope the requirement, then use the mode that matches the delivery work. Implementation Mode, Pilot Studio, Module Builder and Website Builder are separate workflows today. Ask Odoo and Pilot Health sit alongside the delivery flow as information and diagnostic tools when you need them.

Discovery

PaidDiscover

Understand requirements and turn them into structured implementation work: what’s standard, what needs configuration, what’s custom and what’s still unclear. Also called presales and gap analysis.

Use it when
You have a requirements list, from customers or from your own stakeholders, and need to know what it really involves.
For example
  • Classify each requirement as standard, configured, custom or missing, with open questions.
  • Estimate the effort before you commit to a scope.

Implementation Mode

PaidConfigure

Configure supported Odoo requirements using project context. Standard Odoo configuration and supported setup, planned against your connected environment and run as reviewable tasks. Kept separate from custom code.

Use it when
The requirement can be met with native Odoo configuration.
For example
  • Configure a two-step warehouse flow and import the starting master data.
  • Create a reordering rule for a warehouse, reviewed before it runs.

Pilot Studio

PaidCustomise

Go beyond standard configuration with supported customisation directly in the connected database: fields, views, supported visibility and access changes, and supported automations.

Use it when
You need a contained change, not a full custom module.
For example
  • Add PO Urgency (Normal, High, Critical) and an internal procurement note to the Purchase Order view.
  • Add a “Delivery priority” field to the Sales Order form.

Module Builder

PaidDevelop

Build what needs real development: maintainable custom Odoo modules, advanced business logic and deeper integrations, delivered as code your developers can review.

Use it when
The requirement needs a real custom module, advanced business logic or a deeper integration.
For example
  • Generate models, views, access rules and business logic as a module, with GitHub integration where supported.
  • Start from the requirement instead of a blank module scaffold.

Website Builder

PaidWebsite

Turn an approved Figma design into an Odoo website module, so less of the design handoff is rebuilt by hand.

Use it when
The design is approved and it needs to become Odoo website templates and snippets.
For example
  • Map Figma frames to templates, snippets and assets.
  • Get a website module ready for a staging preview.

Across every mode

Paid
  • Project-level contextPilot retains project knowledge, while Discovery, configuration, customisation and development remain separate workflows today.
  • GitHub and Figma integrationsWhere supported, technical work connects to your team’s existing development process.
  • Execution history and rollbackSupported runs keep a record, and eligible changes can be rolled back.

Where a custom module can be installed depends on the environment’s Odoo hosting and version. Check the documentation (opens in a new tab) for what your setup supports.

Pilot Health

See what needs attention before the next change.

Pilot Health is a supporting diagnostic tool for an existing or changing Odoo environment. Use it when you need a prioritised view of what deserves attention; a new delivery project still starts from Presales and Discovery.

  1. What did Pilot find?

    An overall health score, how many items need attention, and the detail across six areas of the environment.

  2. Why does it matter?

    Each area shows something that can affect delivery or day-to-day operation: scheduled actions that fail, email that isn’t configured, customisation that has built up, technical and data issues.

  3. What should I look at first?

    Start with the areas marked Warning and the Technical Alerts. The score helps you decide what to review first. It doesn’t replace judgement.

Pilot Health’s lower sections for a connected Odoo 19 database: Connected Instance, Scheduled Actions, Email Health, Database and Performance, Customisation Footprint and Technical Alerts.
The lower sections of the same view. Product screenshot.

Connected Instance: connected, Odoo 19, 1 company, 1 user. Scheduled Actions: 33 active, 0 failed in the last 24 hours, 0 overdue, 5 disabled. Email Health: SMTP not configured, 0 failed emails, 0 queued emails. Database and Performance: database size, response time, active connections, long-running queries and locks all show a dash, meaning no value. Customisation Footprint: 3 custom fields, 0 custom views, automated actions shown as a dash, 119 server actions, 1 custom module. Technical Alerts: add missing product vendors, complete missing product cost, configure outgoing mail server, and fix journals or configuration issues. The top bar shows a health score of 88, Good, with View Health and Open Odoo Instance buttons.

What the score is, and isn’t

The score helps you decide what to review first. It isn’t a certification, and it doesn’t cover what Pilot can’t see.

Some values need server or PostgreSQL-level access. When that isn’t available, Pilot shows a dash rather than guessing. A dash means there’s no value, not that the value is healthy.

Re-run the check after configuration or fix-up work, and export a report to share with your team or a customer.

Run Pilot Health (opens in a new tab)
Why Odoo Pilot

General AI can help you build. Pilot is built to help you deliver Odoo.

General-purpose AI can answer questions, generate code and increasingly act on systems through tools and connectors. Odoo Pilot adds the Odoo-specific delivery layer around it — so your team doesn’t have to build and maintain that infrastructure itself.

Context
Works from the project and the environment you connect, including its version, modules and customisations, and the project context you keep in Pilot, so answers and plans start from your Odoo.
Structure
Turns requirements into defined Odoo delivery workflows, with a mode for each kind of work, rather than treating every request as an isolated prompt.
Control
Separates planning, review, approval and execution, so changes don’t simply happen because an AI generated them.
Continuity
Retains project-level knowledge so teams can reuse context across the project, while Discovery, configuration, customisation and development remain separate workflows today.
Recovery
Where supported, changes can be traced and rolled back, so the team isn’t left to reconstruct what happened by hand.
Controlled AI execution for Odoo

AI can make changes fast. Pilot helps make those changes controlled.

Odoo is a connected business system. A change to a workflow, field, module, automation or customisation can affect more than the person making it expects. Pilot puts structure around AI-assisted delivery, so teams can understand the work, review what’s proposed and control what’s allowed to run — without slowing the work down.

  1. Describe

    You describe the business outcome. Pilot starts from the requirement, the project and the connected environment.

  2. Plan

    Pilot turns the request into explicit Odoo work, in the mode that fits it.

  3. Review

    You see exactly what will change, before anything is applied.

  4. Approve

    Nothing runs until an authorised person approves it.

  5. Execute

    Pilot performs only the approved, supported actions in that mode.

  6. Record

    The run stays on record, with a change footprint you can roll back where eligible.

Approval is a human decision inside Pilot. On a client project, review the proposed change with the client first, or with the business owner on an internal one, and approve execution only once you agree.

Configuration shouldn’t quietly become custom code.

Execution is bounded by the mode. Each kind of work has its own mode and its own boundary, and Pilot only performs the supported actions available in that mode. If a requirement outgrows its mode, it moves to the next one — so nothing is quietly stretched beyond what the mode is meant to do.

Configure

Implementation Mode

Standard Odoo configuration and supported setup. Intentionally kept separate from custom code.

“Configure a two-step warehouse flow and import the starting master data.”

Customise

Pilot Studio

Supported customisation in the connected database: fields, views, visibility and access changes, and automations.

“Add PO Urgency and an internal procurement note, and show both on the Purchase Order view.”

Develop

Module Builder

Maintainable custom modules, advanced logic and deeper integrations, delivered as code your developers can review.

When a requirement outgrows database configuration, it moves here.

What Pilot does today

  • The intended work is made explicit before anything runs.
  • Supported live changes need approval from an authorised person.
  • Execution stays inside the boundary of the mode.
  • Every run leaves an execution history and a change footprint.

Recovery, stated plainly

Where a change can be safely reversed, Pilot can roll it back. Rollback is limited to eligible actions. It isn’t a universal undo: transactional or externally propagated effects may need a different recovery process.

If the requirement or the configuration was wrong, the task can be corrected and run again in a controlled way.

Pricing

Three plans. One toolkit. Choose the capacity that fits your work.

Solo and Team include hosted AI through Pilot Credits. Custom is built for larger organisations, with custom credit capacity or BYO LLM plus enterprise governance scoped around the way they deliver.

Showing monthly prices.

7-day trial Try Odoo Pilot before you choose a plan.

300 Pilot Credits included. Explore the full toolkit during the trial.

Card required. Cancel any time during the trial before you are charged.

Solo

Full Pilot for one practitioner

For an individual consultant, developer, freelancer or administrator using Pilot to do Odoo work.

$49 /month

or $470 a year with annual billing — save 20%

Start 7-day trial (opens in a new tab)
Most partners

Team

Shared Pilot for your delivery team

For implementation partners, agencies, consulting teams and internal Odoo teams delivering together.

$249 /month

or $2,390 a year with annual billing — save 20%

Start 7-day trial (opens in a new tab)

Custom

Your organisation, under its own governance

For organisations running Odoo delivery at scale, or under security, procurement or AI-governance requirements.

Talk to us

Annual agreement · scoped with our team

Talk to us (opens in a new tab)
Entry and capacity
Users
1 user
5 included+$49 per additional user / month
CustomVolume pricing
Active client projects
3
10
10+ / customTalk to us once you need more than 10 active projects
Pilot usage
5,000 Pilot CreditsEach month
30,000 shared Pilot CreditsEach month · +5,000 per additional user
Custom credits / BYO LLMScoped with our team
Ask Odoo and Pilot Health
Included
Included
Included
Full delivery toolkit
Discovery: presales and gap analysis
Included
Included
Included
Implementation Mode
Included
Included
Included
Pilot Studio
IncludedSupported in-database customisation
IncludedSupported in-database customisation
IncludedSupported in-database customisation
Module Builder
Included
Included
Included
Website Builder
Included
Included
Included
Execution history and rollback
IncludedWhere supported
IncludedWhere supported
IncludedWhere supported
GitHub and Figma integration
Included
Included
Included
Collaboration and operations
Shared projects and context
—
Included
Included
Roles and access controls
—
Team roles
AdvancedRoles and project isolation
Usage visibility
—
Organisation usage
Enterprise visibilityGovernance and spend controls where scoped
Templates and methodology
—
Shared team templates
Advanced / custom
Enterprise controls
Customer Managed AI
—
—
AvailableBring your own supported LLM where preferred
Multiple governed business units
—
—
Included
SSO / SCIM
—
—
Where supported
Audit logs and export
—
—
Included
White-labelled client deliverables
—
—
Included
Support
Standard
Priority
SLA / negotiated

Pilot Credits for Solo and Team

Solo and Team use one Pilot Credit system for hosted AI-assisted work. Different tasks consume different amounts based on the work being performed. Custom is scoped with our team and can use a custom Pilot Credit allowance or a supported BYO LLM setup, depending on the organisation’s requirements.

What changes the number, and what doesn’t

  • Solo vs TeamThe same Pilot job uses the same credit meter; Team simply has a larger shared pool.
  • Hosted AISolo and Team include hosted AI through Pilot Credits. Custom can be scoped with custom credits or a supported BYO LLM setup.
  • The workScope, complexity, database size and the depth of the change are what move usage.

Consumption varies with the work, so we don’t publish a credits-per-task table. Your usage dashboard shows what your own work consumes from day one of the trial.

Team credits are pooled

Everyone on Team draws from one shared pool, so credits go to whoever is doing the work that month rather than being locked equally to individual seats.

  • Team member A: 12,000
  • Team member B: 8,000
  • Team member C: 6,000
  • Left: 4,000

Illustrative exampleMade-up usage of a 30,000-credit month.

Need more? Add Pilot Credits any time

Monthly allowances refresh each month and don’t roll over. Credits you buy as a pack are yours for as long as your subscription is active. Bigger packs cost less per credit.

  • 5,000credits · $49
  • 15,000credits · $129
  • 40,000credits · $299
  • 100,000credits · $599

Pilot always spends your monthly allowance first, then purchased credits. Team includes 5 users; each additional user is $49/month and adds 5,000 credits to the shared pool.

When does an organisation move to Custom?

Talk to us once you need more than 10 active client projects, larger user volumes, custom Pilot Credit capacity or BYO LLM, stronger security and governance, SSO / SCIM, white-labelled delivery or procurement terms. Active-project capacity is not sold as a Team add-on.

How we price it. Custom is an annual agreement sized from enterprise platform access, user capacity, usage volume and any governance, security or support requirements. Usage can be supplied through custom Pilot Credits or BYO LLM.

FAQ

Questions Odoo teams ask us.

About Odoo Pilot

Control and safety

Plans, users and credits

Getting started

Start by understanding your Odoo.

Ask a question, connect an environment and run Pilot Health. When you’re ready to change something, Pilot takes it from there, with approval before anything runs.

7-day trial · 300 Pilot Credits · Cancel any time inside the trial

Talk to us about a Custom plan (opens in a new tab)

What Pilot Health needs to connect

To look at an Odoo environment, Pilot Health needs a way to reach it. You’ll be asked for the details Odoo Pilot needs to connect to it, such as where it’s hosted and how Pilot should sign in.

Connection is the prerequisite for reliable reads and for controlled execution, and Pilot Health confirms that the connection works.

Start with a staging copy where you have one. Use an account whose access you’re comfortable with, and check your client agreement or internal policy before connecting an environment that isn’t yours.

This is a summary. The documentation has the full, current requirements. You don’t need to connect anything to try Ask Odoo.

Product screenshot