From the first conversation to delivery, every decision is explained, every step produces a verifiable result and nothing moves forward without your approval.
We tailor the first days of the engagement to your reality: a brand-new idea, an existing solution or a problem that needs solving fast.
First ERP01
You work with spreadsheets and several tools
We replace your scattered tools with Odoo, module by module, starting with what saves you the most time.
How we get started
Workshop on your sales, purchasing, inventory and invoicing processes
Choice of modules, edition and hosting
Demo on your own data
Odoo in place02
Your Odoo is not delivering
We take over an existing installation, even one built by another provider, and put it back to work for your teams.
How we get started
Audit of configuration, modules and performance
List of pain points raised by users
Prioritised, costed remediation plan
Version upgrade03
You are stuck on an old version
We migrate your data and adapt your custom modules to a recent Odoo version, without losing history.
How we get started
Inventory of custom and third-party modules
Trial migration on a copy of the database
User acceptance testing before cutover
The full process
A clear path forward, with no gray areas.
At every step, you know what was done, what was delivered and what decision is needed to move on.
011 to 2 weeks
Process analysis
We follow how an order, a purchase and an invoice flow through your company to decide what Odoo will do out of the box.
What we do
Interviews with each department
Gap analysis between standard Odoo and your needs
Community or Enterprise; Odoo Online, Odoo.sh or dedicated server
Why this step: A poorly scoped ERP gets configured on assumptions, then corrected at great expense once the teams have been trained. This analysis avoids unnecessary development and budget surprises: before you commit, you know what Odoo will do out of the box, what needs custom work and in what order to proceed.
How we proceed, line by line
1 An initial video call sets the goals, the departments involved and the workshop schedule.
2 We run a video workshop with each department: sales, purchasing, inventory, accounting, manufacturing or projects, depending on your business.
3 During these workshops, you share your screen and we follow together the real journey of an order, a purchase and an invoice, using your current documents.
4 We compare each need with standard Odoo on a demo database and classify the gaps: simple configuration, light customization or custom module.
5 We make the case for Odoo Community or Odoo Enterprise, then for Odoo Online, Odoo.sh or a dedicated server, based on your modules, volumes and budget.
6 In a shared document, we write the configuration specification, the list of costed developments and the module rollout order.
7 A debrief meeting by video call lets us review the document together, adjust the priorities and approve the scope.
Who does what
An Odoo consultant leads the workshops and writes the configuration specification, with a project manager who keeps the schedule and a developer who estimates the custom work. On your side, a project lead and one key user per department describe their real work.
What you provide
One key user per department available for a one- to two-hour workshop.
Examples of current documents: quotes, purchase orders, invoices, tracking spreadsheets.
The list of your current tools and, if applicable, access to your existing Odoo.
Your country's accounting and tax constraints, ideally confirmed by your accountant.
What you receive
Configuration plan, development list and budget
Your approval
You approve the scope, the edition and the module roll-out order.
022-week cycles
Configuration and development
We configure Odoo on a test environment, build the required modules and prepare the data migration.
What we do
Setup of companies, taxes, products and flows
Custom modules, reports and connectors
Test imports of customers, products and balances
Why this step: Configuring Odoo directly in production exposes your operations to every configuration error. By working on a test environment in short cycles, we regularly show you an Odoo running with your own data, and corrections are made early, when they cost little.
How we proceed, line by line
1 We create a staging environment separate from any live activity, on the hosting chosen in the previous step.
2 We first configure the foundation: companies, currencies, languages, chart of accounts, your country's taxes, users and access rights.
3 We then configure the business modules in the approved order, connecting the flows so that a quote becomes an order, a delivery, an invoice and then an accounting entry.
4 The developers build the custom modules, reports and connectors in Python and OWL, in a versioned code repository that belongs to you, with code review before each merge.
5 We clean your customer, supplier, product and balance files, then import them into staging, flagging duplicates and incomplete data.
6 A shared tracking board lists the cycle's tasks, open questions and the points awaiting your approval.
7 Each two-week cycle ends with a video demo on your real cases, followed by the list of adjustments to make.
Who does what
The Odoo consultant configures the modules and prepares the data migration, the developers build the custom work and the project manager tracks progress. Your key users answer questions, check the imported data and attend the demos.
What you provide
Exports of your data: customers, suppliers, products, prices, stock and accounting balances.
Access to the tools to connect, with their API keys or technical documentation.
Your document templates: logo, legal notices, terms and conditions, preferred layouts.
Quick answers to configuration questions and your key users' attendance at every demo.
What you receive
Acceptance Odoo loaded with your data
Your approval
Each cycle ends with a demo on your real cases.
031 to 2 weeks
Training and acceptance
Your teams learn Odoo on their own tasks and confirm that everything works before go-live.
Why this step: An ERP that nobody knows how to use on go-live day causes invoicing delays and a return to spreadsheets. Training on your own tasks and end-to-end acceptance testing ensure every process works, and that your teams use it, before production is touched.
How we proceed, line by line
1 With your key users, we prepare acceptance test scenarios covering your real cases, from quote to accounting entry.
2 We run short role-based training sessions by video call, directly in the staging Odoo filled with your data.
3 We write step-by-step user guides, with screenshots, for each everyday process.
4 Your users run the scenarios themselves and log every issue in a shared acceptance testing sheet.
5 We fix the issues, then your users retest the affected scenarios until they pass.
6 We rehearse the full data cutover on a copy, measuring its duration and checking the totals against your accounts.
7 We set the go-live date and the hour-by-hour cutover plan with you.
Who does what
A trainer and the Odoo consultant lead the sessions and write the guides, the developers fix the issues and the project manager runs acceptance testing. Your key users run the scenarios and sign the acceptance report.
What you provide
Time blocked in your teams' calendars for training and testing.
Verification of the migrated balances and stock by your accountant or logistics manager.
Formal approval of the acceptance report and go-live date.
What you receive
Acceptance report and user guides
Your approval
Key users confirm that their processes work.
04Go-live, then ongoing
Go-live and follow-up
We switch over on a date agreed with you, stay close during the first weeks, then evolve Odoo with your business.
What we do
Final data migration and go-live
Extra support during the first closings
Maintenance, backups and version upgrades
Why this step: The first weeks on a new ERP bring most of the questions and unexpected cases, especially during the first closings. A well-prepared cutover and enhanced support keep the business from slowing down, then maintenance keeps Odoo reliable and up to date as you grow.
How we proceed, line by line
1 On the chosen date, we freeze data entry in the old tools and start the final data migration according to the rehearsed plan.
2 We check balances, stock and open documents with you before opening Odoo to the teams.
3 During the first weeks, we provide enhanced support by messaging and video call, with short daily check-ins at go-live.
4 We support your teams through the first invoicing runs, stock counts and accounting closings.
5 We set up backups, monitoring and a single channel for your change or fix requests.
6 We plan version upgrades, testing first on a copy of the database, including your custom modules.
Who does what
The project manager coordinates the cutover, the Odoo consultant and a developer provide support and fixes, then the maintenance team takes over. On your side, an internal lead centralizes questions and prioritizes improvements.
What you provide
A stop to data entry in the old tools at the agreed time.
An internal contact who reports questions and issues.
Your accountant's availability for the first closing in Odoo.
What you receive
Odoo in production and maintenance plan
Your approval
Your teams work in Odoo every day.
Our commitments
A collaboration designed to stay under your control.
01
Transparency
You see progress, decisions, risks and next steps without waiting for a crisis meeting.
02
Continuous validation
Key choices are demonstrated and approved along the way rather than discovered at delivery.
03
Verifiable quality
Every outcome is tied to concrete criteria for functionality, security, performance or adoption.
04
Knowledge transfer
Documentation and onboarding are part of the engagement, so you never depend on us unnecessarily.
First step
Let's start by understanding your situation.
Tell us about your project, even if it's still vague or already in trouble. Together, we'll find the safest place to start.