° Media company, Germany
Challenge
Sales, projects, and invoicing lived in separate spreadsheets: no overview of which invoices had already been issued for which orders, and no structured lead management. After the ERP rollout came the second chapter: Odoo Enterprise license fees kept recurring for a feature set the company didn't actually need — including Studio-built customizations that don't exist in Odoo Community. Meanwhile, Germany's e-invoicing mandate was approaching.
Solution
36T built the complete ERP on Odoo — sales, projects, accounting, and CRM, including a lead database and AI-powered contact enrichment. We then migrated the instance from Odoo Enterprise to Community 18: reimplemented every Studio customization as versioned custom modules, replaced Enterprise-only features like budget planning with a purpose-built quarterly forecasting module, preserved the full communication history, and built a custom accounting-entry report. Today we keep developing on a dev→test→prod pipeline — most recently German-standard e-invoicing with per-customer opt-in, so the rollout never blocks a single invoice run.