Skip to content
A cream cover with the CDB mark, the words Buying Odoo, and the article title.

Buying Odoo

Author
Clovis de Bontin
Published
14 November 2026
Reading time
7 min read
All articles

What to prepare before an Odoo demo

An Odoo demo is not a product tour. The useful ones start with your operation: the order that gets stuck, the stock count that never matches, the quote that takes three days. If the partner has not seen that before the call, the first twenty minutes are spent explaining it.

Start with one process, not a list of apps

Pick the process that hurts most. Order to invoice, purchase to payment, quote to job, or stock receipt to dispatch. Describe what happens now, who touches it, and where it waits.

One process, told properly, tells a partner more than a list of every app you might want. It also gives the demo a script. The partner can show your order moving through Odoo instead of showing a menu.

The five inputs that make the call useful

InputWhat to sendWhat it decides
The process that hurtsA paragraph and one sample documentThe demo script
Size and shapeCountry, sector, employees, sites, usersThe partner and the scope
Systems in useAccounting, stock, CRM, webshop, spreadsheetsThe integrations
Data you can hand overCustomer, supplier and item lists, opening balancesThe migration effort
People and decisionWho signs, who uses it daily, who can vetoWho should be in the room

A short email with those five answers is enough. It does not need a template, a deck or a consultant.

Send the numbers as ranges

Exact counts are less useful than honest ranges. Two hundred to five hundred orders a month is enough to size a demo. So is three stock locations, four users and one currency. If you do not know a number, say that. A guess presented as a fact will shape the wrong scope.

Name the systems that must stay

Most small companies keep something: the accountant's tool, a webshop, a label printer, a payroll provider. Say which systems must stay and which can go. The demo should show the seam between them, not hide it.

This is also where a partner learns whether the project is an Odoo implementation or an integration project with Odoo at the centre. Those are different scopes.

Bring the data you actually have

Export a customer list, a supplier list, an item list and one month of orders. Do not clean it for the demo. The duplicates and missing fields are the point: they show the migration work that the quote has to cover.

If the data sits in three spreadsheets and an old accounting package, say so before the call. A partner who sees that on the day will spend the demo asking about it instead of showing your process.

Put the person who runs the process in the room

The owner signs the agreement, but the warehouse manager knows where the stock record is wrong. The finance manager knows which report the board asks for. If the people who do the work are not in the demo, the demo is a sales call, and the real questions arrive a week later by email.

Keep the room small. One process owner, one decision maker and the person who will administer Odoo is usually enough.

What not to prepare

  • A forty-page requirements document. It freezes the conversation before the partner has seen the operation.
  • A wishlist of every app in the Odoo catalogue. It turns a demo into a product tour.
  • A licence decision. The edition follows the scope, not the other way round.
  • A clean demo database. You are buying a project, not a presentation.

What the partner should bring

A demo database with your process in it. The same five questions, asked back to you. A named person for the follow-up. If the session is a generic tour of Odoo, stop it and ask for your order, your stock item or your job.

The partner should also be able to say what is out of scope. A demo that shows everything and rules out nothing has not made a decision.

A one-page brief you can send

FieldWhat to write
CountryWhere the company operates. This decides the technical partner.
SectorWhat you make, sell or service.
SizeEmployees, sites, users, orders or jobs a month.
The processThe one that hurts, in five sentences.
SystemsWhat must stay, what can go.
DataWhat you can export and what is missing.
PeopleWho signs, who runs the process, who administers the system.
Next stepThe date you want to decide by.

That brief is the difference between a demo and a meeting. It also lets the partner bring the right consultant, not the nearest salesperson.

After the demo

You should leave with three things: a scope outline, the open questions, and a named next step. Not a licence price on the first call. If the partner cannot explain what is out of scope, that is the finding.

The next step is usually a discovery session, where the scope is tested against your data and your people. The implementation process explains what happens there. If you are still choosing between partners, the partner checklist is the practical comparison.

If you want the demo to start from your operation, book a free demo and send the brief with it. We implement Odoo with our technical partners, and the agreement is with the partner.

I sincerely hope this was helpful, and if you have any remark, suggestion or question, you can email me at louis@cdb.solutions or DM me on LinkedIn.

Thank you,

Clovis

Next step

See this in practice

Book a free demo. The technical partner for your country shows the apps that fit, at no charge.

Canonical URL: https://www.cdb.solutions/articles/what-to-prepare-before-an-odoo-demo

FAQ

Answers to the questions this article raises

The questions buyers ask most, answered here. If yours is not covered, ask us directly.

01Do I need to clean my data before the demo?
No. Bring a sample of what you have, including the duplicates and missing fields. Cleaning comes after the scope is agreed, and the state of the data is part of what the scope has to cover.
02How long should an Odoo demo be?
Forty-five to sixty minutes is enough for one process. A longer session usually means the scope is still unclear, not that the product needs more time.
03Should I invite my accountant?
If they own the ledger or the statutory reports, yes. They will see whether the finance side of the demo matches how the company actually reports.
04What if I do not know which Odoo apps I need?
That is what discovery is for. Start with the process that hurts and let the apps follow. A demo that begins with a list of apps begins in the wrong place.

Next step

Book a free demo

Tell us the country and the operation. The technical partner for your country shows Odoo against your process, at no charge.

+33 7 69 45 83 27UK with SofthealerEverywhere else with AppNvent

Free demo

Put this against your own operation

Country, industry and company size. The technical partner scopes the work and holds the agreement.

  • Country chooses the partner. The UK is implemented with Softhealer. Everywhere else, with AppNvent.

  • The demo is specific. Industry and company size tell the technical partner which apps to show you.

  • No charge, no obligation. Scoping and any agreement come later, and only if you want them.

Tell us about the operation

01/06

United Kingdom: we implement with Softhealer, our technical partner. The agreement is with Softhealer.

Optional
Optional

Routed to Softhealer for United Kingdom. See our privacy policy.