Questions buyers ask us first.

Odoo 18 and 19, Community Edition, extended with open-source and custom modules. We specify modules for both versions so your next upgrade is planned.

Often not. Many reports and features that push companies to Enterprise — financial statements, for example — we build on Community instead.

We build every change as a separate addon that inherits standard models and never edits core code, which keeps upgrades manageable.

You receive the source code of your custom modules, used under our software licence agreement.

Most work runs on prepaid service packs of 50, 100 or 200 hours; we share pricing with a written proposal. Pack hours are valid for 180 days; unused hours then carry over as AMC hours for a further 365 days. Every task is estimated in hours before it starts, and every hour used is logged so you can see exactly where it went. Defined projects can also be quoted at a fixed fee.

It depends on scope; you receive a written estimate after the functional specification, before any build begins.

Yes. We start with a code and configuration review, document what exists, and tell you what is safe to keep.

Yes — Odoo, WordPress and custom applications, with backups, monitoring and SSL. You can also host with your own provider.

All three. We recommend Shopify, WooCommerce or Odoo eCommerce based on your catalogue size, ERP and team — and we can connect any of them to Odoo.

Yes. We structure attributes, write descriptions and prepare images in batches, checking every specification against the manufacturer's source. A 10-SKU pilot comes first, so you approve the format before we scale.

We design AI features with a person approving key outputs, full logging, and the model choice agreed with you.