Skip to Content
How to work with us
40% of our revenue comes from clients we’ve had longer than a year

Six named ways to work with us, each one scoped before either side commits.

Most consultancies answer “how do we start?” with “let’s set up a call.” We’d rather you knew the shape of the commitment before you picked up the phone. Below are the six ways clients engage us: what each one covers, who it’s for, and where each one stops.
Book a call → How we work →
The frame

Why name the engagement models at all?

Because the alternative is a buyer guessing. Fixed bundles and package tiers make the commercial structure legible, but they misprice the work: every serious ERP engagement is scoped to a specific system, not chosen off a menu. Naming the models keeps the honesty of bespoke scoping while telling you, up front, how to begin.

The engagements that promise a fixed price and a fixed timeline before anyone has looked at your system are often the ones whose clients end up calling us. So we don’t sell certainty we can’t hold. We sell a clear on-ramp, and we scope the rest once we’ve seen what’s actually running.

Start here

Find your on-ramp.

Most engagements begin with Discovery. Several begin mid-crisis. Both are normal.

The six models

Each one is a way in, not a package. What it is, the shape of it, who it’s for, where it stops, then how to start.

N° 01

Discovery

A short paid engagement to define the problem before either side commits to anything larger.

The shape
A few workshops with your team, a review of whatever you’ll give us access to (the running system, the code, the integrations) and a written recommendation: where you are, where you should get to, the path between, and the risks along it. It closes with one follow-up session.
Who it’s for
Buyers who know something’s wrong but not what, and anyone who wants a senior outside read before committing real budget.
Where it stops
No build happens here. A Discovery can conclude that you don’t need us, or that another partner fits your case better. Both are real outcomes, and we’ll say so plainly.
Start here
Start a Discovery →
N° 02

Rescue Sprint

A focused stabilization engagement for a system that’s actively losing you money right now.

The shape
A senior diagnostic in the first days (the actual root cause, not the symptom) then a triage report ranking every issue by business impact, then repair on the ones we can hold inside the window. What we can’t finish, we hand over: what’s fixed, what’s left, what you do next.
Who it’s for
Anyone whose Odoo, ERPNext, or custom system is in trouble: reports breaking in production, integrations failing quietly, adoption sliding, the previous partner gone dark, customisations that have frozen every upgrade. This is the on-ramp for the client who’s been let down once already.
Where it stops
No net-new features, no ground-up redesign; those are separate engagements. And if your current partner is still active, we work alongside them, not over them.
Start here
See how we approach rescue → Book a system audit →
N° 03

Implementation

A full build with defined milestones, deliverables, and acceptance gates.

The shape
A new Odoo, ERPNext, or custom system, or a major module rollout onto a footprint you already run. Milestone-based, each gate with something real to sign off. A senior architect leads; a delivery team builds. Requirements, solution design, configuration and development, data migration where it applies, support through user acceptance testing, training for your power users, and support through the weeks after launch.
Who it’s for
Clients standing up a new ERP, retiring a legacy system, or extending an existing Odoo footprint with serious new scope.
Where it stops
Long-term support past the initial post-launch window is its own thing: that’s Managed Continuity. Hardware, network, and infrastructure outside the system aren’t in scope unless we contract them in.
Start here
Most implementations start with a Discovery. Start there →
N° 04

Migration

A version-spanning move, delivered as a multi-phase program, because migration is forensic work, not implementation work.

The shape
Older Odoo to current, ERPNext version jumps, or a move off a legacy platform entirely. It runs in phases: a forensic audit of every customisation, integration, and report dependency; a parallel build of the new version; a data-shape mapping proven on anonymised test runs; then cutover and the intensive stabilisation right after it. A migration is mostly diagnosis (what’s there, why, and what depends on it) and only then a rebuild. Priced as a normal implementation, it’s priced wrong. We’ve carried systems across every version since Odoo v6.
Who it’s for
Clients on an old version whose customisations have made the standard upgrade path impossible, and anyone leaving a legacy ERP behind.
Where it stops
The in-scope and out-of-scope boundaries mirror Implementation, with migration-specific risk language living in the contract rather than on this page.
Start here
Scope a migration →
N° 05

Managed Continuity

An ongoing engineering relationship with a system that’s already live: support, evolution, and someone who answers when it breaks.

The shape
A committed block of hours a month against your deployed system: fixes, minor customisations, version upgrades on an agreed cadence, integration maintenance, escalations from your internal team, and a quarterly review of what’s been done and what’s next. A named senior lead, a dedicated team, and response windows set by severity in the contract. This is where most of our hours actually live: about a third of our effort is post-go-live. Most consultancies treat that work as invisible. We named it.
Who it’s for
Anyone whose system is operations-critical and who’s decided they don’t want to depend on per-ticket consulting, usually a client who’s been through one bad stabilisation and won’t do it again.
Where it stops
Major new module builds are a separate Implementation; replatforming is a Migration; work outside the contracted system is out of scope.
Start here
Most continuity relationships begin after an Implementation or a Rescue Sprint. Talk to us →
N° 06 For partners and agencies - not end clients

Capacity Partnership

Senior engineering and delivery capacity for other Odoo partners, ERPNext consultancies, and agencies who need the bench without building it.

The shape
White-label or co-branded delivery on your client work. We bring the architect and the team; you keep the client relationship. An NDA at the start, and a standing rule: we don’t approach your clients, ever, for any future business.
Who it’s for
Consultancies and agencies. If you’re an end client, one of the five models above is your route in.
Where it stops
The client relationship stays yours. No marketing or sales activity in your market. Logo and case-study rights only by explicit, per-engagement agreement.

We work both sides, and we’d rather you read that here than find it out later.

Start here
Talk about capacity →
What “we stay” looks like in the numbers
6 months–1 year
typical engagement length
5 years
our longest active engagement
40%
of revenue from clients we’ve had over a year
20%
of clients come back for the next thing

None of these are targets. They’re what the timesheets and the contracts already say.

What this page isn’t

What this page isn’t.

Not a price list. We don’t publish rate cards or “starting at” numbers. Bespoke scoping is the whole point: a published price would attract the wrong buyer and box in the right one.

Not an SLA. Response windows, severity definitions, and escalation paths live in the contract, where they can be specific to your system instead of generic on a page.

Not a contract. Everything here describes how we usually work. The agreement for your engagement is the thing that actually governs it.

Not sure which one fits?

Tell us where you’re stuck, and we’ll find the shape together.

One inbox, a human on the other end. Describe the situation and we’ll point you at the right way in, or tell you if it isn’t us.

Book a call → Read how we work →
Talk to us