Odoo ERPOperationsIT

One reference day rate, and the model that goes with it

Before starting a project, you need a budget, but above all a framework: duration, pace, and how the handover will work. Here's how I operate

€850excl. VAT / day
billable by the half-day

One day rate, whatever the project, for end‑to‑end ownership

DesignScoping, and the solution that fits
CoordinationTeams, vendors, trade-offs
DeliveryI get hands-on with the technical side too
HandoverSo everything runs without me, once I'm gone

The framework, in plain terms

My benchmarks for sizing an engagement, before putting a number on anything

✓

An 80-day budget

That's my benchmark, whatever the pace. Beyond that, we redefine the project together, to keep the topics clearly separate

✓

1 to 12 months

Never more than a year. A project that runs longer is no longer about building, it's about running. And that's not what I do

✓

A standard pace, adjustable

The engagement sets a pace that stays adjustable within the month for maximum flexibility: say 3 days one week, 1 day the next

✓

You pay for actual time

If the project ends earlier, you only pay for the days used: the budget is a framework, not a minimum to fund. And if one month runs over, we can adjust by mutual agreement

✓

Full delegation

I bring expertise and a method, which go hand in hand. Without real decision-making power, I can't move forward efficiently or deliver the best possible result

✓

100% remote, or hybrid

I work remotely by default, on site when it makes sense and geography allows. If needed, we discuss it at scoping to check feasibility

Estimate your budget

Pick a pace and a duration, the calculator adapts

Desired pace 2days / week
1 day5 days
Engagement length
1 month
Indicative day rate based on engagement volume
Up to 20 days€850
21 to 40 days€800
41 to 60 days€750
61 to 80 days€700
Indicative monthly budget
excl. VAT
at a day rate of € excl. VAT
Days on the engagement
days

The day rate is of course open to discussion, depending on the length and pace of the engagement

Why a handover?

It's the cornerstone of any build project, not the last box to tick

The prerequisite

A project where nobody can name the end or the successor isn't a defined project yet. If that's your case, that's where we start, and it's already a good chunk of the work

The goal

I'm not here to create one more dependency, but to build something that runs on its own, once I'm gone: tools your teams master, processes they own, and know-how that stays in the company

So from the scoping stage, we answer three questions

QUESTION 1

When is the project considered finished?

QUESTION 2

Who takes over what's been built?

QUESTION 3

In what form is the project handed over?

How does the handover work?

3 forms, usually combined

To a third-party provider

Skills transfer to whoever will run things day to day: training their team, handing over the documentation, and a supported transition

I have partners I can recommend, if needed

To an internal team

Hiring one or more people to handle day-to-day operations, so the know-how stays in-house

I can define the role, run the technical interviews, then handle the upskilling until they're fully autonomous

In every case
Knowledge management

It's a key part of my model: your processes written down, organized, and above all kept up to date by your teams over time. A shared brain for the company, so nobody is left high and dry when someone leaves

The 4 pillars of every engagement

The framework above follows directly from them

Leadership

An official mandate, and a role announced to the teams

Decision

Full delegation over the agreed scope

Definition

A 1 to 12-month project, with a clear objective

Handover

An end date or final deliverable, with a successor

Odoo ERPOperationsIT

Have a project to entrust?

The first conversation is free and with no commitment, to talk about your project and discuss the framework 🙂