Start Odoo projects with process mapping, not modules
The fastest way to burn budget on Odoo is to open the Apps list and install everything that sounds relevant. The systems that stick start somewhere quieter: how work actually moves through the organization.
What goes wrong
- Finance wants accounting first; warehouse wants inventory first; nobody owns the shared process.
- Custom modules get built before the default Odoo flow is understood.
- Data migration starts before statuses, units, and ownership rules are clear.
A discovery checklist I use
- Name the outcomes — close books faster, reduce stockouts, unify CRM — in one sentence each.
- Walk one happy path — quote → order → delivery → invoice (or your equivalent).
- List the exceptions — returns, partial deliveries, multi-warehouse transfers.
- Map roles — who creates, who approves, who can override.
- Only then choose which Odoo apps to enable and what truly needs a custom module.
When customization is worth it
Customize when the process is a real competitive advantage or a regulatory requirement. Configure when Odoo already covers 80% and the gap is training or discipline.
If you are planning an Odoo rollout in Iran (or cleaning up a stalled one), start with a short discovery call — that is the cheapest insurance you can buy.