An ERP implementation built around people

Principles

Implementing an ERP in a small business is not a software change: it is a change of habits. These four principles guide every project decision.

• Listen before configuring. The real process, with its shortcuts and notebooks, is the starting point.
• One place for the truth. Odoo holds the data and the rules; nothing important lives in side spreadsheets.
• Recording must be easy. We design data capture for the person doing it, not for the system.
• Measure usage, not deliveries. A project is done when the system is used and the data is reliable.

Process diagnostic

Before talking about modules, we understand how the company operates today (AS-IS) and agree on how it should operate with the system (TO-BE).

“Show me how you work” (AS-IS)

• We observe and document daily work on the floor, in the warehouse and in the office.
• We identify bottlenecks, double data entry and repetitive manual tasks.
• We measure real times and resources, so the return analysis starts from data rather than assumptions.

Future process design (TO-BE)

• We propose how the system solves each identified problem.
• We validate the proposal with key users from each area before configuring.

Return analysis (ROI)

We moved from the classic gap analysis (what the software lacks) to a return analysis: how much it costs to implement and how much it saves.

What it includes

• Costs: licenses, configuration, data migration, strictly necessary development, training and infrastructure.
• Benefits: manual work hours removed, fewer errors and rework, shorter order-to-cash cycles.
• Break-even: how long it takes for the savings to cover the investment.

A simple example

If preparing a quote takes 30 minutes and the system brings it down to 15, and the company issues 100 quotes a month:

Those hours, multiplied by their real cost, are a concrete benefit. We repeat the calculation for every process where the system creates efficiency.

When it is essential

• Non-standard processes that raise doubts about feasibility.
• Companies that already lived through a failed implementation and need realistic expectations.
• Decisions that need approval from partners or management with a clear business case.
• Teams resistant to change: taking part in the analysis shows them what they gain.

Odoo as the AI harness

Generative AI speeds up development enormously, but on its own it can produce results that look right and are not. That is why we never let it write freely to the database.

• Odoo is the source of truth: products, stock, prices, customers and accounts live in a single data model.
• Rules are not negotiable: every record proposed by an assistant goes through the same validations as one entered by hand.
• Scoped tools: assistants can only run defined, auditable actions.

This constraint is what lets us quickly build tailored forms and reports without losing control over accounting or inventory.

Effort distribution

Every company is different and each project is unique, but a typical distribution of our effort to ensure success looks like this:

• 35% · Design and planning: thoroughly understanding how packing, billing and shipping work in reality before touching code.
• 30% · Odoo setup and dynamic screens: building the harness and creating simple forms people actually want to use.
• 15% · Real-world testing: rehearsals with real orders from past weeks to validate figures with zero room for error.
• 20% · Hands-on training and adoption: floor and office support to ensure notebooks are left behind with clear adoption milestones.

Project phases

1. Diagnostic and return analysis: scope, resources and schedule.
2. Kick-off: we introduce teams, roles and plan, and align expectations.
3. Configuration in short cycles: incremental deliveries the team tests and corrects early.
4. Go-live: the system goes into operation with the critical processes.
5. Support and improvement: assistance, stabilization and a results review one to three months later.

Simplicity

Simplicity is the best tool for controlling cost, time and risk.

• Standard configuration first. Less customization means a more stable system that is easier to upgrade.
• Development only when justified. In our experience, a large share of the customizations requested at the start are solved with a process adjustment.
• Migrate only what is needed. Master data, opening balances and whatever the law requires.

People and roles

Ignoring the human side is one of the most common causes of failure in these projects. Change management starts on day one.

On the company side

• A single point of contact who knows the business and can make decisions.
• Key users in each area, who define, test and later teach their colleagues.

On our side

• A project leader who understands both the business and the system, and is accountable for scope, time and budget.
• Functional experts and developers only when the project requires them.

We prefer direct communication between those who know the business and those who know the solution, with short meetings, few people and clear decisions. Training is hands-on, based on each person’s real workflows, and continues after go-live.

Data curve (6 months)

Data in a business is not born perfect on launch day; it matures through disciplined daily use.

• Months 1 to 3 · Learning curve: the team leaves behind paper notebooks and loose sheets, adopting the habit of immediate recording.
• At 6 months · Reliable averaged data: figures stop being opinions. You start seeing exact profit margins per line, accurate delivery lead times, and optimized purchases.
• Over the years · Strategic decision base: the accumulated database becomes management’s most valuable asset for securing loans, opening locations, or investing in machinery with complete confidence.

How we measure success

A project that goes live but nobody uses is a failed implementation, even if it met the schedule. That is why we agree on indicators from the start:

• Adoption: active users and use of key workflows.
• Data quality: complete, timely records, with no side spreadsheets.
• Impact and stories behind the numbers: late deliveries explained with root causes, margin analysis, and crew productivity.
• Project management: schedule and budget against plan.

We hold regular follow-ups with the client team on a shared board, so progress, risks and open items are always visible.