The demo always works. We deal with everything after that.

Custom software, Odoo, Databricks, and rescuing what AI built. A small senior team — the person who scopes your project is the person who builds it.

Four practices, one team

Most of our work touches more than one of these. An ERP rollout needs integrations; a data platform needs the operational systems feeding it to be correct in the first place.

Custom software

Product teams that ship. We design, build and run the web applications, APIs and integrations that your business runs on.

Odoo consulting

Odoo implemented around how you actually work — not a demo config handed over at go-live. Migrations, custom modules and long-term support.

Databricks consulting

Lakehouse architecture, reliable pipelines and Unity Catalog governance — so your data platform is something the business trusts.

AI code rescue

You built it with AI and it works — on a laptop. We review it, clean it up, harden it, deploy it properly and keep it running.

Senior people, start to finish

There is no layer of account management between you and the engineering, and nothing gets handed down to someone more junior once the contract is signed.

  • We say no

    If a project is a bad fit, or the thing you asked for is not the thing that solves the problem, you will hear it during the first call rather than at the first invoice.

  • Working software early

    You see something running in weeks, not at the end. Scope changes when reality demands it, and that is easier when there is something real to look at.

  • Yours to keep

    Standard tools, documented decisions, your repositories and your cloud accounts. Nothing about the handover should depend on us still being here.

  • We stay on

    Most engagements continue as support and iteration after launch. Systems that no one maintains quietly stop being assets.

What the first month looks like

Discovery call

Free, 60 minutes. What you are trying to achieve, what already exists and what is actually in the way.

Written assessment

A short document: the recommended approach, the risks we can see, a phased plan and an effort range you can budget against.

Paid discovery or build

Larger projects start with a short paid discovery phase. Clear ones go straight into a first delivery milestone.

Delivery in increments

Two-week increments, something demonstrable at the end of each, and a standing call so nothing drifts for a month unnoticed.

Tell us what is actually going wrong.

You will get an honest read on the approach, the effort and whether we are the right people for it — including when we are not.