This is the first question we ask ourselves before recommending custom development. A surprising number of requirements that seem to need custom code can be addressed through configuration, field customisation, or OCA community modules. We will always tell you if a cheaper, faster standard option exists. Custom development is only recommended when no standard or community solution meets the requirement adequately.

Custom modules need to be ported to each new major Odoo version. The effort varies depending on how the module was written and how much the underlying Odoo APIs changed between versions. Modules written to OCA standards (which all of ours are) are significantly easier and cheaper to port than hastily written code. Version upgrade porting is covered under our Managed Services retainer.

Yes. Custom modules developed specifically for your business are yours upon project completion and full payment. You receive the full Git repository, source code, and documentation. You are free to deploy it, modify it, or hand it to another developer. We do not retain licensing rights over bespoke client work.

Yes, and this is more common than you might expect. We start with a code audit to understand what exists, how it’s structured, what it does, and what’s broken or fragile. From there we produce a remediation plan, which might involve targeted fixes, a partial rewrite, or (in some cases) a full replacement. We are honest about the cost-benefit of each option before any work begins.

It depends entirely on complexity. A simple automation or field extension module can be built and deployed in 1–2 weeks. A complex multi-model module with a custom UI and external API integration typically takes 4–8 weeks. We provide a specific timeline estimate during the scoping phase, before any commitment is made. We do not give timeline estimates before scoping because modules that sound simple often aren’t, and vice versa.