We’re a young studio, so we’d rather show you two things straight than dress up a page with borrowed client logos. Below: our actual published apps, and separately, illustrative project patterns that show how we scope and run a typical engagement.
Both live on apps.odoo.com. Install them, read the code, judge the work directly — no claims to take on faith.
A module for binding step-by-step standard operating procedures directly to Odoo records — required-step blocking, frozen procedure versions, and a full audit trail, instead of a shared Google Doc nobody keeps updated.
Tracks EU e-invoicing mandate deadlines and country-by-country readiness directly inside Odoo, so finance teams don’t have to keep a separate spreadsheet of which country goes live when.
Search “Entrophy” or the app name directly on apps.odoo.com to find the live listings.
These are composite, illustrative scenarios based on common Odoo engagement shapes — not attributed to named clients, real or otherwise. They exist to show how we scope work and what a clean outcome looks like.
Required-step blocking and a frozen procedure version per production run, replacing shared docs and a tribal-knowledge spreadsheet.
Inbound replies auto-create leads and stage changes fire templated messages — replacing a stack of point-tools with one module.
Parallel staging, row-level data diff, and a single weekend cutover window — the shape of how we de-risk a version jump.
Unifying e-invoice IRP submission and retry handling across several GST registrations into a single operational view.
We’re actively taking on projects and would rather earn a genuine write-up than fabricate one. Tell us what’s broken and let’s see if we’re a fit.